*Optimal* DHTML interface management libraries and API

As the new browsers have broken my decade old DHTML interface systems which have worked flawlessly for thousands of students managing highly complex abstract data (2000 chars? cropped),

Is there no library that handles dynamic content management (with server structured data types and "ajax" cache management on client side) that works completely using all available functions on all host platforms typical of a decade ago?

Angus's API on twinhelix is functional, though it is missing a bunch of the old standards and has some cross-browser implementation errors, but there is a want of a simple structured content management system using ONLY DHTML STANDARDS.

The primary problem is the cache and preload needed for high density data browsing, business cards or data sheets with complex nested data on selectable overlays, and efficient communication with server to load/post/refresh and stream various content. Also a standard interface and layer manager which handles structured types (drag/resize window with follow and math) and various conventional operations thereto would be expected in a comprehensive project.

Is there anything specific to this purpose which I have not found, SPECIFIC TO 10-YEAR STANDARDS COMPLIANCE (incl msie4/ns/etc), any "browser" systems (including itself in script or binary) that can handle the complete range of scripting needed for comprehensive content interface management, and any libraries that are optimized for efficiency and human interface capability?

Let me know what exists, what is being worked on, and what we need to do if it has do be built entirely for this "modern" world.

Perhaps  there are components that exist which I have not seen today, but DHTML standards (plus svg and some parsing capabilities and dynamic load/post) is really all that is needed for comprehensive interface and data management.

Shall we just do it all again and fix the problem finally?

-Wilfred
WilfredGuerin@Gmail.com

Most of the IOS style systems are depending on flash now, there are a few left that work with pure DHTML/Xhtml and limited external mess, but none has a sanitised internal browser nor do most of them operate on all browsers. Their use of IFrames are horrible, and only one of the 30 has a decent memory management system but its scripting is horribly poor. Minimalist all inclusive library is needed, dojo is not good, and google/yahoo make a profit off microsoft and intel hardware sales and upgrades. the dhtml url above has some cute demos for 3d math using layers... Our old system handles 3d model structures very well including video piping via various methods, but it relies on the graphics rendering of a server cluster far too much for animated sprites and has to render the non grid lines as it was never enhanced for the newer ns line drawing and definitely lacks svg generation. Full emulation via layers is needed to strike out foreign js and plugins when parsing standard html sources. sandboxes are faster! here's a demo from that 3d layer doodling site thats clean on all browsers:

http://www.dhteumeuleu.com/dhtml/rotate3D.html

Noted, but this was historically the problem, as I just commented to another, it wasnt until FF2 did "netscape" bother to include "drawline" and it still doesnt work correctly.

The  basis of the 10 year standard, is that ALL hardware compatible with win98 and the lnx of that time is more than suitable for running realtime interfaces with an optimized dhtml layer system.

The obvious problems when FF3 is vista-only, etc. The opera on fones and pdas run the example ball layer spinner extremely well, however the ie6 models fails with irregularity.

jquery is slower and heavier than needed for many things, and is nothing more than another expansion of the standard fetch/get.

This is where we either need to find or produce something that is fully compatible with minimalist standards and optimized to handle abstract structure models so that future messes (like dyn svg interfaces, antique vrml, and the current crap called yahoo and google) can be accomodated transparently as if on any historical host.

I dont know why this specific standard library has never been released, given its so blatantly obvious and everyone has to build their own for any specific project.

Ours  with dynamic 3d interface, psuedo graphics for angled layer panels or diagonal lines, and a structured parser and schema style (ackhem) structure manager for both layout and data came in around 40k max with dynamic loading.

thoughts on an optimized solution?

Well, good luck writing your new library/interface! I don't think that I can offer much more than the above advice.

- Angus.