Looking for some advice...
-
I'll try to keep this short :) I am working on an app for which I would like the user interface to be customizeable. Not just in appearance (control location) but in terms of content as well. I am considering have a series of DATA tables in the database that contain the content" for the application, and a METADATA table that contains a mapping for DATA fields, and form controls (including screen position, labeling, etc). The mapping capabilities will need to be 2-way, meaning a screen scrape-> persist as well as read from db -> display. (For performance reasons, I am thinking that creating an in-memory cache of "rendered" forms for the different DATA types would be usefull. Not sure exactly how to handle this.) Has anyone else tried something similar? Does anyone see any major "landmines" that I am about to step on? Mike Stanbrook mstanbrook@yahoo.com
-
I'll try to keep this short :) I am working on an app for which I would like the user interface to be customizeable. Not just in appearance (control location) but in terms of content as well. I am considering have a series of DATA tables in the database that contain the content" for the application, and a METADATA table that contains a mapping for DATA fields, and form controls (including screen position, labeling, etc). The mapping capabilities will need to be 2-way, meaning a screen scrape-> persist as well as read from db -> display. (For performance reasons, I am thinking that creating an in-memory cache of "rendered" forms for the different DATA types would be usefull. Not sure exactly how to handle this.) Has anyone else tried something similar? Does anyone see any major "landmines" that I am about to step on? Mike Stanbrook mstanbrook@yahoo.com