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

Re: [Pharo-project] [update] #10185

by StÃ©phane Ducasse

why do you unload Installer? > -- unloads packages: Installer, 39Deprecated, FlexibleVocablaries, > Pinesoft-Removals-EToys, ToolBuilder-MVC Because I think that this is important to have it. May be a small version: Installer and MCInstaller? amazing.... when I see all the stuff that was in there... > > -- remove preferences #timeStampsInMenuTitles #personalizedWorldMenu > #abbreviatedBrowserButtons > > Here is a full list of removals: > -------------------------------- > FileList2, Everything from Installer* > Smalltalk removeClassNamed: #Vocabulary! > Smalltalk removeClassNamed: #BOBTransformationMorph! > > TilePadMorph removeSelector: #prepareToUndoDropOf:! > TileMorph removeSelector: #scriptEdited! > TilePadMorph removeSelector: #addCustomMenuItems:hand:! > TilePadMorph removeSelector: #restoreDefaultTile! > TilePadMorph removeSelector: #setToBearDefaultLiteral! > TilePadMorph removeSelector: #setType:! > TileMorph removeSelector: #slotName! > StandardScriptingSystem removeSelector: #colorForType:! > Slider removeSelector: #wantsSlot! > SimpleHierarchicalListMorph removeSelector: #installModelIn:! > PluggableTextMorph removeSelector: #installModelIn:! > PluggableListMorph removeSelector: #installModelIn:! > ScrollPane removeSelector: #wantsSlot! > BlobMorph removeSelector: #installModelIn:! > PolygonMorph removeSelector: #installModelIn:! > PasteUpMorph removeSelector: #abandonVocabularyPreference! > MorphicModel removeSelector: #compileAccessForSlot:! > MorphicModel removeSelector: #compilePropagationMethods! > MorphicModel removeSelector: #initString! > MorphicModel removeSelector: #installModelIn:! > MorphicModel removeSelector: #recomputeBounds! > MorphicModel removeSelector: #slotName! > MorphicModel removeSelector: #slotSelectorFor:! > MorphicModel removeSelector: #wantsSlot! > HandMorph removeSelector: #addKeyboardListener:! > HandMorph removeSelector: #checkForMoreKeyboard! > HandMorph removeSelector: #generateWindowEvent:! > HandMorph removeSelector: #isCapturingGesturePoints! > HandMorph removeSelector: #keyboardListeners:! > HandMorph removeSelector: #removeKeyboardListener:! > HandMorph removeSelector: #targetOffset:! > Morph removeSelector: #altSpecialCursor3! > Morph removeSelector: #beThisWorldsModel! > Morph removeSelector: #choosePartName! > Morph removeSelector: #imageFormWithout:andStopThere:! > Morph removeSelector: #inAScrollPane! > Morph removeSelector: #initString! > Morph removeSelector: #installModelIn:! > Morph removeSelector: #isModalShell! > Morph removeSelector: #morphReport! > Morph removeSelector: #morphReportFor:! > Morph removeSelector: #morphReportFor:on:indent:! > Morph removeSelector: #nameInModel! > Morph removeSelector: #obtrudesBeyondContainer! > Morph removeSelector: #okayToExtractEasily! > Morph removeSelector: #textToPaste! > Morph removeSelector: #yellowButtonGestureDictionaryOrName:! > Preferences class removeSelector: #chooseInsertionPointColor! > Preferences class removeSelector: #chooseKeyboardFocusColor! > ColorTheme class removeSelector: #apply! > ColorTheme class removeSelector: #applyTheme:! > ColorTheme class removeSelector: #current:! > ColorTheme class removeSelector: #defaultTheme! > ColorTheme removeSelector: #apply! > ColorTheme removeSelector: #balloonColor! > ColorTheme removeSelector: #dark:! > ColorTheme removeSelector: #defaultWorldColor! > ColorTheme removeSelector: #dialogTextBoxBorderColor! > ColorTheme removeSelector: #dialogTextBoxColor! > ColorTheme removeSelector: #initialize! > ColorTheme removeSelector: #insertionPointColor! > ColorTheme removeSelector: #keyboardFocusColor! > ColorTheme removeSelector: #labelForColor:! > ColorTheme removeSelector: #light:! > ColorTheme removeSelector: #textHighlightColor! > CodeHolder removeSelector: #abbreviatedWordingFor:! > Preferences class removeSelector: #abbreviatedBrowserButtons! > Preferences class removeSelector: #chooseEToysFont! > Preferences class removeSelector: #chooseEToysTitleFont! > Preferences class removeSelector: #letUserPersonalizeMenu! > Preferences class removeSelector: #personalizeUserMenu:! > Preferences class removeSelector: #personalizedWorldMenu! > Preferences class removeSelector: #timeStampsInMenuTitles! > PasteUpMorph removeSelector: #yellowButtonClickOnDesktopWithEvent:! > > > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > 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] polymorph UI glitch

by StÃ©phane Ducasse

Yes apparently this is really on "old" windows. stef On Nov 30, 2008, at 4:47 PM, Gary Chambers wrote: > I've only seen that on existing windows in a fresh pickup of an > image release... Not seen it with new windows. > Tricky to track down what has caused the scrollbar frames to get > misadjusted since new windows don't exhibit it. > > If you have found a case where a new window does this please pass > along an image for investigation. > > Regards, Gary. > > ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr > > > To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> > Sent: Saturday, November 29, 2008 8:12 PM > Subject: [Pharo-project] polymorph UI glitch > > >> When I enlarged the window I got that. >> >> > > > -------------------------------------------------------------------------------- > > >> _______________________________________________ >> 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. 2, 2008

[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