Sounds great; please send links or the source along when you have a "release" so we can update the wiki.
Thanks Maarten! Nathan On Thu, Jul 29, 2010 at 5:47 AM, Maarten Zeinstra <[email protected]> wrote: > Great, thanks for the information! > I am now writing a class that extents JPanel to do the license selection, > the classes you mention would a good place to harvest best practice code on > this. > I hope to have it automatically add jurisdiction and license URI using the > the API. > The final product will be a class that extens JPanel that will do the > license selection base upon API that should be easily integrated in other > projects if people please. > Cheers, > Maarten Zeinstra > Kennisland | Knowledgeland > > T: +31.20.575.6720 | E: [email protected] > www.kennisland.nl | www.knowledgeland.org > > On Jul 27, 2010, at 23:53 , Nathan Yergler wrote: > > I think the idea with the OOo plugin was that we wanted it to work > offline. If that's not a requirement, the API is probably a better > idea. Note that you can get the list of jurisdiction codes from the > API through the questions list > (http://api.creativecommons.org/docs/readme_dev.html#license-class-locale-xx), > so you don't need to maintain the list of jurisdictions yourself. > > We used to have a Java wrapper for the API > (http://code.creativecommons.org/viewsvn/api_client/trunk/java/). As > you can see from the timestamps, it hasn't been touched in a few > years. That might be a reasonable starting point for you. > > NRY > > On Tue, Jul 27, 2010 at 2:17 PM, Maarten Zeinstra <[email protected]> wrote: > > Hi Nathan, > > Yes I found the other versions a bit later in the day. > > i was wondering if I could bypass the store idea and have it render an API > > call like /license/standard/get?commercial=n&derivatives=n&jurisdiction=nl > > and stripping it to the URI of the license. That's the only thing I need. > > That way I only need to have list of jurisdictions up to date and have the > > API call do the rest. That would probably be a couple of hours worth of work > > or something for me. > > The only advantage I see in the store structure is keeping some parts easily > > maintainable and up to date, if you get those documents from the cc site > > itself. > > If you are considering making an html request per opened application, than I > > wonder if you need to have a debate on CPU's vs Bandwidth and what would > > cost more. sending all these stores around or creating a small package. that > > is send. I would think the latter is perhaps more efficient. > > What would you think? > > Maarten Zeinstra > > Kennisland | Knowledgeland > > T: +31.20.575.6720 | E: [email protected] > > www.kennisland.nl | www.knowledgeland.org > > On Jul 27, 2010, at 22:28 , Nathan Yergler wrote: > > Hi Maarten, > > We've moved active development off CC Tools sourceforge.net project > > onto our own servers at http://code.creativecommons.org. The OOo > > plugin does have the most complete CC license selection code for Java. > > We have a Summer of Code student working on the plugin right now. > > You can find the license selection code in his branch at > > http://code.creativecommons.org/viewsvn/ccooo/branches/akila-gsoc-2010/src/org/creativecommons/license/. > > If you think this will be useful for you to use (or you have > > patches/features to contribute), we can split it out into its own > > module in Subversion. I think the primary issue right now is probably > > startup speed, as it loads the RDF files from disk into the store; > > there are probably a couple of different ways to tackle optimizing > > that. > > Let me know if you have any other questions. > > Nathan > > > On Tue, Jul 27, 2010 at 1:29 AM, Maarten Zeinstra <[email protected]> wrote: > > Hi list, > > I've been searching the cc sourceforge for the most recent Java Library to > > do CC license selection, wondering if I have to make my own library. > > I found ccooo, would that be the best available library to integrate a Java > > based license selection tool? > > Are there any known issues with that library? I couldn't find any using the > > issue tracker, but maybe someone on list has different experiences with > > that library. > > Cheers, > > Maarten Zeinstra > > Kennisland | Knowledgeland > > T: +31.20.575.6720 | E: [email protected] > > www.kennisland.nl | www.knowledgeland.org > > _______________________________________________ > > cc-devel mailing list > > [email protected] > > http://lists.ibiblio.org/mailman/listinfo/cc-devel > > > > > > > > _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
