- Pharo-users - lists.pharo.org

Spec layout

by Marion Noirbent

Hi, I'm trying to create a widget whith Spec, managing a collection of RadioButton. But I have a problem with defaultSpec (the accessor of the collection is the methods "buttons") : If i put defaultSpec on class side, i can't acces the collection of the instance. (the following code iterate on the string) defaultSpec <spec: #default> ^ SpecLayout composed newColumn: [ :column | #buttons do: [ :item | column add: item ] ]; yourself If i put it on instance side, the lookup don't find it (in the book Building UI with Spec, it said the lookup begin by the instance side and it allow to have specific UI, in part about layout) defaultSpec <spec: #default> ^ SpecLayout composed newColumn: [ :column | self buttons do: [ :item | column add: item ] ]; yourself Any idea ? Marion Noirbent,

May 17, 2016

Re: [Pharo-users] Spec layout

by Peter UhnÃ¡k

I don't have time right now to give you a proper exampleâ¦ however if you have layout on the instance side, then you need to call the build method explicitly with the proper layoutâ¦ well, that's what I do at least https://github.com/dynacase/dynacase/blob/master/repository/DynaCASE-Spec.p… https://github.com/dynacase/dynacase/blob/master/repository/DynaCASE-Spec.p… On Tue, May 17, 2016 at 6:48 PM, Marion Noirbent < ms.noirbent(a)etudiant.univ-lille1.fr> wrote: > Hi, > I'm trying to create a widget whith Spec, managing a collection of > RadioButton. But I have a problem with defaultSpec (the accessor of the > collection is the methods "buttons") : > > If i put defaultSpec on class side, i can't acces the collection of the > instance. (the following code iterate on the string) > > defaultSpec > <spec: #default> > ^ SpecLayout composed > newColumn: [ :column | #buttons do: [ :item | column add: > item ] ]; > yourself > > If i put it on instance side, the lookup don't find it (in the book > Building UI with Spec, it said the lookup begin by the instance side and it > allow to have specific UI, in part about layout) > > defaultSpec > <spec: #default> > ^ SpecLayout composed > newColumn: [ :column | self buttons do: [ :item | column > add: item ] ]; > yourself > > Any idea ? > > Marion Noirbent, > >

May 17, 2016

Re: [Pharo-users] On Class and Method comments

by Peter UhnÃ¡k

> Now, I only know that comments in block closures are placed behind the > block code. > Do you know more examplmes where the formatter still misplaces the comment. Maybe just comments now? I've added a formatting configuration that preserved vertical white space (and I believe also comment position, because I used to write inline comments), but I think it was lost during migration to BlueInk. But I'll have a look. On Tue, May 17, 2016 at 5:32 PM, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: > On 05/17/2016 01:40 AM, Peter UhnÃ¡k wrote: > > As a note, maybe try to avoid inline comments unless formatter is fixed, > because autoformatting _will_ misplace them. (Not to mention that imho > inline comments in Smalltalk are a result of a bad designâ¦ if you need an > inline comment, maybe turn that into actual code). > > > I disagree with the comment about inline comments being bad design. At > least as a broadly applied as the above was. > > Comments often say "Why" we did something. Code says "How" or "What" we > are doing. I have encountered many times where if I did not have a comment > for the "Why". Then at a later date when I don't remember the "Why". I > encounter code that looks strange and I am tempted to refactor and > consequently would introduce bugs. > This doesn't necessarily dispute my point. If you need to have inline comments then you are most likely doing in the method more then you should, otherwise you can just put the intent in the method comment. Of course in real world we have looooong methods in both ancient and (unfortunately) new systems, and adding a comment is better then nothing. Assuming of course, that the comment is correctâ¦ because a wrong or misleading comment can do more harm than goodâ¦ that's why I _personally_ (thus the imho in the original note) prefer code over comments. Because code is what actually happens. And finally I rarely (unless the method is a real mess) have problem understanding a single method (I can poke it, look at tests, go through the code, ...). What I usually lack is high-level overview that would tell me how the system overall works. That you cannot read from method (or class) comments. > Right now I am working on parsing a bunch of xml files. Third party data > sources. > Is it XML or XMI? Couple of weeks back a wrote a simple utility for Synectique to help with analyzing and processing XMI files. Maybe it could help you a bit https://github.com/peteruhnak/xmi-analyzer ? > There is ugliness in the world. I have to clean the ugliness in order to > be able to parse the files. There is no option if I want to do this. I have > no control over the sources. I am not interested in engaging outside > bureaucratic policies and people in order to change their procedures and > policies so that I can have better sources. How often would I be willing to > fight this losing battle. > > The only solution is to do ugly things, for good reasons and comment them > well. So that I know not just what I did, but why. > > I also believe there is some conflicting policy in the code critic or > whatever is telling me my method is too long. > > I have frequently written methods that had a few temp vars with nice > informative names. and the method is involved enough to use these vars > multiple times. I get this nice information informing me my method is long. > Or in Pharo4 going yellow and then red. :) > > However many times if I made these vars short, like x, y, z. Then the > method is a perfectly fine length. Ugh. I am then being punished for length > of names. I have seen this a lot. > Well Code Critic doesn't force you to do all these things. But every time you transgress the rule you should consider whether it's worth it. (And maybe even auto-ignore the rule.) > In any case, there are no guidelines afaikâ¦ otherwise we would have > comments everywhere already. :) > > > Not necessarily. People are busy. Sometimes getting working code out is > more important than commenting it well. > > For example. And I am not saying this is true. It is simply and example. > While pressure is mounting to release Pharo 5. The few over worked people > involved in that final process. Finishing up the final things, might be > pragmatic and let working code go without comments. Or in some similar > situation by a code contributor. > > Then their are people like myself and Dimitris who might not feel > confident in submitting comments for some of these areas without > appropriate guidelines. We want to improve the situation not make bad > examples of what not to do. :) > > Just some of my opinions. > And finally there is never one rule that would fit all, and any guideline or whatever will find an edge case. But Pharo is moving fastâ¦ so I don't see why you wouldn't feel confident about commenting. The worst case scenario is that something breaks and we have a chance to learn something from the mistake. Peter > > > Jimmie > > > Perhaps one thing regarding class comments: There was a push to use PIllar > there if you need formatting, but I am not sure what is the current status > of that. > > Peter > > On Tue, May 17, 2016 at 12:04 AM, Dimitris Chloupis < > <kilon.alios(a)gmail.com>kilon.alios(a)gmail.com> wrote: > >> I really like to start writing some class and method comments to make >> Pharo image more beginner friendly. Are there any guidelines when and how >> to comment classes and methods ? What about inline comments ? >> > > >

May 17, 2016

Re: [Pharo-users] On Class and Method comments

by Jimmie Houchin

On 05/17/2016 01:40 AM, Peter UhnÃ¡k wrote: > As a note, maybe try to avoid inline comments unless formatter is > fixed, because autoformatting _will_ misplace them. (Not to mention > that imho inline comments in Smalltalk are a result of a bad designâ¦ > if you need an inline comment, maybe turn that into actual code). I disagree with the comment about inline comments being bad design. At least as a broadly applied as the above was. Comments often say "Why" we did something. Code says "How" or "What" we are doing. I have encountered many times where if I did not have a comment for the "Why". Then at a later date when I don't remember the "Why". I encounter code that looks strange and I am tempted to refactor and consequently would introduce bugs. Right now I am working on parsing a bunch of xml files. Third party data sources. There is ugliness in the world. I have to clean the ugliness in order to be able to parse the files. There is no option if I want to do this. I have no control over the sources. I am not interested in engaging outside bureaucratic policies and people in order to change their procedures and policies so that I can have better sources. How often would I be willing to fight this losing battle. The only solution is to do ugly things, for good reasons and comment them well. So that I know not just what I did, but why. I also believe there is some conflicting policy in the code critic or whatever is telling me my method is too long. I have frequently written methods that had a few temp vars with nice informative names. and the method is involved enough to use these vars multiple times. I get this nice information informing me my method is long. Or in Pharo4 going yellow and then red. :) However many times if I made these vars short, like x, y, z. Then the method is a perfectly fine length. Ugh. I am then being punished for length of names. I have seen this a lot. > In any case, there are no guidelines afaikâ¦ otherwise we would have > comments everywhere already. :) Not necessarily. People are busy. Sometimes getting working code out is more important than commenting it well. For example. And I am not saying this is true. It is simply and example. While pressure is mounting to release Pharo 5. The few over worked people involved in that final process. Finishing up the final things, might be pragmatic and let working code go without comments. Or in some similar situation by a code contributor. Then their are people like myself and Dimitris who might not feel confident in submitting comments for some of these areas without appropriate guidelines. We want to improve the situation not make bad examples of what not to do. :) Just some of my opinions. Jimmie > Perhaps one thing regarding class comments: There was a push to use > PIllar there if you need formatting, but I am not sure what is the > current status of that. > > Peter > > On Tue, May 17, 2016 at 12:04 AM, Dimitris Chloupis > <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > > I really like to start writing some class and method comments to > make Pharo image more beginner friendly. Are there any guidelines > when and how to comment classes and methods ? What about inline > comments ? > >

May 17, 2016

Re: [Pharo-users] On Class and Method comments

by Nicolai Hess

2016-05-17 8:40 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > As a note, maybe try to avoid inline comments unless formatter is fixed, > because autoformatting _will_ misplace them. > There were some fixes to make this better. Now, I only know that comments in block closures are placed behind the block code. Do you know more examplmes where the formatter still misplaces the comment. > (Not to mention that imho inline comments in Smalltalk are a result of a > bad designâ¦ if you need an inline comment, maybe turn that into actual > code). > > In any case, there are no guidelines afaikâ¦ otherwise we would have > comments everywhere already. :) > > Perhaps one thing regarding class comments: There was a push to use PIllar > there if you need formatting, but I am not sure what is the current status > of that. > > Peter > > On Tue, May 17, 2016 at 12:04 AM, Dimitris Chloupis <kilon.alios(a)gmail.com > > wrote: > >> I really like to start writing some class and method comments to make >> Pharo image more beginner friendly. Are there any guidelines when and how >> to comment classes and methods ? What about inline comments ? >> > >

May 17, 2016

Re: [Pharo-users] On Class and Method comments

by Peter UhnÃ¡k

As a note, maybe try to avoid inline comments unless formatter is fixed, because autoformatting _will_ misplace them. (Not to mention that imho inline comments in Smalltalk are a result of a bad designâ¦ if you need an inline comment, maybe turn that into actual code). In any case, there are no guidelines afaikâ¦ otherwise we would have comments everywhere already. :) Perhaps one thing regarding class comments: There was a push to use PIllar there if you need formatting, but I am not sure what is the current status of that. Peter On Tue, May 17, 2016 at 12:04 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > I really like to start writing some class and method comments to make > Pharo image more beginner friendly. Are there any guidelines when and how > to comment classes and methods ? What about inline comments ? >

May 17, 2016

Retina support in Pharo

by markm

Hi Is it possible to get Pharo (4 or 5) to run with retina support on OS X? I have tried searching for some answers, but alas could only find a handful of posts from a few years back. Any help much appreciated! Mark -- View this message in context: http://forum.world.st/Retina-support-in-Pharo-tp4895245.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 17, 2016

On Class and Method comments

by Dimitris Chloupis

I really like to start writing some class and method comments to make Pharo image more beginner friendly. Are there any guidelines when and how to comment classes and methods ? What about inline comments ?

May 16, 2016

Re: [Pharo-users] TextAction bugs

by stepharo

Hi all :) > Hi All, > > TextAction appears to have a couple of issues: > > > TextAction>>actOnClick: anEvent for: anObject in: paragraph editor: editor > "sent when a user clicks on a piece of text to which I am applied in an editor" > > "may be self is included in the event or an Object. " > ^ actOnClickBlock cull: self cull: anEvent cull: anObject cull: paragraph cull: editor To me this use of cull: is plain plain plain bad. cull: is a plague. People use is far too often. It indicates a lack of - design - object because with one object the block would get it and select what is needed. - then I do not get why we need to pass the paragraph and the editor > #cull:cull:cull:cull:cull: doesn't exist, so should be something like: > > > TextAction>>actOnClick: anEvent for: anObject in: paragraph editor: editor > "sent when a user clicks on a piece of text to which I am applied in an editor" > > "may be self is included in the event or an Object. " > ^ actOnClickBlock valueWithEnoughArguments: (Array with: self with: anEvent with: anObject with: paragraph with: editor) it looks already better. > > > It is also missing the Rubric version: > > > TextAction>>rubActOnClick: anEvent for: anObject in: paragraph editor: editor > "sent when a user clicks on a piece of text to which I am applied in an editor" > > "may be self is included in the event or an Object. " > ^ actOnClickBlock valueWithEnoughArguments: (Array with: self with: anEvent with: anObject with: paragraph with: editor) > > > I've followed the convention in the other implementations of > #rubActOnClick:for:in:editor: and reimplemented the code, but it could > just as easily call #actOnClick:for:in:editor:. > > Any reason not to submit this as a formal bug report? > > Should it be submitted as two separate bug reports since they are in > separate packages? > > Thanks! > Alistair > >

May 16, 2016

Re: [Pharo-users] TextAction bugs

by Alistair Grant

On Mon, May 16, 2016 at 01:42:16PM +0200, Nicolai Hess wrote: > 2016-05-16 8:29 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > > Hi All, > > TextAction appears to have a couple of issues: > > > TextAction>>actOnClick: anEvent for: anObject in: paragraph editor: editor > Â Â Â Â "sent when a user clicks on a piece of text to which I am applied > in an editor" > > Â Â Â Â "may be self is included in the event or an Object. " > Â Â Â Â ^ actOnClickBlock cull: self cull: anEvent cull: anObject cull: > paragraph cull: editor > > > #cull:cull:cull:cull:cull: doesn't exist, so should be something like: > > > TextAction>>actOnClick: anEvent for: anObject in: paragraph editor: editor > Â Â Â Â "sent when a user clicks on a piece of text to which I am applied > in an editor" > > Â Â Â Â "may be self is included in the event or an Object. " > Â Â Â Â ^ actOnClickBlock valueWithEnoughArguments: (Array with: self with: > anEvent with: anObject with: paragraph with: editor) > > > It is also missing the Rubric version: > > > TextAction>>rubActOnClick: anEvent for: anObject in: paragraph editor: > editor > Â Â Â Â "sent when a user clicks on a piece of text to which I am applied > in an editor" > > Â Â Â Â "may be self is included in the event or an Object. " > Â Â Â Â ^ actOnClickBlock valueWithEnoughArguments: (Array with: self with: > anEvent with: anObject with: paragraph with: editor) > > > I've followed the convention in the other implementations of > #rubActOnClick:for:in:editor: and reimplemented the code, but it could > just as easily call #actOnClick:for:in:editor:. > > Any reason not to submit this as a formal bug report? > > Should it be submitted as two separate bug reports since they are in > separate packages? > > > There is already a bug report for the first issue you described: > 18200 > TextAction calls unimplemented method #cull:cull:cull:cull:cull: Sigh, guilty (and embarrassed) about not checking the bug tracker first. It looks like there isn't a fix proposed (I couldn't see it in the bug report or in Pharo60Inbox), so if you don't have any objection I'll add my proposed fix. I also couldn't find any reference to the second issue, so will raise a new issue and submit the proposed fix. Thanks for pointing this out, Alistair

May 16, 2016