- Pharo-dev - lists.pharo.org

[Pharo-project] displaying tags

by Tudor Girba

Hi, I would like to display a tag in the form of a button that is smaller and less prominent than a usual button. See the attached picture for an example taken from the Things program running on Mac. I want to use these tags next to items in in lists or trees, so, ideally the size of the button would be the size of the regular font of a list entry. I looked in the UITheme class, but I could find anything that would resemble this look. Is there someone that has already done this? Otherwise does anyone have suggestions? Cheers, Doru -- www.tudorgirba.com "Beauty is where we see it."

Sept. 13, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by Andrey Larionov

I mean this presentation http://vst.ensm-douai.fr/ESUG2009Media/uploads/1/obEnhancements.ppt On slide Dynamic Navigation there are icons for nvagating across the code. On Sat, Sep 12, 2009 at 23:06, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> In past ESUG media (presentation slides) i saw and briliant example of >> enchancing Shout (or paragraph editor) with interactive icons. Is this >> work incomplete or it can be observed? Â In presentation it was named >> OBEnchancments, but i didnt saw any of this features in Squeak or >> Pharo. > > I do not know. > Now what you have with OB (since lukas push the idea there), is that > you can use the icons > to navigate the class hierarchy and laucnh tests and others. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 13, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by Douglas Brebner

StÃ©phane Ducasse wrote: > I agree. :) > I would love to have that. > this is why we should really have a system to experiment these ideas. > > The Glamour framework looks useful for browser experimentation. I would really like a modern version of the Whisker browser Doug Way created. > On Sep 12, 2009, at 6:15 PM, Philippe Marschall wrote: > > >> StÃ©phane Ducasse wrote: >> >>> well for this we will have to rewrite paragraphEditor :) >>> So in making pharo moves forward we will have to accept losing some >>> feedback. >>> >> The feedback is still there. The piece of code is still marked as a >> problem. It just doesn't get in your way. >> >> >>> But yes your idea is cool. >>> >> You'll have to do more than that. I think this whole 80ies style >> browser >> that's based on scrolling, clicking and popups doesn't cut it anymore >> and adding more tabs and buttons isn't gonna fix it. >> >> Example, why is the browser the size it currently is? Because that was >> more or less full screen in the 80ies. Consequence you'll always >> have to >> resize and scroll when you open a browser because the category and >> class >> panes are too small. I see how this was cool, exciting and new in the >> 80ies but today it gets in my way. >> >> Example, I want to go to a method in a class. Either I click '--all--' >> and scroll, scroll, look, scroll, scroll back or I click through the >> protocols until I found on it. When I'm in Eclipse and want to open a >> variable or method declaration I hit Ctrl + O, Eclipse shows me a >> short >> outline of the class. Like in Firefox Awesome Bar it filters the >> list as >> I type part of the name. Once I select something it closes and goes >> there. Zero mouse activity. Zero additional window. When I'm in a >> method >> and want to go to a method invoked there either I Ctrl + click it or I >> hit F3. When I want to see the hierarchy of a class or the inheritance >> of a method I just do Ctrl + T and an inline window opens. It closes >> when I select something or hit Esc. Pharo stacks so many windows on >> top >> of each other that you're never going to find your way back. So at the >> end of the day you just close dozens of windows. >> >> Short anecdote, I our current project we don't ask the user for >> confirmation, ever. If he decides to delete Migros, we do it without >> asking. The previous version of the product did but users just >> developed >> a reflex to click popups away without even reading them. >> >> And don't get me started on breakpoints. Or blocking the UI. >> >> Cheers >> Philippe >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

Sept. 12, 2009

Re: [Pharo-project] Problems with MC (was Re: May be some problems with MC history)

by Michael Roberts

get better soon! ok i said this in a mail but for this thread I think your second package version is empty. however if I merge 321 from the trunk (carefully!! i.e hand install MCPackageLoader first) then I can load a modified MC version of Eliot's #2 that I made. i will go through all of eliot's fixes tonight. this is progress. check updates to the tracker for each one. cheers, Mike On Sat, Sep 12, 2009 at 8:36 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I just publish a couple of MC packages in the inbox > > Â Â Â Â one just to fix a bad reference to ChangeSorter instead of > ChangesOrganizer (not needed so far) > Â Â Â Â one for 309 (which was a kind of changes to support atomic loading) > but did not really helped > Â Â Â Â one for 321 where andreas patched that so that they could load > closure fixes > Â Â Â Â one with installAll menu in MCPatchBrowser :) > > So let me know if this is working. > I could load eliot fixes for kernel (package two = step two of the > eight) without problem. > > Stef (now I'm sick so going to bed). > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 12, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by Schwab,Wilhelm K

Stef, ... And selecting an item from that log highlights the offending code. The context menu for the log includes help on the violated rule. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Saturday, September 12, 2009 2:38 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] getting rid of these boring questions and popup yeap good idea. A kind of log console. Stef >> >>> Stef, >>> >>> Yes, the popups should go away - far away :) A code mentor pane >>> with lint rule violations would be greatly appreciated, but the >>> modal messages are too much. Sometimes I want to save code that I >>> know will generate errors, with reasons ranging from "I'll let it >>> blow up and choose to implement it from the debugger" to "don't want >>> to lose this, so let's get it accepted before I do something >>> stupid." >> >> same here! >> At least we have a common vision and we can go slowly there. >> > > I having the same vision. Browser should not prevent you from > accepting the badly crafted code. It should allow it unless there is > syntax errors. > All warnings, like unused temps, use of unassigned temps etc, should > pop-up in a list pane below the code pane, so user could see it and > react, or just ignore and go & do something else. Btw, this pane could > be reused for more deeper/complex code analyzing tools, like lint etc. > >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 12, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by StÃ©phane Ducasse

yeap good idea. A kind of log console. Stef >> >>> Stef, >>> >>> Yes, the popups should go away - far away :) A code mentor pane >>> with lint rule violations would be greatly appreciated, but the >>> modal messages are too much. Sometimes I want to save code that I >>> know will generate errors, with reasons ranging from "I'll let it >>> blow up and choose to implement it from the debugger" to "don't want >>> to lose this, so let's get it accepted before I do something >>> stupid." >> >> same here! >> At least we have a common vision and we can go slowly there. >> > > I having the same vision. Browser should not prevent you from > accepting the badly crafted code. It should allow it > unless there is syntax errors. > All warnings, like unused temps, use of unassigned temps etc, should > pop-up in a list pane below the code pane, > so user could see it and react, or just ignore and go & do something > else. Btw, this pane could be reused for more deeper/complex > code analyzing tools, like lint etc. > >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 12, 2009

Re: [Pharo-project] Problems with MC (was Re: May be some problems with MC history)

by StÃ©phane Ducasse

I just publish a couple of MC packages in the inbox one just to fix a bad reference to ChangeSorter instead of ChangesOrganizer (not needed so far) one for 309 (which was a kind of changes to support atomic loading) but did not really helped one for 321 where andreas patched that so that they could load closure fixes one with installAll menu in MCPatchBrowser :) So let me know if this is working. I could load eliot fixes for kernel (package two = step two of the eight) without problem. Stef (now I'm sick so going to bed).

Sept. 12, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by Igor Stasenko

2009/9/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Sep 11, 2009, at 11:32 PM, Schwab,Wilhelm K wrote: > >> Stef, >> >> Yes, the popups should go away - far away :) Â A code mentor pane >> with lint rule violations would be greatly appreciated, but the >> modal messages are too much. Â Sometimes I want to save code that I >> know will generate errors, with reasons ranging from "I'll let it >> blow up and choose to implement it from the debugger" to "don't want >> to lose this, so let's get it accepted before I do something stupid." > > same here! > At least we have a common vision and we can go slowly there. > I having the same vision. Browser should not prevent you from accepting the badly crafted code. It should allow it unless there is syntax errors. All warnings, like unused temps, use of unassigned temps etc, should pop-up in a list pane below the code pane, so user could see it and react, or just ignore and go & do something else. Btw, this pane could be reused for more deeper/complex code analyzing tools, like lint etc. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Sept. 12, 2009

Re: [Pharo-project] Problems with MC (was Re: May be some problems with MC history)

by StÃ©phane Ducasse

On Sep 12, 2009, at 8:51 PM, Michael Roberts wrote: > Stef, we need the changes to MCPackageLoader>>basicLoad from Squeak > trunk. It does a lot more to ensure correct loading of classes and > methods. Our version assumes all additions are the same, both new > methods and changes to existing methods. it's this assumption that > causes the blow up of loading a (pharo compatible) Kernel-eem.242. I > have tested that our version definitely can't load the closure fixes. > > I will start pulling MC changes in and see how it goes. You already > started a review of Pharo version of MC? Oh yes! This is why I started. I missed the changes in 3.10 this is why originally I said that there were no change changing the semantics. So what is left on my plate is 309 and 321. I will send them to you in a minute as cs so that you can try. Stef

Sept. 12, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by StÃ©phane Ducasse

> In past ESUG media (presentation slides) i saw and briliant example of > enchancing Shout (or paragraph editor) with interactive icons. Is this > work incomplete or it can be observed? In presentation it was named > OBEnchancments, but i didnt saw any of this features in Squeak or > Pharo. I do not know. Now what you have with OB (since lukas push the idea there), is that you can use the icons to navigate the class hierarchy and laucnh tests and others.

Sept. 12, 2009