2010-11-25 18:12:32 +00:00
HIGH PRIORITY:
- Allow desktopgui to start, stop and restart I2P. - DONE
2010-11-30 17:08:22 +00:00
- Correct logging system - DONE
2010-12-09 17:22:08 +00:00
- Internationalisation:
2010-12-14 07:19:37 +00:00
* Add strings - DONE
2010-12-20 21:31:17 +00:00
* Add Windows support - NEED TO CHECK
2011-01-03 18:40:18 +00:00
* Might need some kind of trigger to reload the menu (for live language switching) - DONE
2010-12-09 17:22:08 +00:00
* Language choice is not actually set as a parameter in I2P config?
As a result, desktopgui always starts with the default, unless you manually set the language.
2011-01-03 18:40:18 +00:00
DONE - uses routerconsole.lang -- this parameter is now updated in routerconsole as well
- Check if we're inside I2P without using a command-line parameter - DONE
- Modify installer to set I2P directory parameter; or use $I2P? - Is already there
- Include in installer - TODO
2010-12-14 07:19:37 +00:00
- Fix tabs versus spaces ;-)
2010-11-25 18:12:32 +00:00
UNKNOWN:
2010-11-18 20:38:21 +00:00
- API to allow applications to add themselves to the menu?
* registerApplication(); -- should return a positive number on success, -1 on failure
* unregisterApplication(int); -- should return nothing (or bool for success?), and the parameter should be the number given when registering the application
- Fetch I2P localhost from the core I2P application?
- Use I2PAppContext::appDir (something like that) for desktopgui data.
2010-11-25 18:12:32 +00:00
- Consider SWT as option
* Check core/java/src/net/i2p/util/FileUtil.java for dynamic jar loading
* Possible logic:
- First try to load SWT (has the most options and is not ugly)
- Then load AWT
- Access router.jar from other JVM? Is this possible? -- no: use I2CP with auth (not ready yet)
- Start desktopgui with another user than the user starting I2P (required for daemon usage).
