<div>The custom form design and variable length list stuff is default <a href="http://asp.net">asp.net</a> mvc.</div><div><br></div><div>The validation stuff I ended up writing myself using F# quotations, it goes a couple steps farther than what I even mentioned as it converts the F# to javascript so you get server side validation and client side validation for free. Here's the github project: <a href="https://github.com/jgreene/FSharp.Javascript.Mvc">https://github.com/jgreene/FSharp.Javascript.Mvc</a> and you can read more about it here: <a href="http://justsimplecode.com/">http://justsimplecode.com/</a></div>
<div><br></div><div><a href="https://github.com/jgreene/FSharp.Javascript.Mvc"></a>There is not much documentation, and there is some complexity to setting up a framework to do something like this, but it's very doable.</div>
<div><br></div><div><br><br><div class="gmail_quote">On Wed, Jun 1, 2011 at 8:44 AM, Mark Bradley <span dir="ltr"><<a href="mailto:barkmadley@gmail.com">barkmadley@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, Jun 1, 2011 at 11:32 PM, Justin Greene<br>
<<a href="mailto:justin.j.greene@gmail.com">justin.j.greene@gmail.com</a>> wrote:<br>
>> * Forms package: It's been rewritten, but hasn't really had much input<br>
>> from others. Now's the time to speak up if you have any opinions on<br>
>> it. The code is available on Hackage.<br>
><br>
> List of things that should be inside a forms package in my opinion.<br>
> Custom Design: Form layout should be simple to customize and not be based<br>
> around auto generating tables (if both are possible then of course the later<br>
> can be used).<br>
> Variable length lists: It should be possible to add form elements on the<br>
> client side and bind them on the server side. An example of this would be a<br>
> list of addresses. A programmer should be able to add a new address widget<br>
> client side without problems when binding server side.<br>
> Validation: Complex validation scenarios should be simple and should fit<br>
> into the normal validation pipeline. An example would be validating that if<br>
> a checkbox is selected then a textbox becomes required.<br>
> All validation errors should display around the same time, e.g. if a type<br>
> validator fires it should not prevent other validators from firing after it<br>
> unless those validators depend upon that type data.<br>
> These are just my thoughts based upon my experiences writing forms. I can't<br>
> really utilize any framework that doesn't implement these features for the<br>
> types of projects I do.<br>
> If you need any more details/clarification I'd be happy to help.<br>
<br>
</div>out of curiosity, which frameworks have you worked with that have some<br>
or all of these features (particularly the complicated validation)?<br>
<div><div></div><div class="h5"><br>
><br>
><br>
><br>
><br>
> On Mon, May 30, 2011 at 3:41 PM, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>><br>
> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> It's been about a month since the 0.8 release of Yesod. In the release<br>
>> announcement[1], we laid out some goals. Let's take a chance to<br>
>> analyze where we're at:<br>
>><br>
>> * Documentation: Still improving as always. In particular, the new<br>
>> Yesod site is making it much easier for me to write new content (I<br>
>> have a few things on my local system that can finally go up).<br>
>><br>
>> * Static file caching headers: Implemented by Greg Weber. We'll likely<br>
>> be making some API changes to handle embedded files, though that<br>
>> discussion deserves its own blog post.<br>
>><br>
>> * Other template types: For Hamlet 0.9, we're going to be splitting<br>
>> Julius/Coffeescript into their own package, and juggling the type<br>
>> signature for Coffeescript a bit. At that point, it should be<br>
>> straightforward to embed Coffeescript directly into a Yesod app, just<br>
>> like Julius is today.<br>
>><br>
>> * Something like require.js: This is something we haven't started on<br>
>> yet. I'll likely start looking into it this week. Additionally, I know<br>
>> that a lot of my sites (jQuery powered) have numerous onload calls per<br>
>> page; I think we can try to make that more efficient as well. I would<br>
>> especially like people's input on this point.<br>
>><br>
>> * i18n: The solution is written, and I'm using it in production. At<br>
>> this point, I'd call it beta quality, and I'd appreciate input.<br>
>><br>
>><br>
>><br>
>> * Embedded objects in MongoDB: No work done yet.<br>
>><br>
>> * Performance improvements: Nothing in particular. If you have any<br>
>> examples of Yesod performing badly, please let us know.<br>
>><br>
>> The goal is for Yesod 0.9 to be feature complete, and for 1.0 to be a<br>
>> fairly stable API. From the list above, my two priorities are better<br>
>> Javascript loading (require.js) and static file serving. However,<br>
>> there's one other major issue we need to address: the devel server.<br>
>> Unfortunately, it doesn't work very well at all right now. Thankfully,<br>
>> "yesod build" *does* work very well, and for my development I've<br>
>> fallen back to simply "yesod build && ./dist/build/myapp/myapp" on the<br>
>> command line. My guess is that we're 90% of the way there on "yesod<br>
>> devel". This is a project that isn't tightly bound to the rest of the<br>
>> API work, and would be very approachable for someone trying to get<br>
>> started on Yesod development. If you're interested in helping out<br>
>> here, please let me know.<br>
>><br>
>> I have no specific timeframe in mind for Yesod 0.9. As it stands now,<br>
>> it looks like the 0.9 release will involve almost no API breakage,<br>
>> which is a very good sign. But if you have any ideas you'd like to<br>
>> contribute, I'd recommend getting them in in the next week or two.<br>
>><br>
>> Michael<br>
>><br>
>> [1] <a href="http://www.yesodweb.com/blog/2011/4/announcing-yesod-0-8" target="_blank">http://www.yesodweb.com/blog/2011/4/announcing-yesod-0-8</a><br>
>><br>
>> _______________________________________________<br>
>> web-devel mailing list<br>
>> <a href="mailto:web-devel@haskell.org">web-devel@haskell.org</a><br>
>> <a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
><br>
><br>
> _______________________________________________<br>
> web-devel mailing list<br>
> <a href="mailto:web-devel@haskell.org">web-devel@haskell.org</a><br>
> <a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
><br>
><br>
<br>
<br>
<br>
</div></div><font color="#888888">--<br>
-barkmadley<br>
sent from an internet enabled device<br>
</font></blockquote></div><br></div>