oooh and this one is quite cool to. http://kylecordes.com/2008/10/20/rhino-js-swing/
I guess I should clarify my last post too These guys have a pure java impl too http://www.webrenderer.com/ And this is a pure java impl as well. https://xhtmlrenderer.dev.java.net/ On Nov 6, 3:24 pm, Pete F <[EMAIL PROTECTED]> wrote: > What if... > > -Adobe and Microsoft have missed a trick, by jumping directly to an > extensible rich client *that is not html*. > > Shouldn't someone, with a platform capable of doing so (ie Java) do an > HTML based rich client?? > > Why not do for real, what GWT only pretends to do. > > -and hasn't a similar trick worked brilliantly for java once > before... > > Precedent: > > Smalltalk was just too big a leap for C programmers. Java neatly > filled that hole. It wasn't C, but it looked like C and it provided > the glide path from C to the modern world. > > XAML and Flex (and javaFX) are not HTML -and they therefore require > everyone to dump all their experience, and infrastructure based around > HTML. > > *IF* the JRE included an HTML browser, Java developers could move > smoothly from server+ajax, to server+java_client > > It could be like the Java wave of the 90's all over again [man]... > > Adobe and Microsoft would hate it and groan about how backward it was, > like Smalltalkers hated java for its pragmatic co-opting of their > dream. > > Die-hard Ajaxians would hate it, and grumble about speed -like die- > hard C programmers hated Java for solving in one hit, a bunch of > problems they made their livings trying to solve > > Java programmers would be laughing, as they... > > a)Wrote RIA's in java whilst leveraging the ALL THOSE HTML web > frameworks, and ALL THOSE HTML web designers, -while adobe and > microsoft tried to force change > > b)Did what GWT only pretends to do (but still using GWT for when there > is no java client -see what i mean about the html technology re- > use?) > > c) Drove right around all that cross browser nonsense > > d) Extended the damm browser natively (ah, at last!) > > e) Optimised their existing ajax javascript by moving the hot spots to > Java > > f) Watched java client adoption climb, as java became THE way to > normalize IE without replacing it > > g) Avoided having to make a premature "flash or javaFX" decision -and > rolled javaFX seamlessly into html for a while until it suited them to > drop the html > > I have heard somewhere of Adobe eyeing webkit (!!!) Danger Wil > Robinson Danger! > > Java won once, with a straight down the middle play -can it win > again? > > Dust off that HotJava browser Sun. > > Comments? Vote for this question, on the moderator thing, if you > would like to hear the Posse discuss it > > Pete F > > -or did i simply miss a meeting? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
