Fork of Prado PHP framework https://emkael.info/cgit/prado/atom?h=3.2.2.03 2013-07-24T10:22:49Z 2013-07-24T10:22:49Z Ciro Mattia Gonano ciromattia@gmail.com 2013-07-24T10:22:49Z urn:sha1:0f332e6564ed67ef7eb4d715ce3bcb5ff54c50cf 2013-04-24T07:59:48Z Ciro Mattia Gonano ciromattia@gmail.com 2013-04-24T07:59:46Z urn:sha1:daa4dde508865ef0f08e584987b0695d4847809a 2013-01-19T10:17:39Z ctrlaltca 2013-01-19T10:17:39Z urn:sha1:f2a2465a97591ad478ba6b99dc4bb55b09620452 2012-11-08T09:36:28Z ctrlaltca 2012-11-08T09:36:28Z urn:sha1:fbaf4273a46828702ef1428f42e5721720d727f6 2012-10-31T02:35:01Z javalizard@gmail.com 2012-10-31T02:35:01Z urn:sha1:9ed8e2fff531f9188dc55a99e3006f94edc59a5e This adds global 'fx' events, behaviors, class-wide behaviors, intra-object/behavior 'dy' events, and tweaks the raiseEvent to be more advanced (yet backward compatible). A large amount of documentation is in here too. Slight changes to the TApplication object is made to provide events with priorities. TComponent has a massive amount of test cases as well… There are now 512 assertions. Test cases have been added for testing the GetJS and SetJS and ensure functionality of these new getters and setters. The Behaviors are all tested and fully integrated into the TComponent Object. Behaviors are more transparently and widely integrated into TComponent. Class Behaviors rely on the global events to add behaviors to instanced objects. Class behaviors also allow for behaviors to be added during the instancing of new objects of the class. Dynamic events enable the object to send events directly to behaviors as intra-object events. Dynamic events can be chained as multiple behaviors may implement the event. This allows for parameter filtering. RaiseEvent allows for raising global events, capturing results, and feeding results forward into the next handlers parameters should the need arise. This is a forward thinking feature to enable new processes to be designed into the code for PRADO version 3.3 and future version 4.0. This functionality is transparent when unused. We are hoping this is fully backward compatible with the existing code base. It was designed for maximum backward compatibility while expanding the functional base exponentially. This clears the way for a new way of thinking about how objects relate. 2012-07-12T11:21:01Z ctrlaltca 2012-07-12T11:21:01Z urn:sha1:903ae8a581fac1e6917fc3e31d2ad8fb91df80c3 2012-07-12T10:55:10Z ctrlaltca 2012-07-12T10:55:10Z urn:sha1:3e4e6e66aeb3f8fea4e1eb4237498ef9d2358f63 2012-07-10T23:43:14Z ctrlaltca 2012-07-10T23:43:14Z urn:sha1:37c4c3b158994707ab502b1b9bf4994872deeace 2012-05-10T22:05:47Z ctrlaltca 2012-05-10T22:05:47Z urn:sha1:799832a5388260337567611dd2041fc19409a2f1 2011-11-17T16:52:56Z ctrlaltca@gmail.com 2011-11-17T16:52:56Z urn:sha1:d840107832b1f59a9fc3b93ffb97ef976be1b83c 1) TErrorHandler: avoid an error when trying to hide the file path of a lambda function 2) TSecurityManager: avoid a race condition when first generating the encryptionkey or the validationkey 3) TActiveFileUpload: urlencode the base64'ed token since it can contain the "+" character (otherway it would be traslated to a space)