SF.net SVN: fclient: [24] trunk/TODO.txt

[<jU...@us...>]

Revision: 24
          http://fclient.svn.sourceforge.net/fclient/?rev=24&view=rev
Author:   jUrner
Date:     2007-10-31 06:05:50 -0700 (Wed, 31 Oct 2007)

Log Message:
-----------
started a todo.txt, with some major tasks 

Added Paths:
-----------
    trunk/TODO.txt

Added: trunk/TODO.txt
===================================================================
--- trunk/TODO.txt	                        (rev 0)
+++ trunk/TODO.txt	2007-10-31 13:05:50 UTC (rev 24)
@@ -0,0 +1,47 @@
+Major todos
+********************************************************************************************
+x. fist widgets to implement: up / downloads, browser, message board
+	
+	Multipurpose up / downnload widget should be ready to go in relatively short time.
+    This widget is not only intendet to be used for well.. up / downloads, but should
+	serve as a base component for message board and browser. I like to see visual 
+	feedback on every up / download happening in the Gui.
+
+
+x. message board format is quite unclear to me. There are some specs
+    available here: 
+		[http://jtcfrost.svn.sourceforge.net/viewvc/jtcfrost/trunk/frost-wot/specs/]
+	
+	Some java code from freenet-svn: 
+		[http://freenet.googlecode.com/svn/trunk/freenet/src/freenet/frost/message/]
+	
+	..and maybe more.
+	
+		
+x. quite a lot of consts are undocumented. Consts used in config settings for example.
+	Or the string representations of consts describing the status of peers. The node
+	says hapily this peer is "CONNECTED". But couldn't find any info on the const, except 
+	tracking it down to the PEER_NODE_STATUS_CONNECTED const as defined in
+	[http://freenet.googlecode.com/svn/trunk/freenet/node/PeerManager.java]
+	
+	
+x. a widget that can be used to visualize freenet index files. This thingy should give some header information 
+	and allow the user to select any number of uris from an index for download. Already implemented a half 
+	way working prototype. But quite unclear how to handle _massive_ indices reliably. Intersting
+	thing would be to allow for automized creation of index files from a bunch of files ready for
+	insertion (wizzard?).
+
+
+x. developer documentation is written in epydoc. Should be 20-30Mb all in all,
+    so.. to huge to ship alongside. A nice-to-have would be an option to allow the user
+	to generate a fresh set on the fly and integrate it in QAssistant. Job is to write
+	a module that can handle epydoc-output --> assistant-profile generation. 
+
+	done a similar thing berfore to generate Chms from epydoc output. See
+	[https://frogpie.svn.sourceforge.net/svnroot/frogpie/trunk/sandbox/chm].
+	Shouldn't be too hard to polish this package and add the desired functionality.
+	Basically its about adjusting the package to support output writers. Alternative
+	is to flesh "chm_lib/epydoc_fs.py" out and base a standalone module on it.  
+
+
+


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.