- Pharo-dev - lists.pharo.org

[Pharo-project] Shift pressed halos

by StÃ©phane Ducasse

I would really like to make the halos menu only showing up when we press shift and this for all the system. The halso are cool for mroph and duplicating window for example but they get in our way. http://code.google.com/p/pharo/issues/detail?id=367&colspec=ID%20Type%20Sta… Stef

Dec. 2, 2008

Re: [Pharo-project] FFI inside Pharo ?

by StÃ©phane Ducasse

Thanks! On Nov 30, 2008, at 1:54 PM, Michael Rueger wrote: > Igor Stasenko wrote: >> and besides: >> VMs is packaged with FFI as dynamic library. >> So, if you want extra safety - simply don't shipp your application >> with this DLL. >> But still, if you allow arbitrary code to run in your image, then >> what >> prevents script kiddie from doing following: > > the sandbox does that as it prevents writing of files in > "interesting" locations like the VM directory. > > I'm all for using FFI/Alien, what I really tried to make people > aware of is that by using FFI instead of plugins certain things > become more dangerous. For standalone and server applications not > loading any code from the outside this is not a problem at all. > > By using FFI we need to more aware though that we potentially open > up a Squeak application to buffer overflow attacks, something that > wasn't really possible before. > > So I didn't want to put any brakes on, but raise people's awareness > about security. It's a bit like with the Mac: just because hackers > haven't really cared about exploiting vulnerabilities doesn't mean > the Mac is safe. And we Smalltalkers have considered us to use the > Mac of programming languages and thus feeling safe for the longest > time ;-) > > Michael > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 2, 2008

Re: [Pharo-project] FileStream class>>old* methods

by Chris Cunningham

Yes, these are necessary. They refer to an existsing file (old) versus a non-existant file (the new prefixed methods). There are several uses of it, but in my images there are many, many uses of it. Of course, I really wanted to use #readOnlyFileNamed: in most of the cases that I've created - just missed that desired method when I found the old version. Chris

Dec. 2, 2008

Re: [Pharo-project] UIMananger

by Gary Chambers

Sounds good... just need a reasonable default set. I guess I can convince Pinesoft to release some of the Report Builder UI stuff wrt printing... Regards, Gary. ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Monday, December 01, 2008 5:47 PM Subject: Re: [Pharo-project] UIMananger >i started writing a new tool registry, where you don't need to > 'extend' protocol - you just simply registering/unregistering tools. > > Try it out. > - file in .st > - then .cs > > a tool registry completely resembles a ToolSet protocol. > But, in addition, it makes things more flexible: > > 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 openInWorld > > > > 2008/12/1 Gary Chambers <gazzaguru2(a)btinternet.com>: >> Do you all think it might be a good idea to extend the UIManager protocol >> to >> include things like colour pickers (and other, like print etc.)? >> I'm sure we can all think of things that would be desirable as standard >> "utility" dialogs. Best to get the interface in early to ensure adoption. >> >> Regards, Gary. >> >> >> >> _______________________________________________ >> 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 >

Dec. 1, 2008

Re: [Pharo-project] UIMananger

by Igor Stasenko

i started writing a new tool registry, where you don't need to 'extend' protocol - you just simply registering/unregistering tools. Try it out. - file in .st - then .cs a tool registry completely resembles a ToolSet protocol. But, in addition, it makes things more flexible: 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 openInWorld 2008/12/1 Gary Chambers <gazzaguru2(a)btinternet.com>: > Do you all think it might be a good idea to extend the UIManager protocol to > include things like colour pickers (and other, like print etc.)? > I'm sure we can all think of things that would be desirable as standard > "utility" dialogs. Best to get the interface in early to ensure adoption. > > Regards, Gary. > > > > _______________________________________________ > 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.

Dec. 1, 2008

Re: [Pharo-project] UIMananger

by Alexandre Bergel

It would make sense to me. Since there a finite number of widgets (that is not so big after all), best is to have one single place in the system to look for. That said without having looked at other GUI systems. I am wondering how this is done in ObjectiveC/Cocoa. Cheers, Alexandre On 1 Dec 2008, at 14:27, Gary Chambers wrote: > Do you all think it might be a good idea to extend the UIManager > protocol to include things like colour pickers (and other, like > print etc.)? > I'm sure we can all think of things that would be desirable as > standard "utility" dialogs. Best to get the interface in early to > ensure adoption. > > Regards, Gary. > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 1, 2008

[Pharo-project] UIMananger

by Gary Chambers

Do you all think it might be a good idea to extend the UIManager protocol to include things like colour pickers (and other, like print etc.)? I'm sure we can all think of things that would be desirable as standard "utility" dialogs. Best to get the interface in early to ensure adoption. Regards, Gary.

Dec. 1, 2008

Re: [Pharo-project] Re: FileList2 merged with FileList

by HernÃ¡n Morales Durand

Hi StÃ©phane, I'll send it to you this week. Best regards. HernÃ¡n 2008/11/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > hi hernan > > thanks for your contribution. > Could you sign the license agreement and send it to me :) > > Stef > > On Nov 29, 2008, at 11:44 PM, HernÃ¡n Morales Durand wrote: > > I forgot to mention, to install it: >> >> -Remove the Morphic-FileList category. >> -Evaluate: >> >> FileStream fileIn: 'Morphic-FileList.st'. >> FileStream fileIn: 'FileListNewReferences.st' >> >> 2008/11/29 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> >> Issue 269: >> http://code.google.com/p/pharo/issues/detail?id=269&q=FileList2&colspec=ID%… >> >> Attachements: >> Morphic-FileList.st contains FileList merged from old FileList and >> FileList2 >> Removed FileList2 references in FileListNewReferences.st >> >> Two issues: >> -It is possible to establish a preference for saving a method without >> modification of the authorship/annotation information ? >> -Why methods have authors but classes don't ? >> >> Cheers >> >> HernÃ¡n >> >> >> _______________________________________________ >> 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. 1, 2008

[Pharo-project] Fwd: [InriaGforge] Migration du service Gforge / Gforge service migration

by StÃ©phane Ducasse

english version below... Begin forwarded message: > From: <noreply(a)gforge.inria.fr> > Date: December 1, 2008 12:40:47 PM CEST > To: stephane.ducasse(a)inria.fr > Subject: [InriaGforge] Migration du service Gforge / Gforge service > migration > > Bonjour, > > Ainsi que cela a Ã©tÃ© annoncÃ© il y a quelques mois, le service > InriaGforge va subir un changement de plateforme matÃ©rielle et > logicielle, afin de vous offrir un service pÃ©renne et de meilleur > qualitÃ©. > La migration effective du service (de la plateforme actuelle vers la > nouvelle plateforme) est programmÃ©e pour le Jeudi 4 dÃ©cembre au matin. > Le retour du service Ã l'Ã©tat opÃ©rationnel est prÃ©vu pour le > vendredi 5 dÃ©cembre matin. > Durant cette pÃ©riode, la plateforme actuelle sera indisponible > Ã©galement. > L'equipe transversale tiens Ã rappeler quelques points importants > afin que cette opÃ©ration importante impacte le moins possible votre > travail : > - Prenez vos dispositions afin de ne pas dÃ©pendre du service > InriaGforge les 4 et 5 dÃ©cembre. > - Utilisation de Subversion : > - si la commande 'svn info' renvoit une URL dont le nom de domaine > diffÃ¨re de scm.gforge.inria.fr, vous devrez alors relocaliser sur > "scm.gforge.inria.fr" > - Pour cela, utiliser la commande : svn switch --relocate <old_url> > <new_url> > - le point prÃ©cÃ©dent s'applique Ã©galement Ã l'usage de CVS. > > > __ > L'Ã©quipe transversale INRIA Gforge > > ~~~~~~~~~~~~~~~ > Hello, > > As it was announced a few months ago, the INRIA Gforge will undergo > a major change of platform (both hardware and software) > to offer a sustainable and better quality service. > The actual service migration (from the current to the new platform) > is scheduled for Thursday December the 4th in the morning. > The return to operational service is scheduled for Friday morning on > December the 5th. > During this period, the current platform will be unavailable too. > > The INRIA Gforge team would like to remind you cross some key points > so that this important operation the least possible impact your > work: > - Take your provisions in order not to depend on the service > InriaGforge these days (December 4th and 5th) > - If you're using Subversion: > - If the command 'svn info' returns a URL whose domain name differs > from 'scm.gforge.inria.fr', you will have to relocate on > "scm.gforge.inria.fr" > - To do this, use the command: svn switch --relocate <old_url> > <new_url> > - The preceding point shall also apply to the case of CVS. > > __ > The INRIA Gforge team > >

Dec. 1, 2008

Re: [Pharo-project] free fonts

by Damien Pollet

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

Dec. 1, 2008