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

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

by Benjamin

If you have around the pdf you are talking about on your website, I will be glad to read it. Thanks in advance ;) Ben 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

Re: [Pharo-users] focus setting

by Werner Kassens

i noticed that although i dont get a keystroke event for shift-tab, i do get keyUp and keyDown events. obviously they all come from the vm and the new vm in Pharo 1.3 probably cant keep up with my very old linux version. otoh i cant open the 1.3 image with the vm from Pharo 1.2 (This interpreter (vers. 6502) cannot read image file (vers. 6505) ). i guess, one day or another i have to update to a newer linux version. for the moment i just changed the shift-tab keyDown event to a keystroke event, since i need the keystroke event but not the keyDown one. or is there an older vm more similar to the one in Pharo 1.2, that can open the 1.3 image? werner

Jan. 31, 2012

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

by Denis Kudriashov

2012/1/31 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > Denis > we do not want to rely on saving a Morph to a method (serialization). > Now it does not mean that we cannot use the prototype idea. > We could have a spec that creates an object used as a prototype for > building UI. > > Saving a prototypes and building interface are orthogonal. > > Stef > > Yes, I understand this

Jan. 31, 2012

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

by StÃ©phane Ducasse

On Jan 31, 2012, at 3:04 PM, Denis Kudriashov wrote: > 2012/1/31 S Krish <krishnamachari.sudhakar(a)gmail.com> > Sure I will review this pdf.. and come back on this..how well should > integrate the specs part.. > > The framework though is based on the spec and extensibly on direct > composition and does a little more towards building a scalable/ > flexible framework that incorporates in one simpler hierarchy all that > goes into a standard large application creation.. > > How is the Presenty work supposed to work along with this..? > > > For Presenty Specs can be used for code presentation of concrete morphs (view prototypes). > If Specs can save arbitraty morph to method I will use it. > And Presenty will got monticello support. Denis we do not want to rely on saving a Morph to a method (serialization). Now it does not mean that we cannot use the prototype idea. We could have a spec that creates an object used as a prototype for building UI. Saving a prototypes and building interface are orthogonal. Stef

Jan. 31, 2012

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

by StÃ©phane Ducasse

On Jan 31, 2012, at 1:23 PM, S Krish wrote: > Sure I will review this pdf.. and come back on this..how well should > integrate the specs part.. but Spec is a spec based UI builder. > The framework though is based on the spec and extensibly on direct > composition and does a little more towards building a scalable/ > flexible framework that incorporates in one simpler hierarchy all that > goes into a standard large application creation.. Ok but did you ***read*** what benjamin said: he iterated on it and now it is a good basis to build support for a lot of widgets. Have a look at his document. It would be good to avoid to have several frameworks doing the same. For example I would like to have more tests. The prototype part is open. We did not think much about it. > > How is the Presenty work supposed to work along with this..? > > > On 1/31/12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> did you see what benjamin is doing with Spec. >> Because you should join effort >> >> >

Jan. 31, 2012

Re: [Pharo-users] focus setting

by Werner Kassens

> bug in your copy of the image.. possibly.. i just downloaded another Pharo 1.3, used one of the examples in the unchanged image and got the same result. i then made a descendant of StandardWindow with handlesKeyboard: evt ^true and: keyStroke: anEvent anEvent wasHandled: true. self inform: anEvent asString . while this reacts eg on tab or shift-up, it does not react on shift-tab, somehow strange. and it shoudnt be the OS, since Pharo 1.2 gets the shift-tab. werner

Jan. 31, 2012

Re: [Pharo-users] focus setting

by S Krish

bug in your copy of the image.. possibly.. shift-tab seems to work fine for me over most variants I have worked.. just hacked to also include tab windows through ctrl+tab.. which is actually missing.. capability.. when you want to cycle through windows within pharo Morph>>tabKey: event "Check for tab key activity and change focus as appropriate." event controlKeyPressed ifFalse: [*event keyCharacter = Character tab* * ifTrue: [event commandKeyPressed* * ifTrue: [World tabOpenWindows: event].* *event shiftPressed* ifTrue: [self navigateFocusBackward] ifFalse: [self navigateFocusForward]. ^ true]]. ^ false PasteUpMorph>> keyStroke: anEvent ... anEvent keyCharacter == Character tab ifTrue: [self tabAmongFields ifTrue: [ anEvent commandKeyPressed ifTrue: [^ self tabOpenWindows: anEvent]. ... tabOpenWindows: aKeyboardEvent | currentFocus index | currentFocus := aKeyboardEvent hand keyboardFocus. SystemWindow noteTopWindowIn: self. SystemWindow topWindow sendToBack. " could actually raise the next window to top rather" On Tue, Jan 31, 2012 at 6:53 PM, Werner Kassens <wkassens(a)libello.com>wrote: > Hi, > in Pharo 1.2 i could tab through the submorphs using tab and shift-tab. in > Pharo 1.3 shift-tab seems not to work anymore. what can i use to move > backwards through the morphs to set the focus? > werner > >

Jan. 31, 2012

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

by Denis Kudriashov

2012/1/31 S Krish <krishnamachari.sudhakar(a)gmail.com> > Sure I will review this pdf.. and come back on this..how well should > integrate the specs part.. > > The framework though is based on the spec and extensibly on direct > composition and does a little more towards building a scalable/ > flexible framework that incorporates in one simpler hierarchy all that > goes into a standard large application creation.. > > How is the Presenty work supposed to work along with this..? > > For Presenty Specs can be used for code presentation of concrete morphs (view prototypes). If Specs can save arbitraty morph to method I will use it. And Presenty will got monticello support.

Jan. 31, 2012

focus setting

by Werner Kassens

Hi, in Pharo 1.2 i could tab through the submorphs using tab and shift-tab. in Pharo 1.3 shift-tab seems not to work anymore. what can i use to move backwards through the morphs to set the focus? werner

Jan. 31, 2012

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

by S Krish

Sure I will review this pdf.. and come back on this..how well should integrate the specs part.. The framework though is based on the spec and extensibly on direct composition and does a little more towards building a scalable/ flexible framework that incorporates in one simpler hierarchy all that goes into a standard large application creation.. How is the Presenty work supposed to work along with this..? On 1/31/12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > did you see what benjamin is doing with Spec. > Because you should join effort > >

Jan. 31, 2012