Good question. Honestly there are going to be certain limitations, but I've done the best I can to minimize that or at least provide work-arounds for those scenarios where possible.
You can technically create your own Flex-specific features, but that sort of breaks the paradigm of jSeamless being UI abstract. So what you could do instead is make use of the core framework to build what you need. For example, for what you're trying to do, you could simply create a Label object and float it over the chart where you want it. That's going to require a little more weight on the server than if you were to do it directly in Flex, but it shouldn't be noticeable and the gain is 100% Java written applications without having to write a single like of HTML, CSS, ActionScript, JavaScript, etc. ASP.NET still requires you write HTML and CSS, right? It just provides inline code like JSP, correct? Or have they gotten even further away from that now? The idea of jSeamless is more like Swing. You create objects for everything and the implementation interprets and renders on the fly. In Flex this was particularly complicated as I'm sure you realize your application is meant to be pre-rendered as an SWF. There's actually a complex "interpreter" system that generates content on the fly so you could even have BeanShell scripts running on the back-end (or even typed into the front-end) that generates your UI. Good questions, please keep them coming. It's the Java developers that are using Flex now that I really intend this API for and this is probably one of the best places to find them. :) --- In [email protected], "barry.beattie" <[EMAIL PROTECTED]> wrote: > > > How are customisations handled? > > I mean, I'm hung up on needing to do special things with labels on bar > charts at the moment. In a "seamless" case not only do I have to worry > if Flex can do it but also if the abstracted Java code will allow this? > > or is it a case of what you don't know you won't miss? > > There's a HTML and C# (or VB.NET) version of just this "seamlessness" > and also does Ajax calls, etc. Really blurs the line between whether > you're client-side or server-side: According to Microsoft in theory it > doesn't matter. It's called ASP.NET.... >
