Hi list,
I`m working with Seaside for about a couple of weeks and I think it`s excellent. I`m wondering if there is an extension to the UIBuilder in order to build UIs for Seaside. I have little idea of how UIBuilder works with specs so I inspect it and debug some particular cases of examples in order to understand it`s behaviour. After a few tests I realize that UIBuilder and Specs are mostly design for traditional Widgets which understand >>displayOn:. Does anybody question itself to do a refactoring to UIBuilder and Spec implementation. It would be useful to decouple the abstractions of buttons, input fields, checks, etc from their implementations in a particular framework such as MVC, Seaside, Pollock. In this way we can reuse the uipainter, the application model, etc independently from the UI framework we are using, and migrating from a desktop application to a web application just free. If there is some work on this I hope this mail would be forgotten. Regards Esteban ---------------------------------------------------------------- Este mensaje ha sido enviado utilizando IMP desde LIFIA. |
[hidden email] wrote:
[...] It would be useful to decouple the abstractions of > buttons, input fields, checks, etc from their implementations in a > particular framework such as MVC, Seaside, Pollock. It seems Magritte does the above: http://www.lukas-renggli.ch/smalltalk/magritte > In this way we can > reuse the uipainter, the application model, etc independently from the > UI framework we are using, and migrating from a desktop application to a > web application just free. R - |
In reply to this post by erobles-2
This is essentially what VisualWave does, but it doesn't do it for Seaside, but rather for its own mechanisms.
At 08:45 AM 8/17/2006, [hidden email] wrote: >Hi list, >I`m working with Seaside for about a couple of weeks and I think it`s >excellent. I`m wondering if there is an extension to the UIBuilder in >order to build UIs for Seaside. >I have little idea of how UIBuilder works with specs so I inspect it >and debug some particular cases of examples in order to understand >it`s behaviour. After a few tests I realize that UIBuilder and Specs >are mostly design for traditional Widgets which understand >>>displayOn:. Does anybody question itself to do a refactoring to >UIBuilder and Spec implementation. It would be useful to decouple the >abstractions of buttons, input fields, checks, etc from their >implementations in a particular framework such as MVC, Seaside, >Pollock. In this way we can reuse the uipainter, the application >model, etc independently from the UI framework we are using, and >migrating from a desktop application to a web application just free. >If there is some work on this I hope this mail would be forgotten. >Regards >Esteban > > >---------------------------------------------------------------- >Este mensaje ha sido enviado utilizando IMP desde LIFIA. > -- Alan Knight [|], Cincom Smalltalk Development [hidden email] [hidden email] http://www.cincom.com/smalltalk "The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross |
In reply to this post by Reinout Heeck-2
Reinout Heeck wrote:
> [hidden email] wrote: > [...] It would be useful to decouple the abstractions of >> buttons, input fields, checks, etc from their implementations in a >> particular framework such as MVC, Seaside, Pollock. > It seems Magritte does the above: > http://www.lukas-renggli.ch/smalltalk/magritte Not really. Magritte is used to built forms automatically from models. You describe your model (a person is represented by a first name which is a string, a last name which is a string, its birth date which is a date...) and the form to edit or create new persons is built for you dynamically on each rendering. You can even combine descriptions (a person has telephon numbers which is a collection of the model TelephonNumber). This has nothing to do with: I put a button here which will trigger this method, a list here, a menu on the left and a title bar with a big picture). |
Free forum by Nabble | Edit this page |