-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> > Initial commit of a simple in Fproxy help page. Content needs to be added > still and then this can be wired into side menu. To access in the meantime > go to http://127.0.0.1:8888/help/ >> >> Shouldn't we have a official freesite first/instead? > > An official freesite requires we implement RSKs. If you want to I can explain > how. But even then we'd want to bundle it as a binary blob so it can be > accessed even on nodes that haven't connected yet. So IMHO a help bundle > built in to the node is a good start. I'm assuming this will work by pulling > it from the jar, like with the themes etc? >> I intend for it to be a very simple, one page document covering FAQs and troubleshooting and connection info. The really in-depth info can be found on Freesites once the user has delved deeper into the network. Right now, I have just created a simple toadlet to serve a page; The content will actually be stored as strings in the L10n language files so that it may be translated into any language. For example SimpleHelpToadlet.connectivityText=This is how you set up port forwarding: Linksys:Go to 192.168.0.1 blahblahblah, etc etc I imagine it would be 50-100 pagelines of text using 8-10 strings for different sections. This seemed the best approach for my level of Java abilities, but I can try to do it another way or using a separate set of L10n files, but I am less confident I can do it. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: http://getfiregpg.org iD8DBQFJUYrV4esu1mlKOs8RAv+1AKCZcuQTM2u+IDoTqLa7YqYD/D/M8gCfVuC9 e4JHpd1ndeB15iim1D6eVxM= =Bk3v -----END PGP SIGNATURE-----
