> Tatami looks like the best option, indeed, although I don't like the demo > page they have. The > graphics libraries are still immature, mostly because people still prefer > to use Flash for dynamic > pages. Option C would be good if we had infinite time or infinite manpower, > but right now it would > be just a waste of time. > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs >
I think the demo page is so slow because of the fisheye(the mac style menu bar) and because the page is running from a wicked source( ?! ). I've tried it out and it seems much faster. Besides there isn't any other way of doing this, even if i made the API, i would have to create the objects with the CreateElement(namespace, object), i would have to make all the setters and getters like curr_obj.get_path() and so on. So i guess performance shouldn't be an issue and even though i'll be using Tatami, i'll still develop some new features to tweak it! The only thing i haven't tested was to draw many objects in the DOM and see how the responsiveness of the application behaved. But that can be a little bit optimized and it's a problem of the browser. Option D) If you want a really really faster aplication, we could use Canvas objects instead of SVG/VML. The only big downside is that canvas doesn't has the Text object :( That can be worked out with a hack, but then you'll loose the abillity to do Z ordering in the panel (bring forward,.bring back). Good luck to France :), Miguel Bento. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
