March 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 1.4] #14383

by Camillo Bruni

:) cool that it works! :) On 2012-03-09, at 10:04, StÃ©phane Ducasse wrote: > Thanks Ben, Camillo and Marcus. > I should sit with you and see how it works > - when we have to rollback :) > - modify the submission > and I will use it - believe me. > > >> Now, to integrate a fix a generate a new Pharo version, they just have to execute on script which take the issues number as parameter :) >> >> And then, everything is fully automatic (even running the tests ;) ) >> >> >> >> Ben >> >> On Mar 8, 2012, at 2:22 PM, Sven Van Caekenberghe wrote: >> >>> >>> On 08 Mar 2012, at 14:15, Marcus Denker wrote: >>> >>>> The automatic integrator is nearly working! >>> >>> I really hope for you that it makes the integrator work lighter. >>> >>> Sven >> >> > >

March 9, 2012

Re: [Pharo-project] ClassBuilder depending -in some way- on text

by Igor Stasenko

On 9 March 2012 04:28, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > On Thu, Mar 8, 2012 at 5:17 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 9 March 2012 01:22, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>> ClassBuilder>>validateClassName: aString > ... >>> Â Â Â Â Â Â Â Â Â self notify: aString asText allBold, >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ' already exists!\Proceed will store over it.' >>> >>> Is it right to do that asText allBold there? :S >>> Shouldn't an exception be raised instead? >>> >>> Do I open a ticket? >>> >> Yes. >> We should kill dependency by removing asText asBold. >> Notifications should not accept rich-formatted text anyways, >> because not all ui managers can handle it Â (now we having command-line >> ui manager >> which prints message on console). >> > Maybe have the command-line ui manager dumb down the representation - > I'm sure this isn't the only place. > > Guille, > this likely pre-dates Exceptions (or at least wide-spread use of > them). Â A much better direction is to use exceptions (or > Announcements?) here, and have a process capture them and display > appropriately for what they can display. The mechanism should probably > include Class name and exception text, which could be rich-formatted > as above, or plain formatted for command-line UI, or interrogated for > other observers. > if you replace it with exception, it doesn't means that exception should use text and bold.. so... > Just suggestions. > > -Chris > -- Best regards, Igor Stasenko.

March 9, 2012

Re: [Pharo-project] ClassBuilder depending -in some way- on text

by StÃ©phane Ducasse

the beauty of layer tangling! I love that you have a look at that. I realllllly mean it. Everyday we are getting closer to a nice and modular system (even if I got bashed by people not believe the effort we spent on that). Stef > ClassBuilder>>validateClassName: aString > "Validate the new class name" > | allowed | > aString isSymbol > ifFalse: [ ^ false ]. > allowed := ($0 to: $9), {$_}, ($A to: $Z), ($a to: $z). > (aString detect: [:c | (allowed includes: c) not] ifNone: [ ]) > ifNotNil: [ :c | self error: 'Invalid character: ''', c printString, ''''. > ^ false]. > aString first canBeGlobalVarInitial ifFalse:[ > self error: 'Class names must be capitalized'. > ^false]. > environ at: aString ifPresent:[:old| > (old isKindOf: Behavior) ifFalse:[ > self notify: aString asText allBold, > ' already exists!\Proceed will store over it.' withCRs]]. > ^ true > > > Is it right to do that asText allBold there? :S > Shouldn't an exception be raised instead? > > Do I open a ticket? > > Guille

March 9, 2012

Re: [Pharo-project] Ullyse the Monkey not mailing?

by Marcus Denker

On Mar 9, 2012, at 10:13 AM, Marcus Denker wrote: > > On Mar 9, 2012, at 10:04 AM, Pavel Krivanek wrote: > >> Hi, >> >> I see the next updates on CI server (14384, 14385, 14386) but no >> report on the mailing list. Some problems with mails? > > Yes... testing the integration scritps. > > > 14384 > ----- > > The following changes have been integrated: > > Issue 5442: FSFilesystem should continue to provide onDisk and inMemory > http://code.google.com/p/pharo/issues/detail?id=5442 No: 14384 was: Issue 5450: Number does not implement #asFloat http://code.google.com/p/pharo/issues/detail?id=5450 -- Marcus Denker -- http://marcusdenker.de

March 9, 2012

Re: [Pharo-project] more Nautilus feed back

by StÃ©phane Ducasse

>> 1) OB had double-click action: show hierarchy. I miss it a lot :( > > If you activate the "open a class on hierarchy" setting, it does the same :) why not by default and reduce setting (each time you kill a setting you can be happy). >> Also, hierarchy button is too far away when I want to see the hierarchy... ok, if you don't want to add double click functionality... can it be a menu option? (show hierarchy (h)) > > Maybe I should switch the group button and the hierarchy button. It will make more sense :) > >> Even worst: it swaps panels which is very confusing... but that leads to point 2 :) > > There are some good arguments to do that :) But I am quite fed up to tell them again and again ^^ but may be it means that people are right too :) > >> 2) swap panel configuration is not working for me in latest pharo 1.4 > > Ie ? > >> 3) I find "Class", "Instance" buttons very confusing. I liked more the older solution but well, I understand you want to improve visibility of comments, but then, I think class button would be better as a "toggle" button (those buttons who stays pressed) > > Do you have an example of such a button ? Probably instance|Class and when you are on instance side the instance is pushed. >> 5) OB had a #browserIcon method on classes who changed class icon on browser. This is really useful for knowing different types/hierarchies like errors, announcements, morphs, etc. Again, this collides with "uncommented" icon, but I would like to have them back... > > There are icons for Morph/Erros/Announcements/Magnitude/String/Collection/etc... But maybe I could also add a mechanism to let each class defines it's own icon. pay attention to speed :). But yes I do not know how this is implemented right now. Now DO NOT LET PEOPLE NOT COMMENT THEIR $^%&*() CLASS. GUYS IF WE WANT COOL ICONS => WRITE COMMENTS If we all sit down and write decent comments then we will have both: a nicer system and sexy icons. So for me the choice is clear. Focus on your exams :)

March 9, 2012

Re: [Pharo-project] Ullyse the Monkey not mailing?

by Marcus Denker

On Mar 9, 2012, at 10:04 AM, Pavel Krivanek wrote: > Hi, > > I see the next updates on CI server (14384, 14385, 14386) but no > report on the mailing list. Some problems with mails? Yes... testing the integration scritps. 14384 ----- The following changes have been integrated: Issue 5442: FSFilesystem should continue to provide onDisk and inMemory http://code.google.com/p/pharo/issues/detail?id=5442 14385 ----- The following changes have been integrated: Issue 5442: FSFilesystem should continue to provide onDisk and inMemory http://code.google.com/p/pharo/issues/detail?id=5442 14386 --- Issue 3950: SequenceableCollection>>#findBinary and friends (wrong exceptionBlock, delegation) http://code.google.com/p/pharo/issues/detail?id=3950 -- Marcus Denker -- http://marcusdenker.de

March 9, 2012

Re: [Pharo-project] more Nautilus feed back

by StÃ©phane Ducasse

Ben focus on your exams! No fun pharo hacking. Stef On Mar 8, 2012, at 11:24 PM, Benjamin wrote: > > On Mar 8, 2012, at 8:25 PM, Esteban Lorenzano wrote: > >> Hi, >> >> I'm using Nautilus for my current projects since... well... couple of days, and I have some feedback: >> >> (yeah... maybe they are dumb reports, but that's because you did a great work with nautilus, I just have some really small observations :) >> >> 1) OB had double-click action: show hierarchy. I miss it a lot :( > > If you activate the "open a class on hierarchy" setting, it does the same :) > >> Also, hierarchy button is too far away when I want to see the hierarchy... ok, if you don't want to add double click functionality... can it be a menu option? (show hierarchy (h)) > > Maybe I should switch the group button and the hierarchy button. It will make more sense :) > >> Even worst: it swaps panels which is very confusing... but that leads to point 2 :) > > There are some good arguments to do that :) But I am quite fed up to tell them again and again ^^ > >> 2) swap panel configuration is not working for me in latest pharo 1.4 > > Ie ? > >> 3) I find "Class", "Instance" buttons very confusing. I liked more the older solution but well, I understand you want to improve visibility of comments, but then, I think class button would be better as a "toggle" button (those buttons who stays pressed) > > Do you have an example of such a button ? > >> 4) bold for class side method and categories is too strong, I don't see any reason for that, we have panel titles and future ;) toggle button to know which side is. > > Some people (Laurent not toell who) complain about the lack of visibility. And indeed, I found than when you have multiples browsers, it helps a lot to find where you are in a second. > >> 5) OB had a #browserIcon method on classes who changed class icon on browser. This is really useful for knowing different types/hierarchies like errors, announcements, morphs, etc. Again, this collides with "uncommented" icon, but I would like to have them back... > > There are icons for Morph/Erros/Announcements/Magnitude/String/Collection/etc... But maybe I could also add a mechanism to let each class defines it's own icon. > >> 6) I'm sorry for saying this, but I don't like the icons, nor the colored options (source, bytecode, decompiled, etc.) at the side. I would prefer a combo on button panel... and better looking icons (yes Stef, FamFam icons is ok :) > > I will be really glad to use yours :) You know, I am kind of a programmer. It means that making icons is not my work. And due to that, it takes me ages to do them. > I have no problem to change them at all, but I really don't have time to do them. > >> 7) Why we have a button panel (which is in fact a toolbar) in the middle of the browser and not where it belongs: on top? this is a remain of OB, who took this from old Browser... but conceptually (as in usability terms), this is a not-good solution. We could think on change this and place the button bar where it belongs (and add some cool keybindings too) > > You can't say that the hierarchy button is to far, and ask for putting the toolbar on top ^^ > It's here because it's close to the lists (where you spend 20% of your time) and also close to the source code (where you spend 80% of your time). > >> 8) different sized buttons are a really bad concept. Yes... in Smalltalk this is very common: to create buttons with the size of text... but this is bad design because disrupts harmony, and that hurts to the eyes... and when something hurts, you try not to use it :) > > I can't agree more. But buttons are kind of a pain in the ass (because they are embedded into a group morph with its own layout etc). As soon as I can set > vResizing: #rigid; hResizing: #rigid, I'll do it for sure ^^ > >> >> yeah.. most of my observations are also for any other tool we have, and most are about usability... I humbly recommend (for all people doing GUIs), the lecture of this book: http://en.wikipedia.org/wiki/Don't_Make_Me_Think. It is for web design, but is also a great guide when you want to make things people like. >> >> (Also, reading apple design guide is a good way to notice some interesting things... those guys had invest an insanely amount of time and money in development them) >> > > I will try to find time to read them, but as I said, my exams are in 11 days so ;) > > > Thanks for the feedback :) > > Ben > >> best, >> Esteban >> >

March 9, 2012

[Pharo-project] Ullyse the Monkey not mailing?

by Pavel Krivanek

Hi, I see the next updates on CI server (14384, 14385, 14386) but no report on the mailing list. Some problems with mails? -- Pavel

March 9, 2012

Re: [Pharo-project] [update 1.4] #14383

by StÃ©phane Ducasse

Thanks Ben, Camillo and Marcus. I should sit with you and see how it works - when we have to rollback :) - modify the submission and I will use it - believe me. > Now, to integrate a fix a generate a new Pharo version, they just have to execute on script which take the issues number as parameter :) > > And then, everything is fully automatic (even running the tests ;) ) > > > > Ben > > On Mar 8, 2012, at 2:22 PM, Sven Van Caekenberghe wrote: > >> >> On 08 Mar 2012, at 14:15, Marcus Denker wrote: >> >>> The automatic integrator is nearly working! >> >> I really hope for you that it makes the integrator work lighter. >> >> Sven > >

March 9, 2012

Re: [Pharo-project] Testing Morphic Designer

by StÃ©phane Ducasse

On Mar 8, 2012, at 5:14 PM, Torsten Bergmann wrote: > Stef wrote: >> We are getting thereâ¦ >> Did you ever look at the code of both systems? > > No - not really. > >> I like the ui part now > > At least the videos look shiny ;) indeed and this is what I want don't get me wrong :) > >> yes we can express a model and given a spec we >> can create a complex widget > > Sounds like UI specs in VW. kind of > Do we have that already? In Spec But we built experiments and analyze them and iterated now we know that we are in good direction. > > However - a builder/placer should be the goal. > Writing specs by hand can get very complexâ¦ Yes but one step at a time and taking care of not creating yet another layer on top of another layer: - if widgets need some special behavior it should integrated - ... > > What I like about the videos from nullPointer is that > it satisfies the common workflow expectation known from > other UI builders (VisualStudio, Java IDEs): open the builder, > add some widgets, set some properties, double click > a button for the event handler, add code and run. You never modify one? i.e. reopen it and modify it? You never reuse a widget? Because for me I hate to have to reimplement something I already did. This is because benjmain was fed up doing all the time the same that he is so interested in Spec :). > But as you said - that says nothing about the implementation > under the hood. > > Bye > T. > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de >

March 9, 2012