I had looked at Miller columns before but not seriously thought the approach would be useful until I saw Chang's excellent Tensor UI demo.
I have created a working prototype UI based on Miller columns for iotaWave. These are my thoughts thus far: 1. For our purposes, we need N columns; where N is variable depending on use-case but could be up to 8 columns. Therefore the columns need to be re-sizable, minimisable, etc, This causes *a lot* of cross-browser development fun (in particular relating to what Firefox does to iFrame (gadget) content. Chrome is much better. ... haven't started on the various IE flavours yet). 2. Multiple columns (with divs for resize, minimise, maximise, title, grab bars, etc.) is a *real* pain in cross-browser CSS. HTML tables help greatly to manage columns and their content. 3. Sometimes columns need to be visible on the screen at the same time, sometimes scrolling right works ok. (This is design/usability-related but has the expected knock-on effects to coding). 4. Populating the columns with DOM operations (lower-level control but more code) or innerHTML (simpler but faster) has knock-on implications for aforementioned minimising, etc. I've spent 10 days working to create a useable (iotaWave-integrated) UI. Two days on the core development. Eight days on cross-browser issues. Beware. I too agree that inline replies can make a wave horrible. We have been holding-off implementing inline replies for that reason (and the fact that the average user has too many editing options to mentally comprehend), I follow your thoughts/ideas for their extraction with interest. -- Chris iotawave.org Singapore -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
