Juergen Donnerstag wrote:
Question 3:
In our design, we want the customer to be able to lay the
components in a simple, stacked, sequential layout for the future, so
we actually have one Page/PageLayer, which gets the order of the
components and calls them accordingly. So I will probably be using
something like ListView with sequential Panels inside, which will be
the actual components. Has anyone tried something similar, meaning a
one page app instead of the regular multiple pages approach? Will
there be any problems bugging me in the future if I choose this approach?
just out of curiosity. What is the reason why you want to go with this approach?
This is because in the future, the customer wants to be able to arrange the
components and create new pages with them via a GUI interface. So in my
view, this leaves two possibilites for the future: Either have the
future GUI
generate the javacode and the html for the pages (does not look good to me),
or have a design where I already have a metapage actually creating the
pages from page data stored somewhere, so the GUI will act upon that
data to
create the pages. Since I will have to process that data to create the
pages as
well, the one page approach comes in. The customer only wants to
be able to lay the components down in stacked format (meaning on top of
each other no left right stuff) so comes the ListView.
So that was the reason I was thinking of this approach.
utku
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
