Hi Lars, > -----Original Message----- > From: Lars Trieloff [mailto:[EMAIL PROTECTED] On Behalf Of > Lars Trieloff > Sent: Monday, June 09, 2008 8:10 AM > To: [email protected] > Subject: Re: JCR browser > > Hi David, hi Craig, > > On Jun 9, 2008, at 10:19 , David Nuescheler wrote: > > > hi craig, > > > > i think this is a great start. congratulations. > > there are a couple of observations that i made which are > likely to be > > unrelated to the use dojo so i thought i'd share them here. > > > > (1) deep links, bookmarks & backbutton since i am fan of deep links > > into content when i am sharing content locations i think it > would be a > > great feature to expose the current navigation path in the > url that's > > displayed in the browser. > > this can for example be done through a #<path> in the url basically > > whenever i click on a folder in the tree. > > this should also fix back button and bookmarkability. > > Having the #path is a good idea, you should also take a look > at dojo.back > (http://api.dojotoolkit.org/jsdoc/dojo/HEAD/dojo.back) which > offers more sophisticated back button functionality. >
I'll take this all under advisement. I hadn't given any of this any thought yet. > > (2) cookies > > it seems that all the opening states of the tree are stored in > > cookies... i would probably only store the last open > position in the > > cookie since in my experience it is sometimes even more > desirable to > > have sort of a "clean" start, with only my last position reopened ;) > > This is actually a feature of the Dijit Tree Control. But you > can easily disable it using the persist property > http://api.dojotoolkit.org/jsdoc/dijit/HEAD/dijit.Tree.persist > (add persist="false") to the div. My personal opinion is: I > like the way the tree handles persistence right now and would > not change it. > I'll let you guys decide what should happen here, I don't have a preference really. I was just happy I got something for free from the tree control ;-) > > (3) safari works beautifully... > > ...but complains about a slow script 3 times before the > browser starts > > up. > > i think this could be addressed by looking into what takes the load > > time. > > in firefox with firebug enabled for tracking the startup of roughly > > 43s which is probably most network latency related. > > > > (4) network roundtrips > > i think that once the browser is up and running the amount > of network > > traffic that is transported is in very good shape. > > i stumbled over an incident that surprised me a little bit though. > > i expected a single .json to be transported to the client > when i would > > open a new tree node clicking on the [+], which is true for most > > nodes, but not for nodes with deep children underneith... > for example > > opening /images issued 9 http requests. > > Blame Lars :-) The NodeStore issues one request per child > node because only the specified node is fetched. You can > change this, however. > Yeah, I can definitely make the tree do one GET when the node is expanded with "stub" information about the children in that one request. As I alluded to in my other post, I've done this before. > regards, > > Lars > Cheers, Craig
