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

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

by Lorenzo Schiavina

Hi Krish, when I load http://www.squeaksource.com/PharoGoodies/Table-Support-SKR-skrish.5.mcz I receive the error TableMorphResources unknow variable. What I am missing? Thank you Lorenzo ----- Original Message ----- From: Krishsmalltalk To: Krishsmalltalk Cc: <Pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, February 04, 2012 4:08 PM Subject: Re: [Pharo-project] Pharo Morphic View Application Framework Though there is minor typos in PDF like this (MorphicViewPackageBrowser new packageName: 'PharoMorphicView-Core ) open. The package is a base I have... So correction there... On Feb 4, 2012, at 8:34 PM, Krishsmalltalk <krishnamachari.sudhakar(a)gmail.com> wrote: For the Packages listed in the PDF Dependencies are: load these http://www.squeaksource.com/PharoGoodies/Table-Support-SKR-skrish.5.mcz http://www.squeaksource.com/PharoGoodies/Toothpick-skrish.7.mcz http://www.squeaksource.com/XMLSupport/XML-Parser-AlexandreBergel.93.mcz http://www.squeaksource.com/XMLRPC/XMLRPC-Client-Core-GermanArduino.20.mcz I will check and split out the dependencies to make it easy to load the first examples framework easier by tomorrow Then load this.. http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Core-skrish.6.mcz Though if u load ignoring the errors the initial example will work fine... Without dependencies that is reqd for RPC integration Should have the first set that will help you run through the example listed. http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Examples-PackageB… This should get you the example browser code to directly play with http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Examples-skrish.4… http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Tests-skrish.3.mcz For the rest of the examples and tests.. Sudhakar krishnamachari Extn 91-40403012 Cell 9902104814 On Feb 4, 2012, at 7:27 PM, "Lorenzo Schiavina" <lorenzo(a)edor.it> wrote: Hi Krish, I tryed to install http://www.squeaksource.com/PharoGoodies/ into Pharo 3.0, but I got several errors. Can you give me some hints for testing the package with the PDF you sent? Many thanks Ciao Lorenzo ----- Original Message ----- From: S Krish To: pharo-project(a)lists.gforge.inria.fr ; pharo-users(a)lists.gforge.inria.fr Sent: Saturday, February 04, 2012 11:31 AM Subject: Re: [Pharo-project] Pharo Morphic View Application Framework The PDF documentation of the framework. Obliged for review/ read and comment and try out the first release.. Ben, I have done a first read of the Spec and I will get my head around how this should be converge.. Will work on that. Though I must note that the spec framework I have laid out is simplistic, flexible and uses the current framework of classes/ morphs without the ValueModel wrapper. Perhaps there is a common ground there, but I would like to emphasize on flexibility of spec and explicit construction to mix and built out has been central to the thought process. On Tue, Jan 31, 2012 at 10:28 AM, S Krish <krishnamachari.sudhakar(a)gmail.com> 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...

Feb. 4, 2012

[Pharo-project] [update 1.4] #14305

by StÃ©phane Ducasse

14305 ----- - Issue 5223: New approach to tryNamedPrimitive:with:. Thanks Mariano Martinez-Peck. http://code.google.com/p/pharo/issues/detail?id=5223 Issue 4997: isPrime is broken http://code.google.com/p/pharo/issues/detail?id=4997 Stef

Feb. 4, 2012

[Pharo-project] [update 1.4] #14304

by StÃ©phane Ducasse

14304 ----- - Issue 5243: Fix text morph margins. Part two. http://code.google.com/p/pharo/issues/detail?id=5243 - Issue 5245: Cleaning Sorter http://code.google.com/p/pharo/issues/detail?id=5245 - Issue 5244: Add a comment on PluggableTextMorph. Thanks Benjamin van Ryseghem. http://code.google.com/p/pharo/issues/detail?id=5244 Stef

Feb. 4, 2012

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

by Krishsmalltalk

Though there is minor typos in PDF like this (MorphicViewPackageBrowser new packageName: 'PharoMorphicView-Core ) open. The package is a base I have... So correction there... On Feb 4, 2012, at 8:34 PM, Krishsmalltalk <krishnamachari.sudhakar(a)gmail.com> wrote: > For the Packages listed in the PDF > > Dependencies are: load these > http://www.squeaksource.com/PharoGoodies/Table-Support-SKR-skrish.5.mcz > http://www.squeaksource.com/PharoGoodies/Toothpick-skrish.7.mcz > > http://www.squeaksource.com/XMLSupport/XML-Parser-AlexandreBergel.93.mcz > http://www.squeaksource.com/XMLRPC/XMLRPC-Client-Core-GermanArduino.20.mcz > > I will check and split out the dependencies to make it easy to load the first examples framework easier by tomorrow > > Then load this.. > > http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Core-skrish.6.mcz > > Though if u load ignoring the errors the initial example will work fine... Without dependencies that is reqd for RPC integration > > Should have the first set that will help you run through the example listed. > > http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Examples-PackageB… > > This should get you the example browser code to directly play with > > http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Examples-skrish.4… > http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Tests-skrish.3.mcz > > For the rest of the examples and tests.. > > Sudhakar krishnamachari > > Extn 91-40403012 > Cell 9902104814 > > > > On Feb 4, 2012, at 7:27 PM, "Lorenzo Schiavina" <lorenzo(a)edor.it> wrote: > >> Hi Krish, >> >> I tryed to install http://www.squeaksource.com/PharoGoodies/ into Pharo 3.0, but I got several errors. >> Can you give me some hints for testing the package with the PDF you sent? >> Many thanks >> >> Ciao >> >> Lorenzo >> ----- Original Message ----- >> From: S Krish >> To: pharo-project(a)lists.gforge.inria.fr ; pharo-users(a)lists.gforge.inria.fr >> Sent: Saturday, February 04, 2012 11:31 AM >> Subject: Re: [Pharo-project] Pharo Morphic View Application Framework >> >> The PDF documentation of the framework. Obliged for review/ read and comment and try out the first release.. >> >> >> Ben, >> >> I have done a first read of the Spec and I will get my head around how this should be converge.. Will work on that. >> >> Though I must note that the spec framework I have laid out is simplistic, flexible and uses the current framework of classes/ morphs without the ValueModel wrapper. Perhaps there is a common ground there, but I would like to emphasize on flexibility of spec and explicit construction to mix and built out has been central to the thought process. >> >> On Tue, Jan 31, 2012 at 10:28 AM, S Krish <krishnamachari.sudhakar(a)gmail.com> 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... >> >>

Feb. 4, 2012

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

by Krishsmalltalk

For the Packages listed in the PDF Dependencies are: load these http://www.squeaksource.com/PharoGoodies/Table-Support-SKR-skrish.5.mcz http://www.squeaksource.com/PharoGoodies/Toothpick-skrish.7.mcz http://www.squeaksource.com/XMLSupport/XML-Parser-AlexandreBergel.93.mcz http://www.squeaksource.com/XMLRPC/XMLRPC-Client-Core-GermanArduino.20.mcz I will check and split out the dependencies to make it easy to load the first examples framework easier by tomorrow Then load this.. http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Core-skrish.6.mcz Though if u load ignoring the errors the initial example will work fine... Without dependencies that is reqd for RPC integration Should have the first set that will help you run through the example listed. http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Examples-PackageB… This should get you the example browser code to directly play with http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Examples-skrish.4… http://www.squeaksource.com/PharoGoodies/PharoMorphicView-Tests-skrish.3.mcz For the rest of the examples and tests.. Sudhakar krishnamachari Extn 91-40403012 Cell 9902104814 On Feb 4, 2012, at 7:27 PM, "Lorenzo Schiavina" <lorenzo(a)edor.it> wrote: > Hi Krish, > > I tryed to install http://www.squeaksource.com/PharoGoodies/ into Pharo 3.0, but I got several errors. > Can you give me some hints for testing the package with the PDF you sent? > Many thanks > > Ciao > > Lorenzo > ----- Original Message ----- > From: S Krish > To: pharo-project(a)lists.gforge.inria.fr ; pharo-users(a)lists.gforge.inria.fr > Sent: Saturday, February 04, 2012 11:31 AM > Subject: Re: [Pharo-project] Pharo Morphic View Application Framework > > The PDF documentation of the framework. Obliged for review/ read and comment and try out the first release.. > > > Ben, > > I have done a first read of the Spec and I will get my head around how this should be converge.. Will work on that. > > Though I must note that the spec framework I have laid out is simplistic, flexible and uses the current framework of classes/ morphs without the ValueModel wrapper. Perhaps there is a common ground there, but I would like to emphasize on flexibility of spec and explicit construction to mix and built out has been central to the thought process. > > On Tue, Jan 31, 2012 at 10:28 AM, S Krish <krishnamachari.sudhakar(a)gmail.com> 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... > >

Feb. 4, 2012

Re: [Pharo-project] About linkedlist

by Frank Shearar

On 3 February 2012 20:40, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>> >>> I wasn't sure what double-ended versus single-ended meant, and found some >>> answer at the obvious place [1] >>> which mentions Ada.Containers.Vectors is a dynamic array implementation >>> which seems consistent with C++ [2]. >>> While looking around I happened to bump into [3] which was too much for me >>> but may be of interest to anyone playing with data structres. Â Skimming this >>> shows it discussing efficiency of data structures in functional languages >>> together with lazy variants of imperative language data structures. Â Would >>> such apply to Smalltalk or is the object-oriented style of Smalltalk >>> considered imperative rather than functional? >> >> The standard tool set - OrderedCollection, Array, etc., are not >> functional at all - (myArray at: 1 put: 2) mutates myArray, - so I'd >> put them firmly on the "imperative" side of the fence. >> >> There's nothing stopping one from writing functional data structures - >> Levente Uzonyi's written some persistent data structures, as have I. >> ("Persistent" means you get new versions of a data structure; if you >> hang onto those old versions you can roll back your changes.) > > Can you explain a bit more Persistent? Sure! A persistent data structure is an _apparently_ immutable data structure: editing the structure returns you a _new_ structure. If you can modify only the latest version of the structure, it's _partially_persistent_; if you can edit any version it is _fully_persistent_. Of course "edit" here means "get a new collection representing the edit" For example, if you load the PersistentUnionFind package (no external dependencies) and print out this: | p p1 p2 p3 | p := PersistentCollection initially: #(1 2 3). p1 := p at: 1 put: 4. p2 := p1 at: 2 put: 5. p3 := p at: 3 put: 0. {p. p1. p2. p3.} collect: #asArray you get, with inline comments added: #("p:" #(1 2 3) "p1:" #(4 2 3) "p2:" #(4 5 3) "p3:" #(1 2 0)) So you can see the different versions of the original array: p1 is p plus one replacement; p2 is p plus two replacements (or equivalently p1 plus one replacement). You still get efficient access to the latest version, and the old versions describe themselves as a stack of undo operations - "I'm like the latest version, but with these changes". So if you just print out p1, you'll see: p1 printString. 'Ref(Diff(1, 4, Ref(Diff(3, 3, Ref(Arr(#(1 2 0)))))))' The series of Diffs tell you how to get from the latest version - p3 - to the version of p1: "take p3 ( #(1 2 0) ), at index 3 put a 3, and at index 1 put a 1". A Ref is a delegate: it allows your reference to something to stay the same even though the thing referenced changes. Internally, as you access the latest version of the Collection the structure rewrites itself: if it's pointing to a Diff it "reroots" itself. (This does have the issue that if you hang onto two versions of the collection and access each version alternately, the PersistentCollection will waste a lot of time constantly rerooting itself.) You can see then that keeping a reference to an old version allows you to undo arbitrary changes to the collection. PersistentUnionFind _should_ load cleanly into Pharo: if it doesn't, let me know and I'll fix it so it does. frank > Tx > > >> http://www.squeaksource.com/Nutcracker/ is my own play area for these >> sorts of structures - PersistentUnionFind looks like a functional data >> structure while internally massively using side effects. >> http://www.lshift.net/blog/2011/12/31/translating-a-persistent-union-find-f… >> has references to the original papers I used for my translation. >> >> Okasaki's book is really good reading, if a bit advanced. It also has >> a bunch of stuff beyond just showing functional data structures. (Note >> that the red-black tree implementation is _incomplete_ - he leaves >> deleting nodes as an exercise for the reader. (See >> http://matt.might.net/articles/red-black-delete/)) >> >> frank >> >>> [1] http://en.wikipedia.org/wiki/Double-ended_queue >>> [2] http://en.wikipedia.org/wiki/Sequence_container_%28C%2B%2B%29 >>> [3] http://www.cs.cmu.edu/~rwh/theses/okasaki.pdf >>> >> > >

Feb. 4, 2012

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

by Lorenzo Schiavina

Hi Krish, I tryed to install http://www.squeaksource.com/PharoGoodies/ into Pharo 3.0, but I got several errors. Can you give me some hints for testing the package with the PDF you sent? Many thanks Ciao Lorenzo ----- Original Message ----- From: S Krish To: pharo-project(a)lists.gforge.inria.fr ; pharo-users(a)lists.gforge.inria.fr Sent: Saturday, February 04, 2012 11:31 AM Subject: Re: [Pharo-project] Pharo Morphic View Application Framework The PDF documentation of the framework. Obliged for review/ read and comment and try out the first release.. Ben, I have done a first read of the Spec and I will get my head around how this should be converge.. Will work on that. Though I must note that the spec framework I have laid out is simplistic, flexible and uses the current framework of classes/ morphs without the ValueModel wrapper. Perhaps there is a common ground there, but I would like to emphasize on flexibility of spec and explicit construction to mix and built out has been central to the thought process. On Tue, Jan 31, 2012 at 10:28 AM, S Krish <krishnamachari.sudhakar(a)gmail.com> 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...

Feb. 4, 2012

Re: [Pharo-project] About linkedlist

by Henrik Johansen

On Feb 3, 2012, at 10:54 PM, Igor Stasenko wrote: > On 3 February 2012 21:42, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> lukas may be you should send that to the vm mailing-list. >> If you need we can ask igor :) (even if he is busy right now). >> > implementing it wont be a big deal. > > i just trying to understand, what is "destructive" vs > "non-destructive" behavior in > replaceFrom:to:with:startingAt: > receiver replaceFrom: 3 to: 5 with: receiver startingAt: 2. Destructive: slots 3-5 all contains originals value from slot 2. Non-Destructive: slots 3-5 contains originals values from slots 2-4. > is it right in my understanding that you want to always meet a > following criteria: > > receiver replaceFrom: a to: b with: replacement startingAt: c. > > a to: b do: [:i | > self assert: (receiver at: i) == (replacement at: c + i - 1) ] > > ? (irrespectible, of course if receiver == replacement or not ) Yes. Basically the same thing you ensure in C by using memmove instead of memcpy. Cheers. Henry

Feb. 4, 2012

Re: [Pharo-project] Starting the sprint @ lille :)

by StÃ©phane Ducasse

I really hope too :). I cross my fingers. Stef > Cool! I'll hope I'll be joining you for the next one :) > > Cheers, > Nico > > On Sat, 2012-02-04 at 11:44 +0100, StÃ©phane Ducasse wrote: >> > > >

Feb. 4, 2012

[Pharo-project] [update 1.4] #14303

by StÃ©phane Ducasse

14303 ----- - Issue 5243: Fix text morph margins. PartOne. Thanks Benjamin van Ryseghem. http://code.google.com/p/pharo/issues/detail?id=5243 - Issue 5241: MC Commit Dialog Improvements. Thanks Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=5241 - Issue 5242: Don t open Debugger when cancel editing block. Thanks Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=5242 Stef

Feb. 4, 2012