February 2014 - Pharo-users

Re: [Pharo-users] Spec model attributes - is there a strategy

by Benjamin

On 16 Feb 2014, at 14:47, kmo <voxkmp(a)gmail.com> wrote: > Is there some deep philosophical reason behind this that I don't understand? The reason is simply that it was not needed until now, so not yet implemented :) > Spec does not give you control over fonts and colours. One should be able to specify a spec model color. Now, I am not sure the adapters take this attribute into account. > But if you want to write an application you might well want a particular Look and Feel. I do agree :) Ben

Feb. 16, 2014

TextModel and TextInputFieldModel font-size bug?

by kmo

When I create an interface in Spec with TextModel or TextInputFieldModel, the font-size is tiny. Same behaviour in both Windows and Linux. Is this a bug or have I missed something important? <http://forum.world.st/file/n4744094/SmallFont.png> -- View this message in context: http://forum.world.st/TextModel-and-TextInputFieldModel-font-size-bug-tp474… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 16, 2014

Re: [Pharo-users] Spec and Morphs

by Benjamin

On 16 Feb 2014, at 14:36, kmo <voxkmp(a)gmail.com> wrote: > I looked at Spec when it was first introduced. Then I left it alone until now > when the API is more stable. > > I seem to recall that when Spec was first introduced I was able to simply > add arbitrary Morphs to the Composable model layout. In the latest Spec, I > do not seem able to do this. Is this just me? Have I just forgotten how I > used to do it? Is there still a simple way to use Spec to organise morphs? It used to work out of the box before the last API change :) Now `asSpecAdapter` is required > > If there is, can someone provide an example? morph ^ Morph new asSpecAdapter Ben

Feb. 16, 2014

Spec model attributes - is there a strategy

by kmo

I was wondering about how the attributes of Spec models are decided on. Why does LabelModel have no font attribute? It seems obvious to me that a label should have a font. Why should LabelModel have no font attribute but an emphasis attribute? Why are we able to specify a font for a header in TreeColumnModel but not for the text in a TextInputFieldModel? Is there some deep philosophical reason behind this that I don't understand? It seems to me that Spec produces interfaces that look like the pharo interface. Spec does not give you control over fonts and colours. But if you want to write an application you might well want a particular Look and Feel. Spec currently doesn't seem to allow this - you would have to fall back on to simple Morphs. -- View this message in context: http://forum.world.st/Spec-model-attributes-is-there-a-strategy-tp4744089.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 16, 2014

Spec and Morphs

by kmo

I looked at Spec when it was first introduced. Then I left it alone until now when the API is more stable. I seem to recall that when Spec was first introduced I was able to simply add arbitrary Morphs to the Composable model layout. In the latest Spec, I do not seem able to do this. Is this just me? Have I just forgotten how I used to do it? Is there still a simple way to use Spec to organise morphs? If there is, can someone provide an example? Do you really have to write your own MorphicAdaptor for any morph you wish to use that doesn't already have a Spec model? -- View this message in context: http://forum.world.st/Spec-and-Morphs-tp4744084.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 16, 2014

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by Benjamin

Any questions are welcome :) Ben On 16 Feb 2014, at 14:19, kmo <voxkmp(a)gmail.com> wrote: > I would be happy to write some Spec documentation - when I start to > understand it better. I've gained some idea of how the TreeModel works so > perhaps i could do something on that and you could roll it into the Spec > documentation somewhere. Just a suggestion. > > Meanwhile expect a barrage of questions about Spec on this mailing list as I > start to look at Spec more closely. > > > > -- > View this message in context: http://forum.world.st/ANN-Spec-documentation-in-PFTE-book-finished-tp474303… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Feb. 16, 2014

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by kmo

I would be happy to write some Spec documentation - when I start to understand it better. I've gained some idea of how the TreeModel works so perhaps i could do something on that and you could roll it into the Spec documentation somewhere. Just a suggestion. Meanwhile expect a barrage of questions about Spec on this mailing list as I start to look at Spec more closely. -- View this message in context: http://forum.world.st/ANN-Spec-documentation-in-PFTE-book-finished-tp474303… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 16, 2014

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by Benjamin

Thank you for your review :) I have to agree with you and to answer briefly, the main problems with documentation is: - it takes time (*a lot* to me since I am more a code than a writer :P) - things evolve (that can be managed though) I will be super happy to have a more complete documentation I spend(t) time on it (and Johan too, thank you very much again :) ). Now I will be even happier to review any pull request ;) Ben On 16 Feb 2014, at 13:34, kmo <voxkmp(a)gmail.com> wrote: > The Spec documentation is very good /as far as it goes/. As a native speaker, > I would say the English is excellent, though the tone is rather dry and > technical. Generally, I think it is well written and very helpful. That's > not the issue. > > The real problem is that this documentation is no more than an overview. It > is not written from a /How To/ perspective. The result is that it offers > little help to anyone who wants to actually create a user interface with > Spec. > > Here are some obvious questions that might occur to anyone starting to use > Spec. None of them are answered in the current documentation. > > How do use Spec to write an application that fills the pharo window? (There > is no mention of openWorldWithSpec in the document). > > How do I write an application with a main menu at the top, a toolbar under > it, and a status bar at the bottom? > > How to I create, use and close, non-modal windows in my application? > > How do I write a modal dialog, ask for complex information, and get it back? > (There is a modal dialog example in the document under Prototyping a UI but > nothing explicit). > > How do I use a SliderModel, RadioButtonModel etcetera? > > How do I use all those cool Morphs I've found - PianoKeyboardMorph, LEDMorph > etcetera - with Spec? Surely I don't have to write my own Morphic Adapter > for each one? > > How do I migrate my Morphic application to Spec? > > To my mind, this document is only the beginning. It doesn't even have a list > of the available Spec models and their APIs - even the original Spec Report > had a table of these. The approach seems to be - here's a general idea of > how it works - read the source if you actually want to do anything. Well, > even an idiot like me can perhaps work out how to use a LabelModel, but > TreeModel,say, with its TreeColumns and TreeNodes is not so obvious and it > needs trial and error to find out how it all fits together (not helped by > the complete abscebnce of helpful class comments). We don't need tail and > error. We need documentation. > > Finally, can we please stop using class browsers as examples? I know that it > is easy (and cool) to use reflection to get lists of classes, protocols and > methods but this only adds to the impression that the smalltalk community is > self-absorbed and narcissistic. If you want to attract business developers > then use examples that relate to the real world, not to the pharo > environment itself. Why not a database example or a paint application > example? No one wants to write a class browser - that's already available! > > Perhaps I should stop before this becomes filed under /Why is > smalltalk/pharo so unpopular./ > > To sum up, this documentation is a good start - but that's all it is. > > > > > > > > > > -- > View this message in context: http://forum.world.st/ANN-Spec-documentation-in-PFTE-book-finished-tp474303… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Feb. 16, 2014

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by kmo

The Spec documentation is very good /as far as it goes/. As a native speaker, I would say the English is excellent, though the tone is rather dry and technical. Generally, I think it is well written and very helpful. That's not the issue. The real problem is that this documentation is no more than an overview. It is not written from a /How To/ perspective. The result is that it offers little help to anyone who wants to actually create a user interface with Spec. Here are some obvious questions that might occur to anyone starting to use Spec. None of them are answered in the current documentation. How do use Spec to write an application that fills the pharo window? (There is no mention of openWorldWithSpec in the document). How do I write an application with a main menu at the top, a toolbar under it, and a status bar at the bottom? How to I create, use and close, non-modal windows in my application? How do I write a modal dialog, ask for complex information, and get it back? (There is a modal dialog example in the document under Prototyping a UI but nothing explicit). How do I use a SliderModel, RadioButtonModel etcetera? How do I use all those cool Morphs I've found - PianoKeyboardMorph, LEDMorph etcetera - with Spec? Surely I don't have to write my own Morphic Adapter for each one? How do I migrate my Morphic application to Spec? To my mind, this document is only the beginning. It doesn't even have a list of the available Spec models and their APIs - even the original Spec Report had a table of these. The approach seems to be - here's a general idea of how it works - read the source if you actually want to do anything. Well, even an idiot like me can perhaps work out how to use a LabelModel, but TreeModel,say, with its TreeColumns and TreeNodes is not so obvious and it needs trial and error to find out how it all fits together (not helped by the complete abscebnce of helpful class comments). We don't need tail and error. We need documentation. Finally, can we please stop using class browsers as examples? I know that it is easy (and cool) to use reflection to get lists of classes, protocols and methods but this only adds to the impression that the smalltalk community is self-absorbed and narcissistic. If you want to attract business developers then use examples that relate to the real world, not to the pharo environment itself. Why not a database example or a paint application example? No one wants to write a class browser - that's already available! Perhaps I should stop before this becomes filed under /Why is smalltalk/pharo so unpopular./ To sum up, this documentation is a good start - but that's all it is. -- View this message in context: http://forum.world.st/ANN-Spec-documentation-in-PFTE-book-finished-tp474303… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 16, 2014

Re: [Pharo-users] mathematical models

by Natalia Tymchuk

Hello, Code which I used to build that plots is on the repository http://smalltalkhub.com/#!/~NataliaMoskovchuk/SciSmalltalk-Metrificator Best regards, Natalia On Feb 14, 2014, at 9:53 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi Paolo > > Where are you in italy? This is wonderful to hear that :) > > If you need slides about syntax and others. Do not hesitate to ask me. I have a lot of slides. > Now for your question I do not know. > I know that natalia tymchuk worked on differential equation resolvers. > > http://natalia.tymchuk.me/2013/09/code-functionality-assessment.html > > Now I do not know where the code has been published. > > For plotting there are PlotMorph or GraphET. > > >> Hi Guys! >> >> I'm going to start to teach as assistant professor of Operative Research, and i'd like to teach some stuff of Pharo. I was wondering if there are some Packages about mathematical models as Lotka-Volterra or other models about the dynamics of biological systems already implemented (with plot too). >> >> Thanks for the help. >> Paolo >

Feb. 16, 2014