> How hard would it be to mass-convert the existing channels, so that each
> channel is its own page, and the categorization is by Category Pages.
That was part of the reason for the move from the "old" wiki to this
version.. a SQL backend. The old wiki software I was using (forget which
package it was by now), used a flat-file storage system. Not good if I
actually wanted to *DO* something with those urls.
> Also, if there are special instructions (need cookies, must refer from X),
> these could be listed on the channel's own page, instead of cluttering up
> the several-channels-at-once page.
This is somewhat what I prototyped for this (note the date on it):
http://code.gnu-designs.com/mpo_04-07-2003.png
Basically a blow-by-blow channel selection system, which is
currently still being worked on behind the scenes at my.plkr.org, and will
include lots of metadata about the channels, such as size, availability,
defaults (i.e. cookies, HTTP_USER_AGENT spoofing, etc.) and other things.
> It would also make the subcategories more intuitive.
I agree. There is some work going on here, but not as fast as I
would like. Unfortunately, pilot-link needs another release, so I'm focusing
on that at the moment (and the job-hunting thing, an ongoing process). Palm
made some changes to the way HotSync works, and added those new applications
(undocumented, of course) on the T3 and Tungsten E units, so I have to work
on getting those supported. Once pilot-link 0.12.0 is out, I can focus back
on the Plucker/web'ify side of things.
> I expected the Humor category to have something in it; it was a blank
> page. Copying the subcategories from the top page struck me as wrong,
> since the two lists would eventually get out of synch.
We're on the same page here.. no pun intended. Just takes time.
d.
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev