- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 4417a7: 50206
by GitHub Aug. 3, 2015

Aug. 3, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 4417a7875a30c421fe9e3ea96a98718389d48c87 https://github.com/pharo-project/pharo-core/commit/4417a7875a30c421fe9e3ea9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-03 (Mon, 03 Aug 2015) Changed paths: M Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateFiletreeRepositoryFromUrl.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50205.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50206.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50205.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50206.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Diff.package/DiffMorph.class/instance/actions/calibrateScrollbar.st Log Message: ----------- 50206 15990 Failing tests testCanCreateFiletreeRepositoryFromUrl (on windows) https://pharo.fogbugz.com/f/cases/15990 16088 Fix DiffMorph when called from Komitter https://pharo.fogbugz.com/f/cases/16088 http://files.pharo.org/image/50/50206.zip

1 0

Re: [Pharo-dev] Google Code Shutdown
by Blondeau Vincent Aug. 3, 2015

Aug. 3, 2015

That is a solution but not for long term. I donât want to install linux to use pharo.. For now the solution is to use git as standalone app and filetree to export the code. I use it and it works well while you donât have to long paths. Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Dimitris Chloupis EnvoyÃ© : lundi 3 aoÃ»t 2015 13:42 Ã : Pharo Development List Objet : ** SPAM scored: Med **Re: [Pharo-dev] Google Code Shutdown A workaround if you absolutely want to use gitfiletree is to install linux using a VM like virtual box , Ubuntu for example works very well with pharo https://www.virtualbox.org/ This way you avoid booting to another OS , you can also share your git folder to both windows and linux vm. This way you can use gitfiletree without ditching windows. Of course dual boot can work too if you dont need to use Pharo with windoom. VM option works also if you want to install MacOS on your windows pc. On Mon, Aug 3, 2015 at 1:13 PM Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hi, Sorry but I am using Windowsâ¦ not because I want to but because I have to... So the therapy will not work ;) Actually, the bugtracker of Moose can be on github, but the git user experience under Windows has to be improved if we want to use efficiently the other functionalities of github (pull requests, commit, branches,â¦). Cheers, Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org<mailto:pharo-dev-bounces@lists.pharo.org>] De la part de Peter UhnÃ¡k EnvoyÃ© : lundi 3 aoÃ»t 2015 11:56 Ã : Pharo Development List Objet : Re: [Pharo-dev] Google Code Shutdown As long as nobody on your team is using Windows, git(hub) is quite good. :) (And if you have Windows user, then find him a therapy first, or push for libcgit :)) On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com<mailto:alexandre.bergel@me.com>> wrote: Github is indeed appealing. Cheers, Alexandre > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com<mailto:sean@clipperadams.com>> wrote: > > Tudor Girba-2 wrote >> Would you like to help us move the moose-technology project? > > Sure. What do you have in mind? It seems exporting to GitHub is the easiest > option. There are a few limitations, but I've had good experiences... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

1 0

GanttChartMorph openOn: aCollectionOfActivities ?
by H. Hirzel Aug. 3, 2015

Aug. 3, 2015

Hello Has somebody done a GANTT chart? GanttChartMorph openOn: aCollectionOfActivities ? Activities have - id - description - start date - end date ? Regards Hannes

5 22

WhatsUp from: 2015-08-03 until: 2015-08-16
by seaside＠rmod.lille.inria.fr Aug. 3, 2015

Aug. 3, 2015

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-08-16 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

1 0

Re: [Pharo-dev] [ann] jdt2famix - an open-source java importer project
by Tudor Girba Aug. 2, 2015

Aug. 2, 2015

Hi (again), The project below is made possible by JNIPort. Thanks, Joachim! Cheers, Doru On Sun, Aug 2, 2015 at 11:26 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I would like to announce the jdt2famix project. This aims to be an > open-source solution for importing Java projects into Moose: > http://www.smalltalkhub.com/#!/~Moose/Jdt2Famix > > The project is based on: > - JDT for raw parsing. This is implemented in Java. > - JNIPort for delegating to Pharo the Java methods that visit the Java AST. > > Installation details can be found on the main project page. > > The current importing logic is rudimentary, but the first goal was to > setup the whole ping-pong between Pharo and Java. This one works, and I am > quite happy about that. You can take a look at the JdtImporterTest. > > CAVEATS: > - Due to a problem in JNIPort, currently, this project only works in Moose > 5.0. > - Also, for now it works out of the box only for Mac OS X. > - And, on top of that, it requires Java 1.6 for now (until we will get the > Spur VM on 64 bits). > > There are still quite some challenges left, but once we get this going, we > would also be able to use deep AST analysis live, and to do incremental > model update when something changes on disk. Furthermore, if it scales, > this would not be based on an intermediary MSE file anymore. > > I would like to ask for help in several directions: > 1. Implement the full model import. This would require diving into JDT and > implementing the corresponding mapping logic. I spent a few days on this. > It is hairy, but it is not that impossible (only it has a ton of edge > cases). This should be test driven, in that, for each case, we need to have > a corresponding sample. > 2. Fix JNIPort to work in Pharo 5. > 3. Get the whole thing to work out of the box for Linux and Windows. > 4. Check scalability. > > Please let me know your opinions, and let me know if you would like to > participate. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

1 0

deprecation and unit testing?
by Alexandre Bergel Aug. 1, 2015

Aug. 1, 2015

Hi! Apparently deprecated methods called within unit test do not make test fail. Anyone experienced this already? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

ESUG2015 Photos
by Yuriy Tymchuk Aug. 1, 2015

Aug. 1, 2015

Hi all! Photos from ESUG 2015 made by me and Natalia are available at: https://goo.gl/photos/Z15Fc7QpM4kPHRno9 <https://goo.gl/photos/Z15Fc7QpM4kPHRno9> Cheers! Uko

3 4

[pharo-project/pharo-core] c08753: 50205
by GitHub Aug. 1, 2015

Aug. 1, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c0875327c5053fc1fb2f850db006fbc10df6f1ca https://github.com/pharo-project/pharo-core/commit/c0875327c5053fc1fb2f850d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-01 (Sat, 01 Aug 2015) Changed paths: M Morphic-Base.package/TextMorph.class/instance/event handling/mouseDown_.st A Multilingual-Tests.package/MultiByteFileStreamFileOutTestClass.class/README.md A Multilingual-Tests.package/MultiByteFileStreamFileOutTestClass.class/class/accessing/scriptName.st A Multilingual-Tests.package/MultiByteFileStreamFileOutTestClass.class/definition.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/accessing/fileOutTestClass.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testFileOutNonAscii.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testNext.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testNextMatchAll.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testNextPut.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testNextPutAll.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testNextPutAllStartingAt.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testPeek.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testPeekFor.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testReset.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testUpToAnyOfDo.st A Multilingual-Tests.package/MultiByteFileStreamTest.class/instance/testing/testUpToEnd.st R Nautilus.package/AbstractNautilusUI.class/instance/private/textMorphClass.st A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterSequence.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50204.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50205.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50204.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50205.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Shout.package/SHRBTextStyler.class/definition.st A Shout.package/SHRBTextStyler.class/instance/private/styleCloseBracket_.st A Shout.package/SHRBTextStyler.class/instance/private/styleCloseParenthese_.st A Shout.package/SHRBTextStyler.class/instance/private/styleOpenBracket_.st A Shout.package/SHRBTextStyler.class/instance/private/styleOpenParenthese_.st M Shout.package/SHRBTextStyler.class/instance/private/style_ast_.st M Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitBlockNode_.st M Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitMessageNode_.st M Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitSequenceNode_.st M Shout.package/SHTextStylerST80.class/class/initialization/initialize.st M Shout.package/SHTextStylerST80.class/class/initialization/unload.st M Spec-Inspector.package/EyeInspectorTest.class/instance/accessing/instancesToTry.st Log Message: ----------- 50205 14986 Additions to tests for MultiByteFileStream https://pharo.fogbugz.com/f/cases/14986 16049 support differnt colors for nested parentheses / blocks in SHRBTextStyler https://pharo.fogbugz.com/f/cases/16049 16053 less pluggableTextMorph references https://pharo.fogbugz.com/f/cases/16053 16086 reflectivity: testAfterSequence https://pharo.fogbugz.com/f/cases/16086 http://files.pharo.org/image/50/50205.zip

1 0

[pharo-project/pharo-core]
by GitHub Aug. 1, 2015

Aug. 1, 2015

Branch: refs/tags/50205 Home: https://github.com/pharo-project/pharo-core

1 0

NAtiveBoost error
by Alain Rastoul Aug. 1, 2015

Aug. 1, 2015

Hi, I have a problem with a nativeboost call, but I don't see what I do wrong. library function prototype is: int zmq_getsockopt (void *socket, int option_name, void *option_value, size_t *option_len); my calling method in pharo is: zmq_getsockopt: socket option_name: option_name option_value: option_value option_len: option_len <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode> ^self nbCall: #(int zmq_getsockopt (void *socket, int option_name, void * option_value, size_t* option_len) ) when I call it with ... optionValue := (NBExternalArray ofType: 'int') externalNew: 1. optionLen := (NBExternalArray ofType: 'size_t' ) externalNew: 1. [ optionValue at: 1 put: 0 . optionLen at: 1 put: (NBExternalType sizeOf: 'int') . rc := self zmq_getsockopt: socket option_name: option_name option_value: optionValue option_len: optionLen . value := optionValue at: 1 . ] ensure: [ optionValue free. optionLen free ]. ... I allways get an exception: "error during FFI call : nil" After stepping in NBFFICallout generation, I found something strange, the code generation seems not to be called because lastError stays at nil ? handleFailureIn: aContext nativeCode: aBlock lastError := self getErrorFrom: aContext lastError: NativeBoost lastError. >>getErrorFrom: aContext lastError: errorCode ... checks pragmas etc >>getErrorFrom: aContext lastError: errorCode ... lastError := aContext tempAt: method numTemps. => lastError = nil ??? shouldn't be ErrNoNativeCodeInMethod ? "install native code and retry the send" lastError = ErrNoNativeCodeInMethod ifTrue: [ ^ self generateCode: aBlock andRetry: aContext ]. never gets called ... "ok, we're out of options, signal an error here" ^ self signalError: lastError Could it be because I use this image on windows and unix ? Or because I had an exception at prototype parsing the first time because I forgot a ; at the end of the prototype ? Is my prototype correct or is it the origin of the error ? Is there a way to reset the lastError (aContext tempAt: method numTemps) ? I will try to reset it in debugger but may be there is a cleaner way ? would it be ok to change the test in handleFailure to (lastError = ErrNoNativeCodeInMethod) or:[ lastError isNil ] ? (I can open a bug in this case ) Any idea or comment is welcome Thanks in advance Alain

11 55