On Wed, Aug 15, 2012 at 09:28:48AM +0200, Lubos Kosco wrote: > On 14.8.2012 23:13, Jens Elkner wrote: > >On Tue, Aug 14, 2012 at 09:40:10PM +0200, Jens Elkner wrote: > >>On Tue, Aug 14, 2012 at 07:13:33PM +0200, Lubos Kosco wrote: > >... > >>>http://defect.opensolaris.org/bz/show_bug.cgi?id=13985 ... > >Anyway, after having a beer, a possibly easier to implement idea ploppt > >up: The key is Javascript ;-) : Intercept clicks on anchors below #src: > >if the path starts with '/source/' and servlet context is != '/source' > >replace '/source/' with $servletContext/ and pass the modified link to > >the handlers. Otherwise just pass through. > > > >So one could even shrink the '/source/' to a marker like '$', make the > >check even cheaper and gain some savings wrt. size (for AnanlyzerGuru > >~ -5.5% uncompressed). AFAIS no other sources need to be touched. > > > >Better? > if the meta header works (I'll try to dig up an example where it failed > for me, but it might be that I just hit some browser bug back then, > after all it's been couple of years and browsers were in even worse > shape than they are now ;) ), I'd stick with that
Well, as shown, it is possible to do, but it is more complicated than the JS approach, because now relative pathes are resolved against the href base and not the current URL. So much more error-prone and needs additional code clutter, moving/duplicating some list.jsp logic into the includes (*.jspf) and thus even more clutter/overhead. > javascript is nice, but Sunrays are Sunrays Hmmm, sunrays are history. Everybody I know has already replaced or will replace them very soon with Wyse clients. I guess, Oracle will EOL sunrays as soon as all remaining units are sold. Biggest indication is, that there is still no S11 Server Software ... Anyway, IMHO anybody who wants his developers to be productive gives them a real desktop, which is able to utilize the modern stuff, allows them to work efficiently ... > and lynx/links/elinks is the > key - call me old fashioned, Or perhaps unproductive? ;-) > but less javascript, the better and more compatible pages Nah, we're living in the 21st century! If one wanna have user friendly [,powerful] and efficient (both sides) web application, there is no way around JS! JS is the only reason, why HTML+HTTP survived! IMHO the compat reason is void for many years - there is simply almost no site, which doesn't require JS and thus all modern browsers support it and there is probably no one, who doesn't use one of them (Firefox, Chrome, IE, Safari, Opera probably cover 98+%). So JS uncapable browser are certainly far below 1% and thus there is no reason, to rise the complexity, maintainance burden, inefficiency of a web application just to make a very few people happy as well. So may be "the more JS, the better" fits much better into this time/century? > (I know we eventually will want to plug more js in there, but the time > isn't now, maybe in a year or two, Ehmmm, I agree with "not now" -> it is already far too late ;-) > there is already enough js in the > pages, they need a rework anyways, getting some UI test suite and even > more clean up (what you started however is great, so respect!) ) Yes, and it actually opened the door for easier integration into other applications or even a standalone non-web UI client by better separating data from UI (yes, but still far away from the optimum) ... So IMHO if we take into account, that the main opengrok users are developers and researchers, which are usually quite flexible and not old grandpahs, which have difficulties to learn new things, opengrok could make progress much faster ... Or not? Cheers, jel (right now on vacation ;-)). -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768 _______________________________________________ opengrok-discuss mailing list opengrok-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
