Suggestions: File Layout Editor

[Brady Kelly]

I'd would like some suggestions on how to implement the actual bands, or
groupings, editor GUI for a file export system I am busy with. Currently, I
have a tree view on the left, explorer style, which lists as top level nodes
all the Sections in an export, e.g. Customers, Clients, Customer Invoices
etc. Then, under each section I have the data source queries for that
section, and all record defintions, i.e. column collections, for that
section. Now in the XML definition file, under the record definitions, I
have groupings to one level, where each grouping may be on Invoice Number.
Each grouping can have a header, emitted once before each group, body
emitted for each item in the group, and a footer, emitted once after each
group. Header, body, and footer can contain one or more lines that
correspond to record definitions. I'm now looking for ideas on how to
present the layout of these groupings to users for editing.


===================================
This list is hosted by DevelopMentor� http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

[Mike Andrews]

I'm not exactly sure what you mean but I know that you can build a
substantial object model hierarchy that then can be easily adapted to the
tree/listview model. You can also use XML serialization to write out the
objects to and from the file.

Post by Brady Kelly
I'd would like some suggestions on how to implement the actual bands, or
groupings, editor GUI for a file export system I am busy with. Currently, I
have a tree view on the left, explorer style, which lists as top level nodes
all the Sections in an export, e.g. Customers, Clients, Customer Invoices
etc. Then, under each section I have the data source queries for that
section, and all record defintions, i.e. column collections, for that
section. Now in the XML definition file, under the record definitions, I
have groupings to one level, where each grouping may be on Invoice Number.
Each grouping can have a header, emitted once before each group, body
emitted for each item in the group, and a footer, emitted once after each
group. Header, body, and footer can contain one or more lines that
correspond to record definitions. I'm now looking for ideas on how to
present the layout of these groupings to users for editing.
===================================
This list is hosted by DevelopMentor(R) http://www.develop.com
View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentor® http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

[Brady Kelly]

Thanks Mike. I'm sorry I sent this to the DOTNET-WEB accidentally, instead
of DOTNET-WINFORMS.

I've taken it there now, but so long I'm going with a ListBox as a line
editor, with one or two lines per 'report band', and will implement
independant character scrolling on each line. That should take care of most
requirements.

Post by Mike Andrews
I'm not exactly sure what you mean but I know that you can build a
substantial object model hierarchy that then can be easily adapted to the
tree/listview model. You can also use XML serialization to write out the
objects to and from the file.

===================================
This list is hosted by DevelopMentor� http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com