Quoting Damien Cassou <
[hidden email]>:
>
[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.
>
>
> Hi Esteban,
>
> I don't think there already is a ui builder for Seaside. Moreover, in
> my opinion, UIBuilder or such tools can't be used with seaside because
> there is much more things you can do in VW you can't do with web
> applications. And in web applications, you can't say put this widget at
> 29@123 pixels and this one 2 pixels bottom. This can't work. Last but
> not least, forms are most of the time built automatically by
> composition ; not sure how it can be done with a mouse.
>
> However, if you have a solution, I would greatly appreciate to test it :-)
>
> Bye
Hi Damien,
You can place a widget in exactly the position you want in a web
application using css. ie.
.button1{
left:5px;top:5px;
}
Moreover you can compose "subcanvases" using divs. I know that there
are some restrictions on what kind of events can be propagated to an
Application model from a web application but I think that this gap is
so little now with the use of AJAX that it could be possible not to
refresh the whole screen for a little change. May be if there are some
features that are not supported using a SeasideUIBuilder it should log
on the transcript those things.
Although this implementation things it would be nice to separate the
notions of the button abstraccion from it`s implementation.
Regards
Esteban
----------------------------------------------------------------
Este mensaje ha sido enviado utilizando IMP desde LIFIA.
----- Terminar mensaje reenviado -----
----------------------------------------------------------------
Este mensaje ha sido enviado utilizando IMP desde LIFIA.