Mailing-List: contact dev-help@pivot.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pivot.apache.org
Received-SPF: pass (athena.apache.org: domain of dreamtangerine@hotmail.com
 designates 65.55.116.14 as permitted sender)
Message-ID: <BLU0-SMTP3841140923974D663BEAFDDD9C60@phx.gbl>
Subject: Re: Proposal "Pivot goes HTML5"
From: DreamTangerine <dreamtangerine@hotmail.com>
Reply-To: dreamtangeirne@hotmail.com
To: dev@pivot.apache.org
In-Reply-To: 
 <CAH4gT7pz0OzhqdOzxvAb-40EZYavEHamqHhKkBf84p33U7Pa2A@mail.gmail.com>
References: 
 <CADmm+KfX+5BM4Cfs_CCHU40HFBoxj8WCBtVg200AtfHCsAQAYA@mail.gmail.com>
	 <4EC1AE5D.3000009@rbwhitcomb.com>
	 <CAH4gT7pz0OzhqdOzxvAb-40EZYavEHamqHhKkBf84p33U7Pa2A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 15 Nov 2011 20:35:17 -0500
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

On mar, 2011-11-15 at 11:39 +0100, Sandro Martini wrote:
> Just after the pluggable AWT backend I see even a pluggable JavaFX 2
> backend (if compatible by license) ... could give us another vision on
> the future (and start playing with it).
> 

I also like the idea (in fact, I was working also in something similar
for android, using Apache Harmony sources). I think that I can help.

My opinion is that GWT/HTML5 and Android are more important that JavaFX
for now. Maybe from JavaFX we can use the Prism engine, but in any case
the first big and difficult step is split AWT (and maybe some other no
AWT packages like StaX and bsf) from Pivot and create Pivot SPI.