Hi, I'm yet another newbie - sorry if these questions are out of place... Q1) What's the relationship between the wiki and this list? i.e. should discussions be posted here but code examples on the wiki? This list seems "busier" than the wiki - hence this is where I posted. However, IMO, the wiki (or perhaps a bulletin board) is a better vehicle for long running topics (such as requests for screencasts - see below).
Q2) I'd like to suggest a screencast that takes the viewer through developing a reasonably useful widget from an examination of the widgets goals, through good design decisions to the implementation and then leave the viewer with a few ideas of how the design could be extended. Perhaps the ajax_tables example "built from the ground up". OTOH, this might be too ambitious, but OTOH, it would serve a number of purposes: a) demonstrate the capabilities b) teach newbies the essence of Mochi style, patterns, norms c) encourage us newbies to submit possible widgets to the project Q3) I'm currently attempting to create a feature rich data grid (multi-column sort, filtering, in-place editing to name but a few) using the AJAX model with JSON and JSON-RPC. Aside from making the darn thing work I'd like to get the code critiqued - is the best way to simply post it to the wiki and sit back and wait? Or can I more proactively encourage a critique? (BTW, I've nothing to post yet - all I've done so far is hack at the sortable_table example before progressing to "grokking" the ajax_table example. Q4) Is there any interest in creating a "community" section on the wiki? Don't worry I'm not looking for a friendship service ;-) however, I'd like to know and share relevant discussions involving MochiKit and the blog seems to "belong" to Bob (so it doesn't seem appropriate to post there). Lastly MochiKit looks really excellent - I'm excited about programming again. Fwiw, I became a p.h.b. at work 3 years ago and have since only dabbled in programming - however now I'm attempting to start up some personal development projects. 3 years feels like a lifetime - I used to be a reasonably proficient C++ programmer. Thanks for taking the time to read this, John H.
