Camillo First we should get the classBuilder athens slots fully working So it would be good to have that soon in 3.0 :) then naturally people will build MagicMagicMagritte using slots because this will be really cool Stef On Jun 12, 2013, at 9:26 AM, Camillo Bruni <camillobruni@gmail.com> wrote:
cool!
I start to sound like a salesman for vaporware ;) but I think eventually we should replace Magritte with something more explicit directly on Slots + Layouts.
That means you can model everything directly in Pharo without an extension...
On 2013-06-12, at 08:52, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Cool (music) indeed !
On 11 Jun 2013, at 23:18, "Sean P. DeNigris" <sean@clipperadams.com> wrote:
Tired of writing the same UI boilerplate over and over? I mean, basically an object has fields, which have certain properties relevant to the UI. If we could just capture that info once in the right place, a basic UI should almost fall out on its own. Magritte could be the answers to our lazy utopian dreams. The thing is that the Morphic implementation as fallen behind what can be done in Seaside... until now. I took a first pass at bringing Morphic up to date here. It doesn't seem like it will be too hard to have reasonably useful functionality.
Here's a short screencast showing the improvements: http://vimeo.com/68166920 Magritte is an awesome framework to automate common UI tasks. Describe your object's field once, get views everywhere. Everywhere most commonly refers to both the web, via Seaside, and desktop via Morphic. But the Morphic implementation had fallen behind due to disuse. Now, some steps have been taken to bring the Morphic functionality up to date with that of Seaside.