| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Avoid saving in the page state the values of class variables if they’re
still the default.
Reduces page state size, based on the work initiated in
8dc9d4f7d49bcbeaf4998baf74a4f4459967c1f0
|
|
quickstart tutorial translations
|
|
|
|
with git
|
|
|
|
TComponent Update: Behaviors, Class Behaviors, fx global events, and dy
one to one events.
This patchset was currently available only on svn trunk/
|
|
|
|
|
|
(because they did not change from their default values) when the class gets serialized. References #337
This definitely needs better handling of subclasses properties
|
|
|
|
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.
|
|
|
|
|
|
methods prefixed by "js" to indicate that those methods can receive raw javascript. Such methods can be called both in a xss-safe, javascript-encoded way: $xxx->Property="yyy" and in a raw-javascript way: $xxx->jsProperty="zzz". Patch by gabor, documentation is on the way
|
|
|
|
|
|
© 2005-2008 PradoSoft => Copyright © 2005-2011 PradoSoft)
|
|
|
|
|
|
undocumented changes; upported the "cgi workaround" to trunk/; large (fake) changeset are due to mixed cr/crlf used previously
|
|
|
|
path for all objects.
TApplication- Adds final attribute to the parameters in the config so folder config.xml cannot override if set to true. Adds a mergeParameter function to unify parameter setting. Fixed a bug where loadParametersPhp wasn't getting the properties correctly.
TControl- calls the parent::__construct, Adds render blocking. (the PRADO class using this will be added in a week or two)
TParameterModule- Adds final attribute to the parameter option so folder configs cannot override if set to true. Uses the application mergeParameter function. Adds final to the php parameter loader
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
not work
|
|
|
|
|
|
true, not just 1.
|
|
the following: (string) 'true' == (bool) true,(string) '1' == (bool) true,(int) 1 == (bool) true,(bool) true == (bool) true, (string) 'false' == (bool) false,(string) '0' == (bool) false,(int) 0 == (bool) false,(bool) false == (bool) false
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
