Started clean slate rstore + reform version 2.0

- Created Rakefile
- with dependencies
- and proper escaping of commandline
- Build working .so
working app.rb example

- setting up internalize. WIP
- implemented QObject + objectName sec
- new files
- some interesting tests.
- rb_check_array_type returns Qnil and does not raise...
- Data_Get_Struct should check for the proper cObject class if unsure.
- fool proof zombie system
- but memory loss is possible
- since urqt does NOT guard any Q instances!
- ruby signals in < 20 lines of code...
  and MUCH better than the Qt shit
- 16 rspec examples working

- learned: rb_is_instance_of uses the direct class, use rb_is_kind_of
  instead
- 20 examples for object 0 fails

- how can we signal specific events like 'resized'? They are not
  signals in Qt but 'events'. Which seems more or less the same.
- IMPORTANT: we need 'dynamic' properties for all properties with
  'data' like values like ints, floats, strings, colors and
  the like.
  For example: objectName in Object (but not parent or children).
	       size and title in Widget
  This feature is tied to Control class however. So Control.objectName
  might work.
  Technically either a single Hash as argv[0] or a block but
  no other args should trigger special handling, which hopefully
  can be done by 1 function.
  Similar for properties defined in ruby we can use Control::dynamic
  to function like define_setter used to.
- shown -> app.quit and rspec no longer hangs
- BUGFIX: the following scenario:
    p = Widget.new
    ch = Widget.new p, 'herman'
    ch = nil
    GC
    p.findChild('herman').show
  herman has a QWidget with a 'ch' inside it.
  presumably p.findChild('herman') returns a VALUE that is GC'ed!
  OR DOES IT WORK??? INTERESTING.
25 examples 0 fails
label plugin.

- Fixed some badly placed and circular requires
- canvas, but without properties (aka graphicsview)
- more typesafe API
- scene works, but only an empty one
- MILESTONE: working qtcircle!
far better rake include file

- however, it should have cool parameters instead of required
  global constants in the calling Rakefile
- fixed major 'for' bug in rake-include
- I have a slider so the fun can start

- but we need a simple layout next
refactoring to a 'pure' and 'complete' parent/children tree.

- 29 examples, parenting widgets works fine now
- A working read-only model.
- 30 specs

- copyrights
- working lineedit aka edit
- some docu
- made some progress on edit data routing
working vbox

- and hbox
- rb_any_to_s is definetely not the same as to_s
- parenting of layout now works correctly.
- but nested layouts not yet tested.
- also I need a 'collectNames true' property for Control. I think it
  should create methods so we do not rely on method_missing so much.
- done refactor enqueue_children
36 working specs
BLUE !!!

- new files
- GC problem with Block param in SignalProc fixed
- gcguard
propagation works correctly

- graphicsscene should adapt children. Because it is used for mark!
- and the same for items: they should enumerate brush and pen!
- or maybe cObject_mark is WRONG. it should not mark 'children' but
  'qtchildren'!?
  and items need their own overrides for these.
  Because OWNERSHIP is the only thing that matters here. ?
  No, when we store a ruby object inside a C++ object we must mark.
  This is not so for brushes or pens.
- But a graphicsitem holds a ruby VALUE
  So qtchildren is better because it makes sense faking it for g-items.
  And we would skip pens and brushes
- Yes, but.....   Application has children that MUST be enumerated but
  are not qtchildren...
  So children is safer.
MILESTONE: black and blue program in button.rb

- fixed two failing specs
- rectangle graphics class + pens
- points and scaling OK
- pen now works for rectangle/circle
- added lines
triangle example

- scene now has a background brush
- technically polygons should work too, since triangle is just a
  special case of that
- beziers + quads added
- a little cleanup
- it is coming together, 'cap' still todo
joinstyle + capstyle for pens

- +10 dynamic properties for rectangle graphics
- no extra specs, but 36 work
- typo fix
- minimal painterpath functionality
- deleted stuff
- alternative parenting system for noqtcontrol class!
- attempt to revitalize ruby++
- moved shared objects to reform dir. Makes linking easier
- extended ruby++
- r++-ed brush.cpp for 99%
- 36 working specs people!
- And it is BLACK now. And it stays that way.
- MILESTONE: example 003 works.

- TODO: urgent request to extend rpp first and make a 100% spectest
  This can be done by using rpp to create rpprpp.
  Wow, a Godel idea.