Ian Clarke skrev: >> On top of my head: >> - Cleaner code >> - Proper detection of FireFox location >> - profiles.ini watchdog thingy >> - Check if node is running before launching FF (and if not, start or >> inform user in a GUI message box) (and if needed, shutdown node >> afterwards as well) >> - If wanted, GUI warnings about missing daemon, FF or FF profile (we >> talked a bit about the possibility of nagging users without daemon enabled) >> > > I also think we may have a problem getting the user past the "ok, its > up and running, now what?" stage. We need to give the user a natural > path from installation to usage of Freenet, whether its surfing > FProxy, using one of the discussion tools, or creating their own > freesites. > > Anyone got any ideas? > > Ian. >
Random thoughts: - Website does kind of well in leading the user from front page to downloading the installer (could still be a lot more KISS in my opinion though) - Installer should (upon finishing) inform the user that they can/should open the "Browse Freenet" shortcut on their desktop to start. Obviously the shortcut should have a bunny icon. - The first-time wizard is quite good, but could be made even more newbie-friendly with more explanations and automation (there are a couple of bugs regarding this already I think) - Perhaps a proper welcome screen as the very first/last page of the wizard or as the main page of fproxy (either merge with the bookmarks or make it possible to change "main page" to the bookmarks later on, when the user is more experienced) - All software using Freenet should probably have their own page in fproxy (I know work is being done to make this possible) - Zero3
