The good thing is that this gave me the opportunity to document everything: Now every class, property and method its documented accordingly to Ext JS Api Docs. Among other changes, somre classes where moved like Panel, TabPanel and Window to be accordingly to their namespace. There are some new helpere Classes la the strong typed collections (see changelog) and other like ToolConfigObject and IToolbarObject to help the implementation of strong typed collections. The purpose of this is trying to give a hint to the developer of how exactly the class should be used and what kind of objects should be used as parameters.

Another nice change is the implementation of strong typed layouts. This idea was took from the GWT-Ext Project where layout are not set by a string with the layout shortname, but with the corresponding object which has the parameters of that specific layout. Additionally, when adding a component to the items collection of a container, there is a second parameter containing the layout options avaliable for that item according to the layout of the container. This means that if a container its using an AnchorLayout, the item can/should be added with a AnchorLayoutData. This correspondance is checked when adding the item, meaning you will receive an error if the item its added with a layout other than the valid ones for the containers layout. This will save long hours of debugging and fighting because the widget its not showing the ways its supposed to. Anyways, I hope it helps.

The page was changed to. It took a very minor design change, how you like it. And, of course, this blog was added to post News and Announcements, so please, add it to your feeds.

What's to come? Well...Now that the refactor its done, I guess the only path is to implement as many widgets as possible. For instance I have in mind the MessageBox, Viewport and BorderLayout, maybe the Drag + Drop namespace, I don't know, you tell me, write about it on the Discussion Group.

I almost forgot, some people have been raising their hand to help in the project. I want to apologize with all of you because I haven't responde to your mails, its just I've been to busy with this and I wanted to have the complete refactor running before including other people 'cause I was changing the way everything works. It was too much, I prefered to go solo. I'll be organizing things up to gather you all for a meeting on how we can collaborate to this project to make it better. Thanks for the interest.

Nothing more to say... by now. Download the new version now and let me know what you think, and if you find any bugs/issues, please post them on the googlecode page.

CHANGELOG 0.8.2

- No more support for PHP4
- Complete refactor to comply with Zend Framework PHP Coding Standard (http://framework.zend.com/manual/en/coding-standard.html)
- Class naming: i.e.: class renamed from ExtJsonStore to PhpExt_Data_JsonStore.
See API documentation.
- Scopes. Methods like getConfigParams are no longer publicly visible.
- Constructors. Should not affected library usage except for user extensions;
- Class Constants: Constants declared with define() where moved to class contants.
See API documentation.
- Strict Standard compliant.
- Complete PHPDoc for classes, getters and setters
- Panel, TabPanel and Window where moved from PhpExt/Panels to PhpExt/ to reflect the namespace
- Strong typed collections added: ComponentCollection, ListenerCollection, ButtonCollection,
ToolConfigObjectCollection, FieldObjectCollection, ColumnConfigObjectCollection,
BaseItemCollection (Menu), IToolbarCollection. See API Documentation.
- Layouts changed to use strong typed objects for layout config and layout data for the items
of the container.
- Panel tools support
- SplitButton added
- Examples updated to comply with the new coding standard