Dormouse
Doesn't know that mice use holes.
Posts: 2,517
I stand corrected, Brian. Perhaps i was a bit too rash.
What i meant was that i was sketchy about a push to move towards a technology which /currently/ only works on a single line of browser. This isn't to say i don't find the technology very intriguing and with a lot of potential; however it does bring back shades of say the xmlgetrequest hacks used in firefox, which the opera developers for a long time considered strictly non-compliant, leading gmail to only work in firefox until gmail cleaned up their act and code a bit [as far as a i know] and support for it became more possible.
As i mentioned above, the basic interface works in the 8b series of opera at least, however i foresee more in-depth being rather low on the development cycle list of priorities. I will look into it on the boards and suggest work, however full integration may have to wait until the next version [8 being in beta currently].
[edit: i just noticed after scanning the code that the basic interface menuing system is div-based rather than xul-based, so i stand corrected]
On the other hand, i can't see Links/Lynx, as great as they are, ever having support for this, by very nature of their nature, said being exactly one of the reaons i tend to look down on flash-driven interfaces as well. That being a decent part of what i meant by non-portable.
In my personal web design work, and my critique of that of others, i tend to be a strong propnent of the idea that so long as the code is standards-compliant, the actual browser it is on should be virtually transparent from a rendering standpoint. Now i realize this is difficult if not outright impossible at times, particularly when it comes to trying to make ddesigns that work in firefox and opera line up in ie without damaging w3.
If properly laterally implemented, i feel that xul could be radical, however until then i'm not certain how viable it really is.
Also, I can kill you with my brain.