The main problem with that approach is that the <canvas> tag just isn't robust enough to handle our rendering needs. If we went that route, we'd probably be better off creating a theme that is backed by native HTML widgets (like the SWT approach I suggested the other day). We could probably come up with some way to implement decorators on top of that (maybe via a canvas tag that spans the entire display).
On Sep 21, 2010, at 1:48 PM, Todd Volkert wrote: > Are they copying us? :-) > > I think it might argue stronger for the abstraction of the graphics > layer, since that may eventually allow us to run directly in the > browser through the use of something akin to the GWT compiler. > > -T > > On Tue, Sep 21, 2010 at 12:35 PM, Greg Brown <[email protected]> wrote: >> So yes, it seems like we have been on the right track. But we already knew >> that. :-) >> >> I didn't see anything in that article to imply that Prism wouldn't be made >> available to Java SE. Did I miss something? >> >> But here is my concern: Pivot's biggest advantages over JavaFX to date have >> been: >> >> a) You can write Pivot applications in Java or any other JVM language (you >> are not limited to JavaFX Script). >> >> b) It is completely open source. >> >> It sounds like neither of these will apply when JavaFX 2.0 is released next >> year, and it seems clear that JavaFX will have access to the new Prism APIs, >> while Pivot may not. Also (from http://javafx.com/roadmap/#3): >> >> - "The JavaFX APIs will be a variation on typical JavaBeans properties and >> listeners" >> >> - "For JavaFX 2.0, Oracle will release an ObservableList interface, which >> extends the java.util.List interface...Oracle will also release an >> ObservableMap interface and implementation for adding listeners (or binding >> to) instances of ObservableMap." >> >> Basically, it sounds like they are planning to turn JavaFX into something >> very Pivot-like. So, how will Pivot 2.0 ultimately differentiate itself from >> JavaFX 2.0? >> >> I'm not sure we can even attempt to answer that question yet, since we don't >> know how successful Oracle will be (will they release on time, will >> developers be interested, etc.). But it is certainly enough to make me >> wonder what our next steps should be. >> >> G >> >> >> On Sep 21, 2010, at 8:56 AM, Sandro Martini wrote: >> >>> >>> Hi to all, >>> someone has already seen this: >>> http://java.dzone.com/articles/oracle-discontinue-javafx >>> on the future JavaFX 2.0 ? >>> >>> More in detail, this: >>>> This will also make JavaFX resemble Apache Pivot in a few more ways. >>> Reading this type of things I've the confirm that we were/are on the right >>> side !! >>> >>> What do you think ? >>> >>> >>> The real problem that I see (in the med/long term) is that Oracle is >>> rewriting the graphics pipeline, but seems that it will NOT be released as >>> part of Java SE ... too bad in my opinion. >>> Some info here: >>> http://marxsoftware.blogspot.com/2010/09/javaone-2010-opening-keynote.html >>> and an extract: >>>> The "high-performance graphics engine" called Prism (and used with JavaFX >>>> and discussed at last year's JavaOne) will be made available. It renders >>>> 2D objects today, but will eventually support 3D objects. It will support >>>> new hardware Accelerated 2D and 3D Graphics Pipeline. This will be made >>>> available in open source via NetBeans. >>> >>> >>> So probably for future releases of Pivot maybe we should think on a >>> (alternative ?) way to use that new pipeline, or at least to start with an >>> our OpenGL backed pipeline ... let's see in the future. >>> >>> >>> Bye, >>> Sandro >>> >>> -- >>> View this message in context: >>> http://apache-pivot-developers.417237.n3.nabble.com/Announcement-for-the-future-JavaFX-2-0-tp1535160p1535160.html >>> Sent from the Apache Pivot - Developers mailing list archive at Nabble.com. >> >>
