Interesting topic. After reading a few posts talking about the merits of
replacing panels and whatnot, I decided to try to develop an application
that has one page and essentially ALL requests will be AJAX based. I
thought it would be interesting to try to create a webapp that functions as
close
I'm currently working on a project that requires all (or almost all)
pages to be bookmarkable.
My solution is to have different "views" for each page depending on the
input parameters. This is actually working out well, since the page is
really a kind of container with an associated URL space, an
> However, I discovered a navigation issue and am considering adding the
> Breadcrumb feature to this site. Unfortunately, it looks like the
> breadcrumb control uses Panels instead of pages. So it looks like I
> need to switch everything from being page-based to panel-based. Of
> course, doing
I'm interested in how others typically build a web application in
regards to using many Pages or very few Pages with Panels for
different "web pages" of content. I'm not referring to using smaller
reusable panels within pages/panels, but main Panels that encompass
the majority of the content of a
