Prototype Statically Typed Components about vugu

[bketelsen]

I did something like this last summer:
https://github.com/factorapp/playground/blob/master/pages/components.ghtml
May be worth digging to see the pros/cons of that approach, which is quite different from vugu, but does have namespaced components like you describe.

[bradleypeabody]

I'm bumping this up in priority because it's a big change and if it's to be done it should be done early. Several other big issues (#7, #14, #5) are affected by it.

[bradleypeabody]

Just another note on this is to not forget how to deal with some properties being hard fields but have the option of components just getting all other properties passed in as a generic map or something. I.e. if you pass a property to a component that it knows about it should be set in a type safe way which fails at compilation if not. But you also need the ability to just "pass through" things that you want to end up on an HTML tag but don't otherwise need to look at. In order to make the calling component not have to understand too much about the compnent it's calling it might require a different syntax, e.g. :prop means a hard field, whereas -prop would just get added to a generic map - something like that could work.

[bradleypeabody]

Note to self on syntax:

<!-- this could mean look for a Go struct field named "Prop", and fail on bad name or bad type -->
<pkg:comp :Prop="x"/> 

<!-- while this could mean to pass "prop" in a member of map, for dynamic attributes that the component will parse manually -->
<pkg:comp :prop="x"/>

[bradleypeabody]

This is now done and merged into master.