2012-10-03 11:50, Test wrote:
> I have a web page that has a lengthy menu structure containing hundreds of items.
That means a problem in usability, no matter how you implement it. But
sometimes such things may be necessary. Then the first thought should
be: can this be implemented in an application-like manner? That is, as a
"single-page application", or as an "HTML5 application", to use the
common term (which is rather misleading, since it's mainly about
> When user clicks a link the page reloads and depending on the situation a shorter
> version of the list is shown to user.
In an application-like approach, there are no page reloads. Only the
part that needs changing is changed. Maybe just "with style", as you can
hide elements with CSS. But e.g. for a select menu, you would have menu
generated from it, using different setups.
> Currently I am using forms and user is clicking on a:
> <a target="BLAH" href="mypage.php?PARAM=125">Click this</a>
button instead of a link, and clicking on the button would just set a
variable, followed by whatever updates it requires to document content.
Of course, this approach means that client-side scripting must be
enabled in the browser.
> Reloading the entire structure takes time and. Is there a way to keep the
> structuredata and reuse it between page loads? Cookies perhaps?
Well, there are frames... and they have in a sense received absolution
in HTML5 drafts, which make <iframe> a citizen of HTMLland with full
hum... I mean elemental rights. If you are very brave, you could even
use classical frames, with <frameset> and all.
But it really depends on the context and what the big picture really is.