Customization Overrides UI
Summary
Provide UI that guides overrides creation without requiring file name and location knowledge.
Detailed Description
Currently, to perform an override, I need to know the file name and location within Program Files of the file that controls a certain area of function, such as Page.asp. Then, I need to create the structure in my project/stationary, copy the default file to that new location, and modify the file in that location. If the control file name changes between different versions of ePublisher, I need to learn about those changes.
I'd prefer a simple task-based UI that gives certain options, such as "Create custom page layout", that when you select it, it would copy the Page.asp file to the correct location in my project and then open it in a text editor (or an editor of my choice). This way, if you change file names and locations, I don't care (you could even migrate my project overrides for me!!!). I also don't need to learn about all the control file names and locations to make a change (I would learn by selecting the correct option, though).
This approach could also reduce documentation requirements, since this task-based approach, plus comments in the control files, could provide the needed guidance.
Use Cases
Creating all override files, such as Page.asp.
| syd | This would save a lot of us a lot of grief! jjj |
2007-11-08 14:05:56 X | ||
| Emelita | This is a great idea. I'm trying to do project overrides for Mark of the Web. I have not been successful |
2007-12-04 15:10:34 | ||