Commits

Anonymous committed ff8ffa5

Nav-Menu: Cleaned up the TODO by putting items in TODO-Rejects, which
is now part of the distribution.

Comments (0)

Files changed (3)

 MANIFEST
 README
 TODO
+TODO-Rejects
 t/00use.t
 t/01unit.t
 t/02site-map.t
-* Release on CPAN as version 0.4.0.
-    - change the version in $VERSION.
-    - document the changes in Changes.
-    - update the readme.
-
 Long-Term:
 ----------
 
-* Use HTML::Widgets::NavMenu::Tree::Node and its accessors for the rest
-  of the $ptr->{text} etc. manipulations.
-    - for the get_next_coords() and friends functions.
-
 * Use Build.PL instead of Makefile.PL. (?)
 
 * Make the module support URLs with CGI GET parameters properly.
 * In HTML::Widgets::NavMenu::Tree::Node - make sure url_type accepts only
 its enum values.
 
-* Future direction: generate the tree once and then be able to render
-it for different path_info()/current_host() configurations. (and the
-generated tree re-used by all other members).
-
-* Refactor get_next_coords().
-
-* Create a base class for classes with 'subs' functionality - like 
-get_nth_sub, add_sub, num_subs, etc. Both ..::Node and ..::Item share it.
-
 * Give an option to render a sub-set of the navigation-menu, starting
 at a certain coords/url-path.
 
+* Release on CPAN as version 0.6.0.
+   - change the version in $VERSION.
+   - document the changes in Changes.
+   - update the readme.
+

module/TODO-Rejects

+* Refactor get_next_coords().
+
+    - I don't see too much point. It is working as it is, and it's only
+    one function that doesn't affect the rest of the code.
+
+* Create a base class for classes with 'subs' functionality - like 
+get_nth_sub, add_sub, num_subs, etc. Both ..::Node and ..::Item share it.
+
+    - They have slightly different semantics, and besides - it's not
+    too much duplicate code. It would be more trouble than it's worth.
+
+* Future direction: generate the tree once and then be able to render
+it for different path_info()/current_host() configurations. (and the
+generated tree re-used by all other members).
+   
+    - the problem is that the expand() operations and the expanded()
+    flag depends on this combination. Thus, the generated tree is
+    different for any path_info()/current_host().
+
+