- Pharo-users - lists.pharo.org

Re: [Pharo-users] Learning Spec

by Sebastian Heidbrink

I ment both blue parts Sebastian Am 14.02.2015 um 01:56 schrieb Peter UhnÃ¡k: > > So Spec is the Blue stuff and the HP35 example is including the > orange part. > > Just the light blue, no? I thought the dark blue (VIew) is Morpic. > > Peter

Feb. 14, 2015

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

by Ben Coman

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?) On Sat, Feb 14, 2015 at 1:47 AM, 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 > Lets do it! If you recognize in yourself that feeling of "tension"between doing what is right, and the effort to do it - then we should do what is right. So can we first decide that we should and _will_ do something, and then have some debate to finalise the actual term. I proposed ComposableUIModel, but ComposableUI sounds fine, maybe better. And at the same time, are there any other Spec classes that should follow the same philosphy? We should make such change a one-time spoon of medicine! cheers -ben

Feb. 14, 2015

Re: [Pharo-users] Writing a Login Dialog using Spec in 3 methods

by Ben Coman

If ComposableModel's semantics is similar to VW ApplicationModel then calling it the sameis probably an advantage, but but I can't help thinking that ApplicationModel is more related to the application domain than the UI as we need. The suggestion in another thread for ViewModel sounds better - but I haven't dug into Spec enough to get a feel for which is more appropriate. cheers -ben On Sat, Feb 14, 2015 at 5:39 PM, stepharo <stepharo(a)free.fr> wrote: > > Le 13/2/15 14:58, Ben Coman a Ã©crit : > > > > On Fri, Feb 13, 2015 at 4:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> >> >> Spec is not perfect, its main 'issue' is that the UI elements are called >> models, which confuses the hell out of people (me too in the beginning). >> But it does make sense, you model the UI (haha). >> >> > I find the same. So should we really rename ComposableModel to > ComposableUIModel ? (And before Spec becomes more widely used?) > > > Yes we could in VW it is call ApplicationModel > > > cheers -ben > > >

Feb. 14, 2015

Roassal question

by Werner Kassens

Hi, i have a little problem, where i think roassal could perhaps be helpfull, but i have to admit this is the very first time i looked into roassal, hence i have a stupid question: i have a collection of something like rectangles, lets say: coll:=Array with: (Rectangle origin: 500@500 corner: 510@520) with: (Rectangle origin: 505@504 corner: 511@522). now i want to produce a graph that shows these rectangles together with the x & y axis that show their positions (in a sensible way). any simple hints how i could go about this task? werner

Feb. 14, 2015

voyage and couchDB

by Joachim Tuchel

Hi there, a few days ago somebody showed me Pharo with Voyage and MongoDB. I must say I was impressed by how easy this all seemed to be, and how far we got in just two hours of trying stuff. I was thinking about using CouchDB as a storage medium for larger files before I saw Voyage an Mongo in action. And I am still not usure if Mongo would fit as well as CouchDB would. As far as I understand, Esteban wa/is pretty sure Voyage would fit very well with other NoSQL DBs than Mongo. But I am not so sure abot it. AFAIU, part of Voyage's greatness relies on Mongo's nice query facility, which is not present in Couch. Also, as I understand it, the concept of Collections (not Smalltalk collections, but the named lists -maybe kind of db slices - in Mongo) is not present in Couch. So my question is whether anybody has tried to marry Voyage with Couch? Any thoughts or ideas? Joachim

Feb. 14, 2015

Re: [Pharo-users] Learning Spec

by Peter UhnÃ¡k

> > So Spec is the Blue stuff and the HP35 example is including the orange > part. > Just the light blue, no? I thought the dark blue (VIew) is Morpic. Peter

Feb. 14, 2015

Re: [Pharo-users] spec column/ row layout

by Peter UhnÃ¡k

However the more worrying thing I've just noticed is that the usernameField is taller than passwordField... that seems like a bug. Peter

Feb. 14, 2015

Re: [Pharo-users] spec column/ row layout

by Peter UhnÃ¡k

> > > Another remark, why is > height: self inputTextHeight; > needed? > > Should not spec have a default automatic way to set it, deducing from > the row contents? Actually it would do the opposite. The content has no fixed height so if you don't specify the height it will actually expand the content (the layout always uses all available space if not constrained). You can see for yourself if you remove the height here... ================================= view := DynamicComposableModel new instantiateModels: #( usernameLabel LabelModel usernameField TextInputFieldModel passwordLabel LabelModel passwordField TextInputFieldModel showPasswordCheckBox CheckBoxModel ); yourself. view usernameLabel text: 'Username'. view passwordLabel text: 'Password'. view showPasswordCheckBox label: 'Show password'. layout := SpecLayout composed newColumn: [ :col | col newRow: [ :row | row add: #usernameLabel; add: #usernameField ] height: DynamicComposableModel inputTextHeight; newRow: [ :row | row add: #passwordLabel; add: #passwordField ] height: DynamicComposableModel inputTextHeight; newRow: [ :row | row add: #showPasswordCheckBox] height: DynamicComposableModel inputTextHeight; newRow: [ :row | ] ]; yourself. view openWithSpecLayout: layout. ===================================== Peter

Feb. 14, 2015

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

by stepharo

I would like to clean the API with all the changed: [ ] and other I am pro too, but it does influence the docs a bit, ... > I have no problem in fixing the docs, as you might well imagine :-) We should do a pass on all the Spec documentation anyway. I hope to find time somewhere in the beginning of april ... > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > >

Feb. 14, 2015

Re: [Pharo-users] Writing a Login Dialog using Spec in 3 methods

by stepharo

Le 13/2/15 14:58, Ben Coman a Ã©crit : > > > On Fri, Feb 13, 2015 at 4:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>> wrote: > > > > Spec is not perfect, its main 'issue' is that the UI elements are > called models, which confuses the hell out of people (me too in > the beginning). But it does make sense, you model the UI (haha). > > > I find the same. So should we really rename ComposableModel to > ComposableUIModel ? (And before Spec becomes more widely used?) Yes we could in VW it is call ApplicationModel > cheers -ben

Feb. 14, 2015