d0c-s4vage / funder Goto Github PK

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

example (with r19):

{{{
require 'formats/png'
p = Png.new
p.idat.data.to_out
}}}

raises an error:

{{{
TypeError: can't clone NilClass
    from ./fields.rb:117:in `clone'
    from ./fields.rb:117:in `to_out'
    from ./actions.rb:105:in `do_it'
    from ./actions.rb:105:in `map'
    from ./actions.rb:105:in `do_it'
    from ./actions.rb:55:in `do_it_once'
    from ./fields.rb:113:in `to_out'
    from (irb):4
}}}

Create documentation for Funder

a

might want to rename the old one to `png_no_sugar.rb` or something and keep the 
syntactic sugar one as `png.rb`

This should be used to allow Int fields to return their length without actually 
having to calculate their value.  (This behavior will be needed in certain 
situations.)

Didn't replace <ORGANIZATION> with something meaningful

Currently, Funder-derived classes are a mess to use via irb.  Clean up the 
output!

...

actions should be able to be reversed

This is needed when working with indices and object ids

maybe something like only adding an extra require before the normal require 
(would have to be, actually):

{{{
require 'funder_read'
require 'formats/png'

p = Png.parse(File.read("test.png"))
puts p.ihdr.data.width.value
}}}

It's rather hack-ish the way some of the code waits for other objects to be 
created.  Create an init function that the root node calls after it has 
recursively instantiated all of the fields.

Find all the hack-ish init code and put it in the init() method

eat some doritos

Make it so you don't have to reference a separate field when applying an action

Also would be nice to be able to do something like this:

array :items, [Class1, Class2, Class3, Class4]

Should probably have to give which parent structure to use as the base.

Example:

{{{
    ...
    field :tag_table, TagTableEntry, nil, :mult=>true
    field :tags, Tag, nil, :mult=>true
    ...
}}}

Should be able to define the one-to-one relationship between each TagTableEntry 
and each Tag, maybe something like:

{{{
    ...
    field :tag_table, TagTableEntry, nil, :mult=>true,
                                          :rel=>[1, 1, lambda{[tags]}]
    field :tags, Tag, nil, :mult=>true, :rel=>[1, 1, lambda{[tag_table]}]
    ...
}}}

Given `:rel=>[A, B, lambda{[C]}]`, A is the current field ratio, B is the 
external field ratio, and C is the name of the field with which the current one 
must remain in sync.