aspose file tools*
The moose likes OO, Patterns, UML and Refactoring and the fly likes Dynamic screen and table generation Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "Dynamic screen and table generation" Watch "Dynamic screen and table generation" New topic
Author

Dynamic screen and table generation

demo man
Greenhorn

Joined: Oct 06, 2009
Posts: 3
We have an j2ee based web application where currently the screens are static with heavy usage of JavaScript .
we have a requirement where we would need to built the screens dynamically. Each screen denotes one table . Could anybody let me know any web based approach where we could create the screens dynamically. There are lots of calculation occurring in each fields using JavaScript .
we need that all this need to be somehow generated dynamically by the admin user of the application who will have the capability to iinput all the details (formulas, calulations) etc by himself. Also how
could we achive the db design for this approach.

What type of architecture is best suitable for such a requirement where the screen itself can be added by the admin user of the aplication . The biggest challenge i think to how do we create such screens dynamically using some meta data approach and how do we represent such data

Any help on this is highly appreciated
Hong Anderson
Ranch Hand

Joined: Jul 05, 2005
Posts: 1936
My advice is, don't do that. You should use static screens, it's much easier to implement and more importantly ... to change.

From my expirence, it's appealing an idea at first, but it's very difficult to make it flexible, and the code will be much more complicated than using static screens.


SCJA 1.0, SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJP 5.0, SCEA 5, SCBCD 5; OCUP - Fundamental, Intermediate and Advanced; IBM Certified Solution Designer - OOAD, vUML 2; SpringSource Certified Spring Professional
yooon chin
Greenhorn

Joined: Oct 08, 2009
Posts: 7
Each screen denotes one table is not a good idea, but it is a time-saving idea.

The db design solution depends on much more investigation from business level.

And important part is DB designing is the first step to do this task.
Hong Anderson
Ranch Hand

Joined: Jul 05, 2005
Posts: 1936
yooon chin wrote:Each screen denotes one table is not a good idea, but it is a time-saving idea.

In most applications it's not a good idea, but in specific area of applications it's good. For example, DBMS front-end applications can generate screen to edit data dynamically based on the table schema. It's all right because the users of the application are technical users.

But for an application that its users don't have technical perspective doing this might save time at first, but it'll consume more time later in struggling to make the UI richer or make some screens differ from other screens. UI generator is best if all screens look the same, but if each screen can be different it would be difficult to make the UI generator flexible enough and the code will be much more complicated that it's needed to be.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Dynamic screen and table generation