thoughts about the Tapestry and Tacos projects

[tsvetelin <ts...@rushmore-digital.com>]

Dear All,

I would like to share some of my thoughts about the Tapestry and Tacos
projects

1. Project Tacos
  We should make this project more popular in tapestry users mailing list. I
think the people on this list don't know many things about the Tacos. I
really would like to see new components in the project. I thing that one of
the keys for tapestry success is to have a large number of standard/shared
components. So when the new people and companies start to inspect the
framework they will see that most of the thing are made and they are
available for them.

2. Communication and collaboration between Tapestry and Tacos project.
  We know that during the release involving in tapestry there achieve
improvements and receive some differences from previous to next versions. So
we should take care about the state of components during this releases of
tapestry framework. This is important because Tacos is a component
repository and I hope that there will be more and more components in the
project and I think they must be reliable for all tapestry releases. So
there must be closest communication between these 2 projects.
  At the other hand Tacos could be a test for new Tapestry release and
especially of "backward capability" part. (I know that this is a very "thin"
problem and that there was posted a lot of messages on this.)
  The next thing is a part of collaboration. If some tacos component become
a very useful and if the people use it very often the Tacos committers could
make a nomination this component to be removed into Tapestry or Contrib
library. The real example of this is Tacos:Tree. At the other words : Tacos
will be a components incubator for Tapestry.

3. I have wrote: "Working on improving of the existed Tapestry resources
(classes and components) - like bug fixing, drafts documentation
improvements ("drafts" because my English isn't very good for writing of
public tapestry documentation)." Yes, there are a few thing that I am going
to propose:
  3.1 CheckBox component to be extended to take a value parameter. I will
send to the list detailed proposal about this.
  3.2 Adding parameter "raw" to ValidField and FieldLabels - detailed
proposal will be send in separate message.
  3.3 Menu Selection Engine and corresponded two kind of components Menu and
TabPane

Tsvetelin.

PS. I have feeling that I miss something for part 3....more emails could be
expected. :)