Does that mean ExtFS can build a form from a json (or xml)
specification? I've needed that myself.
I don't see anything wrong with your approach. In fact I like it. The
view (form) is nice separated from the model (data).
Frans Thamura wrote:
take a look of this
http://farm3.static.flickr.com/2018/2394469980_a9984272d8.jpg?v=0
this is our current approach, a s2 action for form, and another action for
value
i use the ExtJS, and run well here :)
thx to the ExtJs GUI Designer team
but i am seeking another cool stuff that beter.
Frans
On Mon, Apr 7, 2008 at 10:08 AM, Jeromy Evans <
[EMAIL PROTECTED]> wrote:
I'm not completely sure what you mean but two things come to mind:
- the s:action tag is useful for pages that need to be assembled using the
results from multiple actions. If each each outputs a component of the
view, you can uses Tiles or Sitemesh to assemble a page on the server-side
that invokes numerous actions. You can then reuse the components and design
actions around each data model instead of each page.
- as you're using ExtJS, you can use the same pattern as described above,
but invoke each action XHR. The page can be assembled via ExtJS on the
client-side with your actions returning data or html fragments as
appropriate.
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.519 / Virus Database: 269.22.8/1362 - Release Date: 6/04/2008 11:12 AM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
