mherger wrote: > > But I would think that the change in views should be doable without a > > major amount of work, or am I off base on that? > > We're talking about static HTML web pages. Different views create > different _static_ HTML on the server side. Replacing this would > basically require to replace the static HTML with some client side AJAX > > solution. Which is the biggest chunk of work on the way to a new UI: > implement the SlimBrowse menu.
Would there really be a need for AJAX? What happens if you have the references for the cover images within the static page and then rearranged the page using only JS and CSS? In other words, you generate only one (static) page and the layout is handle client side. Would it mean that all of the small and large covers would be requested/downloaded by the browser every time? Yes, I could see how that's less than ideal. But if that's the case, you could also just get rid of the small artwork references and let the browser resize the larger cover images client-side for the small artwork view. Then, worst case, it's no worse server-side than generating the large artwork page is now. ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=101248 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
