February 2015 - Pharo-users

Re: [Pharo-users] Learning Spec

by Sebastian Heidbrink

Hi Sven, I am still a little confused about the terminologies so please give one last kick into the right direction. I have loaded the Calculator and try to map thingssaid to the implementation. Am 13.02.2015 um 11:04 schrieb Sven Van Caekenberghe: > > > In the talk at 15:35 min Johan mentions the need of a interpreter and this method is mentionded several times during the talk. > Browse your Pharo image,.... there is none! > The class is called SpecInterpreter. But this is an implementation detail, not related to application logic. Well, no he did not mean the SpecInterpreter he ment the receiver/interpreter of an action like a mouse click here. And exactly this link is missing through out the examples.... and makes SPEC so hrad to understand. > >> And last but not least, the all examples have no interpreter/control or real model layer.... > But you are looking too far: your domain model is just an object, its behaviour is the control layer, it uses announcements to signal changes. Looking at the HP35CalculatorModel implementation I think that is what you mean. But I honestly would have expected a class naming like HP35CalculatorApplicationFunction, HP35CalculatorController, or HP35CalculatorComponent or just HP35Calculator instead of HP35CalculatorModel... For me a model is a stupid structure. Somehting that knows what it contains and how to describe itself,... but has no real functionality or mechnisms in it. Extreem example is a DataModel,.... Now since Spec is more a MVVM framework, I assumed that I have to make the distinction between Control/Businesslogic and Model on my own. I prefer this distinction because once a project grows it is much eaiser to navigate, maintian and even port to different architectures like webclient, server app, desktop app.... > > ing like the HPCalculator! > I understand the need. I did my part with the HP35, with a clear model and 2 UI's sharing 1 specification as well as unit tests on 2 levels. > > But like I said, there are lots of real world examples inside and outside the image. How can one find them? I was not aware of the fact that the spec example HP53 was on smaltlakhub. Somehow it is very difficult to find projects on Smalltakhub.... all the projects have tags, but somehow I can't find a search or tool that allows me to search smalltalkhub for certain tags. > You could just start a new repo on smalltalkhub.com or even github.com Well, I would love, too once I know that I have somehow understood the basics ;-) I simply do not want to run into the wrong direction and realize that all my efforts where for nothing. And I, and that is even more importatn, do not want to tell newcomers how to do it and send them into the wrong direction... Give me some time and I'll try to come up with a little application that we could use to discuss on. sebastian

Feb. 13, 2015

Re: [Pharo-users] Learning Spec

by Sven Van Caekenberghe

> On 13 Feb 2015, at 18:49, Sebastian Heidbrink <sheidev(a)yahoo.de> wrote: > > Hallo Sven, > > thank you for the video link, google linked me to a video from 2013 that was not recorded in a way that once could follwo the presentation. > This one is super. > > Well, I think I am slowly getting there and I can more and more provide you with the uneccessary barries of Spec that I encountered. > > In the talk at 15:35 min Johan mentions the need of a interpreter and this method is mentionded several times during the talk. > Browse your Pharo image,.... there is none! The class is called SpecInterpreter. But this is an implementation detail, not related to application logic. > So what is misleading in the current Spec implementation and the examples is the follwong fact. > The developer is confronted with Model classes that actually are ViewModels. > Actions for buttons are implemented in Blocks which gives the developer intially the feeling that Control Layer and Model/ViewModel layer are one. > The SpecDefinitions do not work properly in my case and Stephan just found out some issues with font sizes,.... well I have Moose and Roassal in my image and my fonts are no more default .... well my fault. I just hope I will still be able to somehow find a solution for this issue. Specs certainly work. The font stuff also works, it is just not complete (enough) (yet), but it is good enough. > And last but not least, the all examples have no interpreter/control or real model layer.... But you are looking too far: your domain model is just an object, its behaviour is the control layer, it uses announcements to signal changes. > This is why I think it would be very helpful for beginners to have one example, like a sushi store, where one can actually see how an application is built through all the layers.... But again, there is no 'one' thing, there are many options, styles. > Sushi store?! Well, That was an example for a demo that show cases a whole technology. > And I meant exactly some thing like the HPCalculator! I understand the need. I did my part with the HP35, with a clear model and 2 UI's sharing 1 specification as well as unit tests on 2 levels. But like I said, there are lots of real world examples inside and outside the image. > Well, I need to do some tests based on what I 've learnt now,.... I have no idea about adaptors, yet, but it seems they need to be understod a little later.... > Is there a project/repository where one could push code to give other the chance to review and chance it before it is published as a "demo" or example? You could just start a new repo on smalltalkhub.com or even github.com > Sebastian > > > Am 13.02.2015 um 01:12 schrieb Sven Van Caekenberghe: >> Hi, >> >> >> From now on it is forbidden to complain about Spec in general, unspecific terms unless you have taken the time to learn about it. Here is a guide to documentation about Spec, most recent first. >> >> >> There is an excellent presentation by Johan Fabry did during the last Pharo Days, 'Using Spec to Build a UI'. *MUST WATCH* (the video is not yet fully public, but soon will be, the link should work though): >> >> http://youtu.be/OL23s9ZUIR0?list=PL4actYd6bfnz98ngrKALwwStl3C3odEKG >> >> The slides are also not yet available, but soon will be (the talk is much better that the slides on their own). >> >> >> This draft chapter 'Spec: a framework for describing user interfaces' for an upcoming book: >> >> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… >> >> >> Look in the image. >> >> Browse the hierarchy below AbstractWidgetModel in the category Spec-Core-Widgets in Pharo 4, look at the protocols called 'protocol' & 'protocol-events' mainly. Look for references to each class. Trace senders of methods until you arrive at examples. Study the examples, play with them, change them. >> >> The UI of most tools in Pharo is also implemented using Spec. Browse the hierarchy below ComposableModel to find them. (Komitter, Versionner, Critics, Metacello, the old Eye Inspectors, ..). Watch and learn. >> >> >> The cool Spec website: >> >> http://spec.st >> >> >> Read some cool articles like: >> >> https://medium.com/concerning-pharo/rediscovering-the-ux-of-the-legendary-h… >> >> See the section 'HP35CalculatorModel' for the Spec part. >> >> >> The following papers (some older ones refer to API that has changed): >> >> 'Seamless Composition and Reuse of Customizable User Interfaces with Spec' >> >> http://rmod.lille.inria.fr/archives/papers/Ryse13a-SCICO-Spec.pdf >> >> 'Spec - A Framework for the Specification and Reuse of UIs and their Models' >> >> http://rmod.lille.inria.fr/archives/papers/Ryse12b-Spec-IWST12-Final.pdf >> >> 'Spec â Technical Report' >> >> http://rmod.lille.inria.fr/archives/reports/Ryse12a-SpecTechReport.pdf >> >> >> Use the image to build a couple of simple UIs using Spec. You will be surprised to learn that it is not that difficult. Just go with the flow, don't try to enforce your world view on it, wait until you are further along. >> >> >> Have fun ! >> >> >> Sven >> >> >> PS: Once you have done all the above, you are most welcome to help improve Spec by discussing specific, concrete issues. >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> > >

Feb. 13, 2015

Re: [Pharo-users] Learning Spec

by Sven Van Caekenberghe

> On 13 Feb 2015, at 19:06, Sebastian Heidbrink <sheidev(a)yahoo.de> wrote: > > By the way,.... this is why I am pushing so hard. > > https://makerspacenanaimo.org/software-smalltalk-night/ > > Sebastian Cool. > Am 13.02.2015 um 09:49 schrieb Sebastian Heidbrink: >> Hallo Sven, >> >> thank you for the video link, google linked me to a video from 2013 that was not recorded in a way that once could follwo the presentation. >> This one is super. >> >> Well, I think I am slowly getting there and I can more and more provide you with the uneccessary barries of Spec that I encountered. >> >> In the talk at 15:35 min Johan mentions the need of a interpreter and this method is mentionded several times during the talk. >> Browse your Pharo image,.... there is none! >> So what is misleading in the current Spec implementation and the examples is the follwong fact. >> The developer is confronted with Model classes that actually are ViewModels. >> Actions for buttons are implemented in Blocks which gives the developer intially the feeling that Control Layer and Model/ViewModel layer are one. >> The SpecDefinitions do not work properly in my case and Stephan just found out some issues with font sizes,.... well I have Moose and Roassal in my image and my fonts are no more default .... well my fault. I just hope I will still be able to somehow find a solution for this issue. >> And last but not least, the all examples have no interpreter/control or real model layer.... >> This is why I think it would be very helpful for beginners to have one example, like a sushi store, where one can actually see how an application is built through all the layers.... >> >> Sushi store?! Well, That was an example for a demo that show cases a whole technology. >> And I meant exactly some thing like the HPCalculator! >> >> Well, I need to do some tests based on what I 've learnt now,.... I have no idea about adaptors, yet, but it seems they need to be understod a little later.... >> Is there a project/repository where one could push code to give other the chance to review and chance it before it is published as a "demo" or example? >> >> Sebastian >> >> >> >> Am 13.02.2015 um 01:12 schrieb Sven Van Caekenberghe: >>> Hi, >>> >>> >>> From now on it is forbidden to complain about Spec in general, unspecific terms unless you have taken the time to learn about it. Here is a guide to documentation about Spec, most recent first. >>> >>> >>> There is an excellent presentation by Johan Fabry did during the last Pharo Days, 'Using Spec to Build a UI'. *MUST WATCH* (the video is not yet fully public, but soon will be, the link should work though): >>> >>> http://youtu.be/OL23s9ZUIR0?list=PL4actYd6bfnz98ngrKALwwStl3C3odEKG >>> >>> The slides are also not yet available, but soon will be (the talk is much better that the slides on their own). >>> >>> >>> This draft chapter 'Spec: a framework for describing user interfaces' for an upcoming book: >>> >>> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… >>> >>> >>> Look in the image. >>> >>> Browse the hierarchy below AbstractWidgetModel in the category Spec-Core-Widgets in Pharo 4, look at the protocols called 'protocol' & 'protocol-events' mainly. Look for references to each class. Trace senders of methods until you arrive at examples. Study the examples, play with them, change them. >>> >>> The UI of most tools in Pharo is also implemented using Spec. Browse the hierarchy below ComposableModel to find them. (Komitter, Versionner, Critics, Metacello, the old Eye Inspectors, ..). Watch and learn. >>> >>> >>> The cool Spec website: >>> >>> http://spec.st >>> >>> >>> Read some cool articles like: >>> >>> https://medium.com/concerning-pharo/rediscovering-the-ux-of-the-legendary-h… >>> >>> See the section 'HP35CalculatorModel' for the Spec part. >>> >>> >>> The following papers (some older ones refer to API that has changed): >>> >>> 'Seamless Composition and Reuse of Customizable User Interfaces with Spec' >>> >>> http://rmod.lille.inria.fr/archives/papers/Ryse13a-SCICO-Spec.pdf >>> >>> 'Spec - A Framework for the Specification and Reuse of UIs and their Models' >>> >>> http://rmod.lille.inria.fr/archives/papers/Ryse12b-Spec-IWST12-Final.pdf >>> >>> 'Spec â Technical Report' >>> >>> http://rmod.lille.inria.fr/archives/reports/Ryse12a-SpecTechReport.pdf >>> >>> >>> Use the image to build a couple of simple UIs using Spec. You will be surprised to learn that it is not that difficult. Just go with the flow, don't try to enforce your world view on it, wait until you are further along. >>> >>> >>> Have fun ! >>> >>> >>> Sven >>> >>> >>> PS: Once you have done all the above, you are most welcome to help improve Spec by discussing specific, concrete issues. >>> >>> >>> -- >>> Sven Van Caekenberghe >>> Proudly supporting Pharo >>> http://pharo.org >>> http://association.pharo.org >>> http://consortium.pharo.org >>> >>> >>> >> >> >> > >

Feb. 13, 2015

Re: [Pharo-users] Spec terminology: renaming some terms.

by Sven Van Caekenberghe

> On 13 Feb 2015, at 18:47, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 13 Feb 2015, at 18:29, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: >> >> >> If we think about renaming things in Spec, actually Iâd rename: >> - ComposableModel to ComposableUI >> - all the protocols âprotocol-*â to âAPI-*â > > +100 > Iâm super tired of âprotocolâ category (it is actually a protocolâ¦ as any other category under the âprotocolâ pane :P) > api is a lot better I am pro too, but it does influence the docs a bit, ... >> >>> On Feb 13, 2015, at 14:58, Ben Coman <btc(a)openInWorld.com> wrote: >>> >>> So should we really rename ComposableModel to ComposableUIModel ? (And before Spec becomes more widely used?) >> >> >> >> ---> Save our in-boxes! http://emailcharter.org <--- >> >> Johan Fabry - http://pleiad.cl/~jfabry >> PLEIAD lab - Computer Science Department (DCC) - University of Chile >> >

Feb. 13, 2015

libssl on fedora to new for pharo-vm

by Martin BÃ¤hr

hi, i just discovered that i can't make https requests in pharo because pharo-vm tries to link against libssl.1.0.0, but recent fedora versions have libssl.so.1.0.1e at least since fedora 18 i did discover that the centos version on http://files.pharo.org/vm/pharo/linux/centos/ works however. i wonder if that shouldn't be linked more directly from the download page... greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

Feb. 13, 2015

Re: [Pharo-users] Learning Spec

by Sebastian Heidbrink

By the way,.... this is why I am pushing so hard. https://makerspacenanaimo.org/software-smalltalk-night/ Sebastian Am 13.02.2015 um 09:49 schrieb Sebastian Heidbrink: > Hallo Sven, > > thank you for the video link, google linked me to a video from 2013 > that was not recorded in a way that once could follwo the presentation. > This one is super. > > Well, I think I am slowly getting there and I can more and more > provide you with the uneccessary barries of Spec that I encountered. > > In the talk at 15:35 min Johan mentions the need of a interpreter and > this method is mentionded several times during the talk. > Browse your Pharo image,.... there is none! > So what is misleading in the current Spec implementation and the > examples is the follwong fact. > The developer is confronted with Model classes that actually are > ViewModels. > Actions for buttons are implemented in Blocks which gives the > developer intially the feeling that Control Layer and Model/ViewModel > layer are one. > The SpecDefinitions do not work properly in my case and Stephan just > found out some issues with font sizes,.... well I have Moose and > Roassal in my image and my fonts are no more default .... well my > fault. I just hope I will still be able to somehow find a solution for > this issue. > And last but not least, the all examples have no interpreter/control > or real model layer.... > This is why I think it would be very helpful for beginners to have one > example, like a sushi store, where one can actually see how an > application is built through all the layers.... > > Sushi store?! Well, That was an example for a demo that show cases a > whole technology. > And I meant exactly some thing like the HPCalculator! > > Well, I need to do some tests based on what I 've learnt now,.... I > have no idea about adaptors, yet, but it seems they need to be > understod a little later.... > Is there a project/repository where one could push code to give other > the chance to review and chance it before it is published as a "demo" > or example? > > Sebastian > > > > Am 13.02.2015 um 01:12 schrieb Sven Van Caekenberghe: >> Hi, >> >> >> From now on it is forbidden to complain about Spec in general, >> unspecific terms unless you have taken the time to learn about it. >> Here is a guide to documentation about Spec, most recent first. >> >> >> There is an excellent presentation by Johan Fabry did during the last >> Pharo Days, 'Using Spec to Build a UI'. *MUST WATCH* (the video is >> not yet fully public, but soon will be, the link should work though): >> >> http://youtu.be/OL23s9ZUIR0?list=PL4actYd6bfnz98ngrKALwwStl3C3odEKG >> >> The slides are also not yet available, but soon will be (the talk is >> much better that the slides on their own). >> >> >> This draft chapter 'Spec: a framework for describing user interfaces' >> for an upcoming book: >> >> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… >> >> >> Look in the image. >> >> Browse the hierarchy below AbstractWidgetModel in the category >> Spec-Core-Widgets in Pharo 4, look at the protocols called 'protocol' >> & 'protocol-events' mainly. Look for references to each class. Trace >> senders of methods until you arrive at examples. Study the examples, >> play with them, change them. >> >> The UI of most tools in Pharo is also implemented using Spec. Browse >> the hierarchy below ComposableModel to find them. (Komitter, >> Versionner, Critics, Metacello, the old Eye Inspectors, ..). Watch >> and learn. >> >> >> The cool Spec website: >> >> http://spec.st >> >> >> Read some cool articles like: >> >> https://medium.com/concerning-pharo/rediscovering-the-ux-of-the-legendary-h… >> >> >> See the section 'HP35CalculatorModel' for the Spec part. >> >> >> The following papers (some older ones refer to API that has changed): >> >> 'Seamless Composition and Reuse of Customizable User Interfaces with >> Spec' >> >> http://rmod.lille.inria.fr/archives/papers/Ryse13a-SCICO-Spec.pdf >> >> 'Spec - A Framework for the Specification and Reuse of UIs and their >> Models' >> >> http://rmod.lille.inria.fr/archives/papers/Ryse12b-Spec-IWST12-Final.pdf >> >> 'Spec â Technical Report' >> >> http://rmod.lille.inria.fr/archives/reports/Ryse12a-SpecTechReport.pdf >> >> >> Use the image to build a couple of simple UIs using Spec. You will be >> surprised to learn that it is not that difficult. Just go with the >> flow, don't try to enforce your world view on it, wait until you are >> further along. >> >> >> Have fun ! >> >> >> Sven >> >> >> PS: Once you have done all the above, you are most welcome to help >> improve Spec by discussing specific, concrete issues. >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> > > >

Feb. 13, 2015

Re: [Pharo-users] Learning Spec

by Sebastian Heidbrink

Hallo Sven, thank you for the video link, google linked me to a video from 2013 that was not recorded in a way that once could follwo the presentation. This one is super. Well, I think I am slowly getting there and I can more and more provide you with the uneccessary barries of Spec that I encountered. In the talk at 15:35 min Johan mentions the need of a interpreter and this method is mentionded several times during the talk. Browse your Pharo image,.... there is none! So what is misleading in the current Spec implementation and the examples is the follwong fact. The developer is confronted with Model classes that actually are ViewModels. Actions for buttons are implemented in Blocks which gives the developer intially the feeling that Control Layer and Model/ViewModel layer are one. The SpecDefinitions do not work properly in my case and Stephan just found out some issues with font sizes,.... well I have Moose and Roassal in my image and my fonts are no more default .... well my fault. I just hope I will still be able to somehow find a solution for this issue. And last but not least, the all examples have no interpreter/control or real model layer.... This is why I think it would be very helpful for beginners to have one example, like a sushi store, where one can actually see how an application is built through all the layers.... Sushi store?! Well, That was an example for a demo that show cases a whole technology. And I meant exactly some thing like the HPCalculator! Well, I need to do some tests based on what I 've learnt now,.... I have no idea about adaptors, yet, but it seems they need to be understod a little later.... Is there a project/repository where one could push code to give other the chance to review and chance it before it is published as a "demo" or example? Sebastian Am 13.02.2015 um 01:12 schrieb Sven Van Caekenberghe: > Hi, > > > From now on it is forbidden to complain about Spec in general, unspecific terms unless you have taken the time to learn about it. Here is a guide to documentation about Spec, most recent first. > > > There is an excellent presentation by Johan Fabry did during the last Pharo Days, 'Using Spec to Build a UI'. *MUST WATCH* (the video is not yet fully public, but soon will be, the link should work though): > > http://youtu.be/OL23s9ZUIR0?list=PL4actYd6bfnz98ngrKALwwStl3C3odEKG > > The slides are also not yet available, but soon will be (the talk is much better that the slides on their own). > > > This draft chapter 'Spec: a framework for describing user interfaces' for an upcoming book: > > https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… > > > Look in the image. > > Browse the hierarchy below AbstractWidgetModel in the category Spec-Core-Widgets in Pharo 4, look at the protocols called 'protocol' & 'protocol-events' mainly. Look for references to each class. Trace senders of methods until you arrive at examples. Study the examples, play with them, change them. > > The UI of most tools in Pharo is also implemented using Spec. Browse the hierarchy below ComposableModel to find them. (Komitter, Versionner, Critics, Metacello, the old Eye Inspectors, ..). Watch and learn. > > > The cool Spec website: > > http://spec.st > > > Read some cool articles like: > > https://medium.com/concerning-pharo/rediscovering-the-ux-of-the-legendary-h… > > See the section 'HP35CalculatorModel' for the Spec part. > > > The following papers (some older ones refer to API that has changed): > > 'Seamless Composition and Reuse of Customizable User Interfaces with Spec' > > http://rmod.lille.inria.fr/archives/papers/Ryse13a-SCICO-Spec.pdf > > 'Spec - A Framework for the Specification and Reuse of UIs and their Models' > > http://rmod.lille.inria.fr/archives/papers/Ryse12b-Spec-IWST12-Final.pdf > > 'Spec â Technical Report' > > http://rmod.lille.inria.fr/archives/reports/Ryse12a-SpecTechReport.pdf > > > Use the image to build a couple of simple UIs using Spec. You will be surprised to learn that it is not that difficult. Just go with the flow, don't try to enforce your world view on it, wait until you are further along. > > > Have fun ! > > > Sven > > > PS: Once you have done all the above, you are most welcome to help improve Spec by discussing specific, concrete issues. > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > >

Feb. 13, 2015

Re: [Pharo-users] Spec terminology: renaming some terms.

by Esteban Lorenzano

> On 13 Feb 2015, at 18:29, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > > If we think about renaming things in Spec, actually Iâd rename: > - ComposableModel to ComposableUI > - all the protocols âprotocol-*â to âAPI-*â +100 Iâm super tired of âprotocolâ category (it is actually a protocolâ¦ as any other category under the âprotocolâ pane :P) api is a lot better > >> On Feb 13, 2015, at 14:58, Ben Coman <btc(a)openInWorld.com <mailto:btc@openInWorld.com>> wrote: >> >> So should we really rename ComposableModel to ComposableUIModel ? (And before Spec becomes more widely used?) > > > > ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD lab - Computer Science Department (DCC) - University of Chile >

Feb. 13, 2015

Re: [Pharo-users] Learning Spec

by Johan Fabry

Excellent mails, Sven. Thanks a lot for joining all the info in one place! > On Feb 13, 2015, at 10:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > > From now on it is forbidden to complain about Spec in general, unspecific terms unless you have taken the time to learn about it. Here is a guide to documentation about Spec, most recent first. > > > There is an excellent presentation by Johan Fabry did during the last Pharo Days, 'Using Spec to Build a UI'. *MUST WATCH* (the video is not yet fully public, but soon will be, the link should work though): > > http://youtu.be/OL23s9ZUIR0?list=PL4actYd6bfnz98ngrKALwwStl3C3odEKG > > The slides are also not yet available, but soon will be (the talk is much better that the slides on their own). > > > This draft chapter 'Spec: a framework for describing user interfaces' for an upcoming book: > > https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… > > > Look in the image. > > Browse the hierarchy below AbstractWidgetModel in the category Spec-Core-Widgets in Pharo 4, look at the protocols called 'protocol' & 'protocol-events' mainly. Look for references to each class. Trace senders of methods until you arrive at examples. Study the examples, play with them, change them. > > The UI of most tools in Pharo is also implemented using Spec. Browse the hierarchy below ComposableModel to find them. (Komitter, Versionner, Critics, Metacello, the old Eye Inspectors, ..). Watch and learn. > > > The cool Spec website: > > http://spec.st > > > Read some cool articles like: > > https://medium.com/concerning-pharo/rediscovering-the-ux-of-the-legendary-h… > > See the section 'HP35CalculatorModel' for the Spec part. > > > The following papers (some older ones refer to API that has changed): > > 'Seamless Composition and Reuse of Customizable User Interfaces with Spec' > > http://rmod.lille.inria.fr/archives/papers/Ryse13a-SCICO-Spec.pdf > > 'Spec - A Framework for the Specification and Reuse of UIs and their Models' > > http://rmod.lille.inria.fr/archives/papers/Ryse12b-Spec-IWST12-Final.pdf > > 'Spec â Technical Report' > > http://rmod.lille.inria.fr/archives/reports/Ryse12a-SpecTechReport.pdf > > > Use the image to build a couple of simple UIs using Spec. You will be surprised to learn that it is not that difficult. Just go with the flow, don't try to enforce your world view on it, wait until you are further along. > > > Have fun ! > > > Sven > > > PS: Once you have done all the above, you are most welcome to help improve Spec by discussing specific, concrete issues. > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Feb. 13, 2015

Spec terminology: renaming some terms.

by Johan Fabry

If we think about renaming things in Spec, actually Iâd rename: - ComposableModel to ComposableUI - all the protocols âprotocol-*â to âAPI-*' > On Feb 13, 2015, at 14:58, Ben Coman <btc(a)openInWorld.com> wrote: > > So should we really rename ComposableModel to ComposableUIModel ? (And before Spec becomes more widely used?) ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Feb. 13, 2015