October 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20334

by Marcus Denker

20334 ----- Issue 6790: MC SaveDialog fork fix http://code.google.com/p/pharo/issues/detail?id=6790 Issue 6788: Improve Regex match/search/matchprefix methods comments http://code.google.com/p/pharo/issues/detail?id=6788 Issue 6787: Finder Cleanup 2 http://code.google.com/p/pharo/issues/detail?id=6787 Issue 6756: Type code in editor go crash and show red panel http://code.google.com/p/pharo/issues/detail?id=6756 -- Marcus Denker -- http://marcusdenker.de

Oct. 12, 2012

[Pharo-project] Fwd: Sujet stage Pharo

by StÃ©phane Ducasse

Please distribute widely :) From: LE PORS Eric <eric.lepors(a)fr.thalesgroup.com> Subject: Sujet stage Pharo Date: October 11, 2012 10:01:27 AM GMT+02:00 To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> Cc: Pierre LABORDE <pierre.laborde(a)fr.thalesgroup.com> A diffuser aux Ã©tudiants motivÃ©s : (Sujet de Stage THALES SYSTEMES AEROPORTES BREST, non diffusÃ© officiellement) Titre : Maquettage Innovant avec Pharo (Logiciel). DurÃ©e : 6 mois, dÃ©but en fÃ©vrier ou mars (stage de fin d'Ã©tude) Description (Contexte technique, objectifs et dÃ©finition prÃ©cise du travail) : Notre entitÃ© dÃ©veloppe rÃ©guliÃ¨rement des maquettes dâinterfaces homme-machine innovantes. Lâinnovation se situe autant au niveau de lâergonomie quâau niveau du design graphique visuel ou des Ã©lÃ©ments dâinteraction. Le maquettage est souvent utilisÃ© en sÃ©ance avec les opÃ©rationnels, dâoÃ¹ lâemploi dâun langage dynamique comme Smalltalk permettant la modification rapide (et en sÃ©ance) du code et des Ã©lÃ©ments dâinteraction. Le maquettage/prototypage des interfaces Homme-Machine est donc actuellement rÃ©alisÃ© sous SMOCK, un framework de maquettage dÃ©veloppÃ© en Smalltalk Visualworks (Commercial). De nombreux Smalltalk existent sur le marchÃ©, cependant une communautÃ© parmi les autres semble de plus en plus active et moderne, Ã la fois en terme de langage et dâaspects interfaces homme machine : la communautÃ© Smalltalk Pharo (OpenSource). Nous souhaitons expÃ©rimenter les apports de Pharo en terme dâinterfaces homme-machine innovantes. Pour ce faire nous proposons au candidat dâeffectuer un portage de notre framework de maquettage composÃ© de SCM (modÃ¨le en composant) et de CADE (Framework orientÃ© dessin et animations). Un exemple dâihm utilisant les Ã©lÃ©ments portÃ©s validera le travail effectuÃ©. CONNAISSANCES SOUHAITEES : Le stagiaire devra avoir une connaissance du Smalltalk ou Ãªtre motivÃ© par lâapprentissage de celui-ci. Il devra ensuite Ãªtre motivÃ© par la conception dâinterface homme machine de nouvelles gÃ©nÃ©rations et novatrices.

Oct. 12, 2012

Re: [Pharo-project] Fuel for Squeak stupid questions

by Max Leske

Thanks Edgar. Much appreciated. On 11.10.2012, at 21:14, Edgar J. De Cleene <edgardec2005(a)gmail.com> wrote: > > > > On 10/11/12 12:53 PM, "Max Leske" <maxleske(a)gmail.com> wrote: > >> Ah! >> >> Could you try the Date fix I proposed in a 4.3 image? >> >> BTW I'm working on fixing the other failing tests (for 4.3) aswell. >> >> Cheers, >> Max > > You was right, some changed recently in Squeak as 4.3 11860 (fresh unzipped) > do not fail the two test of Date, the rest is same as 4.4 > > You only need fileIn TClassAndTraitDescription from Pharo when Monticello > complains > > Edgar > > >

Oct. 12, 2012

Re: [Pharo-project] Interconnection of Morphic and Spec (was: [ANN] Phobos)

by Igor Stasenko

On 11 October 2012 23:04, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Unfortunately it is not only about a layer between Morphic and Spec. > Whole Spec design is greatly conforming to Morphic. Check out Spec > definitions, they look almost like transcription of Morphic calls > > MethodToolbar class >> defaultSpec > <spec> > ^ { #Panel. > #changeTableLayout. > #listDirection:. #rightToLeft. > #addMorph:. {#model. #browseModel.}. > #addMorph:. {#model. #sendersModel.}. > #addMorph:. {#model. #implementorsModel.}. > #addMorph:. {#model. #versionModel. }. > #addMorph:. {#model. #dropListModel.}. > #hResizing:. #spaceFill. > #vResizing:. #shrinkWrap. } > > Of course these methods are implemented only in Morphic classes. Whole > layout management is directly taken from Morphic. And the Spec > definitions are unclear and hard to read. They are composed almost > solely from symbols so it is hard to work with and analyze them with > our development tools. We have such beautiful metalanguage where to > create DSL is so easy... > > In comparison with OmniBrowser the Spec is big step back. Sorry, I do > not want to be ugly but I started this impression when I was working > on Periscope and since that time it is deeper and deeper. > yess.. do some ass kicking please :) As for omnibrowser.. well I didn't looked at spec code, but what i saw in omnibrowser code didn't impressed me much, like having own subclass for every toolbuilder class. Anyways, UI stuff is tend to be complex no matter how nicely you wrap it.. because it is UI. > Cheers, > -- Pavel > -- Best regards, Igor Stasenko.

Oct. 11, 2012

Re: [Pharo-project] Interconnection of Morphic and Spec (was: [ANN] Phobos)

by Benjamin

On Oct 11, 2012, at 11:04 PM, Pavel Krivanek wrote: > Unfortunately it is not only about a layer between Morphic and Spec. > Whole Spec design is greatly conforming to Morphic. Check out Spec > definitions, they look almost like transcription of Morphic calls > > MethodToolbar class >> defaultSpec > <spec> > ^ { #Panel. > #changeTableLayout. > #listDirection:. #rightToLeft. > #addMorph:. {#model. #browseModel.}. > #addMorph:. {#model. #sendersModel.}. > #addMorph:. {#model. #implementorsModel.}. > #addMorph:. {#model. #versionModel. }. > #addMorph:. {#model. #dropListModel.}. > #hResizing:. #spaceFill. > #vResizing:. #shrinkWrap. } This is because this method is out dated, it shold be now ^ SpecLayout composed newRow:[: r | r add: #browseModel; add: #sendersModel; add: #implementorsModel; add: #versionsModel; add: #dropListModel ] height: 25 > > Of course these methods are implemented only in Morphic classes. Whole > layout management is directly taken from Morphic. And the Spec > definitions are unclear and hard to read. They are composed almost > solely from symbols so it is hard to work with and analyze them with > our development tools. We have such beautiful metalanguage where to > create DSL is so easy... > > In comparison with OmniBrowser the Spec is big step back. Sorry, I do > not want to be ugly but I started this impression when I was working > on Periscope and since that time it is deeper and deeper. > > Cheers, > -- Pavel > > > > > > On Thu, Oct 11, 2012 at 10:21 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 11 October 2012 20:52, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>> This method is actually the only one from ComposableModel with direct Morphic binding :) >>> >>> >>> I am still trying to move that away, but I needed the rebuild to work >>> >> i think you can introduce own protocol (and put it as extension to >> morphic, if you want to) >> so, instead of saying >> >> widget removeAllMorphs >> >> you will use own extension method ,like: >> >> widget specRemoveAllChilds >> >> etc (spec here is namespacing prefix for a method, to indicate that it >> belongs to spec package >> and to indicate that it is a contract implied between spec and widget) >> >>> Ben >>> >>> On Oct 11, 2012, at 8:49 PM, Pavel Krivanek wrote: >>> >>>> Hi Ben, >>>> >>>> I really would like to write Spec binding for Phobos (Esteban will >>>> want to do it for Mars etc.). But, how to say that, Spec was not >>>> written with UI Independence in mind :-) Very basic example of that >>>> fact: >>>> >>>> ComposableModel>>buildWithSpec: aSpec >>>> "Build the widget using the spec name provided as argument" >>>> | widget | >>>> >>>> (self spec notNil and: [ self needRebuild not ]) >>>> ifTrue: [ | old | >>>> self needRebuild: true. >>>> old := self widget. >>>> old removeAllMorphs. >>>> self ensureExtentFor: old. >>>> widget := SpecInterpreter buildMorphFor: self withSpec: aSpec. >>>> widget submorphs do:[ :e | old addMorphBack: e ]. >>>> self spec instance: old. >>>> ^ old ] >>>> ifFalse: [ widget := SpecInterpreter buildMorphFor: self withSpec: aSpec. ]. >>>> >>>> self ensureExtentFor: widget. >>>> >>>> ^ widget >>>> >>>> Can you please do at least basic steps in the architecture of Spec to >>>> make it more independent on Morphic? >>>> >>>> Cheers, >>>> -- Pavel >>>> >>>> On Wed, Oct 10, 2012 at 12:10 AM, Benjamin >>>> <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>>>> It was part of my battle plan to rule the world ;) >>>>> >>>>> We wanted with Nico to part it to Amber to get the Javascript part for free, then generate some XUL :) >>>>> >>>>> Anyway, really cool job, and impressive as well :) >>>>> >>>>> Ben >>>>> >>>>> On Oct 9, 2012, at 11:07 PM, StÃ©phane Ducasse wrote: >>>>> >>>>>> It looks really nice. >>>>>> I imagine that Spec could generate XUL too. >>>>>> >>>>>> Stef >>>>>> On Oct 9, 2012, at 9:48 PM, Pavel Krivanek wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I would like to introduce you Phobos - the XULRunner based Smalltalk >>>>>>> framework for development of native GUI with standard look&feel for >>>>>>> Linux, Mac OS X and Windows. >>>>>>> >>>>>>> It is based on Zinc, WebSockets and Seaside continuations. For more >>>>>>> information including more screenshots see the project page: >>>>>>> >>>>>>> http://code.google.com/p/phobos-framework/ >>>>>>> >>>>>>> You should pay attentions to FAQ too: >>>>>>> http://code.google.com/p/phobos-framework/wiki/FAQ >>>>>>> >>>>>>> Phobos has Seaside-like components and rendering style, can combine >>>>>>> XUL with HTML or SVG, supports printing etc. >>>>>>> >>>>>>> Cheers, >>>>>>> -- Pavel >>>>>>> <01.png> >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >

Oct. 11, 2012

[Pharo-project] Interconnection of Morphic and Spec (was: [ANN] Phobos)

by Pavel Krivanek

Unfortunately it is not only about a layer between Morphic and Spec. Whole Spec design is greatly conforming to Morphic. Check out Spec definitions, they look almost like transcription of Morphic calls MethodToolbar class >> defaultSpec <spec> ^ { #Panel. #changeTableLayout. #listDirection:. #rightToLeft. #addMorph:. {#model. #browseModel.}. #addMorph:. {#model. #sendersModel.}. #addMorph:. {#model. #implementorsModel.}. #addMorph:. {#model. #versionModel. }. #addMorph:. {#model. #dropListModel.}. #hResizing:. #spaceFill. #vResizing:. #shrinkWrap. } Of course these methods are implemented only in Morphic classes. Whole layout management is directly taken from Morphic. And the Spec definitions are unclear and hard to read. They are composed almost solely from symbols so it is hard to work with and analyze them with our development tools. We have such beautiful metalanguage where to create DSL is so easy... In comparison with OmniBrowser the Spec is big step back. Sorry, I do not want to be ugly but I started this impression when I was working on Periscope and since that time it is deeper and deeper. Cheers, -- Pavel On Thu, Oct 11, 2012 at 10:21 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 11 October 2012 20:52, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> This method is actually the only one from ComposableModel with direct Morphic binding :) >> >> >> I am still trying to move that away, but I needed the rebuild to work >> > i think you can introduce own protocol (and put it as extension to > morphic, if you want to) > so, instead of saying > > widget removeAllMorphs > > you will use own extension method ,like: > > widget specRemoveAllChilds > > etc (spec here is namespacing prefix for a method, to indicate that it > belongs to spec package > and to indicate that it is a contract implied between spec and widget) > >> Ben >> >> On Oct 11, 2012, at 8:49 PM, Pavel Krivanek wrote: >> >>> Hi Ben, >>> >>> I really would like to write Spec binding for Phobos (Esteban will >>> want to do it for Mars etc.). But, how to say that, Spec was not >>> written with UI Independence in mind :-) Very basic example of that >>> fact: >>> >>> ComposableModel>>buildWithSpec: aSpec >>> "Build the widget using the spec name provided as argument" >>> | widget | >>> >>> (self spec notNil and: [ self needRebuild not ]) >>> ifTrue: [ | old | >>> self needRebuild: true. >>> old := self widget. >>> old removeAllMorphs. >>> self ensureExtentFor: old. >>> widget := SpecInterpreter buildMorphFor: self withSpec: aSpec. >>> widget submorphs do:[ :e | old addMorphBack: e ]. >>> self spec instance: old. >>> ^ old ] >>> ifFalse: [ widget := SpecInterpreter buildMorphFor: self withSpec: aSpec. ]. >>> >>> self ensureExtentFor: widget. >>> >>> ^ widget >>> >>> Can you please do at least basic steps in the architecture of Spec to >>> make it more independent on Morphic? >>> >>> Cheers, >>> -- Pavel >>> >>> On Wed, Oct 10, 2012 at 12:10 AM, Benjamin >>> <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>>> It was part of my battle plan to rule the world ;) >>>> >>>> We wanted with Nico to part it to Amber to get the Javascript part for free, then generate some XUL :) >>>> >>>> Anyway, really cool job, and impressive as well :) >>>> >>>> Ben >>>> >>>> On Oct 9, 2012, at 11:07 PM, StÃ©phane Ducasse wrote: >>>> >>>>> It looks really nice. >>>>> I imagine that Spec could generate XUL too. >>>>> >>>>> Stef >>>>> On Oct 9, 2012, at 9:48 PM, Pavel Krivanek wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I would like to introduce you Phobos - the XULRunner based Smalltalk >>>>>> framework for development of native GUI with standard look&feel for >>>>>> Linux, Mac OS X and Windows. >>>>>> >>>>>> It is based on Zinc, WebSockets and Seaside continuations. For more >>>>>> information including more screenshots see the project page: >>>>>> >>>>>> http://code.google.com/p/phobos-framework/ >>>>>> >>>>>> You should pay attentions to FAQ too: >>>>>> http://code.google.com/p/phobos-framework/wiki/FAQ >>>>>> >>>>>> Phobos has Seaside-like components and rendering style, can combine >>>>>> XUL with HTML or SVG, supports printing etc. >>>>>> >>>>>> Cheers, >>>>>> -- Pavel >>>>>> <01.png> >>>>> >>>>> >>>> >>>> >>> >> >> > > > > -- > Best regards, > Igor Stasenko. >

Oct. 11, 2012

Re: [Pharo-project] [ANN] Phobos

by Igor Stasenko

On 11 October 2012 20:52, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > This method is actually the only one from ComposableModel with direct Morphic binding :) > > > I am still trying to move that away, but I needed the rebuild to work > i think you can introduce own protocol (and put it as extension to morphic, if you want to) so, instead of saying widget removeAllMorphs you will use own extension method ,like: widget specRemoveAllChilds etc (spec here is namespacing prefix for a method, to indicate that it belongs to spec package and to indicate that it is a contract implied between spec and widget) > Ben > > On Oct 11, 2012, at 8:49 PM, Pavel Krivanek wrote: > >> Hi Ben, >> >> I really would like to write Spec binding for Phobos (Esteban will >> want to do it for Mars etc.). But, how to say that, Spec was not >> written with UI Independence in mind :-) Very basic example of that >> fact: >> >> ComposableModel>>buildWithSpec: aSpec >> "Build the widget using the spec name provided as argument" >> | widget | >> >> (self spec notNil and: [ self needRebuild not ]) >> ifTrue: [ | old | >> self needRebuild: true. >> old := self widget. >> old removeAllMorphs. >> self ensureExtentFor: old. >> widget := SpecInterpreter buildMorphFor: self withSpec: aSpec. >> widget submorphs do:[ :e | old addMorphBack: e ]. >> self spec instance: old. >> ^ old ] >> ifFalse: [ widget := SpecInterpreter buildMorphFor: self withSpec: aSpec. ]. >> >> self ensureExtentFor: widget. >> >> ^ widget >> >> Can you please do at least basic steps in the architecture of Spec to >> make it more independent on Morphic? >> >> Cheers, >> -- Pavel >> >> On Wed, Oct 10, 2012 at 12:10 AM, Benjamin >> <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>> It was part of my battle plan to rule the world ;) >>> >>> We wanted with Nico to part it to Amber to get the Javascript part for free, then generate some XUL :) >>> >>> Anyway, really cool job, and impressive as well :) >>> >>> Ben >>> >>> On Oct 9, 2012, at 11:07 PM, StÃ©phane Ducasse wrote: >>> >>>> It looks really nice. >>>> I imagine that Spec could generate XUL too. >>>> >>>> Stef >>>> On Oct 9, 2012, at 9:48 PM, Pavel Krivanek wrote: >>>> >>>>> Hi all, >>>>> >>>>> I would like to introduce you Phobos - the XULRunner based Smalltalk >>>>> framework for development of native GUI with standard look&feel for >>>>> Linux, Mac OS X and Windows. >>>>> >>>>> It is based on Zinc, WebSockets and Seaside continuations. For more >>>>> information including more screenshots see the project page: >>>>> >>>>> http://code.google.com/p/phobos-framework/ >>>>> >>>>> You should pay attentions to FAQ too: >>>>> http://code.google.com/p/phobos-framework/wiki/FAQ >>>>> >>>>> Phobos has Seaside-like components and rendering style, can combine >>>>> XUL with HTML or SVG, supports printing etc. >>>>> >>>>> Cheers, >>>>> -- Pavel >>>>> <01.png> >>>> >>>> >>> >>> >> > > -- Best regards, Igor Stasenko.

Oct. 11, 2012

Re: [Pharo-project] Phobos and OmniBrowser

by Tudor Girba

+1 On Thu, Oct 11, 2012 at 9:17 PM, Edgar J. De Cleene <edgardec2005(a)gmail.com>wrote: > > > > On 10/11/12 12:46 PM, "Pavel Krivanek" <pavel.krivanek(a)gmail.com> wrote: > > > Hi, > > > > for Phobos [1] I created a very basic support for CodeMirror (HTML > > code editor) and OmniBrowser (on Pharo 1.4) so I can share some cool > > screenshot with you again ;-) > > > > [1] http://code.google.com/p/phobos-framework/ > > > > Cheers, > > -- Pavel > > > Excellent as always !! > > Edgar > > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 11, 2012

Re: [Pharo-project] Pharo on retina display

by Tudor Girba

:( On Thu, Oct 11, 2012 at 3:14 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Tudor Girba-2 wrote > > Did anyone find a solution to this problem? > > I just got used to the fuzziness :) > > > > -- > View this message in context: > http://forum.world.st/Pharo-on-retina-display-tp4642567p4650783.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 11, 2012

Re: [Pharo-project] Phobos and OmniBrowser

by Edgar J. De Cleene

On 10/11/12 12:46 PM, "Pavel Krivanek" <pavel.krivanek(a)gmail.com> wrote: > Hi, > > for Phobos [1] I created a very basic support for CodeMirror (HTML > code editor) and OmniBrowser (on Pharo 1.4) so I can share some cool > screenshot with you again ;-) > > [1] http://code.google.com/p/phobos-framework/ > > Cheers, > -- Pavel Excellent as always !! Edgar

Oct. 11, 2012