June 2014 - Pharo-dev - lists.pharo.org

The importance of Class Comments

by kilon alios

I completely understand the inability to create full blown documentation because of lack of free time. I am not referring to any Pharo Library out there. Please pharo developers comment your classes. Dont even comment the small ones, comment the big ones (over 20 methods). 5 minutes per class , is 150 words (assuming you are a slow 30 words/per minute , 3 times more if you type fast). Just a class comment, I can live without method comments. 15 lines, enough to provide valuable information to your users. Even for very big libraries like Spec it should not take more than 10 key classes to be documented this way , no more than 1 hour total of documentation for a project that can take months of coding to complete. It can't be this hard. Saying that I will start adding class comments wherever I can but obviously the people that have created the code are far more qualified than me . Have a nice day :)

June 20, 2014

Re: [Pharo-dev] Complaints about Spec

by Yuriy Tymchuk

Yes Stef, I know. And in the end Iâve made and adapter for CodeCity: http://quick.as/blq9f5d1 cool, no? We all get frustrated from time to time, I just wanted to point out that we need a straightforward tutorial on building apps with UIs. And Spec is not bad. And I will take a look at the tutorial in Pharo for the Enterprise. Have a nice Friday. Uko On 20 Jun 2014, at 08:39, stepharo <stepharo(a)free.fr> wrote: > Did you check that in Phro for the entreprise there is a calculator tutorial based on spec. > > Sven I'm interested reading yours. > > > Yuriy if you give us 1% of the money spent on Cocoa pharo will not look the same at all. > Did you see that most of us are not payed to develop pharo? > > Stef > > > On 18/6/14 12:04, Sven Van Caekenberghe wrote: >> Hi Yuriy, >> >> I can't really comment on the overal questions you are asking. But please keep in mind that Apple's Cocoa has had a little bit more resource behind it, for many decades, of course they have a nice design and excellent documentation. >> >> I actually have a calculator project which contains a Spec GUI and Seaside GUI on the same model ready, with shared unit tests at the model and both GUI levels. I even use some kind of meta spec to generate both GUIs automatically. My goal is to write a Pharo tutorial about that. But I need more time (I haven't started yet). I'll see what I can do. >> >> Overall, although Spec is new to me, I found it acceptable for building functional GUIs. >> >> Sven >> >> On 18 Jun 2014, at 11:40, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >>> Hi guys, >>> >>> I was very frustrated, but as usually complaints are useless, Iâll try to be constructive. Maybe the problem is not about Spec itself but all the UI related tool-chain. >>> >>> I find UI very fragile part in software design. And by now Iâve seen only 2 very nice documentations on how to develop UI (with MVC). One was for Ruby on Rails, and another was for iOS applications. Documentation was straightforward: 1) this is how your model, view and controller should look like, 2) this is how they have to talk, 3) other useful cases. >>> >>> Now, there is description about how to do something with Spec, and itâs cool, but for example I always get myself caught in initialisation stuff. Spec intends that I provide some default solution if itâs not initialised with proper data. And I even cannot initialise some variables, because initialisation of superclass initialises widgets and they need default behaviour. I can move to sort of lazy initialisation stuff, but maybe there is some reason in making some calculator example tutorial that will show how mvc apps should be developed in Pharo? >>> >>> Uko >>> >>> >> >> >> > >

June 20, 2014

Re: [Pharo-dev] Pharo VM crash on seom DrGeo sketch

by stepharo

Hilaire do you have the error stack? Because the vm crash does not help. Stef On 19/6/14 18:25, Hilaire Fernandes wrote: > Hi, > > I have some VM crash on some DrGeo. It happens from the DrGeo file > dialog when the preview of a sketch is computed. It is repeatable. > > I saw it on Mac, then in Linux as well. > > See below the log > > Hilaire > >

June 20, 2014

Re: [Pharo-dev] Complaints about Spec

by stepharo

Hi ben > I understand your frustration, but writing doc takes time. > > I have a more industry oriented example in polishing mode I can review it if you need. Stef

June 20, 2014

Re: [Pharo-dev] Athens and StrikeFont ( again )

by stepharo

On 20/6/14 00:26, Nicolai Hess wrote: > > If I take a fresh pharo image I always have to reenable FT fonts before > doing any athens rendering with text > (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight). > > Ok, I know I have to > open settings > disable then > enable FreeType > and choose a FreeType font. > > But what exactly is the problem with Athens rendering and non FT fonts? StrikeFonts and FT are different beasts. I should take the time concentrate and go over my roadmap (it feels to me like a "chemin de croix" :( > > > Nicolai

June 20, 2014

Re: [Pharo-dev] Complaints about Spec

by stepharo

Did you check that in Phro for the entreprise there is a calculator tutorial based on spec. Sven I'm interested reading yours. Yuriy if you give us 1% of the money spent on Cocoa pharo will not look the same at all. Did you see that most of us are not payed to develop pharo? Stef On 18/6/14 12:04, Sven Van Caekenberghe wrote: > Hi Yuriy, > > I can't really comment on the overal questions you are asking. But please keep in mind that Apple's Cocoa has had a little bit more resource behind it, for many decades, of course they have a nice design and excellent documentation. > > I actually have a calculator project which contains a Spec GUI and Seaside GUI on the same model ready, with shared unit tests at the model and both GUI levels. I even use some kind of meta spec to generate both GUIs automatically. My goal is to write a Pharo tutorial about that. But I need more time (I haven't started yet). I'll see what I can do. > > Overall, although Spec is new to me, I found it acceptable for building functional GUIs. > > Sven > > On 18 Jun 2014, at 11:40, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Hi guys, >> >> I was very frustrated, but as usually complaints are useless, Iâll try to be constructive. Maybe the problem is not about Spec itself but all the UI related tool-chain. >> >> I find UI very fragile part in software design. And by now Iâve seen only 2 very nice documentations on how to develop UI (with MVC). One was for Ruby on Rails, and another was for iOS applications. Documentation was straightforward: 1) this is how your model, view and controller should look like, 2) this is how they have to talk, 3) other useful cases. >> >> Now, there is description about how to do something with Spec, and itâs cool, but for example I always get myself caught in initialisation stuff. Spec intends that I provide some default solution if itâs not initialised with proper data. And I even cannot initialise some variables, because initialisation of superclass initialises widgets and they need default behaviour. I can move to sort of lazy initialisation stuff, but maybe there is some reason in making some calculator example tutorial that will show how mvc apps should be developed in Pharo? >> >> Uko >> >> > > >

June 20, 2014

Re: [Pharo-dev] Implementing cull:cull: in symbol

by phil＠highoctane.be

Le 20 juin 2014 02:16, "David T. Lewis" <lewis(a)mail.msen.com> a Ã©crit : > > On Thu, Jun 19, 2014 at 11:24:33AM -0300, Esteban A. Maringolo wrote: > > Can somebody please tell me the semantic difference between #cull: and #value: ? > > 'Cull' is not a word I ever used in any english based conversation :) > > Hi Esteban, > > I am an American English speaker, and I have never used the word 'cull' in > conversation or in writing. I recognize it as a real word, but I had to look > it up in a dictionary to see what it means. > > Dave > > Extensive usage here... http://stargate.wikia.com/wiki/Culling You'll see cull: with a new eye now :-p Phil

June 20, 2014

Re: [Pharo-dev] Implementing cull:cull: in symbol

by David T. Lewis

On Thu, Jun 19, 2014 at 11:24:33AM -0300, Esteban A. Maringolo wrote: > Can somebody please tell me the semantic difference between #cull: and #value: ? > 'Cull' is not a word I ever used in any english based conversation :) Hi Esteban, I am an American English speaker, and I have never used the word 'cull' in conversation or in writing. I recognize it as a real word, but I had to look it up in a dictionary to see what it means. Dave

June 20, 2014

Re: [Pharo-dev] Athens and StrikeFont ( again )

by Alexandre Bergel

Times to times, font are displayed in a very weir fashion: small and big letter. Width is not properly computed in addition. Alexandre > Le 19-06-2014 Ã 18:26, Nicolai Hess <nicolaihess(a)web.de> a Ã©crit : > > > If I take a fresh pharo image I always have to reenable FT fonts before > doing any athens rendering with text > (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight). > > Ok, I know I have to > open settings > disable then > enable FreeType > and choose a FreeType font. > > But what exactly is the problem with Athens rendering and non FT fonts? > > > Nicolai

June 20, 2014

Athens and StrikeFont ( again )

by Nicolai Hess

If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight). Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font. But what exactly is the problem with Athens rendering and non FT fonts? Nicolai

June 19, 2014