- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [GT] seeing morph **And** textpane

by Tudor Girba

Indeed, this is something I would like since quite a while. Of course, we could add the evaluator at the bottom of everything (I tried that), but this will take away from the interaction and make up for an ugly UI. What I would want is a kind of a pane that appears/disappears on demand. We still need to create that support. Cheers, Doru On Sun, Oct 5, 2014 at 2:40 PM, stepharo <stepharo(a)free.fr> wrote: > Hi andrei/doru > > > When I inspect a morph I only see it, while when I look at state I see the > variables and the textpane to evaluate expression. > I think that the expression is really important in the inspector and we > should see it all the time. > > Stef > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 5, 2014

Re: [Pharo-dev] GT first impressions

by Tudor Girba

Ok :) Doru On Sun, Oct 5, 2014 at 2:45 PM, kmo <voxkmp(a)gmail.com> wrote: > Doru - > > Don't take me too seriously. There was no offence. > > > > -- > View this message in context: > http://forum.world.st/GT-first-impressions-tp4782636p4782721.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 5, 2014

Re: [Pharo-dev] GT first impressions

by kmo

Doru - Don't take me too seriously. There was no offence. -- View this message in context: http://forum.world.st/GT-first-impressions-tp4782636p4782721.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 5, 2014

[GT] seeing morph **And** textpane

by stepharo

Hi andrei/doru When I inspect a morph I only see it, while when I look at state I see the variables and the textpane to evaluate expression. I think that the expression is really important in the inspector and we should see it all the time. Stef

Oct. 5, 2014

structuring widget examples

by stepharo

Hi guys I started to systematically defined widget example using the pragram <exampleWidget> rowPrototype "Answer a prototypical row" "self rowPrototype openInHand" <exampleWidget> | sampleMorphs aRow | sampleMorphs := (1 to: (2 + 3 atRandom)) collect: [:integer | EllipseMorph new extent: ((60 + (20 atRandom)) @ (80 + ((20 atRandom)))); color: Color random; setNameTo: ('egg', integer asString); yourself]. aRow := self inARow: sampleMorphs. aRow setNameTo: 'Row'. aRow enableDragNDrop. aRow cellInset: 6. aRow layoutInset: 8. aRow setBalloonText: 'Things dropped into here will automatically be organized into a row. Once you have added your own items here, you will want to remove the sample colored eggs that this started with, and you will want to change this balloon help message to one of your own!'. aRow color: Color veryVeryLightGray. ^ aRow This means that GTool will get instances for free to play with and the finder get really handy to browse widgets. If you want to join the effort you are welcome. Stef

Oct. 5, 2014

Re: [Pharo-dev] GT first impressions

by Tudor Girba

Hi, My remark was not meant to be derogative. If it came out like this, I apologize. I simply stated what my assumption was. You prove to refute my assumption (at least for your specific case). Cheers, Doru On Sun, Oct 5, 2014 at 1:35 PM, kmo <voxkmp(a)gmail.com> wrote: > I don't even use shortcuts for copy and paste. I can't be much of a > programmer. > > > > -- > View this message in context: > http://forum.world.st/GT-first-impressions-tp4782636p4782710.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 5, 2014

Re: [Pharo-dev] "Browser" on a single class

by Yuriy Tymchuk

> On 05 Oct 2014, at 11:56, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > lazy Yury > Iâm just not so UI hacker as you are :). Thanks! > > browser := GLMTabulator new > row: [ :row | > row > column: #protocols; > column: #methods ]; > row: #code; > yourself. > > browser transmit > to: #protocols; > andShow: [ :a| > a list > allowDropOnItem: [:draggedObject :targetItem :list | true ]; > dropOnItem: [:draggedObject :targetItem :list | > browser entity organization > classify: draggedObject > under: targetItem name. > list update. > true ]; > display: [ :class | class organization protocols ]; format: #name ]. > browser transmit > from: #protocols; > to: #methods; > andShow: [ :a| > a list > allowItemDrag: [:item :list | true ]; > display: [ :protocol | protocol methods ] ]. > browser transmit > from: #methods; > to: #code; > andShow: [ :a | > a smalltalkCode > smalltalkClass: [ browser entity ]; > display: [ :method | (browser entity>>method) sourceCode ] ]. > > browser openOn: Morph > >> On 05 Oct 2014, at 10:08, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >> >> Yes, but as Iâve mentioned earlier, Iâm interested in drag-n-drop recategorization. I donât know if itâs doable with glamour. >> >> Uko >> >>> On 04 Oct 2014, at 15:58, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>> >>> and this is same with glamour: >>> >>> browser := GLMTabulator new >>> row: [ :row | >>> row >>> column: #protocols; >>> column: #methods ]; >>> row: #code; >>> yourself. >>> >>> browser transmit >>> to: #protocols; >>> andShow: [ :a| a list display: [ :class | class organization protocols ]; format: #name ]. >>> browser transmit >>> from: #protocols; >>> to: #methods; >>> andShow: [ :a| a list display: [ :protocol | protocol methods ] ]. >>> browser transmit >>> from: #methods; >>> to: #code; >>> andShow: [ :a | >>> a smalltalkCode >>> smalltalkClass: [ browser entity ]; >>> display: [ :method | (browser entity>>method) sourceCode ] ]. >>> >>> browser openOn: Morph. >>> >>> Of course spec is capable of doing that. >>> But glamour is designed with transitions and scripting in mind (thinking specially on browsers), while spec is designed for components and composition. >>> >>> Esteban >>> >>>> On 04 Oct 2014, at 15:35, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >>>> >>>> >>>> 2014-10-03 13:26 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >>>> >>>>> On 03 Oct 2014, at 13:14, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >>>>> >>>>> >>>>> Am 03.10.2014 12:34 schrieb "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >>>>> > >>>>> > Hi. >>>>> > >>>>> > I want to make something like a browser on a single class. I.e. just use 2 last lists out if 4 in standard browser. >>>>> > >>>>> > Is there already something like that? If not, should I use existing widgets, or implement my own using spec? >>>>> > >>>>> > Cheers! >>>>> > Uko >>>>> > >>>>> > Sent from my iPhone >>>>> >>>>> I think that is pretty easy with some spec models. >>>>> Maybe there is already an example >>>>> >>>> yes, but a few models means a few classes :) >>>> in a single class, it will e a lot easier glamour (which btw, is specially designed for that: to make browsers). >>>> >>>> You can work with ready made models like ListModel/TextModel and just need one class for sticking them >>>> together. Here some code, evaluateable from workspace, that shows how we >>>> can build a "simple browser" with spec models: >>>> This is just the simple skeleton, for more details it would be a bit confusing doing all this >>>> in one workspace "script" :) >>>> >>>> class:=Morph. >>>> method:=class>>#openInWorld. >>>> >>>> composed:= DynamicComposableModel new. >>>> composed instantiateModels: #(code TextModel protocols ListModel methods ListModel). >>>> composed code text:method sourceCode. >>>> composed protocols items: class protocols. >>>> composed methods items: class selectors. >>>> composed code aboutToStyle:true. >>>> composed code behavior:class. >>>> composed title: class asString. >>>> composed code acceptBlock:[:text | >>>> class compile:text notifying:nil. >>>> ]. >>>> composed protocols whenSelectedItemChanged:[:item | >>>> composed methods items:( class selectorsInProtocol: item) >>>> ]. >>>> composed methods whenSelectedItemChanged:[:item | >>>> item ifNotNil:[ >>>> method:=class methodDict at:item. >>>> composed code text:method sourceCode] >>>> ]. >>>> composed openWithSpecLayout:( >>>> SpecLayout composed >>>> newColumn:[:c | c >>>> newRow:[:r | r >>>> add: #protocols; >>>> add: #methods >>>> ]; >>>> add: #code]; >>>> yourself). >>>> >>>> >>>> Esteban >>>>> Hilaire asked for a simple Method editor and >>>>> i wrote a simple example build with DynamicComposableModel, search the Mailingliste. >>>>> >>> >> >

Oct. 5, 2014

Re: [Pharo-dev] "Browser" on a single class

by Esteban Lorenzano

> On 05 Oct 2014, at 13:21, Nicolai Hess <nicolaihess(a)web.de> wrote: > > Yes, Glamour is cool. > > But two issues (can you solve them? :) ) > 1. the source list is not updated, the dragged method is still visible in the > old protocol until you change the selected protocol item > 2. (critical) the image hangs if you drop the methods list item in the methods list. thatâs an issue for Doru ;) > > > > > 2014-10-05 11:56 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > lazy Yury > > > browser := GLMTabulator new > row: [ :row | > row > column: #protocols; > column: #methods ]; > row: #code; > yourself. > > browser transmit > to: #protocols; > andShow: [ :a| > a list > allowDropOnItem: [:draggedObject :targetItem :list | true ]; > dropOnItem: [:draggedObject :targetItem :list | > browser entity organization > classify: draggedObject > under: targetItem name. > list update. > true ]; > display: [ :class | class organization protocols ]; format: #name ]. > browser transmit > from: #protocols; > to: #methods; > andShow: [ :a| > a list > allowItemDrag: [:item :list | true ]; > display: [ :protocol | protocol methods ] ]. > browser transmit > from: #methods; > to: #code; > andShow: [ :a | > a smalltalkCode > smalltalkClass: [ browser entity ]; > display: [ :method | (browser entity>>method) sourceCode ] ]. > > browser openOn: Morph > >> On 05 Oct 2014, at 10:08, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >> >> Yes, but as Iâve mentioned earlier, Iâm interested in drag-n-drop recategorization. I donât know if itâs doable with glamour. >> >> Uko >> >>> On 04 Oct 2014, at 15:58, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>> >>> and this is same with glamour: >>> >>> browser := GLMTabulator new >>> row: [ :row | >>> row >>> column: #protocols; >>> column: #methods ]; >>> row: #code; >>> yourself. >>> >>> browser transmit >>> to: #protocols; >>> andShow: [ :a| a list display: [ :class | class organization protocols ]; format: #name ]. >>> browser transmit >>> from: #protocols; >>> to: #methods; >>> andShow: [ :a| a list display: [ :protocol | protocol methods ] ]. >>> browser transmit >>> from: #methods; >>> to: #code; >>> andShow: [ :a | >>> a smalltalkCode >>> smalltalkClass: [ browser entity ]; >>> display: [ :method | (browser entity>>method) sourceCode ] ]. >>> >>> browser openOn: Morph. >>> >>> Of course spec is capable of doing that. >>> But glamour is designed with transitions and scripting in mind (thinking specially on browsers), while spec is designed for components and composition. >>> >>> Esteban >>> >>>> On 04 Oct 2014, at 15:35, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >>>> >>>> >>>> 2014-10-03 13:26 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >>>> >>>>> On 03 Oct 2014, at 13:14, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >>>>> >>>>> >>>>> Am 03.10.2014 12:34 schrieb "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >>>>> > >>>>> > Hi. >>>>> > >>>>> > I want to make something like a browser on a single class. I.e. just use 2 last lists out if 4 in standard browser. >>>>> > >>>>> > Is there already something like that? If not, should I use existing widgets, or implement my own using spec? >>>>> > >>>>> > Cheers! >>>>> > Uko >>>>> > >>>>> > Sent from my iPhone >>>>> >>>>> I think that is pretty easy with some spec models. >>>>> Maybe there is already an example >>>>> >>>> yes, but a few models means a few classes :) >>>> in a single class, it will e a lot easier glamour (which btw, is specially designed for that: to make browsers). >>>> >>>> You can work with ready made models like ListModel/TextModel and just need one class for sticking them >>>> together. Here some code, evaluateable from workspace, that shows how we >>>> can build a "simple browser" with spec models: >>>> This is just the simple skeleton, for more details it would be a bit confusing doing all this >>>> in one workspace "script" :) >>>> >>>> class:=Morph. >>>> method:=class>>#openInWorld. >>>> >>>> composed:= DynamicComposableModel new. >>>> composed instantiateModels: #(code TextModel protocols ListModel methods ListModel). >>>> composed code text:method sourceCode. >>>> composed protocols items: class protocols. >>>> composed methods items: class selectors. >>>> composed code aboutToStyle:true. >>>> composed code behavior:class. >>>> composed title: class asString. >>>> composed code acceptBlock:[:text | >>>> class compile:text notifying:nil. >>>> ]. >>>> composed protocols whenSelectedItemChanged:[:item | >>>> composed methods items:( class selectorsInProtocol: item) >>>> ]. >>>> composed methods whenSelectedItemChanged:[:item | >>>> item ifNotNil:[ >>>> method:=class methodDict at:item. >>>> composed code text:method sourceCode] >>>> ]. >>>> composed openWithSpecLayout:( >>>> SpecLayout composed >>>> newColumn:[:c | c >>>> newRow:[:r | r >>>> add: #protocols; >>>> add: #methods >>>> ]; >>>> add: #code]; >>>> yourself). >>>> >>>> >>>> Esteban >>>>> Hilaire asked for a simple Method editor and >>>>> i wrote a simple example build with DynamicComposableModel, search the Mailingliste. >>>>> >>> >> > >

Oct. 5, 2014

Re: [Pharo-dev] GT first impressions

by kmo

I don't even use shortcuts for copy and paste. I can't be much of a programmer. -- View this message in context: http://forum.world.st/GT-first-impressions-tp4782636p4782710.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 5, 2014

Re: [Pharo-dev] "Browser" on a single class

by Nicolai Hess

Yes, Glamour is cool. But two issues (can you solve them? :) ) 1. the source list is not updated, the dragged method is still visible in the old protocol until you change the selected protocol item 2. (critical) the image hangs if you drop the methods list item in the methods list. 2014-10-05 11:56 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > lazy Yury > > > browser := GLMTabulator new > row: [ :row | > row > column: #protocols; > column: #methods ]; > row: #code; > yourself. > browser transmit > to: #protocols; > andShow: [ :a| > a list > allowDropOnItem: [:draggedObject :targetItem :list | true ]; > dropOnItem: [:draggedObject :targetItem :list | > browser entity organization > classify: draggedObject > under: targetItem name. > list update. > true ]; > display: [ :class | class organization protocols ]; format: #name ]. > browser transmit > from: #protocols; > to: #methods; > andShow: [ :a| > a list > allowItemDrag: [:item :list | true ]; > display: [ :protocol | protocol methods ] ]. > browser transmit > from: #methods; > to: #code; > andShow: [ :a | > a smalltalkCode > smalltalkClass: [ browser entity ]; > display: [ :method | (browser entity>>method) sourceCode ] ]. > > browser openOn: Morph > > On 05 Oct 2014, at 10:08, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Yes, but as Iâve mentioned earlier, Iâm interested in drag-n-drop > recategorization. I donât know if itâs doable with glamour. > > Uko > > On 04 Oct 2014, at 15:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > and this is same with glamour: > > browser := GLMTabulator new > row: [ :row | > row > column: #protocols; > column: #methods ]; > row: #code; > yourself. > browser transmit > to: #protocols; > andShow: [ :a| a list display: [ :class | class organization protocols ]; > format: #name ]. > browser transmit > from: #protocols; > to: #methods; > andShow: [ :a| a list display: [ :protocol | protocol methods ] ]. > browser transmit > from: #methods; > to: #code; > andShow: [ :a | > a smalltalkCode > smalltalkClass: [ browser entity ]; > display: [ :method | (browser entity>>method) sourceCode ] ]. > > browser openOn: Morph. > > Of course spec is capable of doing that. > But glamour is designed with transitions and scripting in mind (thinking > specially on browsers), while spec is designed for components and > composition. > > Esteban > > On 04 Oct 2014, at 15:35, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2014-10-03 13:26 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 03 Oct 2014, at 13:14, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> >> Am 03.10.2014 12:34 schrieb "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com>: >> > >> > Hi. >> > >> > I want to make something like a browser on a single class. I.e. just >> use 2 last lists out if 4 in standard browser. >> > >> > Is there already something like that? If not, should I use existing >> widgets, or implement my own using spec? >> > >> > Cheers! >> > Uko >> > >> > Sent from my iPhone >> >> I think that is pretty easy with some spec models. >> Maybe there is already an example >> >> yes, but a few models means a few classes :) >> in a single class, it will e a lot easier glamour (which btw, is >> specially designed for that: to make browsers). >> > > You can work with ready made models like ListModel/TextModel and just need > one class for sticking them > together. Here some code, evaluateable from workspace, that shows how we > can build a "simple browser" with spec models: > This is just the simple skeleton, for more details it would be a bit confusing > doing all this > in one workspace "script" :) > > class:=Morph. > method:=class>>#openInWorld. > > composed:= DynamicComposableModel new. > composed instantiateModels: #(code TextModel protocols ListModel methods > ListModel). > composed code text:method sourceCode. > composed protocols items: class protocols. > composed methods items: class selectors. > composed code aboutToStyle:true. > composed code behavior:class. > composed title: class asString. > composed code acceptBlock:[:text | > class compile:text notifying:nil. > ]. > composed protocols whenSelectedItemChanged:[:item | > composed methods items:( class selectorsInProtocol: item) > ]. > composed methods whenSelectedItemChanged:[:item | > item ifNotNil:[ > method:=class methodDict at:item. > composed code text:method sourceCode] > ]. > composed openWithSpecLayout:( > SpecLayout composed > newColumn:[:c | c > newRow:[:r | r > add: #protocols; > add: #methods > ]; > add: #code]; > yourself). > > >> >> Esteban >> >> Hilaire asked for a simple Method editor and >> i wrote a simple example build with DynamicComposableModel, search the >> Mailingliste. >> >> > > >

Oct. 5, 2014