-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I guess this message is for David.
Ut oh =)
> I was browsing the download section of the website, specifically looking
> at what Windows downloads were available.
> I think if I was a new user, I wouldn't know what to download. I think I
> would have ended up downloading the zip (which says it contains no parser)
> that contains the viewer.
I think I should probably define (on that page) what a parser,
distiller, etc. are for new users.
> Did we do away with Dirk's Windows stuff that installs the Python parser?
> If it needs to be built, perhaps I can do that.
Nobody's been able to locate or contact Dirk in over a year,
including via snail mail. We're not even sure he's still alive anymore..
> If the Plucker Desktop package includes everything needed, shouldn't that
> be listed first?
My only concern with that approach is that Plucker isn't just
Plucker Desktop, so what I've tried to do is "build up" from the viewer on
up, and also, encourage people to test and use Plucker, without having to
install anything. Grab the viewer (no parser/distiller) zipfile, then head
over to "Samples" and download a few and test it out. If/when it works,
trundle back to "Download" and grab the next tool of choice for your OS that
_does_ include a parser/distiller, such as Plucker Desktop or the Java
version.
> I haven't tried the download and install, but won't the Plucker Desktop
> setup install the Python parser? Last time I tried it I thought it did
> this.
Yes, however there seems to be an open issue we've found with the
version of Python that it installs, which I'm investigating today.
> If so, maybe the text could says that it includes everything needed to
> parse and view web pages on the Palm or something. I think for Windows
> users, this should be the first thing they download and install.
I'll make a note of it on the page, I'll try to be more clear about
what needs to be used for what type of user. You bring up a valid point. I
automatically assume that Windows users know what they're doing in most
cases, and that tends to NOT be the case 90% of the time.
> Also, the blurb in the upper left corner of the page is written in such a
> way that it seems like we are just testing the software (like a beta)
> instead of these being the actual release files.
I'll update that as well.
> I'd try to get rid of the last line too. Maybe change it to say something
> about Open Source wanting everyone to pitch in? But then that might scare
> away some users since they will assume there are lots of bugs.
The only issue with that is that users assume that when/if they find
bugs, they are _guaranteed_ to have them fixed, and that isn't always the
case with OSS software. Plucker isn't "Plucker, Inc." so bugs may exist or
linger for a long time, based on our own priorities to fix them.
Good points overall, I'll make the necessary updates. There's a few
other things I want to do to make the site more usable (there are two menu
options still not exposed, that leads to the other tools I've taken offline
awhile ago, which will be coming back).
d.
perldoc -qa.j | perl -lpe '($_)=m("(.*)")'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.1.92 (GNU/Linux)
iD8DBQE9y6xIkRQERnB1rkoRAjTXAKCb2BahP0WVz/a0F8phjQ+/4LEnxQCffEdd
5SqxJMh70tqho9fIdByxkIY=
=Yt31
-----END PGP SIGNATURE-----
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
