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

thanks I will have a look. Now busy building furnitures :) Le 2/1/15 08:36, Daniel Lyons a écrit : On Dec 28, 2014, at 3:17 PM, stepharo > wrote: I would be interested by having an example that I could use to rewrite the spec documentation: - would be good to have

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

All that and I forgot to include the link to the code. http://smalltalkhub.com/#!/~DanielLyons/PERT — Daniel Lyons

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

> On Dec 28, 2014, at 3:17 PM, stepharo wrote: > > I would be interested by having an example that I could use to rewrite the > spec documentation: >- would be good to have a kind of container relationships >to be able to display multiple list >- the model should not be too complex

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

I would be interested by having an example that I could use to rewrite the spec documentation: - would be good to have a kind of container relationships to be able to display multiple list - the model should not be too complex to explain. So if you have data and idea I'm all ears. S

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

> On 28 Dec 2014, at 19:05, Offray Vladimir Luna Cárdenas > wrote: > > Hi, > > Just reviewing the old message I found this: > > [...] > > >> 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

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

Hi, Just reviewing the old message I found this: [...] > 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-abs

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

Thanks for your comments and questions. We will try to address them in a second version of the documentation, together with the other questions and answers that have appeared on the mailing list in the mean time. So, if anybody else has more comments and questions, do ask. They will be integra

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

Any questions are welcome :) Ben On 16 Feb 2014, at 14:19, kmo 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 > do

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

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

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

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

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

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

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

On Thu, 13 Feb 2014 15:08:32 -, kilon alios wrote:I think its great that Spec has finally documentation, it makes it far easier for me to use Spec and evaluate its usefulness. Thank you for your effort. Seconded. If the English is at this level all the way through I, as a native English speak

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

I think its great that Spec has finally documentation, it makes it far easier for me to use Spec and evaluate its usefulness. Thank you for your effort. On Thu, Feb 13, 2014 at 4:57 PM, Johan Fabry wrote: > > Ben and I focused on getting a readable text out there that is useful for > people wan

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

Ben and I focused on getting a readable text out there that is useful for people wanting to use Spec. Personally, having experience with writing lots of English, I'm actually quite happy with how it turned out and I think the text is quite readable. This being said, we are nonnative English sp

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

On Thu, 13 Feb 2014 12:42:59 -, Robert Shiplett wrote:"Creating a specific UI always starts with the subclassing of ""ComposableModel""."The above is passive with 2 gerunds. But is perfectly good and clear English nonetheless.

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

humour: license to practice English humor note; 'subclass' may be a verb at wiktionary.org but not in current standard English (e.g. m-w.org or 2002 10th Ed, hardcover Merriam-Webster) ... so word is being used as a technical term in 2014 ... life was easier when a verb had one spelling and a noun

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

" Creating a specific UI always starts with the subclassing of ""ComposableModel"". " The above is passive with 2 gerunds. No experienced tech editor should let that pass as an English instruction for an action or task to be performed by a reader - especially if the reader may be using English a

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

Hi all, I am happy to announce that Ben and I finished the documentation of Spec for the Pharo For The Enterprise book. This documentation is up-to-date with the latest version of Spec, and is focused towards people wanting to use it and even extend it (in contrast to the academic papers which