11May/053
Quick Elementer 2.0 is coming
I am in the works of adding two more features to Quick Elementer. This might be a little of a shock since 1.0 was release just over two weeks ago, and 1.1 just 4 days ago. Even if you are shocked you might like the improvements.
- Elementer dependancies - This will follow the OO concept and reduce the maintenance of quick elementers by having elementers inherit the design information from other elementers
- Copy documents - This would allow the coping documents with the design elements. This would allow the quick elementer information to be moved with the design elements, sorry no inheritance for documents.
This is all I had ever planned for this tool, I just did not think that I would be implementing all of them so quickly. Please let me know if you have any other suggestions.
May 12th, 2005 - 08:35
Is there a way to grab just one shared action? Right now it’s showing $ACTIONS which I would assume would take all of them.
Also, while you are sorting elements by name or type, it would be nice to be able to filter by type. I can imagine there could be a lot of elements eventually so it might be more convenient to isolate the design elements.
Just some thoughts. It’s a great database!!
May 12th, 2005 - 09:11
Shared actions contain all the actions, it would be like asking for a field on a form. When every I implement reusable design elements all my actions appear in the view, form or subform just for this reason.
I do like the idea of filtering by a type. Would you expect to see the selecting items in the list? Maybe at the bottom of the list.
May 12th, 2005 - 11:36
Chad,
Ideally I think the box on the form should only display the elements associated with the module. Currently you’re showing all elements on each document but only have checked the appropriate ones. So maybe you should only store the selected items on the document, and do something else to actually choose the items… wether it’s a dialog box or whatever… Maybe we have a selection form in a dialog box with radio options for all the design elements… or something.. Maybe in the database open event, you write all the design elements (name and key) to lookup documents. Then you can even use an embedded view…
Now for a pie in the sky thought….
Do you know what would really be sweet? You combine quick elementer with the concepts behind Alan Lepofsky’s Paste Information Application. (http://www.alanlepofsky.net/alepofsky/alanblog.nsf/dx/paste-information-application)
It would be cool to add that to Quick Elementer so you could also store code snippets, functions etc.. So now you have those in the same place as your forms and other elements.
A toolbar icon that would let you get to the snippets, or module form to initiate the copy would also be awesome. Now this might almost be a complete replacement for the TeamStudio product.
Just some thoughts…