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

[Pharo-project] Issue 3550 in pharo: MenuItemMorph>>mouseDown: has unnecessary check

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3550 by sean.p.d...(a)gmail.com: MenuItemMorph>>mouseDown: has unnecessary check http://code.google.com/p/pharo/issues/detail?id=3550 Pharo1.2rc1 Latest update: #12310 If a menu item is clicked while it's pinned-down menu is obscured, the following code brings the menu to the front without executing the item's command: "Quick hack to bring menu to the front if it is obscured. See http://bugs.squeak.org/view.php?id=1780" "fixed by gvc to work with embedded menus" " self owner owner = self world ifTrue: [ self world morphsInFrontOf: self owner overlapping: self owner bounds do: [:ignored | ^ self owner comeToFront]]." However, in 1.2, it does not seem that a pinned-down menu /can/ be obscured - it magically stays on top. So this check seems redundant.

Jan. 19, 2011

[Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by Torsten Bergmann

>I've implemented a Morphic-Animations pacakge, adding the bitmap >animations as strategy objects for each animation. If there's interest >i could decouple it from Gaucho, and post it. Yes, if thats easy to do. I played with JavaFX last year and (even when it is now abondened and will reappear as Java API) it was a nice way to easily build visual appealing applications with transition effects, shadows, ... (see http://javafx.com/samples) Would like to see that in future for Pharo too easily allow people to build sexy apps. Thx T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

Jan. 19, 2011

[Pharo-project] [ANN 1.3 started] Core 1.3#13001

by Marcus Denker

https://gforge.inria.fr/frs/download.php/28163/PharoCore-1.3-13001.zip .. same as 1.2rc1, just a 13 Scriptloader. (this way we can deep-freeze 1.2 and start adding to 1.3 instead) Hudson project to follow.... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 19, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by Fernando Olivero

You already have the page flip animation in Smalltalk, just look at Form and page warp animation. It allows you to go from a form to another. pd: I've implemented a Morphic-Animations pacakge, adding the bitmap animations as strategy objects for each animation. If there's interest i could decouple it from Gaucho, and post it. Fernando On Wed, Jan 19, 2011 at 12:13 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > inspirations to switch between worlds: > > Â http://clickheredammit.com/pageflip (a page flip) > Â combined with a peeling effect in the upper corner: > Â http://www.sohtanaka.com/web-design/examples/peeling-effect/ > > or a carousel of world thumbnails: > > Â http://jquery-ui.googlecode.com/svn/branches/labs/carousel/demo/dynamic.html > > or a coverslide: > > Â http://jquery-ui.googlecode.com/svn/branches/labs/coverslide/index.html > > > If you want to port a more mac like UI to Pharo also check: > > http://www.wizzud.com/jqDock Â (a dock done in JavaScript, check the properties) > > > > > > > > -- > NEU: FreePhone - kostenlos mobil telefonieren und surfen! > Jetzt informieren: http://www.gmx.net/de/go/freephone > >

Jan. 19, 2011

Re: [Pharo-project] About XML Support in the 1.2

by laurent laffont

I put ConfigurationOfXMLSupport version 1.0 because blessing was #release. But I agree to change. Laurent On Wed, Jan 19, 2011 at 12:15 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: > > > Indeed, this is a problem for Moose in general. We depend on XMLSupport, > but now we cannot update it in PharoDev. I would also strongly support the > idea of removing XMLSupport from PharoDev. > > > > What would be important: we need the latest version in Pharo 1.2... else > how can we ever have a version where the tests are green? > (not of XML, but in general) > > Marcus > > > Cheers, > > Doru > > > > > > On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: > > > >> Hi, > >> > >> I have a problem with the XMLSupport version from Pharo 1.2. > >> > >> The problem is that I need to work with one of the last version of > XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport > (I mean a version from Jan 2010). I did try to load a newer version of > XMLSupport using ConfigurationOfXMLSupport but some errors make this > operation impossible. > >> So either Pharo-dev 1.2 load a newer (possibly the last) version of > XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. > >> > >> I think that doesn't make sense to use by default such an old version, > also considering that the last XMLSupport has nice and useful features like > the XMLPluggableElementFactory. > >> > >> By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let > people free to use the version that they like. > >> > >> Thanks, > >> > >> Fabrizio > >> > > > > -- > > www.tudorgirba.com > > > > "We cannot reach the flow of things unless we let go." > > > > > > > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

Jan. 19, 2011

Re: [Pharo-project] About XML Support in the 1.2

by Marcus Denker

On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: > Indeed, this is a problem for Moose in general. We depend on XMLSupport, but now we cannot update it in PharoDev. I would also strongly support the idea of removing XMLSupport from PharoDev. > What would be important: we need the latest version in Pharo 1.2... else how can we ever have a version where the tests are green? (not of XML, but in general) Marcus > Cheers, > Doru > > > On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: > >> Hi, >> >> I have a problem with the XMLSupport version from Pharo 1.2. >> >> The problem is that I need to work with one of the last version of XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport (I mean a version from Jan 2010). I did try to load a newer version of XMLSupport using ConfigurationOfXMLSupport but some errors make this operation impossible. >> So either Pharo-dev 1.2 load a newer (possibly the last) version of XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. >> >> I think that doesn't make sense to use by default such an old version, also considering that the last XMLSupport has nice and useful features like the XMLPluggableElementFactory. >> >> By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let people free to use the version that they like. >> >> Thanks, >> >> Fabrizio >> > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 19, 2011

[Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by Torsten Bergmann

inspirations to switch between worlds: http://clickheredammit.com/pageflip (a page flip) combined with a peeling effect in the upper corner: http://www.sohtanaka.com/web-design/examples/peeling-effect/ or a carousel of world thumbnails: http://jquery-ui.googlecode.com/svn/branches/labs/carousel/demo/dynamic.html or a coverslide: http://jquery-ui.googlecode.com/svn/branches/labs/coverslide/index.html If you want to port a more mac like UI to Pharo also check: http://www.wizzud.com/jqDock (a dock done in JavaScript, check the properties) -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

Jan. 19, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by Sean P. DeNigris

Does anyone have a great example of a multiple desktop switching UI (something like Mac Spaces)? I might take a hack at creating one for Pharo on top of this API and I'm looking for inspiration. Thanks. Sean -- View this message in context: http://forum.world.st/Issue-3545-in-pharo-FEATURE-Multiple-Worlds-tp3222698… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 19, 2011

Re: [Pharo-project] About XML Support in the 1.2

by Tudor Girba

Indeed, this is a problem for Moose in general. We depend on XMLSupport, but now we cannot update it in PharoDev. I would also strongly support the idea of removing XMLSupport from PharoDev. Cheers, Doru On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: > Hi, > > I have a problem with the XMLSupport version from Pharo 1.2. > > The problem is that I need to work with one of the last version of XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport (I mean a version from Jan 2010). I did try to load a newer version of XMLSupport using ConfigurationOfXMLSupport but some errors make this operation impossible. > So either Pharo-dev 1.2 load a newer (possibly the last) version of XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. > > I think that doesn't make sense to use by default such an old version, also considering that the last XMLSupport has nice and useful features like the XMLPluggableElementFactory. > > By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let people free to use the version that they like. > > Thanks, > > Fabrizio > -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

Jan. 19, 2011

Re: [Pharo-project] list on he fly selection :)

by Benjamin

It "works" now (there is some bugs again but minors one I think) Let me know if it works for you ^^ I've played a little with GlobalKeys () so I've added a global shortcut(cmd+e) which execute this block: [(DummyTest on: (Smalltalk allClasses)) openInWorld] and I have implemented a new kind of AutoSelection list which react to an enter hit. Like that, I push cmd+e, it opens the list of classes, then I choose the one I want, hit enter, and then it opens a browser on it. (Like that, I do not open tons of workspace just to type the name of a class then cmd+b ^^) Give me feedback please ^^ Thanks in advance, Ben On Jan 19, 2011, at 11:14 AM, Tudor Girba wrote: > Could you let me know when I should try again? I am very interested in this. > > Cheers, > Doru > > > On 18 Jan 2011, at 21:39, Benjamin wrote: > >> You must have tried between two commits on squeaksource (I hope ^^) >> I will refactor that because the inst var is named lastKeystrokes but the method is named lastKeyStrokes ... >> >> >> Thanks for your feedback :) >> >> >> >> Ben >> >> On Jan 18, 2011, at 8:34 PM, Tudor Girba wrote: >> >>> I am not sure where it should work, but I tried in Pharo 1.2 and it does not work. First, there is a "self self". Second, even if I fix this one, I still get a DNU for OnTheFlySelectionPluggableListMorph>>lastKeystrokes. >>> >>> Cheers, >>> Doru >>> >>> >>> On 18 Jan 2011, at 20:21, StÃ©phane Ducasse wrote: >>> >>>> close your eyes and imagine that you can just type as to get all the methods starting with as* >>>> without extra shortcut whatever.... >>>> same for classes, packages... of course. >>>> >>>> Stef >>>> >>>> On Jan 18, 2011, at 4:16 PM, Alexandre Bergel wrote: >>>> >>>>> Just tried. I could not immediately figure out what is the difference with the "Find Class" panel (pressing Cmd-f in OB)? >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> >>>>> >>>>> On 18 Jan 2011, at 12:00, StÃ©phane Ducasse wrote: >>>>> >>>>>> Hi guys >>>>>> >>>>>> I'm sure that some of you will really like to type on that list and see it auto selectioning its elements.... >>>>>> >>>>>> Gofer it >>>>>> squeaksource: 'DirtyExperiments'; >>>>>> package: 'DirtyExperiments'; >>>>>> load >>>>>> >>>>>> | test | >>>>>> test := DummyTest on: (Smalltalk allClasses). >>>>>> test openInWorld >>>>>> >>>>>> Of course I would love to have that for a lot of lists..... :) >>>>>> >>>>>> Thanks Benjamin for this first version :) >>>>>> Stef >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Sometimes the best solution is not the best solution." >>> >>> >> >> > > -- > www.tudorgirba.com > > "One cannot do more than one can do." > > > >

Jan. 19, 2011