January 2012 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo Morphic View Application Framework

by StÃ©phane Ducasse

did you see what benjamin is doing with Spec. Because you should join effort the idea is that we can define object with spec and compose them and their logic using value holder. Stef On Jan 31, 2012, at 5:58 AM, S Krish wrote: > http://skrishnamachari.wordpress.com/2012/01/31/pharo-application-framework… > > Obliged for feedback ... > > For details and links.. > Sharing this little framework that should go some way to ease creating large applications ( currently morphic oriented). > > AbstractMorphicView subclass: #MyNewView â¦ > > #createMorphsSpecs > > ^{ > > âpanel1â² -> #SomeOtherView. > âlabel1â² -> #LabelMorph. > âtext1â² -> #PluggableTextMorph. > âbutton1â² -> #PluggableButtonMorph. > } > > layoutSpecsArray > > ^{ > âwidgetNameInMorphsDictionaryâ -> { > #fractions -> (0 @ 0 corner: 1 @ 0.5). â fractional value 0 to 1 range â > #offsets -> (10 @ 10 corner: 0 @ 0). â offsets relative to the fractional position â > }. > > ââ¦ add other widgetspecsâ¦â > } > > Thats it.. you should have a prototype UI neatly laid out.. and then specify: #morphsPrimaryPropertiesSpecs and #morphsSecondaryPropertiesSpecs for full functionality that composes views inside views and scales well. > > AbstractSimpleMorphicView can make it simpler for TableLayout stuff without requiring #layoutSpecsArray. > > ..... the main post has other details and links to package... >

Jan. 31, 2012

Pharo Morphic View Application Framework

by S Krish

http://skrishnamachari.wordpress.com/2012/01/31/pharo-application-framework… Obliged for feedback ... For details and links.. Sharing this little framework that should go some way to ease creating large applications ( currently morphic oriented). AbstractMorphicView subclass: #MyNewView â¦ #createMorphsSpecs ^{ âpanel1â² -> #SomeOtherView. âlabel1â² -> #LabelMorph. âtext1â² -> #PluggableTextMorph. âbutton1â² -> #PluggableButtonMorph. } layoutSpecsArray ^{ âwidgetNameInMorphsDictionaryâ -> { #fractions -> (0 @ 0 corner: 1 @ 0.5). â fractional value 0 to 1 range â #offsets -> (10 @ 10 corner: 0 @ 0). â offsets relative to the fractional position â }. ââ¦ add other widgetspecsâ¦â } Thats it.. you should have a prototype UI neatly laid out.. and then specify: #morphsPrimaryPropertiesSpecs and #morphsSecondaryPropertiesSpecs for full functionality that composes views inside views and scales well. AbstractSimpleMorphicView can make it simpler for TableLayout stuff without requiring #layoutSpecsArray. ..... the main post has other details and links to package...

Jan. 31, 2012

Re: [Pharo-users] Command Line Interface using FFI

by Guillermo Polito

Hmm, I've tried doing it from a non-headless image. Maybe it has something to do with it? Guille On Mon, Jan 30, 2012 at 8:34 AM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 30 Jan 2012, at 11:44, Guillermo Polito wrote: > > > FileStream stdout nextPutAll: 'something';crlf. > > > > Works great, but > > > > FileStream stdin next. > > > > Never returns :/. Whatever I try. > > > > Any idea? > > That is not good, I must admit I only tried #stout, so I did: > > $ cat run.sh > > #!/bin/bash > script_home=$(dirname $0) > script_home=$(cd $script_home && pwd) > image=$script_home/experimental.image > script=$script_home/run.st > args=$* > vm=$script_home/bin/CogVM > options="-vm-display-null -vm-sound-null" > #echo $vm $options $image $script $args > $vm $options $image $script $args > > $ cat run.st > [ FileStream stdin atEnd ] whileFalse: [ > FileStream stdout nextPut: FileStream stdin next ]. > ! > Smalltalk snapshot: false andQuit: true. > > $ cat /tmp/foo.txt > Hello there! > Welcome to Smalltalk. > > > > $ cat /tmp/foo.txt | ./run.sh > Hello there! > Welcome to Smalltalk. > > > > So that seems to work. > > HTH, > > Sven > > >

Jan. 30, 2012

Re: [Pharo-users] Command Line Interface using FFI

by Guillermo Polito

On Mon, Jan 30, 2012 at 9:17 AM, David T. Lewis <lewis(a)mail.msen.com> wrote: > On Mon, Jan 30, 2012 at 07:44:40AM -0300, Guillermo Polito wrote: > > FileStream stdout nextPutAll: 'something';crlf. > > > > Works great, but > > > > FileStream stdin next. > > > > Never returns :/. Whatever I try. > > > > Any idea? > > > > This is because no data was received on the standard input stream. Try > typing something followed by <enter> so that the operating system terminal > actually sends some data. > I did :/. I always open my images from the terminal. And the stdout prints in the terminal where I've opened the image. But when if I use stdin and write to that console, it does not work :/. However, if I do this with fgets+FFI it works... (It blocks but when I enter data into the terminal the control is returned to the image). > By default, the stdin, stdout, and stderr streams are all in blocking mode > unless you set them otherwise. If you want to set the stdin to nonblocking > mode, see #setNonBlocking in package OSProcess. Note that there is no > "correct" setting for this, it depends on what you are trying to do with > the stream. > > HTH, > Dave > > Thanks!

Jan. 30, 2012

**Important** Pharo Conference Call for Date Feedback

by StÃ©phane Ducasse

Hi guys We want to organize a Pharo Conference @ lille around business and companies in May/June 2012. Now we need you to understand what is the best to organize because we have some constraints (like not good access to rooms on saturday). Could you reply to the following questions: Are you planning to attend: Yes No Would you attend two days: Yes No Would you like to present something: Yes No Would you prefer to have (remove the one you do not like) - one friday and one saturday or - two days during the week would be not a problem. Would you like to have Handons: Yes No Business/Experience returns: Yes No What are the following dates that are ok for you? Frid 11- Satur 12 May 2012: Yes No Thur 10- Frid 11 May 2012: Yes No Mond 14- Tuesd 15 May 2012: Yes No Tuesd 15- Wedn 16 May 2012: Yes No Thur 24 - Frid 25 May 2012: Yes No Frid 25- Satur 26 May 2012: Yes No Stef

Jan. 30, 2012

Re: [Pharo-users] Command Line Interface using FFI

by David T. Lewis

On Mon, Jan 30, 2012 at 07:44:40AM -0300, Guillermo Polito wrote: > FileStream stdout nextPutAll: 'something';crlf. > > Works great, but > > FileStream stdin next. > > Never returns :/. Whatever I try. > > Any idea? > This is because no data was received on the standard input stream. Try typing something followed by <enter> so that the operating system terminal actually sends some data. By default, the stdin, stdout, and stderr streams are all in blocking mode unless you set them otherwise. If you want to set the stdin to nonblocking mode, see #setNonBlocking in package OSProcess. Note that there is no "correct" setting for this, it depends on what you are trying to do with the stream. HTH, Dave

Jan. 30, 2012

Re: [Pharo-users] Command Line Interface using FFI

by Sven Van Caekenberghe

On 30 Jan 2012, at 11:44, Guillermo Polito wrote: > FileStream stdout nextPutAll: 'something';crlf. > > Works great, but > > FileStream stdin next. > > Never returns :/. Whatever I try. > > Any idea? That is not good, I must admit I only tried #stout, so I did: $ cat run.sh #!/bin/bash script_home=$(dirname $0) script_home=$(cd $script_home && pwd) image=$script_home/experimental.image script=$script_home/run.st args=$* vm=$script_home/bin/CogVM options="-vm-display-null -vm-sound-null" #echo $vm $options $image $script $args $vm $options $image $script $args $ cat run.st [ FileStream stdin atEnd ] whileFalse: [ FileStream stdout nextPut: FileStream stdin next ]. ! Smalltalk snapshot: false andQuit: true. $ cat /tmp/foo.txt Hello there! Welcome to Smalltalk. $ cat /tmp/foo.txt | ./run.sh Hello there! Welcome to Smalltalk. So that seems to work. HTH, Sven

Jan. 30, 2012

Re: [Pharo-users] Command Line Interface using FFI

by Guillermo Polito

FileStream stdout nextPutAll: 'something';crlf. Works great, but FileStream stdin next. Never returns :/. Whatever I try. Any idea? On Mon, Jan 30, 2012 at 1:29 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > > > On Sun, Jan 29, 2012 at 6:58 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > >> Hi Guillermo, >> >> On 29 Jan 2012, at 21:11, Guillermo Polito wrote: >> >> > I've spent a few hours playing with Alien+FFI and I did want to have a >> Command line interface to play and use as a quick browser. >> > >> > Gofer it >> > squeaksource: 'CLInterface'; >> > package: 'ConfigurationOfCLInterface'; >> > load. >> > >> > ConfigurationOfCLInterface load. >> > >> > >> > To play with it write a script, for example startCLI.st, with the >> following: >> > >> > CLInterface start >> > >> > >> > >> > And then, from the command line >> > >> > CogVM -vm-display-null <image> startCLI.st >> > >> > >> > What it does support? >> > - executes smalltalk expressions >> > - handles the errors and shows them into the stdout (so it does not >> explode :P) >> > - stores variables as a workspace >> > Since I used standard C functions (fgets and printf only) this should >> work on every platform from scratch (having a VM with FFI working, of >> course)... >> > >> > The problems I've ran so far: >> > - blocking FFI blocks the vm. I've not tried yet to use threads >> through FFI (and I don't know if it works. Does it?). But It should be >> great to start a headless seaside server with a command line :/. >> > >> > Ok, it's a very simple thing, but it allows to execute a expression >> from a remote server via ssh without doing much :). >> > >> > Guille >> >> Cool, but why do you need to access those C functions ? >> You do know that you can access std* from Smalltalk, do you ? >> > > No! :D > > >> Have a look at the FileStream class 'stdio' category. >> > > will do :). Will that solve the vm-block issue? > > >> >> Apart from that, nice small, readable and useful hack. >> >> Thanks :P. > > >> Regards, >> >> Sven >> >> >> >

Jan. 30, 2012

Re: [Pharo-users] Command Line Interface using FFI

by Guillermo Polito

On Sun, Jan 29, 2012 at 6:58 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > Hi Guillermo, > > On 29 Jan 2012, at 21:11, Guillermo Polito wrote: > > > I've spent a few hours playing with Alien+FFI and I did want to have a > Command line interface to play and use as a quick browser. > > > > Gofer it > > squeaksource: 'CLInterface'; > > package: 'ConfigurationOfCLInterface'; > > load. > > > > ConfigurationOfCLInterface load. > > > > > > To play with it write a script, for example startCLI.st, with the > following: > > > > CLInterface start > > > > > > > > And then, from the command line > > > > CogVM -vm-display-null <image> startCLI.st > > > > > > What it does support? > > - executes smalltalk expressions > > - handles the errors and shows them into the stdout (so it does not > explode :P) > > - stores variables as a workspace > > Since I used standard C functions (fgets and printf only) this should > work on every platform from scratch (having a VM with FFI working, of > course)... > > > > The problems I've ran so far: > > - blocking FFI blocks the vm. I've not tried yet to use threads through > FFI (and I don't know if it works. Does it?). But It should be great to > start a headless seaside server with a command line :/. > > > > Ok, it's a very simple thing, but it allows to execute a expression from > a remote server via ssh without doing much :). > > > > Guille > > Cool, but why do you need to access those C functions ? > You do know that you can access std* from Smalltalk, do you ? > No! :D > Have a look at the FileStream class 'stdio' category. > will do :). Will that solve the vm-block issue? > > Apart from that, nice small, readable and useful hack. > > Thanks :P. > Regards, > > Sven > > >

Jan. 30, 2012

Re: [Pharo-users] Command Line Interface using FFI

by Sven Van Caekenberghe

Hi Guillermo, On 29 Jan 2012, at 21:11, Guillermo Polito wrote: > I've spent a few hours playing with Alien+FFI and I did want to have a Command line interface to play and use as a quick browser. > > Gofer it > squeaksource: 'CLInterface'; > package: 'ConfigurationOfCLInterface'; > load. > > ConfigurationOfCLInterface load. > > > To play with it write a script, for example startCLI.st, with the following: > > CLInterface start > > > > And then, from the command line > > CogVM -vm-display-null <image> startCLI.st > > > What it does support? > - executes smalltalk expressions > - handles the errors and shows them into the stdout (so it does not explode :P) > - stores variables as a workspace > Since I used standard C functions (fgets and printf only) this should work on every platform from scratch (having a VM with FFI working, of course)... > > The problems I've ran so far: > - blocking FFI blocks the vm. I've not tried yet to use threads through FFI (and I don't know if it works. Does it?). But It should be great to start a headless seaside server with a command line :/. > > Ok, it's a very simple thing, but it allows to execute a expression from a remote server via ssh without doing much :). > > Guille Cool, but why do you need to access those C functions ? You do know that you can access std* from Smalltalk, do you ? Have a look at the FileStream class 'stdio' category. Apart from that, nice small, readable and useful hack. Regards, Sven

Jan. 29, 2012