On Wed, 17 Sep 2003, Ian Clarke wrote: > On Wed, Sep 17, 2003 at 07:08:54PM -0700, Ian Clarke wrote: > > This is what we did before someone decided that we were violating > [snip] > > In fact, rereading your comment, what we had before was even better > than your suggestion - the installer would detect whether the user > needed a JVM and only download it if they did.
Let's not get sidtracked on THIS discussion again. It comes down to a disconnect: Our installer was/is legal. Having the JVM sitting in /snapshots/ for browsing and downloading would not be. Sticking it in a non-indexable /jvm directory would solve the problem. Back on track: Beautifying freenet is way too much work. And it's work that is best left in the hands of our users. Rather then read the files from the freenet.jar, check if a /html or /templates directory is there. If it is, read from that. I note that there's already a Freenet Themes freesite out there. It's WAY beyond the average user, as it requires downloading the source (without CVS access, a 11.4 meg .tar.bz2 for every build, I might add) replacing the content there, and building it. Let's redirect that effort into giving creative people the ability to modify the themes WITHOUT rebuilding all of freenet. In fact, a /themes/themename/<files> scheme would allow us to get a directory listing of /themes, and set the current theme in fproxy without restarting the node. Talk about user friendly! Let coders and creative people do what they do best. Right now either webdesigners have to learn java, or toad has to spend productive time making things pretty. Obviously, neither is an optimal solution. --Dan
pgp00000.pgp
Description: PGP signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
