November 2013 - Pharo-users

Re: [Pharo-users] Spec - Text alignment in LabelModel

by ClÃ©ment Bera

I checked it seems that TextAlignment is currently broken. Only other text attributes work. sorry. 2013/11/7 ClÃ©ment Bera <bera.clement(a)gmail.com> > Hey, > > I'm not sure this is the good way to do it, but you can store in your > labelModel a Text instead of a String: > > myComposableModel label text: 'someString' asText. > > Then you can add attribute to the text: > > myComposableModel label text addAttribute: TextColor red. > myComposableModel label text addAttribute: TextAlignment rightFlush. > > Try first with TextColor red, because for TextAlignment rightFlush there > might be other reason it does not work > (i.e. the label model has the width of the text, so modifying the > alignment will not modify anything). > > Best, > > > 2013/11/7 nacho <0800nacho(a)gmail.com> > >> Hi, >> After spending almost two hours digging into Spec I couldn't figure out >> how >> to change the alignment of the text in LabelModel. As I'm building a >> simple >> calculator, the text has to be right-aligned. The default is >> left-alginement >> which makes the calculator display look weird. >> Any help would be much appreciated. >> best regards >> Nacho >> >> >> >> >> >> ----- >> Nacho >> Smalltalker apprentice. >> Buenos Aires, Argentina. >> -- >> View this message in context: >> http://forum.world.st/Spec-Text-alignment-in-LabelModel-tp4719750.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >

Nov. 7, 2013

Re: [Pharo-users] Spec - Nested Layouts

by Benjamin

>From memory: - 11920 (the valueHolder one) - 12054 (TreeNode and TreeColumn) - There is one also about SpecMenu, I do not remember the number Ben On 07 Nov 2013, at 21:10, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Nov 7, 2013, at 6:45 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> About table, I have an example which will be running soon in Pharo (the changes are waiting to be integrated) > > which ones? > Because I was crawling all the ones I could? > > Stef > > >> >> tree := TreeModel new. >> tree openWithSpec. >> >> tree columns: (Array >> with: (TreeColumnModel new displayBlock: [:node | node content first asString ]; headerLabel: 'Name'; yourself) >> with: (TreeColumnModel new displayBlock: [:node | node content second asString ]; headerLabel: 'Last Name'; yourself) >> with: (TreeColumnModel new displayBlock: [:node | node content third asString ]; headerLabel: 'Age'; yourself) >> with: (TreeColumnModel new displayBlock: [:node | node content fourth asString ]; headerLabel: 'Gender'; yourself)). >> >> tree roots: { >> {'Benjamin'.'Van Ryseghem'.'26'.'M'}. >> {'Pamela'.'Anderson'.'Far too much'.'F'} >> } >> >> Will produce >> >> <Screen Shot 2013-11-07 at 18.38.21.png> >> >> Right now, you can get the same by >> - adding MorphTreeAdapter>>#columns: >> columns: columns >> self widgetDo: [ :w | >> w columns: columns. >> w resizerChanged. >> w updateList ] >> >> And then evaluating: >> >> tree := TreeModel new. >> tree openWithSpec. >> >> tree columns: (Array >> with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item first asString asMorph ]; headerButtonLabel: 'Name' font: nil; yourself) >> with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; yourself) >> with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself) >> with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item fourth asString asMorph ]; headerButtonLabel: 'Gender' font: nil; yourself)). >> >> tree roots: { >> {'Benjamin'.'Van Ryseghem'.'26'.'M'}. >> {'Pamela'.'Anderson'.'Far too much'.'F'} >> } >> >> Ben >> >> On 07 Nov 2013, at 15:54, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >>> >>> 2013/11/7 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> >>> Just a general remark: you should try as much as possible to avoid hard coding width/height :) >>> >>> there are some methods on ComposableModel you could use like buttonHeight toolbarHeight etc. that you should use instead :) >>> >>> >>> Ben >>> >>> On 07 Nov 2013, at 13:22, Bahman Movaqar <Bahman(a)BahmanM.com> wrote: >>> >>>> On 11/07/2013 12:45, ClÃ©ment Bera wrote: >>>>> Hey, >>>>> >>>>> I don't know what you want exactly. >>>>> >>>>> You can do: >>>>> >>>>> spec >>>>> <spec> >>>>> ^ SpecLayout composed >>>>> newRow: [:row | >>>>> row >>>>> newColumn: [ :col | >>>>> col >>>>> add: #list width: 135; >>>>> add: #description ] ]; >>>>> yourself >>>>> >>>>> and nest that as many times as you want (but I don't know if this was your question). >>>> >>>> I just tried this one and it works (see the code below) BUT, the code is so hard to read and understand just for 3 rows and 7 widgets! >>>> >>>> <code> >>>> defaultSpec >>>> ^ SpecLayout composed >>>> newColumn: [ :mainColumn | >>>> mainColumn >>>> newRow: [ :nameRow | >>>> nameRow >>>> add: #labelName; >>>> add: #textName ] >>>> height: 25. >>>> mainColumn >>>> newRow: [ :titleRow | >>>> titleRow >>>> add: #labelTitle; >>>> newRow: [ :titleRadioRow | >>>> titleRadioRow >>>> add: #radioMr; >>>> add: #radioMrs; >>>> add: #radioMs ] ] >>>> height: 25. >>>> mainColumn newRow: [ :buttonRow | buttonRow add: #buttonGreet ] height: 25 ]; >>>> yourself >>>> </code> >>>> >>>> Am I doing it right? >>> >>> I guess this is right. But I think you need to generate this layout out of collections, not to write it. >>>> >>>>> >>>>> Another feature is: >>>>> >>>>> debuggerSpec >>>>> <spec: #default> >>>>> ^ SpecLayout composed >>>>> add: #inspector withSpec: #debuggerSpec; >>>>> yourself >>>>> >>>>> #inspector being the instance variable name that holds a subclass of ComposableModel that defines class side #debuggerSpec, which answers a SpecLayout. >>>>> >>>> >>>> Does this mean that for every table cell I have to create a new class? >>> >>> Yeah well I was just pointing out all the choices you had. Depending on what you want to do you could have a class hierarchy similar to this: >>> >>> SpecTable >>> AbstractSpecColumn >>> SpecColumnA >>> SpecColumnB >>> AbstractSpecCell >>> SpecCellA >>> SpecCellB >>> >>> SpecTable having column, column having cells. >>> But this may not be the best choice. >>> >>> Now that you caught my interest, I tried to do a table. I put it in attachment the result. It is a .st file, so drag and drop it in your image, then click file in entire file. Then try to run 'SpecTable new', it opens a table with 3 columns and 5 rows, with no complex layout method. All the code is in SpecTable (Cmd+f,Cmd+c to find a class in nautilus or write the class name in workspace then select it and press Cmd+m), in the method protocol table logic. It's like 6 methods. >>> >>> However: >>> - vertical splitters are not sync. >>> - I don't know how to color the border of each cell to make it beautiful. >>> >>> Of course you need to polish it ... >>> >>> I hope it helped you :) >>> >>>> >>>>> Not sure if this helped. >>>>> >>>>> All of these questions are for your tutorials ? >>>>> >>>>> >>>>> >>>>> >>>>> 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com> >>>>> Hi all, >>>>> >>>>> Is it possible to nest layouts in Spec? For example can I combine >>>>> `SpecColumnLayout` and `SpecRowLayout` together? >>>>> >>>>> >>>>> -- >>>>> Bahman Movaqar (http://BahmanM.com) >>>>> >>>>> ERP Evaluation, Implementation & Deployment Consultant >>>>> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) >>>>> -- >>>>> Bahman Movaqar (http://BahmanM.com) >>>>> >>>>> ERP Evaluation, Implementation & Deployment Consultant >>>>> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) >>> >>> >>> <SpecTable.st> >> >

Nov. 7, 2013

Re: [Pharo-users] Spec - Nested Layouts

by StÃ©phane Ducasse

On Nov 7, 2013, at 6:45 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > About table, I have an example which will be running soon in Pharo (the changes are waiting to be integrated) which ones? Because I was crawling all the ones I could? Stef > > tree := TreeModel new. > tree openWithSpec. > > tree columns: (Array > with: (TreeColumnModel new displayBlock: [:node | node content first asString ]; headerLabel: 'Name'; yourself) > with: (TreeColumnModel new displayBlock: [:node | node content second asString ]; headerLabel: 'Last Name'; yourself) > with: (TreeColumnModel new displayBlock: [:node | node content third asString ]; headerLabel: 'Age'; yourself) > with: (TreeColumnModel new displayBlock: [:node | node content fourth asString ]; headerLabel: 'Gender'; yourself)). > > tree roots: { > {'Benjamin'.'Van Ryseghem'.'26'.'M'}. > {'Pamela'.'Anderson'.'Far too much'.'F'} > } > > Will produce > > <Screen Shot 2013-11-07 at 18.38.21.png> > > Right now, you can get the same by > - adding MorphTreeAdapter>>#columns: > columns: columns > self widgetDo: [ :w | > w columns: columns. > w resizerChanged. > w updateList ] > > And then evaluating: > > tree := TreeModel new. > tree openWithSpec. > > tree columns: (Array > with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item first asString asMorph ]; headerButtonLabel: 'Name' font: nil; yourself) > with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; yourself) > with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself) > with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item fourth asString asMorph ]; headerButtonLabel: 'Gender' font: nil; yourself)). > > tree roots: { > {'Benjamin'.'Van Ryseghem'.'26'.'M'}. > {'Pamela'.'Anderson'.'Far too much'.'F'} > } > > Ben > > On 07 Nov 2013, at 15:54, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > >> >> 2013/11/7 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> >> Just a general remark: you should try as much as possible to avoid hard coding width/height :) >> >> there are some methods on ComposableModel you could use like buttonHeight toolbarHeight etc. that you should use instead :) >> >> >> Ben >> >> On 07 Nov 2013, at 13:22, Bahman Movaqar <Bahman(a)BahmanM.com> wrote: >> >>> On 11/07/2013 12:45, ClÃ©ment Bera wrote: >>>> Hey, >>>> >>>> I don't know what you want exactly. >>>> >>>> You can do: >>>> >>>> spec >>>> <spec> >>>> ^ SpecLayout composed >>>> newRow: [:row | >>>> row >>>> newColumn: [ :col | >>>> col >>>> add: #list width: 135; >>>> add: #description ] ]; >>>> yourself >>>> >>>> and nest that as many times as you want (but I don't know if this was your question). >>> >>> I just tried this one and it works (see the code below) BUT, the code is so hard to read and understand just for 3 rows and 7 widgets! >>> >>> <code> >>> defaultSpec >>> ^ SpecLayout composed >>> newColumn: [ :mainColumn | >>> mainColumn >>> newRow: [ :nameRow | >>> nameRow >>> add: #labelName; >>> add: #textName ] >>> height: 25. >>> mainColumn >>> newRow: [ :titleRow | >>> titleRow >>> add: #labelTitle; >>> newRow: [ :titleRadioRow | >>> titleRadioRow >>> add: #radioMr; >>> add: #radioMrs; >>> add: #radioMs ] ] >>> height: 25. >>> mainColumn newRow: [ :buttonRow | buttonRow add: #buttonGreet ] height: 25 ]; >>> yourself >>> </code> >>> >>> Am I doing it right? >> >> I guess this is right. But I think you need to generate this layout out of collections, not to write it. >>> >>>> >>>> Another feature is: >>>> >>>> debuggerSpec >>>> <spec: #default> >>>> ^ SpecLayout composed >>>> add: #inspector withSpec: #debuggerSpec; >>>> yourself >>>> >>>> #inspector being the instance variable name that holds a subclass of ComposableModel that defines class side #debuggerSpec, which answers a SpecLayout. >>>> >>> >>> Does this mean that for every table cell I have to create a new class? >> >> Yeah well I was just pointing out all the choices you had. Depending on what you want to do you could have a class hierarchy similar to this: >> >> SpecTable >> AbstractSpecColumn >> SpecColumnA >> SpecColumnB >> AbstractSpecCell >> SpecCellA >> SpecCellB >> >> SpecTable having column, column having cells. >> But this may not be the best choice. >> >> Now that you caught my interest, I tried to do a table. I put it in attachment the result. It is a .st file, so drag and drop it in your image, then click file in entire file. Then try to run 'SpecTable new', it opens a table with 3 columns and 5 rows, with no complex layout method. All the code is in SpecTable (Cmd+f,Cmd+c to find a class in nautilus or write the class name in workspace then select it and press Cmd+m), in the method protocol table logic. It's like 6 methods. >> >> However: >> - vertical splitters are not sync. >> - I don't know how to color the border of each cell to make it beautiful. >> >> Of course you need to polish it ... >> >> I hope it helped you :) >> >>> >>>> Not sure if this helped. >>>> >>>> All of these questions are for your tutorials ? >>>> >>>> >>>> >>>> >>>> 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com> >>>> Hi all, >>>> >>>> Is it possible to nest layouts in Spec? For example can I combine >>>> `SpecColumnLayout` and `SpecRowLayout` together? >>>> >>>> >>>> -- >>>> Bahman Movaqar (http://BahmanM.com) >>>> >>>> ERP Evaluation, Implementation & Deployment Consultant >>>> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) >>>> -- >>>> Bahman Movaqar (http://BahmanM.com) >>>> >>>> ERP Evaluation, Implementation & Deployment Consultant >>>> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) >> >> >> <SpecTable.st> >

Nov. 7, 2013

Pharo 3.0.0.dmg for Mac OSX - problem loading on OS 10.9

by Bruce Prior

Joachim said, I tried CTRL-click to open Pharo.app. I still get the above result. I used Damien's "new" Nov 7 dmg: Bruce

Nov. 7, 2013

Re: [Pharo-users] Why won't my Pharo download run?

by PBK Research

Just a little more information. Out of curiosity, I downloaded Pharo 3.0 and tried it, with the same result - message from Windows says 'Pharo.exe has encountered a problem and needs to close'. To complete the set, I downloaded Pharo 1.4 and tried it. This time it failed saying 'CogVM.exe has encoun....'. I presume all versions now use the Cog VM, and it looks as though this machine just won't run it. Is there still a 'traditional' VM I can use instead of Cog? It might not be practical, but it would at least prove that it is a VM problem. Is there any information about Cog giving problems with AMD processors? _____ From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of PBK Research Sent: 07 November 2013 15:07 To: 'Any question about pharo is welcome' Subject: Re: [Pharo-users] Why won't my Pharo download run? OK. I opened a command line prompt, cd to Pharo 2.0 directory (created in today's download), enter 'pharo.exe pharo2.0.image'. Same result - immediate failure. I had previously changed the association of the image file to the newly downloaded pharo.exe. So I think I must be using the VM in today's download. _____ From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Igor Stasenko Sent: 07 November 2013 14:48 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Why won't my Pharo download run? On 7 November 2013 15:31, PBK Research <peter(a)pbkresearch.co.uk> wrote: Thanks. I am using the latest one-click distribution of Pharo, downloaded today from the Pharo website. Presumably that should have the latest VM? yes, but if .image file extension associated with wrong version of VM binary, which you installed previously (as you mentioned), it won't automagically use proper one. unless you run vm from command line e.g.: pharo.exe myimage.image or change the association to use different vm. _____ From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Igor Stasenko Sent: 07 November 2013 13:53 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Why won't my Pharo download run? On 7 November 2013 14:18, PBK Research <peter(a)pbkresearch.co.uk> wrote: Hello! I have a problem with running Pharo 2.0 on one of my machines. I have two machines, both running Windows XP with SP3. On one of them I have a successful load of Pharo (actually it's a distribution of the Moose system, but that is just an application built on Pharo 2.0). This loads successfully when I double click on pharo.exe. On the other machine, the same action produces an immediate message: 'Pharo.exe has encountered a problem and needs to close'. Just in case this was some problem with Moose, I have just downloaded the latest one-click installation of Pharo 2.0 for Windows. This displays exactly the same behaviour - an immediate fail when I try to start it. I have tried to work out what may be different between the two machines. The one which will run Pharo has an Intel Celeron processor, the other an AMD Athlon XP (yes, they are both pretty ancient!), but I can't see why that should make any difference. The one curious thing is that Windows Explorer displays the type of the Pharo2.0.image file as 'Squeak image file'. There is an old version of Squeak installed on that machine; could that have any effect? I am a bit flummoxed by all this. Does anyone have any suggestions about how to diagnose the problem? If you using too old VM , it simply does not supports an image format, which pharo 2.0 uses. But there could be different reasons.. a first step towards to solution is to use VM for pharo, which we maintain and use.. Many thanks Peter Kenny -- Best regards, Igor Stasenko. -- Best regards, Igor Stasenko.

Nov. 7, 2013

Re: [Pharo-users] Spec - Nested Layouts

by Bahman Movaqar

On 11/07/2013 16:14, Benjamin wrote: > Just a general remark: you should try as much as possible to avoid > hard coding width/height :) > > there are some methods on ComposableModel you could use like > buttonHeight toolbarHeight etc. that you should use instead :) Correct. Thanks for the pointer. -- Bahman Movaqar (http://BahmanM.com) ERP Evaluation, Implementation & Deployment Consultant PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)

Nov. 7, 2013

Re: [Pharo-users] [FEEDBACK] Install Pharo on MacOSX

by Ignacio MatÃas Sniechowski

Damien, The new dmg works perfect in my system OS X 10.9. The issue with the sources is fixed. Thanks for this. It's great to have all the images in the same launcher. Nacho. *Lic. Ignacio Sniechowski, MBA* On Thu, Nov 7, 2013 at 11:24 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > > On Tue, Nov 5, 2013 at 6:50 PM, Manfred KrÃ¶hnert < > mkroehnert42(a)googlemail.com> wrote: > >> Just a minor issue with the DMG itself. >> When I opened it on OS X 10.6.8 the lower text was cut off by the window. >> See attached image. >> > > > Would you please try the new dmg? > > > https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/18/art… > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing > enthusiasm." > Winston Churchill >

Nov. 7, 2013

Re: [Pharo-users] Spec - Nested Layouts

by Benjamin

About table, I have an example which will be running soon in Pharo (the changes are waiting to be integrated) tree := TreeModel new. tree openWithSpec. tree columns: (Array with: (TreeColumnModel new displayBlock: [:node | node content first asString ]; headerLabel: 'Name'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content second asString ]; headerLabel: 'Last Name'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content third asString ]; headerLabel: 'Age'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content fourth asString ]; headerLabel: 'Gender'; yourself)). tree roots: { {'Benjamin'.'Van Ryseghem'.'26'.'M'}. {'Pamela'.'Anderson'.'Far too much'.'F'} } Will produce Right now, you can get the same by - adding MorphTreeAdapter>>#columns: columns: columns self widgetDo: [ :w | w columns: columns. w resizerChanged. w updateList ] And then evaluating: tree := TreeModel new. tree openWithSpec. tree columns: (Array with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item first asString asMorph ]; headerButtonLabel: 'Name' font: nil; yourself) with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; yourself) with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself) with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item fourth asString asMorph ]; headerButtonLabel: 'Gender' font: nil; yourself)). tree roots: { {'Benjamin'.'Van Ryseghem'.'26'.'M'}. {'Pamela'.'Anderson'.'Far too much'.'F'} } Ben On 07 Nov 2013, at 15:54, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > 2013/11/7 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> > Just a general remark: you should try as much as possible to avoid hard coding width/height :) > > there are some methods on ComposableModel you could use like buttonHeight toolbarHeight etc. that you should use instead :) > > > Ben > > On 07 Nov 2013, at 13:22, Bahman Movaqar <Bahman(a)BahmanM.com> wrote: > >> On 11/07/2013 12:45, ClÃ©ment Bera wrote: >>> Hey, >>> >>> I don't know what you want exactly. >>> >>> You can do: >>> >>> spec >>> <spec> >>> ^ SpecLayout composed >>> newRow: [:row | >>> row >>> newColumn: [ :col | >>> col >>> add: #list width: 135; >>> add: #description ] ]; >>> yourself >>> >>> and nest that as many times as you want (but I don't know if this was your question). >> >> I just tried this one and it works (see the code below) BUT, the code is so hard to read and understand just for 3 rows and 7 widgets! >> >> <code> >> defaultSpec >> ^ SpecLayout composed >> newColumn: [ :mainColumn | >> mainColumn >> newRow: [ :nameRow | >> nameRow >> add: #labelName; >> add: #textName ] >> height: 25. >> mainColumn >> newRow: [ :titleRow | >> titleRow >> add: #labelTitle; >> newRow: [ :titleRadioRow | >> titleRadioRow >> add: #radioMr; >> add: #radioMrs; >> add: #radioMs ] ] >> height: 25. >> mainColumn newRow: [ :buttonRow | buttonRow add: #buttonGreet ] height: 25 ]; >> yourself >> </code> >> >> Am I doing it right? > > I guess this is right. But I think you need to generate this layout out of collections, not to write it. >> >>> >>> Another feature is: >>> >>> debuggerSpec >>> <spec: #default> >>> ^ SpecLayout composed >>> add: #inspector withSpec: #debuggerSpec; >>> yourself >>> >>> #inspector being the instance variable name that holds a subclass of ComposableModel that defines class side #debuggerSpec, which answers a SpecLayout. >>> >> >> Does this mean that for every table cell I have to create a new class? > > Yeah well I was just pointing out all the choices you had. Depending on what you want to do you could have a class hierarchy similar to this: > > SpecTable > AbstractSpecColumn > SpecColumnA > SpecColumnB > AbstractSpecCell > SpecCellA > SpecCellB > > SpecTable having column, column having cells. > But this may not be the best choice. > > Now that you caught my interest, I tried to do a table. I put it in attachment the result. It is a .st file, so drag and drop it in your image, then click file in entire file. Then try to run 'SpecTable new', it opens a table with 3 columns and 5 rows, with no complex layout method. All the code is in SpecTable (Cmd+f,Cmd+c to find a class in nautilus or write the class name in workspace then select it and press Cmd+m), in the method protocol table logic. It's like 6 methods. > > However: > - vertical splitters are not sync. > - I don't know how to color the border of each cell to make it beautiful. > > Of course you need to polish it ... > > I hope it helped you :) > >> >>> Not sure if this helped. >>> >>> All of these questions are for your tutorials ? >>> >>> >>> >>> >>> 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com> >>> Hi all, >>> >>> Is it possible to nest layouts in Spec? For example can I combine >>> `SpecColumnLayout` and `SpecRowLayout` together? >>> >>> >>> -- >>> Bahman Movaqar (http://BahmanM.com) >>> >>> ERP Evaluation, Implementation & Deployment Consultant >>> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) >>> -- >>> Bahman Movaqar (http://BahmanM.com) >>> >>> ERP Evaluation, Implementation & Deployment Consultant >>> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) > > > <SpecTable.st>

Nov. 7, 2013

Re: [Pharo-users] Spec - Tutorial Series

by Ignacio MatÃas Sniechowski

Very nice tutorial! Keep on posting! best regards nacho *Lic. Ignacio Sniechowski, MBA* On Thu, Nov 7, 2013 at 2:36 PM, Bahman Movaqar <Bahman(a)bahmanm.com> wrote: > On 11/07/2013 09:13, Bahman Movaqar wrote: > > Hi all, > > > > I'm writing a series of tutorials for Spec for beginners like myself and > > I'd really appreciate any input on the material. > > The first episode is done: > http://www.bahmanm.com/blogs/spec-part-1-basics > > > > Thank you folks for your encouraging! To be honest, that's one of the > things that caught my attention to Pharo at first. The positive and > helpful community. Glad that I could contribute a tad bit. > > @Ben: > My website is running Plone (http://plone.org) using my own Plone > hosting service (http://www.bahmanm.com/services/plone-hosting) Let me > know if you're interested :-) Also the code highlighting is done by > Good old Emacs :-) > RE setupTitleRadioButtons: That's correct. The `:` should be left out > of highlighting. > RE userTitle: Cool! It takes time for me to change my Swing'ish way of > looking at things. I'll add that. > RE package: Subtle point. I'll change the package name. > > -- > Bahman Movaqar (http://BahmanM.com) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) > > >

Nov. 7, 2013

Re: [Pharo-users] Spec - Tutorial Series

by Bahman Movaqar

On 11/07/2013 09:13, Bahman Movaqar wrote: > Hi all, > > I'm writing a series of tutorials for Spec for beginners like myself and > I'd really appreciate any input on the material. > The first episode is done: http://www.bahmanm.com/blogs/spec-part-1-basics > Thank you folks for your encouraging! To be honest, that's one of the things that caught my attention to Pharo at first. The positive and helpful community. Glad that I could contribute a tad bit. @Ben: My website is running Plone (http://plone.org) using my own Plone hosting service (http://www.bahmanm.com/services/plone-hosting) Let me know if you're interested :-) Also the code highlighting is done by Good old Emacs :-) RE setupTitleRadioButtons: That's correct. The `:` should be left out of highlighting. RE userTitle: Cool! It takes time for me to change my Swing'ish way of looking at things. I'll add that. RE package: Subtle point. I'll change the package name. -- Bahman Movaqar (http://BahmanM.com) ERP Evaluation, Implementation & Deployment Consultant PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)

Nov. 7, 2013