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

Re: [Pharo-project] About a better look

by Gary Chambers

It was nice at ESUG to be able to demo the UI Enhancements (henceforth renamed "Polymorph"), hands on describes better than any screenshots! To whet the appetite of those that haven't seen: http://www.flickr.com/photos/12018791@N06/ Though, the screenshots don't make obvious the "feel" enhancements! Regards, Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, August 20, 2008 7:57 AM Subject: Re: [Pharo-project] About a better look > Yes we know. but for now we should do want can be done easily. > The feel is always more difficult. > Stef > > On Aug 19, 2008, at 10:38 PM, Bill Schwab wrote: > >> Stef, Adrian, >> >> Where reasonable to do so, I encourage thinking in terms of Pinesoft's >> work, perhaps a new theme. If we can do better, that's ok too. While >> the thought appears to be catching on, it is worth saying again: >> Squeak's GUI woes are more often of feel than of look. >> >> Bill >> >> >> >> >> Wilhelm K. Schwab, Ph.D. >> University of Florida >> Department of Anesthesiology >> PO Box 100254 >> Gainesville, FL 32610-0254 >> >> Email: bschwab(a)anest.ufl.edu >> Tel: (352) 273-6785 >> FAX: (352) 392-7029 >> >> >>>>> stephane.ducasse(a)inria.fr 8/18/2008 2:17:53 PM >>> >> Adrian >> >> Marcus told me that you did a grey look. >> Do you have that around? >> >> Stef >> >> _______________________________________________ >> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 1, 2008

Re: [Pharo-project] Discussion summary and milestones

by Gary Chambers

Sounds good, I'll take a more recent look at Rome again. Last time I looked it was a little raw, guess things have moved on for the better now! ----- Original Message ----- From: "Michael Rueger" <m.rueger(a)acm.org> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> Sent: Monday, September 01, 2008 1:23 PM Subject: Re: [Pharo-project] Discussion summary and milestones > Gary Chambers wrote: > >> Would be nice to replace the Balloon engine with Cario sometime... > > Did you take a look at the Rome stuff? It has a Cairo and a Balloon > subclass, so you can switch the rendering backend without affecting the > API. > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 1, 2008

[Pharo-project] [ANN] SqueakGTK

by Gwenael Casaccio

Hi, A new version of SqueakGTK is published. I've corrected 2 annoying bugs that make Squeak crashes. Here is the roadmap of the next versions : * binaries for windows, mac os x, linux * save and restore the widgets * Support canvas inside cairo we can use the morphs with GTK :p * Improve all the tools * And off course correct the bugs -_-' * A new website http://code.google.com/p/squeakgtk/ Cheers, Gwenael Casaccio

Sept. 1, 2008

Re: [Pharo-project] Discussion summary and milestones

by Michael Rueger

Gary Chambers wrote: > Would be nice to replace the Balloon engine with Cario sometime... Did you take a look at the Rome stuff? It has a Cairo and a Balloon subclass, so you can switch the rendering backend without affecting the API. Michael

Sept. 1, 2008

Re: [Pharo-project] Discussion summary and milestones

by Gary Chambers

Just about catching up with work emails etc... Great to see you at ESUG, a most excellent event! I'll post the EToys removals package (more for reference, has #toRemove stubs and changed methods) once I've reviewed the changes (over 600 changed/removed methods). I'm sure I've missed a couple ;-) Should be able to do that tomorrow and rename the Pinesoft-Widgets to Polymorph. Would be nice to replace the Balloon engine with Cario sometime... Regards, Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <Pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, August 30, 2008 11:35 AM Subject: [Pharo-project] Discussion summary and milestones > Hi all > > we got an extremely positive ESUG. Thanks all of you for your great > software: > Thanks Gary it was great to see you. Now I would like to summarize some > of the discussions we got. > > For milestone1 > ----------------- > > - we will integrate the Polymorph package of gary. This means we may try > to remove some old morphic > and integrate really gary's work. Now this task could be continued > further in milestone 2. > > - gary could you send around (not only to adrian) the etoy removal so > that we do it? > > - Marcus plans to integrate the stack interpreter made by eliot > so that we will get fullclosures. > > - We will integrate the freetype plugging (we will need some VM guys > probably). > > - We want to have a one click image! > > - internally we will work on a core and set of package but publicly we > would like to avoid > to have a distribution that is not tested/used. > > For the dev image we would like to only have a set of selected packages, > so the idea > is that damien will collect the key package that would go in the dev > version. (which may be the > one click image). We really want to have package without overrides. > > - We would like to push the idea of a package manifesto. > > For milestone 2 > ------------------- > - GTK binding > > - the newcompiler will replace the old one > > - marcus is really interested in COG and helping there. > I will try to help and learn from mathieu. > > - popUp plague -> notification mechanism (check the OBNotification > hierarchy). > We need to push infrastructural work so that everything benefit of it. > > > > There are certainly point I forgot to mention but the future is full of > new perspectives. > > Stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 1, 2008

Re: [Pharo-project] Discussion summary and milestones

by StÃ©phane Ducasse

Michael This is not a question for us. Let us face it seriously we are not expert on VM building for the moment. Now we may start to build them. And yes using git would be a good idea. Stef On Aug 31, 2008, at 10:54 PM, Michael Rueger wrote: > StÃ©phane Ducasse wrote: > >> It means that we should then produce our own VMs I imagine. So what >> are the plans there? > > Knowing that I'm touching flame bait here, but how is the general > consensus on continuing to use VMMaker and Slang for generating VMs? > Alternatives could be pure C code and/or code management using Git. > > Michael > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 1, 2008

Re: [Pharo-project] Discussion summary and milestones

by Bill Schwab

Serge, I agree more than I disagree. However, I will take my usual stance that it is the FEEL of Squeak that is suffering. Fortunately, Gary has helped there too! IMHO, the _real_ benefit of Morphic is as an emulated widget framework. Don't say this to a static language guru<g>, but native widgets do not scale well; eventually large grids, etc. need a way to escape the overhead of washing everything trough the OS. Absolutely, we should not kill Morphic w/o having a replacement emulated framework. Failing a replacement, we should keep it. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> serge.stinckwich(a)doesnotunderstand.org 08/30/08 12:35 PM >>> 2008/8/30 Hilaire Fernandes <hilaire(a)ofset.org>: > 2008/8/30 Marcus Denker <denker(a)iam.unibe.ch>: > >>> For milestone 2 >>> ------------------- >>> - GTK binding >> >> Optional or replacing morphic? > > > Don't run too fast to kill Morphic. > There are a lot of value in Morphic and GTK+ is not a replacement for > it, more an alternative for different purpose. And with the work of Gary, Morphs are looking much better ;-) GTK is great have to better acceptance by non-smalltalkers but it's a bit premature to switch to GTK. -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/ _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 1, 2008