mak: and form: taglib/product separation
Makumba has two original ideas:
- query fragment combination
- multiple forms
It may be that some outsiders won't want to use both ideas, but just
one of them
Brief:
- consider publishing 2 taglibs: mak:
and form:
- there still exist dependencies between the two. Think of how they
can be reduced, or can be left as a default, but not necessarily
- consider how this would affect existing applications
- consider deprecation of mak:*form and mak:input without affecting
existing code