March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] More GSoC ideas wanted, 3 days left ....

by Sean P. DeNigris

ClÃ©ment Bera-4 wrote > Title: A Pharo Image running on top of VirtualBox with the help of a Linux > micro kernel I wrapped some of the VirtualBox command line. The code is on ss3. ----- Cheers, Sean -- View this message in context: http://forum.world.st/More-GSoC-ideas-wanted-3-days-left-tp4678353p4678639.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 27, 2013

Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by Paul DeBruicker

StÃ©phane Ducasse wrote > Hi guys > > we would like to use seaside to validate the VM and also make sure that > Seaside31. works perfectly in Pharo2.0. > I saw that some of you have a working configuration. Where can we find it > because we would like to publish it in the > MetaRepoForPharo20. > > Stef 3.1 is not released. That being said see if this set of packages works for you http://dl.dropbox.com/u/4460862/seaside31Config.zip but they are also not official versions of anything and the official ones will likely be different. they are just something I cobbled together that seemed to work at the beginning of the month. -- View this message in context: http://forum.world.st/Looking-for-a-Seaside-3-1-Configuration-for-Pharo-2-0… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 27, 2013

Re: [Pharo-project] How to open a file with external app

by Camillo Bruni

The only solution currently is to use OSProcess and - open under OSX - gnome-open under linux On 2013-03-27, at 23:05, jannik.laval <jannik.laval(a)gmail.com> wrote: > Hi pharoers, > > Is it possible to select a file and open it with an external application ? > For example, I need to open a pdf file. > > How can I do that ? > > Thank you for the help, > Jannik >

March 27, 2013

[Pharo-project] How to open a file with external app

by jannik.laval

Hi pharoers, Is it possible to select a file and open it with an external application ? For example, I need to open a pdf file. How can I do that ? Thank you for the help, Jannik

March 27, 2013

Re: [Pharo-project] Non-Smalltalk content in Pharo and Nautilus

by Guillermo Polito

On Wed, Mar 27, 2013 at 9:18 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > When working with Seaside (or other frameworks) one often works with > non-Smalltalk resources > stored within the image (CSS styles, images, ...) often stored as strings > within > methods: > > > myCss > ^'body { > background-color: #ffffce; > }' > > or > > script > ^'alert("hello from Javascript");' > > > I also often see Base64 encoded images, or when working with XML a method > might return XML content. > > With things like Helvetia [1], the reworked autocompletion/syntax > highlighting and new > browsers like Nautilus in mind I wonder if (may be in the not so far > future) I can: > > - click on a Smalltalk method to get ST styling and edit functionality > - click on a CSS content method to do CSS styling and completion > - click on a method with a form content to display the picture (and not > the Base64 encoded string) > - click on an XML content to browse the XML tree > - click on an HTML providing method to edit HTML and maybe preview > - click on a method with CSV to edit the tabular data within a grid > - click on a primitive method to see Slang or C/C++ code > - ... > > Internally the content can be distinguished using pragmas: > > > myCss > <mime-type: text/css> > ^'body { > background-color: #ffffce; > }' > > > Are there any plans to move Pharo into this "not only Smalltalk" in > methods direction? > > Is it already possible to easily extend Nautilus with "pluggable" custom > panes depending on the > method content. > > I see that there are buttons on the Nautilus side. Wouldnt it be better to > have "Tabs" > with "Source" as default and where I can add my own custom tabs? > > Would be a lot of work to provide editors and stylers for all the > mime-types or autocompletion > for JavaScript, SQL, ... whatever. But the question is more "do we have > the groundwork so > people can built up on it." > > Any comments? > I'd like to see something like that... a GSOC? > > Thx > T. > > [1] http://scg.unibe.ch/research/helvetia > > >

March 27, 2013

[Pharo-project] Non-Smalltalk content in Pharo and Nautilus

by Torsten Bergmann

When working with Seaside (or other frameworks) one often works with non-Smalltalk resources stored within the image (CSS styles, images, ...) often stored as strings within methods: myCss ^'body { background-color: #ffffce; }' or script ^'alert("hello from Javascript");' I also often see Base64 encoded images, or when working with XML a method might return XML content. With things like Helvetia [1], the reworked autocompletion/syntax highlighting and new browsers like Nautilus in mind I wonder if (may be in the not so far future) I can: - click on a Smalltalk method to get ST styling and edit functionality - click on a CSS content method to do CSS styling and completion - click on a method with a form content to display the picture (and not the Base64 encoded string) - click on an XML content to browse the XML tree - click on an HTML providing method to edit HTML and maybe preview - click on a method with CSV to edit the tabular data within a grid - click on a primitive method to see Slang or C/C++ code - ... Internally the content can be distinguished using pragmas: myCss <mime-type: text/css> ^'body { background-color: #ffffce; }' Are there any plans to move Pharo into this "not only Smalltalk" in methods direction? Is it already possible to easily extend Nautilus with "pluggable" custom panes depending on the method content. I see that there are buttons on the Nautilus side. Wouldnt it be better to have "Tabs" with "Source" as default and where I can add my own custom tabs? Would be a lot of work to provide editors and stylers for all the mime-types or autocompletion for JavaScript, SQL, ... whatever. But the question is more "do we have the groundwork so people can built up on it." Any comments? Thx T. [1] http://scg.unibe.ch/research/helvetia

March 27, 2013

Re: [Pharo-project] ClassTestCase should be in SUnit not in Tests, agree?

by Marcus Denker

On Mar 27, 2013, at 7:50 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi All, > > I'm trying to load NetworkTests into a Newspeak image. This image doesn't include Tests, but does contain SUnit and SUnitGUI. I can't load NetworkTests because it depends on ClassTestCase which is in Tests-Utilities. IMO ClassTestCase should be in SUnit. Any disagreements? Any agreements? Mind if I move it there? I checked, in Pharo it is already in SUnit-Core-Utilities. Marcus

March 27, 2013

Re: [Pharo-project] Suggestion about Phexample and StateSpecs(Mocketry) integration

by Yuriy Tymchuk

If you can write step by step instruction what to show, I can do it. Right now all my time is used to prepare my own presentation, so I can't do it myself. uko On 27 Ð±ÐµÑ. 2013, at 18:41, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2013/3/27 Tudor Girba <tudor(a)tudorgirba.com> > Perhaps Mocketry would be a good topic for a "Show us your projects" session. Then we can try to go into a couple of more details. > > > Unfortunately I can't participate conference this year > > Cheers, > Doru > > > On Mar 27, 2013, at 12:42 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > Sounds good to me. > > > > On 26 Ð±ÐµÑ. 2013, at 23:00, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > > >> > >> On 2013-03-26, at 19:45, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > >> > >>> 2013/3/26 Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > >>> > >>>> Ok, and what if we will change behavior a bit so if no definitions were > >>>> found it will send the incoming message to enclosed object? This way it > >>>> will work like phexample but will also allow to define some fancy DSL. > >>>> > >>> > >>> We can copy all phexample syntax methods into single class inside > >>> StateSpecs package but replace implementation with pragmas approach. So > >>> anybody can browse implementors like usual and it will not required any > >>> special cases. > >>> > >>> How I can influence your interest, guys? I can provide cleaning, comments, > >>> improvements to StateSpecs. I opened for your requirements. > >>> Phexample become quite popular and can be part of Pharo sometimes. > >>> Mocketry/StateSpecs used by people too. > >>> It would be bad if this packages can't be used together. > >> > >> sorry for starting the whole rant :) I am veery busy at least until tomorrow > >> > >> Yuriy we can discuss that after tomorrow? > >> I would as well appreciate some common solution to avoid the selector clash. > >> > >> > >> > >>>> On 26 Ð±ÐµÑ. 2013, at 07:46, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > >>>> > >>>> Hello > >>>> 2013/3/26 Camillo Bruni <camillobruni(a)gmail.com> > >>>> > >>>>> Definitely StateSpec looks more mature and can be used in a more flexible > >>>>> way. > >>>>> But I am not a big fan of the pragma magic. Why? > >>>>> It breaks all tools for me :/. If I see a message send I want to be able > >>>>> to: > >>>>> - browse it, so I can see who implements it? > >>>>> - debug it directly to get to the real method. > >>>>> > >>>>> SateSpec does indeed help writing readable code by allowing almost > >>>>> grammatically > >>>>> correct sentences. However I don't think this is the way to program. I am > >>>>> a big > >>>>> fan of stupid english: > >>>>> > >>>>> `foo should isKindOf: Bar` vs. `foo should be an instance of: Bar` > >>>>> > >>>>> If I want to figure out how the first one works, I can simply browse the > >>>>> implementors of #should and/or #isKindOf: where is the StateSpec version > >>>>> I am > >>>>> lost. I have to rely on "contains string literal" to get the sources, for > >>>>> me > >>>>> that is very strange. > >>>>> > >>>> > >>>> I think main thing you want is easilly explore all available should > >>>> syntax. And StateSpecs can be easilly adopted for such task. We can just > >>>> move all methods with syntax pragmas to single class. So you can open this > >>>> class and see what available. > >>>> > >>>> To get implementors of some "should expression" you should use senders > >>>> search of syntax words instead of implementors. Syntax words in StateSpecs > >>>> is just method literals ( <syntax: #(be an instance of:)>, #() is just > >>>> array of symbols). > >>>> > >>>> Interesting that StateSpecs has more explicit syntax system. How you can > >>>> explore in Phexample expression: > >>>> > >>>> object should be true > >>>> ? > >>>> > >>>> You have separate PheMatcher>>be and PheMatcher>>true methods and there is > >>>> no places in code where you can see that this messages can and should be > >>>> used together. > >>>> But with StateSpecs you should put pragma with explicit expression like: > >>>> > >>>> Equal>>true: anObject > >>>> <syntax: #(be true)> > >>>> ^self return: (IdentitySpec pattern: true) > >>>> > >>>> So with StateSpecs you have full syntax expression at one place which can > >>>> be easy explored. > >>>> And for example to support Phexample mesage #beTrue you should just add > >>>> another pragma: > >>>> > >>>> Equal>>true: anObject > >>>> <syntax: #(be true)> > >>>> <syntax: #(beTrue)> > >>>> ^self return: (IdentitySpec pattern: true) > >>>> > >>>> So with Phexample you can browse implementors of "single word should > >>>> expressions". But with Phexample if you browse implementors of #be like > >>>> messages you have no idea how it can be used. > >>>> In StateSpecs you should use senders. And with StateSpecs if you browse > >>>> "any syntax word implementors" by senders seach you will see all possible > >>>> usage cases. And if I move all methods with syntax pragmas to single class > >>>> you can easilly see all possible expressions in one place. > >>>> > >>>> `foo should isKindOf: Bar` vs. `foo should be an instance of: Bar` > >>>>> > >>>> > >>>> With StateSpecs it should be > >>>> > >>>> foo should be a kind of: Bar > >>>> > >>>> And as I said before It is simple task to support all Phexample > >>>> expressions by StateSpecs pragmas > >>>> > >>>> Best regards, > >>>> Denis > >>>> > >>>> > >>>> > >> > >> > > > > > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > > >

March 27, 2013

[Pharo-project] ClassTestCase should be in SUnit not in Tests, agree?

by Eliot Miranda

Hi All, I'm trying to load NetworkTests into a Newspeak image. This image doesn't include Tests, but does contain SUnit and SUnitGUI. I can't load NetworkTests because it depends on ClassTestCase which is in Tests-Utilities. IMO ClassTestCase should be in SUnit. Any disagreements? Any agreements? Mind if I move it there? -- best, Eliot

March 27, 2013

Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by Johan Brichau

I'm merging mine and Paul's configuration for Seaside 3.0.7 into Diego's and Stefan's work. Of course, there's always stuff that gets in the way of finishing that (like moving our offices ;-). I hope to have one by end of the week for Seaside 3.0.7. The intention is that we merge this into the Seaside3.1 configuration. On 27 Mar 2013, at 18:28, Stephan Eggermont <stephan(a)stack.nl> wrote: > Stef wrote: >> we would like to use seaside to validate the VM and also make sure that Seaside31. works perfectly in Pharo2.0. >> I saw that some of you have a working configuration. Where can we find it because we would like to publish it in the >> MetaRepoForPharo20. > > We have it working, but it does not have the Seaside Panel (& browser). At last Esug Seaside sprint I started redoing > them in Spec, but never managed to spend more time on them. They are in the Seaside31 repository > on squeaksource: Seaside-Pharo-Tools-Spec (might need renaming to Pharo20). > > Stephan > > > >

March 27, 2013