> The JSON plugin is stable in all respects except that it hasn't been
> released as a 1.x. I use it a lot and haven't encountered any problems
> since adding enum support.
>
we are finding this issue also.
>
> However the REST Plugin itself actually uses json-lib:
> http://json-lib.sourceforge.
Frans Thamura wrote:
right,
i think that it is nice they separated view meta to create the form, and
model meta to fill the value in the input form inside form
but.. if we move all of our project, the json plugins is not stable version,
will this make the code of mine become unstable
that w
On Tue, Apr 8, 2008 at 6:07 AM, Jeromy Evans <
[EMAIL PROTECTED]> wrote:
> 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
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
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.
Fran
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 i
6 matches
Mail list logo
