December 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Inspector Gadget

by StÃ©phane Ducasse

It is not this is that the servers were migrated today and yesterday On Dec 5, 2008, at 3:28 PM, David Pennell wrote: > [this bounced yesterday] > > OK - where is the agreement? The link on http://code.google.com/p/pharo/wiki/LicenseAgreement > is broken. > > On Thu, Dec 4, 2008 at 4:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > +1 > send the code and sign the agreement :) > > Stef > On Dec 4, 2008, at 1:32 AM, David Pennell wrote: > > > We currently have both "inspect" and "explore". It would be nice to > > have one tool. I'd vote for "explore" as a base with some > > enhancements to pick up the useful features from "inspect". > > > > -david > > _______________________________________________ > > 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 > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 5, 2008

[Pharo-project] about UI

by StÃ©phane Ducasse

Hi I would like to ask you if you do not get the same proble, as me. When I do not know an application I try to clik on the pane to see if there is a menu and it is like blind testing... It would be great if the mouse would change when the pane can display a menu. Stef

Dec. 5, 2008

[Pharo-project] Fwd: UIMananger

by StÃ©phane Ducasse

Begin forwarded message: > From: "Igor Stasenko" <siguctua(a)gmail.com> > Date: December 5, 2008 9:37:30 AM CEST > To: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > Subject: Fwd: [Pharo-project] UIMananger > > i got strange error 'relay not permitted' when sending this mail to > pharo list. > So, i sending it to you. > > > ---------- Forwarded message ---------- > From: Igor Stasenko <siguctua(a)gmail.com> > Date: 2008/12/4 > Subject: Re: [Pharo-project] UIMananger > To: pharo-project(a)gforge.inria.fr > > > 2008/12/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Igor >> >> I was thinking about what you propose. I do not understand why a >> simple extension >> is not better. >> >> I do not understand why we should involved Smalltalk > > it can be different class playing as access point to tools registry. > why its better - because your code does not rely on specific classes, > which can be missing in image. > The idead is, that to get a service (or tool) you need to send a > message, without referring to specific class(es). > Then any installed packages may add/remove/replace entries in registry > and can be used directly by your code without any specific knownledge > about who or what is standing behind it. > >>> you write >>> >>> Smalltalk tools UIManager >>> >>> instead of >>> UIManager default >>> >>> or >>> Smalltalk tools browser >>> >>> instead of >>> SystemBrowser default >>> >>> it would be nice to see similar in UIManager, e.g. >>> >>> manager registerTool: #colorPicker class: MyCoolColorPicker. >>> >>> and then simply use: >>> >>> manager colorPicker new openInWorl >> >> I do not understand the gain of your approach. >> >> Stef >> >> _______________________________________________ >> 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. > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Dec. 5, 2008

[Pharo-project] Fwd: Migration INRIAGforge terminÃ©

by StÃ©phane Ducasse

Begin forwarded message: > From: <noreply(a)gforge.inria.fr> > Date: December 5, 2008 1:43:12 PM CEST > To: stephane.ducasse(a)inria.fr > Subject: Migration INRIAGforge terminÃ© > > Bonjour, > la migration INRIAGForge est terminÃ©e. > Les problÃ¨mes Ã©ventuels sont Ã signaler via help.et.gforge(a)inria.fr > > Merci pour votre comprÃ©hension, > L'Ã©quipe transversale INRIA GForge. > > ------------------------------------ > > Hello, > gforge migration is complete. > > If you encounter some problem, please send a email at help.et.gforge(a)inria.fr > > Thank you for your understanding, > INRIA GForge Team. > > ------------------------------------ > >

Dec. 5, 2008

Re: [Pharo-project] Inspector Gadget

by David Pennell

[this bounced yesterday] OK - where is the agreement? The link on http://code.google.com/p/pharo/wiki/LicenseAgreement is broken. On Thu, Dec 4, 2008 at 4:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > +1 > send the code and sign the agreement :) > > Stef > On Dec 4, 2008, at 1:32 AM, David Pennell wrote: > > > We currently have both "inspect" and "explore". It would be nice to > > have one tool. I'd vote for "explore" as a base with some > > enhancements to pick up the useful features from "inspect". > > > > -david > > _______________________________________________ > > 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 >

Dec. 5, 2008

[Pharo-project] Fwd: free fonts

by Damien Pollet

On Thu, Dec 4, 2008 at 22:09, Hilaire Fernandes <hilaire(a)ofset.org> wrote: > I agree with Damien, Bitsream Vera fonts really looks great, > especially with the freetype plugin. Acually I looked into that a bit more and I would definitely recommend the DejaVu version over Vera. Apparently Vera only covers latin scripts, while DejaVu has nice Unicode coverage. I guess for the shapes/weights they have in common they are virtually identical. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Dec. 5, 2008

Re: [Pharo-project] about vm dropping privileges

by Janko MivÅ¡ek

StÃ©phane Ducasse wrote: > "Dedicated web servers such as Apache drop > their root privileges after startup." > > So I was wondering why a SMalltalk VM cannot do the same? Here is how I managed to do that from a workspace after making a class LibC according to recent guidelines from Gerardo Richarte on squeak-dev: from Workspace: "be sure FFI is installed" "sudo ln -s /lib/libc-2.3.5.so /usr/local/lib/squeak/3.10-1/libc.so" "start Swazoo as root" libc := LibC new. libc setruid: 1000 euid: 1000 suid: 1000. "check that user is no more root" LibC code: Object subclass: #LibC instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'FFI-Unix' ... setruid: realUid euid: effectiveUid suid: savedUid <cdecl: long 'setresuid' (long long long) module: 'libc'> ^ self externalCallFailed ... The only problem is the path to libc library, which must be found linked manually (see sudo ln..). If VM can be modified to use it more directly... I hope this help a bit. Best regards Janko -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Dec. 5, 2008

Re: [Pharo-project] inspector gadget

by Simon Denier

On 4 dÃ©c. 08, at 07:15, Matthew Fulmer wrote: > On Wed, Dec 03, 2008 at 11:59:10PM -0600, David Pennell wrote: >> You can modify iVars in Explorer, but it doesn't update the display. > > How do you do that? using accessors in the bottom pane, which is not very intuitive because you dont see the result in the upper pane. Actually, it does update is you close/open again the tree. So I'm also interested in a merge of inspector and explorer, where the explorer would get the auto update and edit facilities of Inspector. And take whatever name you like. > > > In inspector, you select the ivar in the top-left pane, edit the > value in the top-right pane, and press alt-s. > > I didn't know explorer had anything similar. > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Simon

Dec. 5, 2008

Re: [Pharo-project] free fonts

by Hilaire Fernandes

I agree with Damien, Bitsream Vera fonts really looks great, especially with the freetype plugin. Since one week, I am now using Pharo with these fonts for development and it's incredibly confortable. Oh by the way it seems that it is only when I am using these fonts from my Linux distribution I can enjoy the beautifull rendering. So may be user now in Windows and Mac has never so how nice the rendering is with these fonts. I am using both Bitstream Vera Sans and Bitstream Vera Sans Mono. This last one is especially good for code to avoid reading confusion between 0O, l1 (see screenshot) When using the embedded Bitstream font, it seems the old not-so-nice True Type rendering is used. I saw that from the latest PharoPolymorphTT distribution where the original Bitstream Vera fonts are still there.. By the way, how to add a TT font in the image so it can be used by the FreeType rendering engine? Hilaire 2008/12/1 Damien Pollet <damien.pollet(a)gmail.com>: > On Sun, Nov 30, 2008 at 12:33, Adrian Lienhard <adi(a)netstyle.ch> wrote: >> I think Bitstream Vera Sans Mono would be quite good. > > Yes, especially since it has a full family of bold/italics and > variable-width sans/serif variants. > The DejaVu fonts are derived from Vera but have a condensed (less wide) version. > Also both have very good unicode coverage, so unless someone finds a > prettier alternative with the same technical qualities, I would say > the choice is rather obvious. > >> I slightly prefer Monaco, which is shipped with OS X, but I don't know its >> license (http://en.wikipedia.org/wiki/Monaco_(typeface)) > > I doubt you can redistribute it like that. > >> http://www.ms-studio.com/FontSales/anonymous.html which looks nice too. > > Yuck, looks like Courier and unknown license. > > For a single mono-space font, Inconsolata looks more like Monaco, is > under OFL, and has a bit more glyphs (up arrow). > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://blog.ofset.org/hilaire

Dec. 4, 2008

Re: [Pharo-project] inspector gadget

by John M McIntosh

Ok, well let me comment about a few usablity issues. Explorer is a heavy weight inspection book, you have it, inspect and don't forget basicInspect. When working with objects that are subclassed off of ProtoObject like the objective-c class I ended up with dragging lots of methods from Object into the subclass to support Explore. Lastly when dealing with complex objects with twisty interconnects, like in a Sophie book structure Explorer would cheerfully be helpful and run off to visual show lots of things likely forever... requiring a cmd-interrupt to seize back control. Ensuring there is a way to do basic inspect would be helpful in rare cases then. On 3-Dec-08, at 8:26 PM, David Pennell wrote: > I agree. > > Just to be clear - I use both because neither does all I need. > Explorer is my default choice, but if I need to look at the innards > of a String, I launch an Inspector. It seems like it would be easy > enough to fix these in Explorer and then make that the default > inspector. > > I'm just returning to Squeak after 8 years and wondering if there > are other reasons folks use Inspector instead of Explorer. > > -david -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Dec. 4, 2008