2010/2/27 Schwab,Wilhelm K <bschwab@anest.ufl.edu>

Just checking :)

�

In that case however, I would like to see a nice(r) way to construct Polymorph interfaces.� Dolphin's MVP framework is very powerful.� One thing that it does not seem to do well is allow domain objects to insert themselves into a GUI; Seaside and Magritte have an advantage there.� I find Magritte a little too helpful, and #description *much* too helpful, meaning that it does so much for me that I forget how things work.

�

There is probably nothing to stop us from taking a little more control over Magritte descriptions and containers, and IIRC, there is a Polymorph version of Magritte (or is that just wishful thinking??).� Rather than write HTML to feed into what we all agree is a sub-optimal browser, I suggest putting the energy into refining Smalltalk idioms to turn data into a GUI using Polymorph.� The end result should be better user interfaces all around.

�

Bill

�

I agree with these comments (don't know if the way to go is Polymorph being that I don't know it deeper) but as I also think that Magritte is a BIG help to write almost any sort of applications.

I we could have a better (more productive) way of write desktop UIs then we can take over the win-linux.mac market :) I would try myself with my PasswordsPro application (currently in Dolphin). It would be nice to me port PasswordsPro to Pharo and sell it as a real desktop app (native in any operating system) and reuse the same model to have it on web also.

Having a only one model, with UI in desktop and web will be really awesome, even when a lot of people may claim that is possible today, I'm not really convinced with complex applications.