June 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] OCompletion is broken in 1.3

by Benjamin

In fact, I have posted two things: - a little improvement in OCompletion (not related to the bug) - then I take a look at OCompletionPharoCompatibility, but I have done a mistake because the package is OcompletionPharoCompatibility (with a minus "c") So finally, the only thing I have done to fix the bug is to change the ConfigurationOfOCompletion which now call a post load method to reset the default toolset and take in account the registry method. I hope I haven't done too many stupid things :) Ben On Jun 10, 2011, at 12:05 PM, Mariano Martinez Peck wrote: > so...I saw you commit in OCompletion and then rollback the pharo-ish part. So..can that be put instead to OCompletionPharoCompatibilty and we are done? > then we update ConfigurationOfOCompletion and we fix it :) > > On Fri, Jun 10, 2011 at 11:59 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Thu, Jun 9, 2011 at 12:45 PM, Benjamin Van Ryseghem <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > It's fixed, I am looking where to post the fix :) > > Thanks!!!!!!!!!!!!! > > Put it somewhere please :) > > OCompletionPharoCompatibilty is not enough? you have commit rights there.... > > > Ben > > 2011/6/9 Benjamin Van Ryseghem <benjamin.vanryseghem.pharo(a)gmail.com> > It comes from Toolset change. > > OCompletion should be registered as a Completion tool (but I do not remember the magic formula ^^) > > > Ben > > > 2011/6/9 Marcus Denker <marcus.denker(a)inria.fr> > > On Jun 9, 2011, at 12:21 PM, Benjamin Van Ryseghem wrote: > > > It happened between 13217 and 13234 ... > > > > Maybe the Paragraph changes ? > > > > The Dev vs. Core is killing us. We need *one* image. We should really try to do that with 1.4, it will > make everything simpler and easier to manage. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com >

June 10, 2011

Re: [Pharo-project] Tab widget improvements

by Gary Chambers

Fix for tab group page contents "jumping around" slightly. Beware if using Morph>>replaceSubmorph:by: It uses #referencePositionInWorld which, in turn, eventually uses #rotationCenter (typically 0.5 @ 0.5). This was causing the replacement page to be mis-aligned depending on the previous page causing positional movement when moving back and forth between tabs. Changed to remove old page and add new instead. Regards, Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, June 09, 2011 2:34 PM Subject: Re: [Pharo-project] Tab widget improvements > Small fix for index out of range when pages are deleted in some > circumstances... > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, June 08, 2011 5:58 PM > Subject: Re: [Pharo-project] Tab widget improvements > > > in 1.3 > > Stef > > On Jun 8, 2011, at 4:00 PM, Marcus Denker wrote: > >> >> On Jun 8, 2011, at 3:55 PM, Gary Chambers wrote: >> >>> Attached, some improvements to the TabGroupMorph etc. having had >>> feedback >>> from Doru. >>> >>> Provides scrolling buttons when insufficient room for all tabs and >>> displays only tabs for which there is room! (excepting at least one). >>> >>> Can optionally set wrapScrolling on the TabSelectorMorph to allow >>> wraparound scrolling via the buttons. >>> >> >> Do we put that in 1.3 or 1.4? >> >> http://code.google.com/p/pharo/issues/list?thanks=4376 >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > >

June 10, 2011

Re: [Pharo-project] OCompletion is broken in 1.3

by Mariano Martinez Peck

so...I saw you commit in OCompletion and then rollback the pharo-ish part. So..can that be put instead to OCompletionPharoCompatibilty and we are done? then we update ConfigurationOfOCompletion and we fix it :) On Fri, Jun 10, 2011 at 11:59 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Thu, Jun 9, 2011 at 12:45 PM, Benjamin Van Ryseghem < > benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> It's fixed, I am looking where to post the fix :) > > > Thanks!!!!!!!!!!!!! > > Put it somewhere please :) > > OCompletionPharoCompatibilty is not enough? you have commit rights > there.... > > >> >> Ben >> >> 2011/6/9 Benjamin Van Ryseghem <benjamin.vanryseghem.pharo(a)gmail.com> >> >>> It comes from Toolset change. >>> >>> OCompletion should be registered as a Completion tool (but I do not >>> remember the magic formula ^^) >>> >>> >>> Ben >>> >>> >>> 2011/6/9 Marcus Denker <marcus.denker(a)inria.fr> >>> >>>> >>>> On Jun 9, 2011, at 12:21 PM, Benjamin Van Ryseghem wrote: >>>> >>>> > It happened between 13217 and 13234 ... >>>> > >>>> > Maybe the Paragraph changes ? >>>> > >>>> >>>> The Dev vs. Core is killing us. We need *one* image. We should really >>>> try to do that with 1.4, it will >>>> make everything simpler and easier to manage. >>>> >>>> Marcus >>>> >>>> -- >>>> Marcus Denker -- http://www.marcusdenker.de >>>> INRIA Lille -- Nord Europe. Team RMoD. >>>> >>>> >>>> >>> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

June 10, 2011

Re: [Pharo-project] WindowOrganiser (was: Tab widget improvements)

by Gary Chambers

Small fix attached for issues when a SystemWindows has no label (as when embedded etc.) Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Friday, June 10, 2011 7:52 AM Subject: Re: [Pharo-project] WindowOrganiser (was: Tab widget improvements) Hi Gary, I've played a little and changed: DockingBarMorph subclass: #WindowOrganiser uses: TEasilyThemed instanceVariableNames: 'tabGroup' classVariableNames: '' poolDictionaries: '' category: 'Guru' (sorry, I feel stupid, I don't know how to make a changeset, need to look at this :) So I can open a sort of docking panel: (see attached screenshot) WindowOrganiser new openInWorld; height:200; adhereToBottom. That means we can have docking panels like the IDEs Java students use :) Moreover TWM tile windows only in clear area, so all this play nicely together. I wonder what's the best way to package all this. In Polymorph ? Laurent Laffont - @lolgzs Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st On Thu, Jun 9, 2011 at 3:33 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: Even better when working more properly (attached) Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, June 09, 2011 2:12 PM Subject: Re: [Pharo-project] Tab widget improvements On Thu, Jun 9, 2011 at 3:01 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: Something to get you started... ;-0 aaaaargggggggg THAT'S SO DAMN COOOOOOOOOOOOOOOOOOL !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Laurent WindowOrganiser new open Optionally, via halo, turn on "Accept drops" for the window, else use the window menu to "Grab window...". Plenty of evilness left to sort out with it, naturally. Have fun! Regards, Gary ----- Original Message ----- From: Gary Chambers To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, June 09, 2011 10:03 AM Subject: Re: [Pharo-project] Tab widget improvements Hi Laurent. Sounds like a cool idea and is possible. You'd likely need to modify SystemWindow somewhat to deal with being within a tab (remove grips, forward label changes to the tab, handle activation (TopWindow stuff might be tricky) etc.). You'd also want an option (perhaps a button in the tab label) to break the window out again. For some of this you could get some ideas from StandardWindow with respect to fullscreen, #noteNewOwner: Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, June 08, 2011 5:20 PM Subject: Re: [Pharo-project] Tab widget improvements Hi Gary, I wanted to try what follows while coding TWM, maybe with your magic super powers its easy :) Create a SystemWindow subclass: #TabbedWindow (or better name). In this window's menu there's the list of all other SystemWindows. When you click on it, the window goes as tab. So I can group several windows in a tabbed container. Like the group windows feature of KDE. See http://blip.tv/sebastian-kgler/window-managing-features-in-kde-plasma-4-4-3… at 1'50. Is it hard ? Idea how to do this ? Laurent. On Wed, Jun 8, 2011 at 4:57 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: For another example, just a quickly hacked together (i.e. quick and dirty) multi workspace thing attached. MultiWorkspaceWindow new open Use the window menu to add workspaces, otherwise works like a workspace for the selected tab. Regards, Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 08, 2011 3:26 PM Subject: Re: [Pharo-project] Tab widget improvements Lol Regards, Gary ----- Original Message ----- From: "Tudor Girba" <tudor(a)tudorgirba.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 08, 2011 3:19 PM Subject: Re: [Pharo-project] Tab widget improvements You know my soft spot :) Doru On 8 Jun 2011, at 16:04, Gary Chambers wrote: I expect Doru will want it in 1.3 for Moose ;-) Regards, Gary ----- Original Message ----- From: "Marcus Denker" <marcus.denker(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 08, 2011 3:00 PM Subject: Re: [Pharo-project] Tab widget improvements On Jun 8, 2011, at 3:55 PM, Gary Chambers wrote: Attached, some improvements to the TabGroupMorph etc. having had feedback from Doru. Provides scrolling buttons when insufficient room for all tabs and displays only tabs for which there is room! (excepting at least one). Can optionally set wrapScrolling on the TabSelectorMorph to allow wraparound scrolling via the buttons. Do we put that in 1.3 or 1.4? http://code.google.com/p/pharo/issues/list?thanks=4376 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. -- www.tudorgirba.com "Live like you mean it."

June 10, 2011

Re: [Pharo-project] OCompletion is broken in 1.3

by Mariano Martinez Peck

On Thu, Jun 9, 2011 at 12:45 PM, Benjamin Van Ryseghem < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > It's fixed, I am looking where to post the fix :) Thanks!!!!!!!!!!!!! Put it somewhere please :) OCompletionPharoCompatibilty is not enough? you have commit rights there.... > > Ben > > 2011/6/9 Benjamin Van Ryseghem <benjamin.vanryseghem.pharo(a)gmail.com> > >> It comes from Toolset change. >> >> OCompletion should be registered as a Completion tool (but I do not >> remember the magic formula ^^) >> >> >> Ben >> >> >> 2011/6/9 Marcus Denker <marcus.denker(a)inria.fr> >> >>> >>> On Jun 9, 2011, at 12:21 PM, Benjamin Van Ryseghem wrote: >>> >>> > It happened between 13217 and 13234 ... >>> > >>> > Maybe the Paragraph changes ? >>> > >>> >>> The Dev vs. Core is killing us. We need *one* image. We should really try >>> to do that with 1.4, it will >>> make everything simpler and easier to manage. >>> >>> Marcus >>> >>> -- >>> Marcus Denker -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >>> >> > -- Mariano http://marianopeck.wordpress.com

June 10, 2011

Re: [Pharo-project] WindowOrganiser (was: Tab widget improvements)

by Gary Chambers

Another thought, subclass from Morph instead of DockingBarMorph (if that's what you've done) to make it more generally usable in other compositions. Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Friday, June 10, 2011 7:52 AM Subject: Re: [Pharo-project] WindowOrganiser (was: Tab widget improvements) Hi Gary, I've played a little and changed: DockingBarMorph subclass: #WindowOrganiser uses: TEasilyThemed instanceVariableNames: 'tabGroup' classVariableNames: '' poolDictionaries: '' category: 'Guru' (sorry, I feel stupid, I don't know how to make a changeset, need to look at this :) So I can open a sort of docking panel: (see attached screenshot) WindowOrganiser new openInWorld; height:200; adhereToBottom. That means we can have docking panels like the IDEs Java students use :) Moreover TWM tile windows only in clear area, so all this play nicely together. I wonder what's the best way to package all this. In Polymorph ? Laurent Laffont - @lolgzs Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st On Thu, Jun 9, 2011 at 3:33 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: Even better when working more properly (attached) Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, June 09, 2011 2:12 PM Subject: Re: [Pharo-project] Tab widget improvements On Thu, Jun 9, 2011 at 3:01 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: Something to get you started... ;-0 aaaaargggggggg THAT'S SO DAMN COOOOOOOOOOOOOOOOOOL !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Laurent WindowOrganiser new open Optionally, via halo, turn on "Accept drops" for the window, else use the window menu to "Grab window...". Plenty of evilness left to sort out with it, naturally. Have fun! Regards, Gary ----- Original Message ----- From: Gary Chambers To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, June 09, 2011 10:03 AM Subject: Re: [Pharo-project] Tab widget improvements Hi Laurent. Sounds like a cool idea and is possible. You'd likely need to modify SystemWindow somewhat to deal with being within a tab (remove grips, forward label changes to the tab, handle activation (TopWindow stuff might be tricky) etc.). You'd also want an option (perhaps a button in the tab label) to break the window out again. For some of this you could get some ideas from StandardWindow with respect to fullscreen, #noteNewOwner: Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, June 08, 2011 5:20 PM Subject: Re: [Pharo-project] Tab widget improvements Hi Gary, I wanted to try what follows while coding TWM, maybe with your magic super powers its easy :) Create a SystemWindow subclass: #TabbedWindow (or better name). In this window's menu there's the list of all other SystemWindows. When you click on it, the window goes as tab. So I can group several windows in a tabbed container. Like the group windows feature of KDE. See http://blip.tv/sebastian-kgler/window-managing-features-in-kde-plasma-4-4-3… at 1'50. Is it hard ? Idea how to do this ? Laurent. On Wed, Jun 8, 2011 at 4:57 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: For another example, just a quickly hacked together (i.e. quick and dirty) multi workspace thing attached. MultiWorkspaceWindow new open Use the window menu to add workspaces, otherwise works like a workspace for the selected tab. Regards, Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 08, 2011 3:26 PM Subject: Re: [Pharo-project] Tab widget improvements Lol Regards, Gary ----- Original Message ----- From: "Tudor Girba" <tudor(a)tudorgirba.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 08, 2011 3:19 PM Subject: Re: [Pharo-project] Tab widget improvements You know my soft spot :) Doru On 8 Jun 2011, at 16:04, Gary Chambers wrote: I expect Doru will want it in 1.3 for Moose ;-) Regards, Gary ----- Original Message ----- From: "Marcus Denker" <marcus.denker(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 08, 2011 3:00 PM Subject: Re: [Pharo-project] Tab widget improvements On Jun 8, 2011, at 3:55 PM, Gary Chambers wrote: Attached, some improvements to the TabGroupMorph etc. having had feedback from Doru. Provides scrolling buttons when insufficient room for all tabs and displays only tabs for which there is room! (excepting at least one). Can optionally set wrapScrolling on the TabSelectorMorph to allow wraparound scrolling via the buttons. Do we put that in 1.3 or 1.4? http://code.google.com/p/pharo/issues/list?thanks=4376 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. -- www.tudorgirba.com "Live like you mean it."

June 10, 2011

Re: [Pharo-project] WindowOrganiser (was: Tab widget improvements)

by Gary Chambers

Tools->Change Sorter for changesets... Not sure where to put it for now, probably Polymorph-Widgets. One other nicety (adapt the first bit as required for dock)... addWindow: aSystemWindow "Add an existing window to the pages." TopWindow = aSystemWindow ifTrue: [self class passivateTopWindow]. self tabGroup addPage: aSystemWindow configureForEmbedding label: (self tabLabelFor: aSystemWindow); selectedPageIndex: self tabGroup pages size. self isActive ifFalse: [self tabGroup selectedTab passivate]. self tabGroup selectedTab on: #startDrag send: #dragTab:event:in: to: self withValue: aSystemWindow dragTab: aSystemWindow event: anEvent in: aTabLabel "Drag a tab. Remove the window from the organiser and place in hand." self removeWindow: aSystemWindow. anEvent hand grabMorph: aSystemWindow Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Friday, June 10, 2011 7:52 AM Subject: Re: [Pharo-project] WindowOrganiser (was: Tab widget improvements) Hi Gary, I've played a little and changed: DockingBarMorph subclass: #WindowOrganiser uses: TEasilyThemed instanceVariableNames: 'tabGroup' classVariableNames: '' poolDictionaries: '' category: 'Guru' (sorry, I feel stupid, I don't know how to make a changeset, need to look at this :) So I can open a sort of docking panel: (see attached screenshot) WindowOrganiser new openInWorld; height:200; adhereToBottom. That means we can have docking panels like the IDEs Java students use :) Moreover TWM tile windows only in clear area, so all this play nicely together. I wonder what's the best way to package all this. In Polymorph ? Laurent Laffont - @lolgzs Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st On Thu, Jun 9, 2011 at 3:33 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: Even better when working more properly (attached) Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, June 09, 2011 2:12 PM Subject: Re: [Pharo-project] Tab widget improvements On Thu, Jun 9, 2011 at 3:01 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: Something to get you started... ;-0 aaaaargggggggg THAT'S SO DAMN COOOOOOOOOOOOOOOOOOL !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Laurent WindowOrganiser new open Optionally, via halo, turn on "Accept drops" for the window, else use the window menu to "Grab window...". Plenty of evilness left to sort out with it, naturally. Have fun! Regards, Gary ----- Original Message ----- From: Gary Chambers To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, June 09, 2011 10:03 AM Subject: Re: [Pharo-project] Tab widget improvements Hi Laurent. Sounds like a cool idea and is possible. You'd likely need to modify SystemWindow somewhat to deal with being within a tab (remove grips, forward label changes to the tab, handle activation (TopWindow stuff might be tricky) etc.). You'd also want an option (perhaps a button in the tab label) to break the window out again. For some of this you could get some ideas from StandardWindow with respect to fullscreen, #noteNewOwner: Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, June 08, 2011 5:20 PM Subject: Re: [Pharo-project] Tab widget improvements Hi Gary, I wanted to try what follows while coding TWM, maybe with your magic super powers its easy :) Create a SystemWindow subclass: #TabbedWindow (or better name). In this window's menu there's the list of all other SystemWindows. When you click on it, the window goes as tab. So I can group several windows in a tabbed container. Like the group windows feature of KDE. See http://blip.tv/sebastian-kgler/window-managing-features-in-kde-plasma-4-4-3… at 1'50. Is it hard ? Idea how to do this ? Laurent. On Wed, Jun 8, 2011 at 4:57 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: For another example, just a quickly hacked together (i.e. quick and dirty) multi workspace thing attached. MultiWorkspaceWindow new open Use the window menu to add workspaces, otherwise works like a workspace for the selected tab. Regards, Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 08, 2011 3:26 PM Subject: Re: [Pharo-project] Tab widget improvements Lol Regards, Gary ----- Original Message ----- From: "Tudor Girba" <tudor(a)tudorgirba.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 08, 2011 3:19 PM Subject: Re: [Pharo-project] Tab widget improvements You know my soft spot :) Doru On 8 Jun 2011, at 16:04, Gary Chambers wrote: I expect Doru will want it in 1.3 for Moose ;-) Regards, Gary ----- Original Message ----- From: "Marcus Denker" <marcus.denker(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 08, 2011 3:00 PM Subject: Re: [Pharo-project] Tab widget improvements On Jun 8, 2011, at 3:55 PM, Gary Chambers wrote: Attached, some improvements to the TabGroupMorph etc. having had feedback from Doru. Provides scrolling buttons when insufficient room for all tabs and displays only tabs for which there is room! (excepting at least one). Can optionally set wrapScrolling on the TabSelectorMorph to allow wraparound scrolling via the buttons. Do we put that in 1.3 or 1.4? http://code.google.com/p/pharo/issues/list?thanks=4376 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. -- www.tudorgirba.com "Live like you mean it."

June 10, 2011

Re: [Pharo-project] Deleting packages in squeaksource.com?

by Mariano Martinez Peck

Go to your project. Go to the last (on the right) tab "Latest". Select the last version of the package you want to remove. Now on the left pane you should have the option "Delete Package". good luck Mariano On Fri, Jun 10, 2011 at 6:57 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > You need to login and be administrator of the project, then you get > some links on the left side to delete versions, packages, etc. > > Lukas > > On 10 June 2011 03:55, HwaJong Oh <daliot.oh(a)gmail.com> wrote: > > Hi, > > > > I want to delete some packages that are in my squeaksource repository. > They > > are either empty or old or part of aborted project. I want to keep my > > repository neat and focused. > > > > Couldn't find any buttons in Monticello Browser nor links in > > squeaksource.com. > > Plz Help. > > > > > > Best Regards > > HwaJong Oh > > > > -- > > View this message in context: > http://forum.world.st/Deleting-packages-in-squeaksource-com-tp3587292p35872… > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > -- Mariano http://marianopeck.wordpress.com

June 10, 2011

Re: [Pharo-project] Fuel - a fast object deployment tool

by Eliot Miranda

On Thu, Jun 9, 2011 at 1:26 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > > > FLSerializationSettings newDefault > > onClass: ClassWithTransients > > declareTransients: #(myTransientValue1 myTransientValue1). > > > > Do you have a better idea? > > I'm dead tired and not having clear idea but is it better to mention what > should be save or what > should not be saved? > IMO, what should not, since this is the exception. Most times one wants to save all inst vars. e. > Stef >

June 10, 2011

Re: [Pharo-project] FFI versus Alien versus NativeBoost (was FFI versus Aloen)

by Igor Stasenko

On 10 June 2011 06:58, Chris Cunnington <smalltalktelevision(a)gmail.com> wrote: > >>What shortcomings? > > I believe there are three outlined in the description on SqueakSource: > > "It supports faster call sequence, return code setting, and callbacks to > execute smalltalk code from the FFI routine." > > There's something about that last one: callbacks. I think FFI gives a return > value, but you can't create a callback. > >> NativeBoost is faster than FFI, but NB is a whole other ball-of-wax, and >> I'd like to support it eventually as well as FFI/Alien. > > Another way to look at it is via what Goran said: in terms of age. FFI is > oldest and most well known. Alien less so. NativeBoost is > Igor's project and I don't think is widely adopted yet. (Igor's going to > show up and squish me like a bug, but oh well... ) > > Igor did say something interesting about FFI versus plugins at Deep Into > Smalltalk. I believe he wrote Native Boost because he was > tired of endlessly recompiling vms with plugins. I don't think there is any > standard vm with NB in it, which means that's exactly > what you're going to need to do to use NB. > Indeed. You need to build own VM. The Last One :) This is not a problem to me - i can build it in 5 minutes (it builds about 5 minutes). But i could understand people who need to learn a lot before doing that. I plan to add a Hudson job for building VMs with NativeBoost. The VM-side changes are so small, that i even tempting to propose adding it to standard VMs. > FFI has a reputation as something that's a bit touchy. Well, apart from problems with dynamic library search/load, it is quite solid. Of course, new multithreaded stuff, added recently by Eliot, needs to be tested. But for that you need to build different VM :) > It looks a little easier than it is. The prudent choice would be for you to use > FFI and curb your ambition away from Alien or NB until later. > > There are lots more examples of FFI around than Alien and NB combined. > OpenSophie has copious code examples. > > http://opensophie.org/ > > I have to stop now. I'm only making it worse for when Igor arrives... must > go! :p > Why? The FFI implemented in C are more portable. And it is the only choice for nasty platforms (everyone knows the name ;) where no JIT allowed. (If you don't wanna do a plugin, of coure). > Chris > -- Best regards, Igor Stasenko AKA sig.

June 10, 2011