"Spec is all about *composing* models.
If you want a GUI with many UI elements and try to build this with
a single model, spec won't be much help."

whats a model ?

whats a composing model ?

"Not both are needed, either you call newXmodel for every model or you call
instantatieModels with an array of "instanceVars and Models""

no idea what newXmodel is

"spec is designed to provide *reusable* models."

dont understand what that means since I dont understand model and
documentation does explain it clearly.

"Take a look at DynamicComposableModel (the examples in pharo or the
examples posted on this list), for a simple GUI you only need some few
lines of code."

yes that is more to what I like but I was trying to do thing the "default"
way of Spec.

"That's not unusual. 90% spec means "not 90% morphic"

no what I meant is that 90% is what Spec requires and 10% what is actually
would make sense to me that Spec should require.

"If you have 100 buttons in one GUI without the possiblity to divide it in
small reusable
parts, then spec may be your smallest problem."

divinding something to smaller parts you dont make it simpler or less
verbose you make it more manageable.

"The two years I am working with pharo and reading this list, I have read
more
complains than constructive critics (about morphic and spec).
We have the following options:
- complain
- constructive critics
- contribute
- develop a new framework (develop *active*)"

My choice is pretty much final on "neither" . I want to use Morphic and
extend it where it does not fit my style or my needs.

Just a side note, what I did with Spec is follow its documentation and its
examples, its not as if I made all this up out of my head.

On the matter of complaining , you may want to think that coding is about
gettting a job done but I can assure you this definetly NOT how I see
coding. For me coding is for fun and anything that kills my fun I pay it
back by not using it.  At some point obviously we have to be practical
about how we get things done but anyone who believes that what motivates
coding in general is practical application and not personal emotions is a
person about to be severely surprised.

We can also debate what is "constructive criticism" but it wont be a long
pointless debate since its a very vague definition anyway. I know however
one thing in life, that complain is way more valuable than applauding,
though less desirable.

Reply via email to