[Pharo-dev] Test for the string class available on SmalltalkHub

Hi to all, I'm writing missing test for the String class methods to improve the test coverage. I will commit my changes in this project at SmalltalkHub: http://smalltalkhub.com/#!/~DanielaMeneses/ImprovingStringAPI Feel free to take a look. Any feedback will be really welcome and useful. :D --

Re: [Pharo-dev] Desktop Apps with Pharo 3

Hi Noury, You can implement a custom world menu to replace the existing one, see my post here for a description: http://lists.gforge.inria.fr/pipermail/pharo-project/2010-September/032696.html You implement an own world menu by using a pragma and then switching to it. Ideally you have a s

Re: [Pharo-dev] Desktop Apps with Pharo 3

On 18 Feb 2014, at 17:26, Noury Bouraqadi wrote: > Hi, > > For my Pharo Lecture I want to show students how to make a desktop app in > Pharo 3.0 (Yes I'm using a Beta for my lecture, because Pharo 3 is cool :-) > > - I wonder if there are any new cool solution to strip out dev tools or at >

Re: [Pharo-dev] ./pharo .st argument and quit/no quit

> 1. It’s worth mention that for starting a server image you can also > install/hook to the #startUp: message in the right class with the benefit of > not relying in an external script that might generate a problem not tested by > the image builder or CI environment (which is what I’m doing BTW

Re: [Pharo-dev] ./pharo .st argument and quit/no quit

On Feb 18, 2014, at 12:02 PM, Tudor Girba wrote: > As far as I see it, you use the two in distinct cases: > - save alone is exclusively used for copying an image. There is no point in > no quitting in this case. that’s okay > - execution+save is used either to start a server process (hence

[Pharo-dev] Desktop Apps with Pharo 3

Hi, For my Pharo Lecture I want to show students how to make a desktop app in Pharo 3.0 (Yes I'm using a Beta for my lecture, because Pharo 3 is cool :-) - I wonder if there are any new cool solution to strip out dev tools or at least lock the world menu? - Is there any way to set the OS windo

Re: [Pharo-dev] ./pharo .st argument and quit/no quit

As far as I see it, you use the two in distinct cases: - save alone is exclusively used for copying an image. There is no point in no quitting in this case. - execution+save is used either to start a server process (hence noquit is desired), or to setup an image (hence, quit is desired). I think fa

Re: [Pharo-dev] On things we do when our stack overflows

The VM could sure use stack overflow protection, it would/could help catch numerous 'hangs' due to infinite loops. On 18 Feb 2014, at 13:08, Sebastian Sastre wrote: > Hi there, > > Toyota shoot its foot and learnt how not to anymore. > > This is a nice read on the things our software do when

Re: [Pharo-dev] ./pharo .st argument and quit/no quit

true Tudor. Do you know why the default behaviour is inverted for that case? sebastian o/ On Feb 18, 2014, at 11:47 AM, Tudor Girba wrote: > You can find the answer to your question in the class comment: > > Usage: st [--help] [ --quit ] > --helplist this help message >

Re: [Pharo-dev] ./pharo .st argument and quit/no quit

ok just found out that when you send an .st file in the arguments the default behaviour is inverted Beware! It seems we have our very own Smalltalk Experience Gremlins messing around =/ sebastian o/ PD: this works as one would expect: pharo-vm-nox some.image ImageBuilder.st —quit=true save a

Re: [Pharo-dev] ./pharo .st argument and quit/no quit

You can find the answer to your question in the class comment: Usage: st [--help] [ --quit ] --helplist this help message --quitif specified, the image exits without saving after evaluating FILE --saveif specified, save the image after evaluating FILE a file containing valid Pharo

Re: [Pharo-dev] installing opendbx for postgres on mac

On 18 Feb 2014, at 13:24, Tudor Girba wrote: > Well, I wanted to test DBXTalk, and this is why I wanted to go through the > pain of hooking to a DB, and the only way I know is to install the OpenDBX > libraries. Yes, I understood that is your main objective. > Do you mean to suggest to try w

[Pharo-dev] ./pharo .st argument and quit/no quit

Hi there, can someone clarify this for me? lets say you execute in the terminal: pharo-vm-nox some.image save awesome.image —delete-old it starts, saves the image and deletes the old one and quits returning control to terminal but if you do: pharo-vm-nox some.image ImageBuilder.st save aweso

Re: [Pharo-dev] Connection closed while waiting for data in bootstrapped image

They seem to be ok. I tried to look at the sockets during waiting in other thread and signal their semaphores but no change. Socket loopbackTest WORKS. -- Pavel 2014-02-17 11:18 GMT+01:00 Guillermo Polito : > ExternalSemaphores table may be not well initialized? I can help having a > look this

Re: [Pharo-dev] installing opendbx for postgres on mac

I certainly will :). I will also provide support for DB manipulation inside the GTInspector. Doru On Tue, Feb 18, 2014 at 2:56 PM, Torsten Bergmann wrote: > Hi Tudor, > > if possible you should sum it all up in a short video or tutorial/blog > post for others to know about the "how to". > > T

Re: [Pharo-dev] installing opendbx for postgres on mac

Hi Tudor,   if possible you should sum it all up in a short video or tutorial/blog post for others to know about the "how to".   Thx T.   Gesendet: Dienstag, 18. Februar 2014 um 07:33 Uhr Von: "Tudor Girba" An: dbxt...@googlegroups.com, "Discusses Development of Pharo" Betreff: [Pharo-de

Re: [Pharo-dev] installing opendbx for postgres on mac

Hi, Well, I wanted to test DBXTalk, and this is why I wanted to go through the pain of hooking to a DB, and the only way I know is to install the OpenDBX libraries. Do you mean to suggest to try with using the binding from http://smalltalkhub.com/#!/~PharoExtras/PostgresV2/ to hook directly to a

Re: [Pharo-dev] On things we do when our stack overflows

Is anyone porting the CogVM on a bare Cortex-M without OS :P ? Thierry Le 18/02/2014 13:08, Sebastian Sastre a écrit : Hi there, Toyota shoot its foot and learnt how not to anymore. This is a nice read on the things our software

[Pharo-dev] On things we do when our stack overflows

Hi there, Toyota shoot its foot and learnt how not to anymore. This is a nice read on the things our software do when the stack overflows. Are We Shooting Ourselves in the Foot with Stack Overflow? http://embeddedgurus.com/state-space/2014/02/are-we-shooting-ourselves-in-the-foot-with-stack-overf

Re: [Pharo-dev] Fuel: fix for Squeak trunk

I’ve opened an issue for this: https://code.google.com/p/fuel/issues/detail?id=206 Max On 18.02.2014, at 11:16, Stephan Eggermont wrote: > Max wrote: >> Good idea. What would we put there? I can’t think of anything else than >> globals… >> If globals is the only thing then I’m not sure that

Re: [Pharo-dev] Fuel: fix for Squeak trunk

Max wrote: >Good idea. What would we put there? I can’t think of anything else than >globals… >If globals is the only thing then I’m not sure that it’s worth the effort. Make sure the code loads (not runs) in gemstone. Then you know. At least the calls to primitives should be moved. Stephan

Re: [Pharo-dev] XMLParser does not close input stream

Please try the latest version. > - Original Message - > From: paolo.bernardi...@gmail.com > Sent: 02/17/14 07:02 PM > To: Pharo Development List > Subject: [Pharo-dev] XMLParser does not close input stream > > hi, > after parsing the input stream is left open, > so Dia can't save the next

[Pharo-dev] [pharo-project/pharo-core] e21080: 30767

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: e21080920362debd2ca9b2b14ba25878e7ee640e https://github.com/pharo-project/pharo-core/commit/e21080920362debd2ca9b2b14ba25878e7ee640e Author: Jenkins Build Server Date: 2014-02-18 (Tue, 18 Feb 2014

[Pharo-dev] [pharo-project/pharo-core]

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