> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:devl- > [EMAIL PROTECTED] On Behalf Of Toad > Sent: 18 September 2003 16:45 > To: Discussion of development issues > Subject: Re: [freenet-dev] Beautifying Freenet > > On Thu, Sep 18, 2003 at 07:53:03AM +0100, Simon Porter wrote: > > My suggestion, > > > > Why not have a setup wizard that runs in the browser on first run. This > > is how nearly all php programs setup themselves such osCommerce and > > Kayako heldesk. It would be great to be able to guide users through some > > of the more difficult parts of installation such as port forwarding. > > > > IMO port forwarding is one of the most difficult things to setup. Most > > users don't even know what it is let alone how to set it up. When I > > first tried out freenet I gave up and left it for a month before trying > > again. It was only after much bugging people on the IRC chat and reading > > through my huge 200 page manual for my ADSL router that I found out. > > Yes, it's a big problem. And we have no way to help them, which makes it > worse. > > > > Here in the UK nearly everyone I know uses an ADSL router to connect to > > the Internet. My experience with friends has been that installing the > > JVM is the easy part. It's port forwarding that is the road block. If I > > even mention it usually people just scratch their head. > > Well, that's their problem. Unless you want to maintain a substantial > amount of platform specific code to try to find and reconfigure every > known DSL router - and hope it doesn't have any authentication system, > because the user will have forgotten or lost any login details.
Eugh no. That was not at all what I was suggesting. It wouldn't be at all realistic to even attempt such a thing. What my suggestion was to have an in browser setup wizard which basically walks you through step by step setting up Freenet. For example: 1. Welcome page - general spiel on what Freenet is and how to access it (ie. By typing in 127.0.0.1:8888) Click next to begin setup. 2. Java VM detected or not. Optional depending on if you get round to putting this in the setup routine or not. Might be good for linux users though. 3. A page explaining what port forwarding is and general instructions on how to go about setting it up. 4. Detect if Freenet can receive incoming connections. If not offer the option to run as transient or for the user to retry. 5. Freenet is successfully set up page. Nothing really more complicated than that. > > I think if freenet is to become easy to use then this is one of the > > biggest things to address rather than more eye candy for the fproxy. > > > > Simon > > Well volunteered! Seriously, it's way outside my field of expertise, > it's just possible that there's some free code somewhere that does it, > somebody should google for it. I'd love to but I'm no programmer. I'm currently involved in another project at the moment (http://roxos.sunsite.dk if anyone is interested). C is probably the first programming language I'm going to learn. Hope my suggestion is of some help though. Simon _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
