I've got a situation where plucker (v1.4) seems to not be working for me any longer. I looked at the 1.8 tar file, couldn't figure out how to install it, and started wondering if I should just learn about jplucker.
I think you mean JPluck. jPlucker is a slightly different project, based loosely on the same codebase as JPluck itself.
however, when I go to the jplucker web page, I start off with a strike against me. I don't seem to be able to locate any info on installing or using it. Given my novice state, I am left perplexed.
Which site are you using?
http://jpluck.sf.net/ <- this is probably right
or:
http://www.nouvelles-solutions.com/iplucker/
So, does that leave the palm linux/solaris/whatever user out of luck? Or is there some new application people are moving to that a) has documentation for the _user_ as to how to install and use it and b) has plans to continue development?
No, you have several options:
1.) Plucker's standard Python distiller (shipped with Plucker)
2.) Plucker Desktop (gui on top of 1.) above)
3.) JPluck, a completely independent Java-based distiller
4.) Bill Nalen's Plucker conduit:
http://nalens.com/articles/173.aspx
5.) SiteScooperJust curious?
JPluck development, from Laurens' perspective is dead. He is focusing his efforts on his new RSS-centric project, Sunrise. It is destined to be a proprietary product, which currently outputs Plucker-formatted documents, but will not when his Palm viewer is complete.
When his Palm-side viewer is complete, Plucker support in Sunrise will be terminated, and users will either have to fall back to earlier Sunrise versions, JPluck versions, or buy his viewer (a commercial product), and use that instead (incompatible with Plucker, of course).
From my perspective, JPluck is a valuable asset to the user community, and its development will be continued, under my immediate management in the short term.
I've been speaking with some full-time Java developers about some new features that need to be added, lots of bugs that need to be closed, and quite a few rewrites of sections of Laurens' original code. Hopefully, out of this will come a task list of deliverables we can delegate to those developers to write, test, and deploy.
When I finally get my arms wrapped around the project itself (trust me, you don't want me writing Java, I'll end up rewriting it all in C, and losing the portability =), I will set up a mailing list for development to continue on the successor to JPluck.
The existing will be rewritten where necessary, other pieces will be thrown away, the project will be renamed, and it will be relicensed under a license that allows others to continue to develop against it without the fear of someone taking the code and turning it proprietary again, orphaning off the existing userbase.
Does that help?
d.
_______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
