If you are generating XML, perhaps that should be left to SIXX?? The result should be very close to Dolphin's ViewComposer, which is a very powerful tool. There are some traps to avoid with conversion of the serializer's output, but I can hopefully advise on where those might arise. It's unclear to me whether Dolphin's "recent" conversion to view resources as source code is a bad idea or simply under-supported in the area of conversion of existing view resources. Serializer output worked, with some caveats of dependence on layout changes and limitations on browsing into view resources, at least when they are in their dormant state. We are starting with real closures, dodging a bullet that hurt Dolphin.
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of laurent laffont Sent: Wednesday, June 30, 2010 9:15 AM To: [email protected] Subject: Re: [Pharo-project] CLFramework and Pharo On Wed, Jun 30, 2010 at 3:55 PM, nullPointer <[email protected]<mailto:[email protected]>> wrote: >> I believe is best create another from scratch, >> but with WPF like model and XAML >> as UI definition language. That is for people with best knowledges. > > I'm not convinced that we cannot learn from your development. Because is needed change the current exposition to something like that: http://www.youtube.com/watch?v=4-T-yF3tXCc&feature=related http://www.youtube.com/watch?v=RyO7v06xlWM&feature=related Forget for a moment that is from M$ XD The wonderful of that is the language for define the UI interface, XAML, where you can describe not only basic propertys of "morph" like colors or positions, but too animations, mouseOver effects, timers, movies... And you can use editors of XAML, external from environment, for create more rich UIs. I don't think WPF/XAML/whatever is good or bad (indeed I don't care :). But I think there's lot of value in having UIBuilder with "old mechanism" *now*. Do you think we can easily get it out of experimental / alpha state ? Or is there design/architecture mistakes such as thinking of creating applications with it is harmful ? For the future, something based on Morphic 3 isn't the right way ? Cheers, Laurent The current UIBuilder is based on old mechanism for build views, and surely with a lot of errors. I believe that that is the best direction for something more new and correct. _______________________________________________ Pharo-project mailing list [email protected]<mailto:[email protected]> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
