PRADO ma w Polsce wciąż małą popularność, a uważam że zasługuje na większą uwagę. To naprawdę dobry framework napisany w PHP. Chciałem złożyć propozycję wszystkim osobom, które korzystają z niego, aby umieściły anty-pixel który zrobiłem (wiem że nie jest zbyt finezyjny, ale miałem tylko kilka wolnych chwil na jego stworzenie) na swoich stronach - oczywiście jako odnośnik do xisc.com:

The next major version of PRADO will be version 3.0. The main goal of this version is to improve performance and robustness, and provide more functionality. The framework core is being completely rewritten. Unit tests are added to ensure the quality. Application controller is being redesigned to provide a looser coupling. More components are being written. And several complete demo systems will be included. (...) Below is a list of the implemented features in v3 that was written about two months ago: - component spec file discarded - relationship change between controls, now with parent-child (presentational) and naming container-containee relationships. - enhanced control id management and rendering (the rendered IDs are much shorter now) - enhanced event binding syntax besides the existing one (e.g. $control->Click=$callback; or $control->Click[0]=$callback;) - subproperty support (e.g. Font.Size="20") - component can be specified in a namespace format in template (e.g. - theme/skin support, can be personalized - master/content support at control level, and $this->contentID->controlID reference is no longer needed - page lifecycles modified, close to that of asp.net 2.0 - template comments supported ( unlike HTML comments, template comments are not rendered.) - enhanced template syntax: changing databinding syntax to property=<%# expr %> ; added dynamic property value property=<%= expr %>, which is evaluated and set when the property is initialized. - unified special template tag <% %>, which initializes properties of the template owner - enhanced template parsing error report: now with line number and error reason. - a module-based application architecture - pages organized in directories and aliases are used to access pages rather than their class names (for better security) - generic cache support with TMemCache and TSqliteCache provided (users can develop other cache classes and plug in easily) - complete request, response, session, cookie classes (in v2 they lack many features) - an auth framework is provided, including TAuthManager and TUserManager (plan to do TMembershipManager and login controls) - support of "classless" pages - parameters can be components now - asset management - enhanced theme syntax and support Features to be implemented in the near future: - enhanced javascript support - ajax integration

Komentarze [0]