[Seaside] Re: Form generation and validation

[Esteban A. Maringolo]

I also use Magritte for form validation and editors.

As others also mentioned, Magritte has the building blocks to start
doing what you need.

However, it is not perfectly suited for highly interactive UI's like
nowadays web interfaces, where lots of parts of the UI change in
reaction to others.

I found QCMagritte covers a lot of what could be missing in Magritte,
but its discovery is not straightforward as it is with Magritte, so
you have to look at tests or examples to figure out if it does what
you need and how to use it.

Regards!


Esteban A. Maringolo


2015-02-09 10:18 GMT-03:00 Mariano Martinez Peck <marianopeck at gmail.com>:
> Hi Hilaire.
>
> For the customer I have been working, we are using Magritte. However, we
> have extended it soooo much that I am not sure which % of magritte we are
> still using. We use our each component for each type of description (most of
> them subclasses of Magritte ones), some own descriptions, own memento + own
> hooks, own table renderer, own magritte-report, own columns... Everything is
> AJAXfied and Bootstrap styled.
> Quite similar to QCMagritte I would say, but maybe more features. The code
> is not mine (but my client one) and we are analyzing different possibilities
> to do something with this CRUD system we developed.  But we must first focus
> in the domain usage of it (financial app) that we have now.
>
> All of this is to say that Magritte is good to use it, but you likely need
> to understand it and extend it to have something really useful.
>
> Best,

>