- Pharo-dev - lists.pharo.org

Re: [Pharo-project] VM Exit Value

by StÃ©phane Ducasse

sven could you add an entry on the cog bug tracker? Stef On Nov 25, 2011, at 9:48 AM, Sven Van Caekenberghe wrote: > > On 25 Nov 2011, at 09:37, Lukas Renggli wrote: > >> Not nice, but works reasonably well. The invoking script "listens" to Pharo generating some output file. >> Have a look at builder.sh, it does that. > > Thx, I knew about that one. > And indeed, it does seems to work, but it is not very nice compared to how everything else in *nix is supposed to work. > > Sven > >

Nov. 25, 2011

[Pharo-project] deprecated: in Deprecated14

by Pavel Krivanek

Hi, I would like to ask if the current solution where the method Object>>#deprecated: is placed in the package Deprecated14, is good. For images where this package is not present (e.g. Pharo-Kernel) we got unimplemented call and possible DNU. The method #deprecated:on:in: is in the kernel. Of course if you do not have deprecated code in the image then call of it should raise error. However some external packages (and some internal packages like Zinc) do not have deprecated code in separate package and do use #deprecated: for deprecation warnings. Because #deprecated: is bound to Pharo version, I think it would be better solution to have a message named pharoDeprecated: that will be called from Pharo packages that will be placed in Deprecated14 package and then have #deprecated: message placed in the kernel that will be used by external packages. Cheers, -- Pavel

Nov. 25, 2011

[Pharo-project] Issue 5028: failing MCPackageManager initialization

by Pavel Krivanek

http://code.google.com/p/pharo/issues/detail?id=5028 MCPackageManager class >> #initialize contains unimplemented call of #unregisterForNotifications so Monticello cannot be loaded to a fresh image. This method is no more present in the image. Does anyone know why it was removed? It seems to be related to same changes done by Stef. -- Pavel

Nov. 25, 2011

Re: [Pharo-project] Morphic replacement

by Igor Stasenko

On 25 November 2011 11:00, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: > Dear all, > > I've been working on a hole replacement of Morphic myself, because if > was tired of fixing Morphic (or porting CUIS Morphic into Pharo), and > found much more productive the approach of rewriting it from scratch. > > In my expierience, i was 100% more productive by not trying to be > backward compatible with Morphic, Polymorph , etc. > > I found it easier to Â come up with a new set of widgets (EntryField, > AutoCompletionEntryField, Button, Label, Column, Row, > ScrollableColumns) from scratch. They are all fairly tested also. > > Maybe it's time to move on, and develop from the ground up a > Morphic-like successor, instead of fixing the current Morphic. There's > no problem with preserving the current UI for all the apps that are > out there, and provide a cleaner, simpler UI framework for the new > apps. > > Regarding the new "morphic", I only assume that i have a scalable > canvas, and the vm's notifying me of the user events. On top of that i > recreated a World, that can have multiple views. There's only one > World at a given time. Views are presented within the world in a given > viewport, and present a scene. Scene are were the shapes live in. > No World as a subclass of PasteUpMorph, no globals such as World, > ActiveWorld, Hand. ActiveHand, etcs.. > > The world has a mouse and a keyboard, which take care of events > announced by the world. For example GMouse>>down: aDisplayPosition, > would take care of transforming the display position into a world > position, into a view position, into a scene position, and finally > notifying the proper shape under the mouse that it has been clicked at > a certain local position. GShape>>clickedAt: , > GShape>>secondaryClickedAt:, etc.. > No Events hierarchy, or the awful switch currently in HandMorph ( > generateMouseEvent: or generateKeyboardEvent:). > > I have a "Gaucho" system working now, Â with GShape (instead of > Morphs), using the simple new layouts developed by Juan in CUIS, > uniform usage of keybindings across the whole GShape hierarchy, > amongst other goodies. It's still tailored to be a Morphic replacement > for Gaucho, so first i need to polish a few things prior to releasing > it. > > For example, i'm going to ditch my current scalable canvas > implementation, in favor of Athens. > Glad to hear that. > Hope that very soon i can provide more details, but my plans are to > release it as part of the next Gaucho version, to provide a working > example. > > Fernando > > -- Best regards, Igor Stasenko.

Nov. 25, 2011

[Pharo-project] [update 1.4] #14236

by Marcus Denker

14236 ----- Issue 5024: incomplete SUnit http://code.google.com/p/pharo/issues/detail?id=5024 Issue 5022: UITheme uncategorized method http://code.google.com/p/pharo/issues/detail?id=5022 -- Marcus Denker -- http://marcusdenker.de

Nov. 25, 2011

Re: [Pharo-project] Morphic replacement

by Tudor Girba

Sounds exciting. Doru On Fri, Nov 25, 2011 at 1:07 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Impressive! > Let us know > > Alexandre > > > On 25 Nov 2011, at 07:00, Fernando Olivero wrote: > >> Dear all, >> >> I've been working on a hole replacement of Morphic myself, because if >> was tired of fixing Morphic (or porting CUIS Morphic into Pharo), and >> found much more productive the approach of rewriting it from scratch. >> >> In my expierience, i was 100% more productive by not trying to be >> backward compatible with Morphic, Polymorph , etc. >> >> I found it easier to Â come up with a new set of widgets (EntryField, >> AutoCompletionEntryField, Button, Label, Column, Row, >> ScrollableColumns) from scratch. They are all fairly tested also. >> >> Maybe it's time to move on, and develop from the ground up a >> Morphic-like successor, instead of fixing the current Morphic. There's >> no problem with preserving the current UI for all the apps that are >> out there, and provide a cleaner, simpler UI framework for the new >> apps. >> >> Regarding the new "morphic", I only assume that i have a scalable >> canvas, and the vm's notifying me of the user events. On top of that i >> recreated a World, that can have multiple views. There's only one >> World at a given time. Views are presented within the world in a given >> viewport, and present a scene. Scene are were the shapes live in. >> No World as a subclass of PasteUpMorph, no globals such as World, >> ActiveWorld, Hand. ActiveHand, etcs.. >> >> The world has a mouse and a keyboard, which take care of events >> announced by the world. For example GMouse>>down: aDisplayPosition, >> would take care of transforming the display position into a world >> position, into a view position, into a scene position, and finally >> notifying the proper shape under the mouse that it has been clicked at >> a certain local position. GShape>>clickedAt: , >> GShape>>secondaryClickedAt:, etc.. >> No Events hierarchy, or the awful switch currently in HandMorph ( >> generateMouseEvent: or generateKeyboardEvent:). >> >> I have a "Gaucho" system working now, Â with GShape (instead of >> Morphs), using the simple new layouts developed by Juan in CUIS, >> uniform usage of keybindings across the whole GShape hierarchy, >> amongst other goodies. It's still tailored to be a Morphic replacement >> for Gaucho, so first i need to polish a few things prior to releasing >> it. >> >> For example, i'm going to ditch my current scalable canvas >> implementation, in favor of Athens. >> >> Hope that very soon i can provide more details, but my plans are to >> release it as part of the next Gaucho version, to provide a working >> example. >> >> Fernando >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel Â http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 25, 2011

Re: [Pharo-project] Morphic replacement

by Alexandre Bergel

Impressive! Let us know Alexandre On 25 Nov 2011, at 07:00, Fernando Olivero wrote: > Dear all, > > I've been working on a hole replacement of Morphic myself, because if > was tired of fixing Morphic (or porting CUIS Morphic into Pharo), and > found much more productive the approach of rewriting it from scratch. > > In my expierience, i was 100% more productive by not trying to be > backward compatible with Morphic, Polymorph , etc. > > I found it easier to come up with a new set of widgets (EntryField, > AutoCompletionEntryField, Button, Label, Column, Row, > ScrollableColumns) from scratch. They are all fairly tested also. > > Maybe it's time to move on, and develop from the ground up a > Morphic-like successor, instead of fixing the current Morphic. There's > no problem with preserving the current UI for all the apps that are > out there, and provide a cleaner, simpler UI framework for the new > apps. > > Regarding the new "morphic", I only assume that i have a scalable > canvas, and the vm's notifying me of the user events. On top of that i > recreated a World, that can have multiple views. There's only one > World at a given time. Views are presented within the world in a given > viewport, and present a scene. Scene are were the shapes live in. > No World as a subclass of PasteUpMorph, no globals such as World, > ActiveWorld, Hand. ActiveHand, etcs.. > > The world has a mouse and a keyboard, which take care of events > announced by the world. For example GMouse>>down: aDisplayPosition, > would take care of transforming the display position into a world > position, into a view position, into a scene position, and finally > notifying the proper shape under the mouse that it has been clicked at > a certain local position. GShape>>clickedAt: , > GShape>>secondaryClickedAt:, etc.. > No Events hierarchy, or the awful switch currently in HandMorph ( > generateMouseEvent: or generateKeyboardEvent:). > > I have a "Gaucho" system working now, with GShape (instead of > Morphs), using the simple new layouts developed by Juan in CUIS, > uniform usage of keybindings across the whole GShape hierarchy, > amongst other goodies. It's still tailored to be a Morphic replacement > for Gaucho, so first i need to polish a few things prior to releasing > it. > > For example, i'm going to ditch my current scalable canvas > implementation, in favor of Athens. > > Hope that very soon i can provide more details, but my plans are to > release it as part of the next Gaucho version, to provide a working > example. > > Fernando > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 25, 2011

Re: [Pharo-project] issue 5024: incomplete SUnit

by Pavel Krivanek

link: http://code.google.com/p/pharo/issues/detail?id=5024 On Fri, Nov 25, 2011 at 12:41 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Messages #sunitExitxWith: and #sunitAnnounce:toResult: still have only > *SUnit category in some classes. Because this package was renamed to > SUnit-Core, this methods do not belong to any package. > > There would not be bad idea to check whole image ;-) > > -- Pavel >

Nov. 25, 2011

[Pharo-project] issue 5024: incomplete SUnit

by Pavel Krivanek

Messages #sunitExitxWith: and #sunitAnnounce:toResult: still have only *SUnit category in some classes. Because this package was renamed to SUnit-Core, this methods do not belong to any package. There would not be bad idea to check whole image ;-) -- Pavel

Nov. 25, 2011

Re: [Pharo-project] Morphic Cleanup Status

by Fernando Olivero

Hi Sean, i got overwhelmed last year with the task of porting CUIS Morphic, to Pharo. There's just to much differences on several common classes, it's hard to fully understand how to merge both ui frameworks. Even though i believe Juan has a did an excellent work in simplifying Morphic, and adding simpler code, like for example his new layouts (download CUIS and try them out). But my overall impression , was that we need to stop being backward compatible in order to create a simple Morphic-like framework for Pharo, and start from scratch. Fixing current Morphic is also a humongous task, for example see Stef's nice work on cleaning the event handling mechanism. Fernando On Fri, Nov 25, 2011 at 9:38 AM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: > Le 25/11/2011 07:39, Sean P. DeNigris a Ã©crit : >> What's currently in progress? SimpleMorphic? CUIS related? Other? >> >> I was pulling my hair out with Morphic layouts yesterday and started to >> clean, but I don't want to duplicate efforts on things already being worked >> on. There are a bunch of open issues and discussions on the list. What's >> actively being done right now? > Hi Sean, > AFAIK, no deep cleaning action. nothing from my side for now. > I think they have done some refactoring around layout managing in CUIS > (SimpleMorphic). > btw, **thanks a lot** for all you are doing. > Cheers > Alain > >> >> Thanks. >> Sean >> >> -- >> View this message in context: http://forum.world.st/Morphic-Cleanup-Status-tp4106566p4106566.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >

Nov. 25, 2011