Skip to content

Commit

Permalink
Updated TODO list
Browse files Browse the repository at this point in the history
git-svn-id: svn://badgerpower.com/Badger/trunk/badger@65 f7e19ab9-6750-0410-bcef-57680045ec6a
  • Loading branch information
abw committed Jul 8, 2008
1 parent 5e11ee8 commit ef2bfb1
Showing 1 changed file with 48 additions and 30 deletions.
78 changes: 48 additions & 30 deletions TODO
@@ -1,12 +1,50 @@
Filesystem
----------
Badger::Class
-------------

* finish cleanup and documentation

* pkg() alias for name()

* AUTOLOAD method to delegate to real class if possible?


Badger::Codec
--------------

* encoded()/decoded() methods (e.g. for utf8)


Badger::Config
--------------

* Just a basic implementation at moment. Merge in TT3 config, AppConfig
and other stuff.


Badger::Debug
-------------

* move in debug() from Badger::Base and make it a mixin.


Badger::Exception
-----------------

* needs good cleanup


Badger::Filesystem
------------------

* documentation

* exists() should check the type for file/dir

* directory files/directories/dirs

* virtual filesystems composed across several real filesystems


Badger::Storage
---------------

Expand All @@ -19,37 +57,17 @@ Badger::Storage

* create/destroy connect/disconnect open/close

Misc
----

* Move Badger::Exception to Badger::Error and clean out


Badger::Test
------------

=head3 Configuration Options
* Could do with some proper testing. Although all the other test scripts
do tend to thrash it quite well...

The following configuration options are provided by default for
all objects derived from the Badger::Base module that inherit
its C<new()> method and C<init()> methods.

=head4 throws

This option can be set to cause the object to throw as exceptions any
and all errors raised by calls to the C<error($msg)> method. A
L<Badger::Exception> object is created (or an object of whatever class
is defined in the C<$EXCEPTION> package variable) with its C<type>
set to the value of the C<throws> parameter and C<info> field containing
the error message passed to the C<error($msg)> method.

my $object = My::Badger::Forager->new( throws => 'hungry' );

$object->error('No nuts or berries found!');

In the preceding example, the call to the C<error()> method
results in an exception object being throw via die with a C<type>
of C<fruit> and C<info> set to C<No berries found>.

fruit error - No berries found!
Misc
----

See the C<error()> and C<throw()> methods for further details.
* Move Badger::Exception to Badger::Error and clean out. Hmm... nah,
maybe not.

0 comments on commit ef2bfb1

Please sign in to comment.