Some questions about Magritte

> Hi!
>
> I and a collegue are building a "form engine portal"-kinda-thingie  
> and we are using Seaside3.0 and Magritte. The goal is to create a  
> "standard" for describing wizard-like-forms and then to use Magritte  
> to create a good looking "engine" for these wizards.
>
> Now, as I can see it seems that Magritte has no notion of "pages" as  
> in a wizard or anything wizard-like, right? So my current conclusion  
> is that it would be best for us to create the Wizard component that  
> uses a dynamically generated Magritte component for each "page",  
> seems reasonable?
>
> Secondly, how hard is it - or can Magritte already use say JQuery to  
> do "immediate" validation etc on fields? We need to be a biz snazzy  
> here and make it look good so I want to be able to do validation  
> when the user moves focus from a field etc.
>
> Anyway, it is fun to get into Magritte (last time I looked it was  
> slightly immature and we opted to build our own "similar" thing in  
> Gjallar instead of reusing Magritte) - but could someone point to  
> more good examples perhaps? The unit tests are written in an ...  
> "economic" style which doesn't leave them as easily digested  
> examples IMHO. ;)
>
> regards, Göran
>

> Hi!
>
> I and a collegue are building a "form engine portal"-kinda-thingie and we
> are using Seaside3.0 and Magritte. The goal is to create a "standard" for
> describing wizard-like-forms and then to use Magritte to create a good
> looking "engine" for these wizards.
>
> Now, as I can see it seems that Magritte has no notion of "pages" as in a
> wizard or anything wizard-like, right? So my current conclusion is that it
> would be best for us to create the Wizard component that uses a dynamically
> generated Magritte component for each "page", seems reasonable?

> Secondly, how hard is it - or can Magritte already use say JQuery to do
> "immediate" validation etc on fields? We need to be a biz snazzy here and
> make it look good so I want to be able to do validation when the user moves
> focus from a field etc.
>
> Anyway, it is fun to get into Magritte (last time I looked it was slightly
> immature and we opted to build our own "similar" thing in Gjallar instead of
> reusing Magritte) - but could someone point to more good examples perhaps?
> The unit tests are written in an ... "economic" style which doesn't leave
> them as easily digested examples IMHO. ;)

> Hi!
>
> I and a collegue are building a "form engine portal"-kinda-thingie and we
> are using Seaside3.0 and Magritte. The goal is to create a "standard" for
> describing wizard-like-forms and then to use Magritte to create a good
> looking "engine" for these wizards.
>
> Now, as I can see it seems that Magritte has no notion of "pages" as in a
> wizard or anything wizard-like, right? So my current conclusion is that it
> would be best for us to create the Wizard component that uses a dynamically
> generated Magritte component for each "page", seems reasonable?
>
> Secondly, how hard is it - or can Magritte already use say JQuery to do
> "immediate" validation etc on fields? We need to be a biz snazzy here and
> make it look good so I want to be able to do validation when the user moves
> focus from a field etc.
>
> Anyway, it is fun to get into Magritte (last time I looked it was slightly
> immature and we opted to build our own "similar" thing in Gjallar instead of
> reusing Magritte) - but could someone point to more good examples perhaps?
> The unit tests are written in an ... "economic" style which doesn't leave
> them as easily digested examples IMHO. ;)
>
> regards, Göran
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

> Hi!
>
> I and a collegue are building a "form engine portal"-kinda-thingie  
> and we are using Seaside3.0 and Magritte. The goal is to create a  
> "standard" for describing wizard-like-forms and then to use Magritte  
> to create a good looking "engine" for these wizards.
>
> Now, as I can see it seems that Magritte has no notion of "pages" as  
> in a wizard or anything wizard-like, right? So my current conclusion  
> is that it would be best for us to create the Wizard component that  
> uses a dynamically generated Magritte component for each "page",  
> seems reasonable?
>
> Secondly, how hard is it - or can Magritte already use say JQuery to  
> do "immediate" validation etc on fields? We need to be a biz snazzy  
> here and make it look good so I want to be able to do validation  
> when the user moves focus from a field etc.
>
> Anyway, it is fun to get into Magritte (last time I looked it was  
> slightly immature and we opted to build our own "similar" thing in  
> Gjallar instead of reusing Magritte) - but could someone point to  
> more good examples perhaps? The unit tests are written in an ...  
> "economic" style which doesn't leave them as easily digested  
> examples IMHO. ;)
>
> regards, Göran