Hi It sounds nice, but to be honest, as a UI developer for 20+ years now, I've seen a lot of these multi-backend UI toolkit projects come and go. They normally start out with fanfare and then bog down quickly when the realities of the difficulties of meshing several different backends come to light.
They have several draw-backs - they require a ton of work - they have lots of problems with things that work with one backend but not with another - they suffer from impendance mismatch where the toolkit and the back-end don't mesh well, frustrating developers - they require multiple skill sets from the maintainers, which is not common All that being said, don't let me stop you. I'd just prefer if the work was done on a branch, where things can get worked before we commit to such an approach. Regards, Noel Grandin On Mon, Nov 14, 2011 at 15:43, Sandro Martini <[email protected]> wrote: > Hi all, > I like the proposal from Niclas, the only problem I see now is to not > separate our efforts in multiple developments, so none of our goals > risk to be completed. > > For sure we need more developers to help us and/or to work on it. > > As Niclas I see (in my real-world experience) that currently Pivot > suffer from the single (JVM only, and only on PC) target platform, so > in my opinion a task like this is really important (we already have it > for 3.0, but with our slow times could be too much). > > It someone of us is interested I think we could even open a new > pivot-3 branch in main svn, or if someone other is interested maybe > hosting the experimental repository in another public and shared place > would be the best (to avoid Apache bureaucracy, at least for the > beginning) like apache-extras or GitHub ... > > What do you think ? > > Bye, > Sandro >
