CFTL is now CFC-based. The whole form right now only instantiates 3 objects regardless of number of fields the form has. So it is very lightweight. It makes the code a lot cleaner.

I just realized with text fields, most of the times you only want them to show up when they have values. I hate looking at pages that have labels like email, phone, fax, address, etc. and they are all blank. Why displaying them if they are blank. So I am thinking of adding an attribute to the text tag so that it would only display on certain condition. I have not finalized on whether to add an attribute called showOnBlank or just have a general attribute condition for people to put in any kind of conditions to meet their needs. I may do both.

I also want to add another attribute to the select tag to reload the page on change selection. I think I will make it submit to itself instead of reloading so no data would be lost. It would work something like this.

Of course if you don't like this implementation or it is intefering with something on your page, you can always implement your own theme.

We decided to change direction a little bit. Previously, whatever attributes you specify, it would try to figure out the name attribute first. So name is the key attribute in all of our tags so far. Everything else can be figured out from that attribute.

However, this week we started to tackle the table tag group, and we realized that table tags don't have name attribute. They do have id attribute.

So we change direction. The id attribute is going to be the key attribute. We should get all the changes done by the end of next week.

We finish programming all the form tags. We are moving on to table tags now. So we need people to test out the form tags to find bugs, to request additional features or to request features change, and to tell us what you like or don't like about our library. So please download the code and test it out. Thank you.

Johnny