Hello
Lukas. <br><br><span class="q"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><span class="gmail_quote"></span>> In order to ease the work with our web application we have added component
<br>> support for Seaside. It's what is called "AJAX Framework" out there,<br>> although we preferred not to call it "framework" nor toolkit by now. Much of<br>> the ideas of this package are based on WindowBuilder Pro, a commercial
<br>> window builder that enables visual programming.<br><br>That sounds very exciting. Is the JavaScript part specific to Seaside<br>or did you reuse an existing libraries?</blockquote></span><div><br>Javascript is specific to Seaside, we are trying to provide a
common interface for event handling and to mix well with Scriptaculous
but we are evaluating alternatives.<br><br></div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Right now we have support for most common web controls (TextField, Panel,
<br>> RadioButton, TextArea, Label, Button, Anchor, CheckBoxGroup,<br>> RadioButtonGroup, ListBox, FieldSet) and we are working on a builder tool<br>> for generate Seaside components (pages) dinamically. We call it
<br>> SeasideBuilder.<br><br>Will SeasideBuilder also allow to visually connect controls with each<br>other and the model, like this is done for example in Cocoa? How does<br>it update the control (polling, server push)?
</blockquote></span><div><br>No. If you are thinking in Visual Language
Systems with icons like LabVIEW, ProGraph or even PARTS, that's not
what we had in mind at first. Right now it would fall into a web
interface for a textual language. <br>If I understood right your question, the builder uses a proxy
over the control, that's updated after you finished with the properties.<br></div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> With the builder you'll have to pick the control you want, configure<br>> properties, preview if you want it, and finally add to a page layout tree.<br>> When the tree is already configured properly, code for the rendering and
<br>> controls is compiled into the class, along with tree support for future<br>> editing with the tool, although this is under heavy developement.<br><br>Drag & Drop? Will you be able to edit a control again, after it has been added?
</blockquote></span><div><br>That's the idea. <br><br></div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Maybe this work could be interesting for someone out there. If so, we'd
<br>> have to ask our institution for permission to release a public version under<br>> an appropiate licensing (GPL, LGPL, BSD, etc).
<br><br>That would be great! Please consider that Seaside and most (if not<br>all) Seaside related frameworks are released under the MIT license.<br><br>Looking forward testing your "framework".<br><br>Lukas</blockquote>
<div><br>Juan M. <br></div><br></span>