You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by Todd Volkert <tv...@gmail.com> on 2009/04/16 23:57:35 UTC
Demos and JFreeChart provider have moved
All:
For those of you not on the general@incubator.apache.org or
legal-discuss@apache.org lists, there has been an active discussion
today about whether it is OK to keep code in your subversion
repository that is not apache-license-friendly. The gist is that it
is recommended not to do so, and if you decide to forego that
recommendation, it is strongly recommended that you segregate such
code away from the compliant code within your SVN hierarchy.
As such, I've made the following changes:
* I've migrated our demos out of the repository -- they now live at
http://code.google.com/p/pivot-demos/. I've added you all to that
sub-project, so you should have write access to that repository. If
you don't, let me know.
* I've migrated the JFreeChart provider out of the repository -- it
now lives at http://code.google.com/p/pivot-jfree/. Again, I've added
you all to that sub-project.
We're hoping to get the JFreeChart provider eventually integrated
directly into JFreeChart itself (Greg is discussing this with the
owner of JFreeChart), so that was always destined to go away. As for
the demos, some could have stayed without any issues, but it seemed
cleaner to just migrate them all, thus freeing us from any future
licensing worries when writing demos.
All this really means to you is that if you want to work on a demo or
the JFreeChart provider, you'll need to checkout from those other
repositories. Everything in the main repository still builds as it
always did - just without demos.
Let me know if you have any questions,
-T
Re: Demos and JFreeChart provider have moved
Posted by Sandro Martini <sa...@gmail.com>.
Hi to all,
I agree with Noel ... so if wouldn't be possible to re-license code,
would it be possible to move to Google Code only Demos with non-Apache
license, like Charts, and keep others and all related things in the
Apache Incubator (Subversion, Jira, mailing lists, etc) ?
Thanks,
Sandro
Re: Demos and JFreeChart provider have moved
Posted by Todd Volkert <tv...@gmail.com>.
> I think it is likely that we are always going to have some demos that rely
> on incompatible code. However, any demo that doesn't have such a dependency
> will probably be rolled into the tutorials, which are included with the
> distribution and stored in the ASF SVN; e.g.:
>
> - Kitchen Sink (already in tutorials)
> - Stock Tracker (already in tutorials)
> - File browser
> - File drag/drop
> - Table row editor
> - Large data sets
> - DOM interaction
> - Decorators
> - Fixed column tables
> - Scripting (possibly; currently has a Mozilla dependency since OSX JDK
> doesn't include a JavaScript engine and we need to use Rhino)
>
> Basically, these demos showcase topics that we haven't gotten to in the
> tutorial yet. When we do, I imagine that we'll migrate them.
Put another way, the only demos that are destined to always stay in
Google Code are the Charts, Google Contacts, and AMF. So at the end
of the day, this change doesn't really affect us all that much.
Re: Demos and JFreeChart provider have moved
Posted by Christopher Brind <br...@brindy.org.uk>.
I guess the dependency on Rhino piqued my attention there, but I suppose
that's just a demo.
I thought I saw some Groovy support in the code base somewhere... was I
imagining that?
I might get round to do doing a Groovy scripting demo (if I can squeeze more
hours in the day).
Cheers,
Chris
2009/4/17 Greg Brown <gk...@mac.com>
> With regards to this are you talking about Pivot apps interacting with
>> their
>> containing web-page, or actually providing scripting within Pivot?
>>
>
> The latter.
>
> In the latter case I don't see the point in JavaScript support within
>> Pivot. This is Java-land after all and while this is a RIA which can run
>> in
>> a browser, one of the appealing things to a lot of developers will be that
>> they can create a functional, server-backed RIA in Java end to end... so
>> why
>> not just use Groovy and dump JavaScript support within Pivot?
>>
>
> We're not doing anything to support JavaScript specifically. Pivot's
> scripting support simply sits on top of the JVM's scripting support, so any
> JVM-compatible scripting language will (should?) work.
>
> BTW, I actually like JavaScript as a scripting language and, as a
> developer, might use it in a Pivot application for simple use cases.
>
>
Re: Demos and JFreeChart provider have moved
Posted by Greg Brown <gk...@mac.com>.
> With regards to this are you talking about Pivot apps interacting
> with their
> containing web-page, or actually providing scripting within Pivot?
The latter.
> In the latter case I don't see the point in JavaScript support within
> Pivot. This is Java-land after all and while this is a RIA which
> can run in
> a browser, one of the appealing things to a lot of developers will
> be that
> they can create a functional, server-backed RIA in Java end to
> end... so why
> not just use Groovy and dump JavaScript support within Pivot?
We're not doing anything to support JavaScript specifically. Pivot's
scripting support simply sits on top of the JVM's scripting support,
so any JVM-compatible scripting language will (should?) work.
BTW, I actually like JavaScript as a scripting language and, as a
developer, might use it in a Pivot application for simple use cases.
Re: Demos and JFreeChart provider have moved
Posted by Christopher Brind <br...@brindy.org.uk>.
> - Scripting (possibly; currently has a Mozilla dependency since OSX JDK
doesn't include a JavaScript engine and we need to use Rhino)
With regards to this are you talking about Pivot apps interacting with their
containing web-page, or actually providing scripting within Pivot?
In the latter case I don't see the point in JavaScript support within
Pivot. This is Java-land after all and while this is a RIA which can run in
a browser, one of the appealing things to a lot of developers will be that
they can create a functional, server-backed RIA in Java end to end... so why
not just use Groovy and dump JavaScript support within Pivot?
Just a thought.
Cheers,
Chris
2009/4/17 Greg Brown <gk...@mac.com>
> I found them extremely valuable in getting up to speed, and it's a
>>> nuisance for new people to checkout code from multiple sources.
>>>
>>
>> IMHO, the incompatible code should be moved, and the demos that can
>> stay stay. Then it becomes a matter of time when all demos are finally
>> Apache Licensed only. Inconvenient, yes, but we look at things in very
>> long perspectives here (say Harmony or Geronimo, if you want to look
>> at painstakingly long clearance of encumbered code).
>>
>
> I think it is likely that we are always going to have some demos that rely
> on incompatible code. However, any demo that doesn't have such a dependency
> will probably be rolled into the tutorials, which are included with the
> distribution and stored in the ASF SVN; e.g.:
>
> - Kitchen Sink (already in tutorials)
> - Stock Tracker (already in tutorials)
> - File browser
> - File drag/drop
> - Table row editor
> - Large data sets
> - DOM interaction
> - Decorators
> - Fixed column tables
> - Scripting (possibly; currently has a Mozilla dependency since OSX JDK
> doesn't include a JavaScript engine and we need to use Rhino)
>
> Basically, these demos showcase topics that we haven't gotten to in the
> tutorial yet. When we do, I imagine that we'll migrate them.
>
> G
>
>
Re: Demos and JFreeChart provider have moved
Posted by Greg Brown <gk...@mac.com>.
>> I found them extremely valuable in getting up to speed, and it's a
>> nuisance for new people to checkout code from multiple sources.
>
> IMHO, the incompatible code should be moved, and the demos that can
> stay stay. Then it becomes a matter of time when all demos are finally
> Apache Licensed only. Inconvenient, yes, but we look at things in very
> long perspectives here (say Harmony or Geronimo, if you want to look
> at painstakingly long clearance of encumbered code).
I think it is likely that we are always going to have some demos that
rely on incompatible code. However, any demo that doesn't have such a
dependency will probably be rolled into the tutorials, which are
included with the distribution and stored in the ASF SVN; e.g.:
- Kitchen Sink (already in tutorials)
- Stock Tracker (already in tutorials)
- File browser
- File drag/drop
- Table row editor
- Large data sets
- DOM interaction
- Decorators
- Fixed column tables
- Scripting (possibly; currently has a Mozilla dependency since OSX
JDK doesn't include a JavaScript engine and we need to use Rhino)
Basically, these demos showcase topics that we haven't gotten to in
the tutorial yet. When we do, I imagine that we'll migrate them.
G
Re: Demos and JFreeChart provider have moved
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Fri, Apr 17, 2009 at 4:33 PM, Noel Grandin <no...@gmail.com> wrote:
> Hi
>
> Is there a reason that the demos can't be relicensed to the Apache license?
There are dependencies on licensed code that are incompatible with
Apache policies.
> I found them extremely valuable in getting up to speed, and it's a
> nuisance for new people to checkout code from multiple sources.
IMHO, the incompatible code should be moved, and the demos that can
stay stay. Then it becomes a matter of time when all demos are finally
Apache Licensed only. Inconvenient, yes, but we look at things in very
long perspectives here (say Harmony or Geronimo, if you want to look
at painstakingly long clearance of encumbered code).
Cheers
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
Re: Demos and JFreeChart provider have moved
Posted by Noel Grandin <no...@gmail.com>.
Hi
Is there a reason that the demos can't be relicensed to the Apache license?
I found them extremely valuable in getting up to speed, and it's a
nuisance for new people to checkout code from multiple sources.
Regards, Noel.
Todd Volkert wrote:
> All:
>
> For those of you not on the general@incubator.apache.org or
> legal-discuss@apache.org lists, there has been an active discussion
> today about whether it is OK to keep code in your subversion
> repository that is not apache-license-friendly. The gist is that it
> is recommended not to do so, and if you decide to forego that
> recommendation, it is strongly recommended that you segregate such
> code away from the compliant code within your SVN hierarchy.
>
> As such, I've made the following changes:
>
> * I've migrated our demos out of the repository -- they now live at
> http://code.google.com/p/pivot-demos/. I've added you all to that
> sub-project, so you should have write access to that repository. If
> you don't, let me know.
>
> * I've migrated the JFreeChart provider out of the repository -- it
> now lives at http://code.google.com/p/pivot-jfree/. Again, I've added
> you all to that sub-project.
>
> We're hoping to get the JFreeChart provider eventually integrated
> directly into JFreeChart itself (Greg is discussing this with the
> owner of JFreeChart), so that was always destined to go away. As for
> the demos, some could have stayed without any issues, but it seemed
> cleaner to just migrate them all, thus freeing us from any future
> licensing worries when writing demos.
>
> All this really means to you is that if you want to work on a demo or
> the JFreeChart provider, you'll need to checkout from those other
> repositories. Everything in the main repository still builds as it
> always did - just without demos.
>
> Let me know if you have any questions,
> -T
>