Simplifying the designer - Saving a lot of mouseclicks

Edit Subject

I add,

3) bulk delete items (fields, datafields, pages)
4) a option to apply all changes made in Edit Form to Create Form or vice versa (templates, fields)

Yes, there could be lots of streamling, these are great ideas.
I'm wearing my mouse out!

pat.

#5 - Ditch the "wizard" That's fine for the first time you set up a project but after that, all the settings should be available in a filterable tree view so you can just search for things like reporting and get all the reporting options that otherwise you have to go back and forth in the opening dialogs to find.

Another usability item that bites almost everyone in the butt at some point is refreshing metadata. This should be a step-by-step confirmation of the changes being introduced through adding tables and updating the field metadata. Popping up a spreadsheet may be useful but it confuses everyone until you get a chance to play with it.

Hello everyone,

you may be right, my proposals aimed to simple implementation. It looks to me that those changes could be made simply by using codeontime generator for the designer.

Anyway, i was looking for the projects and stuff and found a lot of xml files in my projects directory.

DataAquarium.MetaData.xml, *.Application.xml, Controllers.xml

Is my guess correct, that this is the generators metadata? Which encoding do them files have (utf-8)?

I could spare a lot of time patching these files using scripts and little proggies, then?

Greetings,
Stefan

hi Stefan,
Yes, the .xml files are where all the changes are kept.
I did consider too writing utilities to parse the changes, but haven't done so yet.
It is still a bugbear that changes cannot easily be rolled back.

ie you make a change that breaks your app, but not sure which change broke it!

Currently it is not possible to roll back changes or to point in time; that would be a godsend..

Pat.