August 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] System Windows not closing on using #close

by Jigyasa Grover

Hi Stephan I got your point, I think. I tried searching for the such methods which would help me make a separate frame for 'box' so as to re-position 'box' within 'boxWindow' but in vain. Any pointers pls ? Thanks Jigyasa -- View this message in context: http://forum.world.st/System-Windows-not-closing-on-using-close-tp4841568p4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 10, 2015

Re: [Pharo-users] [ANN] New ISO 3166-1 Wrapper

by Ben Coman

Thanks HernÃ¡n. On Mon, Aug 10, 2015 at 2:34 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Dear all, > > > I developed a Pharo ISO 3166-1 wrapper to access objects into a ISO3166-1 > model. See the following post for details on installation and usage: > > http://80738163270632.blogspot.com.ar/2015/08/new-iso-3166-1-implementation… > > I also wrote some documentation about it: > https://dl.dropboxusercontent.com/u/103833630/ISO3166.pdf > > Hope you find it useful. > > > > Cheers, > > > HernÃ¡n >

Aug. 10, 2015

[ANN] New ISO 3166-1 Wrapper

by HernÃ¡n Morales Durand

Dear all, I developed a Pharo ISO 3166-1 wrapper to access objects into a ISO3166-1 model. See the following post for details on installation and usage: http://80738163270632.blogspot.com.ar/2015/08/new-iso-3166-1-implementation… I also wrote some documentation about it: https://dl.dropboxusercontent.com/u/103833630/ISO3166.pdf Hope you find it useful. Cheers, HernÃ¡n

Aug. 10, 2015

Re: [Pharo-users] troubles with JNIPort on Pharo 5 / Java 8

by Joachim Geidel

Thanks a lot! I will look into the problem with the test package as soon as possible. Joachim Am 9. August 2015 17:29:42 MESZ, schrieb "Tudor Girba-2 [via Smalltalk]" <ml-node+s1294792n4841826h94(a)n4.nabble.com>: > > >Ok. I added now: >- 3.1-alpha with packages for pharo 5 >- development and stable symbolic versions for pharo 3 and pharo 5. > >The tests problem should still be solved. Do you still want to look at >that? > >Once that is done, the tests packages should be added to the version. I >can >do that. > >Cheers, >Doru > > > >On Sun, Aug 9, 2015 at 2:51 PM, Joachim Geidel ><joachim.geidel(a)onlinehome.de >> wrote: > >> >> > Am 09.08.2015 um 14:36 schrieb Tudor Girba-2 [via Smalltalk] ><[hidden >> email] <http:///user/SendEmail.jtp?type=node&node=4841820&i=0>>: >> > However, I notice that you have some distinct version names, and >this >> seems to throw MC off. For example, when trying to load the latest >version >> of ConfigurationOfJNIPort: >> > - we get: ConfigurationOfJNIPort-JoachimGeidel.3.0a3 >> > - instead of: ConfigurationOfJNIPort-JoachimGeidel.3.0a4 >> > >> > This problem would be fixed if we would change the numbering a bit. >For >> example, when I try to commit a new version of the configuration, >> Monticello offers: >> > ConfigurationOfJNIPort-TudorGirba.3.5 >> > >> > Is it Ok if I commit it like this? >> >> Yes, of course, do whatever it takes. I used the âaNâ suffer because >I >> considered that version as an alpha release, and wanted to do a lot >more >> before publishing a ârealâ release. >> >> Cheers, >> Joachim >> >> >> ------------------------------ >> View this message in context: Re: troubles with JNIPort on Pharo 5 / >Java >> 8 >> ><http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p484…> >> Sent from the Pharo Smalltalk Users mailing list archive >> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at >Nabble.com. >> > > > >-- >www.tudorgirba.com > >"Every thing has its own flow" > > > > >_______________________________________________ >If you reply to this email, your message will be added to the >discussion below: >http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p484… > >To unsubscribe from troubles with JNIPort on Pharo 5 / Java 8, visit >http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no… -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. -- View this message in context: http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p484… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 10, 2015

Re: [Pharo-users] troubles with JNIPort on Pharo 5 / Java 8

by Tudor Girba

Ok. I added now: - 3.1-alpha with packages for pharo 5 - development and stable symbolic versions for pharo 3 and pharo 5. The tests problem should still be solved. Do you still want to look at that? Once that is done, the tests packages should be added to the version. I can do that. Cheers, Doru On Sun, Aug 9, 2015 at 2:51 PM, Joachim Geidel <joachim.geidel(a)onlinehome.de > wrote: > > > Am 09.08.2015 um 14:36 schrieb Tudor Girba-2 [via Smalltalk] <[hidden > email] <http:///user/SendEmail.jtp?type=node&node=4841820&i=0>>: > > However, I notice that you have some distinct version names, and this > seems to throw MC off. For example, when trying to load the latest version > of ConfigurationOfJNIPort: > > - we get: ConfigurationOfJNIPort-JoachimGeidel.3.0a3 > > - instead of: ConfigurationOfJNIPort-JoachimGeidel.3.0a4 > > > > This problem would be fixed if we would change the numbering a bit. For > example, when I try to commit a new version of the configuration, > Monticello offers: > > ConfigurationOfJNIPort-TudorGirba.3.5 > > > > Is it Ok if I commit it like this? > > Yes, of course, do whatever it takes. I used the âaNâ suffer because I > considered that version as an alpha release, and wanted to do a lot more > before publishing a ârealâ release. > > Cheers, > Joachim > > > ------------------------------ > View this message in context: Re: troubles with JNIPort on Pharo 5 / Java > 8 > <http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p484…> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 9, 2015

Re: [Pharo-users] Image cannot grow beyond 500Mb

by stepharo

> I am trying to use Moose to do run graph algorithms on data with about > 300,000 nodes. This data is map data downloaded from OpenStreetMap, > and I am trying to analyze it with the Moose-Analysis-Graphs package. This is cool :) Once you fix the problem --memory 1024m do not forget to tell us about your experience. I do not remember having a so large graph in Moose (we have model with more than 600000 entities but we do not feed them to the graph algo directly). > However, it seems completely unable to handle this, partially due to > unoptimized algorithms, but mostly due to memory limits of the VM or > image itself. > > I am using the vm and image of the moose one-click image for mac: > http://www.moosetechnology.org/#install . I believe this is a pharo vm > and image, I donât know if pharo and squeak are still different these > days, or if it matters. Been out of squeak for a few years Welcome back. Pharo is moving fast :). We hope to have the Spur release soon. > > This platform is seemingly unable to use more than about 500Mb of > memory. I watch it in macâs activity monitor. Once it reaches about > 450Mb as measured by activity monitor, it is spending nearly all itâs > time in the garbage collector, (as measured by activity monitorâs > Sample Process tool). The most Iâve seen it eventually reach is 556Mb, > after about an hour, then it does a hard VM crash (Pharo has quit > unexpectedly). > > Is there a way to remedy this? I tried running the image in 4 > alternative VMâs: > - The latest pharo mac vm from http://files.pharo.org/vm/pharo/mac/ . > Same issue as above. likely the same vm > - Cocoa Cog vm from http://squeakvm.org/mac/ : crashed at startup. > could not load image > - Cocoa Stack vm from http://squeakvm.org/mac/ : crashed at startup; > could not load image > - Carbon Stack vm from http://squeakvm.org/mac/ : refused to start > > Is it possible to allocate more than 500Mb of memory to squeak?

Aug. 9, 2015

Re: [Pharo-users] troubles with JNIPort on Pharo 5 / Java 8

by Joachim Geidel

> Am 09.08.2015 um 14:36 schrieb Tudor Girba-2 [via Smalltalk] <ml-node+s1294792n4841819h77(a)n4.nabble.com>: > However, I notice that you have some distinct version names, and this seems to throw MC off. For example, when trying to load the latest version of ConfigurationOfJNIPort: > - we get: ConfigurationOfJNIPort-JoachimGeidel.3.0a3 > - instead of: ConfigurationOfJNIPort-JoachimGeidel.3.0a4 > > This problem would be fixed if we would change the numbering a bit. For example, when I try to commit a new version of the configuration, Monticello offers: > ConfigurationOfJNIPort-TudorGirba.3.5 > > Is it Ok if I commit it like this? Yes, of course, do whatever it takes. I used the âaNâ suffer because I considered that version as an alpha release, and wanted to do a lot more before publishing a ârealâ release. Cheers, Joachim -- View this message in context: http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p484… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 9, 2015

Re: [Pharo-users] troubles with JNIPort on Pharo 5 / Java 8

by Tudor Girba

Hi, Great. However, I notice that you have some distinct version names, and this seems to throw MC off. For example, when trying to load the latest version of ConfigurationOfJNIPort: - we get: ConfigurationOfJNIPort-JoachimGeidel.3.0a3 - instead of: ConfigurationOfJNIPort-JoachimGeidel.3.0a4 This problem would be fixed if we would change the numbering a bit. For example, when I try to commit a new version of the configuration, Monticello offers: ConfigurationOfJNIPort-TudorGirba.3.5 Is it Ok if I commit it like this? Cheers, Doru On Sun, Aug 9, 2015 at 1:44 PM, Joachim Geidel <joachim.geidel(a)onlinehome.de > wrote: > Hi Tudor, > > Am 09.08.2015 um 13:27 schrieb Tudor Girba: > I tested your changes, and I confirm that the code works fine in Pharo 5. > Now, we just need to get them published :). > > > I tend to avoid words like âjustâ, âsimplyâ etc. when talking about > software. ;-) The ConfigurationOfJNIPort should be updated in a way which > lets one load the current package versions when using Pharo 3, and new ones > when using Pharo 4 or 5. I havenât used this stuff for a while, and will > have to read the documentation again before being able to publish something > useable. > > I have just added you as a contributor to the JNIPort project and as a > member to the JNIPort team at SmalltalkHub, so you can publish changes. > > Cheers, > Joachim > > > ------------------------------ > View this message in context: Re: troubles with JNIPort on Pharo 5 / Java > 8 > <http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p484…> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 9, 2015

Re: [Pharo-users] troubles with JNIPort on Pharo 5 / Java 8

by Joachim Geidel

Hi Tudor, > Am 09.08.2015 um 13:27 schrieb Tudor Girba: > I tested your changes, and I confirm that the code works fine in Pharo 5. Now, we just need to get them published :). I tend to avoid words like âjustâ, âsimplyâ etc. when talking about software. ;-) The ConfigurationOfJNIPort should be updated in a way which lets one load the current package versions when using Pharo 3, and new ones when using Pharo 4 or 5. I havenât used this stuff for a while, and will have to read the documentation again before being able to publish something useable. I have just added you as a contributor to the JNIPort project and as a member to the JNIPort team at SmalltalkHub, so you can publish changes. Cheers, Joachim -- View this message in context: http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p484… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 9, 2015

Re: [Pharo-users] troubles with JNIPort on Pharo 5 / Java 8

by Tudor Girba

Hi, I tested your changes, and I confirm that the code works fine in Pharo 5. Now, we just need to get them published :). Cheers, Doru On Sun, Aug 9, 2015 at 12:50 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Joachim, > > This is great news! Thanks a lot for looking into this. > > Could you commit your changes? Or could you grant me access to the JNIPort > project? > > Cheers, > Doru > > > > On Sun, Aug 9, 2015 at 12:25 PM, Joachim Geidel < > joachim.geidel(a)onlinehome.de> wrote: > >> Hi Tudor, >> >> some progress in Pharo 5: >> >> > Am 28.07.2015 um 16:10 schrieb Tudor Girba-2 [via Smalltalk] <[hidden >> email] <http:///user/SendEmail.jtp?type=node&node=4841798&i=0>>: >> > >> > I also tried with Pharo4 and Pharo5, but it does not work because I get >> a MNU for GhostClassBuilder>>#client:. >> > >> > I fixed it in a Pharo5 image by using #installer: instead, but the >> computation of "JVM newWithSettings: jvmSettings" does not seem to finish >> and it blocks the VM. >> >> Changing the call of #client: to #installer: in >> GhostClassInstaller>>#initialize: was correct. >> >> > Any idea of what goes wrong? >> >> Someone declared String>>subStrings: as deprecated in Pharo 4 or 5. When >> I ran âJVM newWithSettings: jvmSettingsâ, a notifier opened which warned >> about the deprecated method. I changed the method which used it in the >> debugger, then proceeded. The image blocked until I hit <cmd-.>. A debugger >> opened, it was in the middle of writing to the Pharo error log file. I >> proceeded, the image blocked again, I hit <cmd-.> again. A debugger opened >> which contained a very large stack of contexts with the method >> handleSignal: calling itself endlessly. There seems to be something wrong >> with handling/logging deprecation warnings in Pharo 5. Why do they have to >> be written to the error log in the first place? I donât think that they >> belong there. >> >> There are four methods sending subStrings: in the package >> JNIPort-Java-Base. I changed them to use substrings: instead. >> >> There are two methods in JNIPort-StringEncoding which send "Smalltalk >> isLittleEndianâ, String>>#asJavaLangStringEncodedByteArray and >> String>>#fromJavaLangStringEncodedByteArray:. This does not work anymore. I >> replaced this with "EndianDetector isLittleEndianâ. >> >> After these changes, starting a JVM and executing the example script >> which you posted just worked fine. >> >> Unfortunately, loading the test package JNIPort-Tests-Java-Base fails >> with an exception: >> >> UTF8InvalidText(Object)>>subclassResponsibility >> UTF8InvalidText(Exception)>>defaultAction >> UndefinedObject>>handleSignal: >> Context>>handleSignal: >> >> AFAIK, there was no problem when loading the package in Pharo 3. There >> seem to be two problems: The UTF8TextConverter seems to think that there is >> an invalid character in the source code file, and UTF8InvalidText has no >> #defaultAction method. Looks like a bug in Pharo 5 to me. >> >> HTH >> Joachim >> >> >> ------------------------------ >> View this message in context: Re: troubles with JNIPort on Pharo 5 / >> Java 8 >> <http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p484…> >> Sent from the Pharo Smalltalk Users mailing list archive >> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at >> Nabble.com. >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 9, 2015