I actually made a conscious decision not to build property inspector because I wanted to explore the idea of building a tool that gives you visual feedback as you *code* (ignoring the fact that the drag and drop part seems the most useful at the moment!).
This could involve something like inline documentation, where if you are typing inside an array property the docs (including all the attributes of the array formtool) could appear in a panel to the satire, and a popup list of attributes could assist you as you type (code completion). It may turn out that all 3 ideas are as useful as each other, but I like the idea of the developer learning what they are building rather than just configuring a toolbox of options and hoping for the best :) Haha.. Please keep the discussion coming though, it's all useful in shaping where we can go with this. cheers, Justin On Nov 12, 2012 5:41 PM, "Jeff Coughlin" <[email protected]> wrote: > Yeah, but I think AJ's right in that having a property inspector not only > helps developers when building forms, but also gives them insight into > other options and features they might not be aware of or maybe forgot about. > > -- > Jeff Coughlin > > On Nov 11, 2012, at 21:10, Geoff Bowers <[email protected]> wrote: > > On Saturday, 10 November 2012 07:22:51 UTC+11, Sean Coyne wrote: > >> I used it recently for a rule, but ran into an issue. It was "user >> error" but it brought something to mind. So I had created the whole rule >> and then accidentally I performed a swipe gesture on my trackpad which >> triggered the browser's back button wiping out all my work! This was a >> little upsetting :) >> >> So I was wondering if you could use the browser's local storage to store >> the current working file and even add a "Save" feature which saves it to a >> file on the disk somewhere or just in local storage in the browser. I >> realize that is probably complicated but it would make it a little more >> idiot proof for idiots like me! >> > > I think a local store of the changes would be great too. I wonder if > using the Chrome Extension has this effect by default? Should certainly > block hitting the back button by default. > > >> Another idea I had was related to the other metadata. You can add the >> field to the form but you can't update the name easily and other metadata >> values (ftList for a list for example). If you could double click in a >> form item or somehow open up a little dialog w/ the other options and >> quickly adjust them that would be useful as well. >> > > You can change any of the metadata on the code side by just editing the > code. Changes on other side of the editor ie visual or code, are reflected > in the other automatically. > > All the best, > > -- geoff > http://www.daemon.com.au/ > skype. gb.daemon > twitter. @modius > > -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: [email protected] > To unsubscribe, email: [email protected] > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry > > > > -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: [email protected] > To unsubscribe, email: [email protected] > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry > > > -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
