From 151b2f7d102a5988b63255d27c9ad78202c16355 Mon Sep 17 00:00:00 2001 From: Fabio Bas Date: Mon, 9 Nov 2015 00:33:08 +0100 Subject: Added (partial) website + misc updates for release * recreated the prado website in demos/ * updated some docs to reflect the usage of jquery; removed guide to prototype * updated composer * added task for apigen4 (theme still missing) --- demos/quickstart/protected/controls/TopicList.tpl | 2 - .../quickstart/protected/controls/de/TopicList.tpl | 2 - .../quickstart/protected/controls/es/TopicList.tpl | 2 - .../quickstart/protected/controls/fr/TopicList.tpl | 2 - .../quickstart/protected/controls/id/TopicList.tpl | 2 - .../quickstart/protected/controls/ja/TopicList.tpl | 2 - .../quickstart/protected/controls/pl/TopicList.tpl | 2 - .../quickstart/protected/controls/zh/TopicList.tpl | 2 - .../pages/ActiveControls/ActiveRatingList.page | 2 +- .../pages/ActiveControls/Introduction.page | 4 +- .../protected/pages/Advanced/Scripts1.page | 96 -------- .../protected/pages/Advanced/Scripts2.page | 253 --------------------- .../protected/pages/Advanced/Scripts3.page | 29 ++- .../protected/pages/Advanced/es/Scripts1.page | 96 -------- .../protected/pages/Advanced/es/Scripts2.page | 253 --------------------- .../protected/pages/Advanced/id/Scripts1.page | 86 ------- .../protected/pages/Advanced/id/Scripts2.page | 214 ----------------- .../protected/pages/Controls/HtmlArea4.page | 2 +- .../protected/pages/Controls/Markdown.page | 2 +- .../protected/pages/Database/ViewsArUpdate.page | 14 +- .../protected/pages/Fundamentals/Pages.page | 2 +- .../pages/GettingStarted/CommandLine.page | 12 +- .../pages/GettingStarted/Installation.page | 4 +- .../pages/GettingStarted/Upgrading32.page | 8 +- .../protected/pages/GettingStarted/Wsat.page | 10 +- .../protected/pages/JuiControls/Home.page | 10 +- .../protected/pages/JuiControls/Interactions.page | 12 +- .../protected/pages/JuiControls/Widgets.page | 10 +- 28 files changed, 65 insertions(+), 1070 deletions(-) delete mode 100755 demos/quickstart/protected/pages/Advanced/Scripts1.page delete mode 100755 demos/quickstart/protected/pages/Advanced/Scripts2.page delete mode 100755 demos/quickstart/protected/pages/Advanced/es/Scripts1.page delete mode 100755 demos/quickstart/protected/pages/Advanced/es/Scripts2.page delete mode 100755 demos/quickstart/protected/pages/Advanced/id/Scripts1.page delete mode 100755 demos/quickstart/protected/pages/Advanced/id/Scripts2.page (limited to 'demos/quickstart/protected') diff --git a/demos/quickstart/protected/controls/TopicList.tpl b/demos/quickstart/protected/controls/TopicList.tpl index ed57a4b0..c23bd2be 100644 --- a/demos/quickstart/protected/controls/TopicList.tpl +++ b/demos/quickstart/protected/controls/TopicList.tpl @@ -106,8 +106,6 @@
Client-side Scripting
diff --git a/demos/quickstart/protected/controls/de/TopicList.tpl b/demos/quickstart/protected/controls/de/TopicList.tpl index 470927da..3c358b43 100755 --- a/demos/quickstart/protected/controls/de/TopicList.tpl +++ b/demos/quickstart/protected/controls/de/TopicList.tpl @@ -106,8 +106,6 @@
Client-side Scripting
diff --git a/demos/quickstart/protected/controls/es/TopicList.tpl b/demos/quickstart/protected/controls/es/TopicList.tpl index 62451700..ba5f83c4 100644 --- a/demos/quickstart/protected/controls/es/TopicList.tpl +++ b/demos/quickstart/protected/controls/es/TopicList.tpl @@ -103,8 +103,6 @@
Scripts del lado del cliente (Client-side Scripting)
diff --git a/demos/quickstart/protected/controls/fr/TopicList.tpl b/demos/quickstart/protected/controls/fr/TopicList.tpl index c37609ab..1959fcbc 100644 --- a/demos/quickstart/protected/controls/fr/TopicList.tpl +++ b/demos/quickstart/protected/controls/fr/TopicList.tpl @@ -101,8 +101,6 @@
Script côté client
diff --git a/demos/quickstart/protected/controls/id/TopicList.tpl b/demos/quickstart/protected/controls/id/TopicList.tpl index a35db55d..1f1f9403 100644 --- a/demos/quickstart/protected/controls/id/TopicList.tpl +++ b/demos/quickstart/protected/controls/id/TopicList.tpl @@ -102,8 +102,6 @@
Penaskahan sisi-Klien
diff --git a/demos/quickstart/protected/controls/ja/TopicList.tpl b/demos/quickstart/protected/controls/ja/TopicList.tpl index f24994e0..dc025b1a 100644 --- a/demos/quickstart/protected/controls/ja/TopicList.tpl +++ b/demos/quickstart/protected/controls/ja/TopicList.tpl @@ -102,8 +102,6 @@
クライアントサイドスクリプト
diff --git a/demos/quickstart/protected/controls/pl/TopicList.tpl b/demos/quickstart/protected/controls/pl/TopicList.tpl index a494d94e..c92962f9 100644 --- a/demos/quickstart/protected/controls/pl/TopicList.tpl +++ b/demos/quickstart/protected/controls/pl/TopicList.tpl @@ -102,8 +102,6 @@
Skrypty po stronie klienta
diff --git a/demos/quickstart/protected/controls/zh/TopicList.tpl b/demos/quickstart/protected/controls/zh/TopicList.tpl index 73e1d5a8..79293c18 100644 --- a/demos/quickstart/protected/controls/zh/TopicList.tpl +++ b/demos/quickstart/protected/controls/zh/TopicList.tpl @@ -101,8 +101,6 @@
客户端编程
diff --git a/demos/quickstart/protected/pages/ActiveControls/ActiveRatingList.page b/demos/quickstart/protected/pages/ActiveControls/ActiveRatingList.page index 7b6fb83d..fa0e25c4 100644 --- a/demos/quickstart/protected/pages/ActiveControls/ActiveRatingList.page +++ b/demos/quickstart/protected/pages/ActiveControls/ActiveRatingList.page @@ -1,6 +1,6 @@ -

TActiveRatingList

+

TActiveRatingList

diff --git a/demos/quickstart/protected/pages/ActiveControls/Introduction.page b/demos/quickstart/protected/pages/ActiveControls/Introduction.page index edc0b5bc..275da737 100755 --- a/demos/quickstart/protected/pages/ActiveControls/Introduction.page +++ b/demos/quickstart/protected/pages/ActiveControls/Introduction.page @@ -9,7 +9,7 @@ A classic webpage can only transfer data back to the server using an http postba A common solution to this problem is the use of AJAX (Asynchronous JavaScript and XML) callbacks. After the first full page load, the web application can make subsequents requests using javascript. The callback requests are asynchronous, so the user can continue to interact with the page while the response is loading. The response contains a list of changes that will be applied to the page "on the fly", like replacing existing elements with new content or add some css style to an existing element.

-

Interacting with a page on callback

+

Interacting with a page on callback

PRADO has builtin support for AJAX callbacks in the form of Active Controls. These controls can trigger a callback request and have their properties (value, css style, attributes, ..) updated during a callback. @@ -28,7 +28,7 @@ public function onClick($sender, $param) } -

Active Controls (AJAX enabled Controls)

+

Active Controls (AJAX enabled Controls)

Active controls extends standard PRADO controls adding the ability to automatically update themselves on callbacks without the need of ad-hoc javascript calls. Active controls are reliant on a collection of javascript classes that gets added to the page automatically when needed.

diff --git a/demos/quickstart/protected/pages/Advanced/Scripts1.page b/demos/quickstart/protected/pages/Advanced/Scripts1.page deleted file mode 100755 index 96ab7760..00000000 --- a/demos/quickstart/protected/pages/Advanced/Scripts1.page +++ /dev/null @@ -1,96 +0,0 @@ - - -

Developer Notes for prototype.js

-This guide is based on the -Developer Notes for prototype.js by Sergio Pereira. - -

What is that?

-

-In case you haven't already used it, prototype.js is a - JavaScript library written by Sam Stephenson. - This amazingly well thought and well written piece of standards-compliant code takes a lot of - the burden associated with creating rich, highly interactive web pages that characterize the Web 2.0 off your back. -

- -

- If you tried to use this library recently, you probably noticed that documentation is not one - of its strongest points. As many other developers before me, I got my head around prototype.js by - reading the source code and experimenting with it. I thought it would be nice to take notes while - I learned and share with everybody else. -

-

- As you read the examples and the reference, developers familiar with the Ruby - programming language will notice an intentional similarity between Ruby's - built-in classes and many of the extensions implemented by this library. -

- - -

Using the $() function

-

- The $() function is a handy shortcut to the all-too-frequent document.getElementById() function - of the DOM. Like the DOM function, this one returns the element that has the id passed as an argument. -

- -

- Unlike the DOM function, though, this one goes further. You can pass more than one id and - $() will return an Array object with - all the requested elements. The example below should illustrate this. -

- -<com:TClientScript UsingClientScripts="prado" /> -
-

This is a paragraph

-
- -
-

This is another paragraph

-
- - - - - - -

- Another nice thing about this function is that you can pass either the id string or the element object itself, - which makes this function very useful when creating other functions that can also take either form of argument. -

- -

Using the $F() function

- -

- The $F() function is a another welcome shortcut. It returns the value of any field input control, - like text boxes or drop-down lists. The function can take as argument either the element id or the element object itself. -

- - - - - - - - diff --git a/demos/quickstart/protected/pages/Advanced/Scripts2.page b/demos/quickstart/protected/pages/Advanced/Scripts2.page deleted file mode 100755 index 5d88b065..00000000 --- a/demos/quickstart/protected/pages/Advanced/Scripts2.page +++ /dev/null @@ -1,253 +0,0 @@ - -

DOM Events and Javascript

- -

Basic event handling

- -

The syntax for working with events looks like the code below.

- - -Event.observe(element, name, observer, [useCapture]); - - -

Assuming for a moment that we want to observe when a link was clicked, -we could do the following:

- - -// <a id="clicker" href="http://foo.com">Click me</a> -Event.observe('clicker', 'click', function(event) -{ - alert('clicked!'); -}); - - -

If we wanted to get the element that fired the event, we'd do this:

- - -Event.observe('clicker', 'click', function(event) -{ - alert(Event.element(event)); -}); - - -

Observing keystrokes

- -

If we wanted to observe keystrokes for the entire document, we could do the following:

- - -Event.observe(document, 'keypress', function(event) -{ - if(Event.keyCode(event) == Event.KEY_TAB) - alert('Tab Pressed'); -}); - - -

And lets say we wanted to keep track of what has been typed :

- - -Event.observe('search', 'keypress', function(event) -{ - Element.update('search-results', $F(Event.element(event))); -}); - - -

Prototype defines properties inside the event object for some -of the more common keys, so feel free to dig around in Prototype to -see which ones those are.

- -

A final note on keypress events; If you'd like to detect a -left click you can use Event.isLeftClick(event).

- -

Getting the coordinates of the mouse pointer

- -

Drag and drop, dynamic element resizing, games, and -much more all require the ability to track the X and Y location of -the mouse. Prototype makes this fairly simple. The code below tracks -the X and Y position of the mouse and spits out those values into -an input box named mouse.

- - -Event.observe(document, 'mousemove', function(event) -{ - $('mouse').value = "X: " + Event.pointerX(event) + - "px Y: " + Event.pointerY(event) + "px"; -}); - - -

If we wanted to observe the mouse location when it was -hovering over a certain element, we'd just change the document argument to -the id or element that was relevant.

- -

Stopping Propagation

- -

Event.stop(event) will stop the propagation of an event .

- -

Events, Binding, and Objects

- -

Everything has been fairly straight forward so far, but things -start getting a little trickier when you need to work with events in -and object-oriented environment. You have to deal with binding and funky -looking syntax that might take a moment to get your head around.

- -

Lets look at some code so you can get a better understanding of what I'm talking about.

- -EventDispenser = Class.create(); -EventDispenser.prototype = -{ - initialize: function(list) - { - this.list = list; - - // Observe clicks on our list items - $$(this.list + " li").each(function(item) - { - Event.observe(item, 'click', this.showTagName.bindEvent(this)); - }.bind(this)); - - // Observe when a key on the keyboard is pressed. - // In the observer, we check for - // the tab key and alert a message if it is pressed. - Event.observe(document, 'keypress', this.onKeyPress.bindEvent(this)); - - // Observe our fake live search box. When a user types - // something into the box, the observer will take that - // value(-1) and update our search-results div with it. - Event.observe('search', 'keypress', this.onSearch.bindEvent(this)); - - Event.observe(document, 'mousemove', this.onMouseMove.bindEvent(this)); - }, - - // Arbitrary functions to respond to events - showTagName: function(event) - { - alert(Event.element(event).tagName); - }, - - onKeyPress: function(event) - { - var code = event.keyCode; - if(code == Event.KEY_TAB) - alert('Tab key was pressed'); - }, - - onSearch: function(event) - { - Element.update('search-results', $F(Event.element(event))); - }, - - onMouseMove: function(event) - { - $('mouse').value = "X: " + Event.pointerX(event) + - "px Y: " + Event.pointerY(event) + "px"; - } -} - -

Whoa! What's going on here? Well, we've defined our a -custom class EventDispenser. We're going to be using this class -to setup events for our document. Most of this code is a -rewrite of the code we looked at earlier except this time, we -are working from inside an object.

- -

Looking at the initialize method, we can really see how -things are different now. Take a look at the code below:

- -// Observe clicks on our list items -$$(this.list + " li").each(function(item) -{ - Event.observe(item, 'click', this.showTagName.bindEvent(this)); -}.bind(this)); - - -

We've got iterators, binding and all sorts of stuff going on. -Lets break down what this chunk of code is doing.

- -

First we are hunting for a collection of elements based on -it's CSS selector. This uses the Prototype selector function $$(). -After we've found the list items we are dealing with we send -those into an each iteration where we will add our observers.

- - -Event.observe(item, 'click', this.showTagName.bindEvent(this)); - - -

Now looking at the code above, you'll notice the bindEvent function. -This takes the method before it showTagName and treats it as the -method that will be triggered when, in this case, -someone clicks one of our list items.

- -

You'll also notice we pass this as an argument to the bindEvent function. -This simply allows us to reference the object in context EventDispenser -inside our function showTagName(event). If the showTagName function -requires additional parameters, you can attach them to the later parameters of bindEvent. For example

- -this.showTagName.bindEvent(this, param1, param2); - -//where the showTagName function is defined as -showTime : function (event, param1, param2) { ... } - - -

Moving on, you'll see bind(this) attached to our iterator function. -This really has nothing to do with events, it is only here to allow me to -use this inside the iterator. If we did not use bind(this), I could not -reference the method showTagName inside the iterator.

- -

Ok, so we'll move on to looking at our methods that actually get -called when an event occurs. Since we've been dealing with showTagName, lets look at it.

- - -showTagName: function(event) -{ - alert(Event.element(event).tagName); -} - - -

As you can see, this function accepts one argument--the event. -In order for us to get the element which fired the event we need to -pass that argument to Event.element. Now we can manipulate it at will.

- -

This covers the most confusing parts of our code. The text above is also -relevant to the remaining parts of our code. If there is anything about -this you don't understand, feel free to ask questions in the forum.

- -

Removing Event Listeners

- -

This one threw me for a loop the first time I tried to use it. -I tried something similar to what I did in the Event.observe -call with the exception of using stopObserving, but nothing seemed -to change. In other words, the code below does NOT work.

- - -$$(this.list + " li").each(function(item) -{ - Event.stopObserving(item, 'click', this.showTagName); -}.bind(this)); - - -

What's the deal here? The reason this does not work is because there -is no pointer to the observer. This means that when we passed this.showTagName -in the Event.observe method before hand, we passed it as an -anonymous function. We can't reference an anonymous function -because it simply does not have a pointer.

- -

So how do we get the job done? All we need to do is give the -observing function a pointer, or the jargon free version: Set a variable -that points to this.showTagName. Ok, lets change our code a bit.

- - -this.showTagObserver = this.showTagName.bindEvent(this); - -// Observe clicks on our list items -$$(this.list + " li").each(function(item) -{ - Event.observe(item, 'click', this.showTagObserver); -}.bind(this)); - - -

Now we can remove the event listeners from our list like this:

- -$$(this.list + " li").each(function(item) -{ - Event.stopObserving(item, 'click', this.showTagObserver); -}.bind(this)); - - - diff --git a/demos/quickstart/protected/pages/Advanced/Scripts3.page b/demos/quickstart/protected/pages/Advanced/Scripts3.page index 3f41abe1..b937e274 100755 --- a/demos/quickstart/protected/pages/Advanced/Scripts3.page +++ b/demos/quickstart/protected/pages/Advanced/Scripts3.page @@ -19,22 +19,31 @@ $this->getPage()->getClientScript()->registerPradoScript("effects"); The available packaged libraries included in Prado are
    -
  • prado : basic PRADO javascript framework based on Prototype
    • -
  • effects : visual effects from script.aculo.us
    • -
  • ajax : ajax and callback related based on Prototype
    • -
  • validator : validation
    • +
  • jquery : jQuery javascript framework
    • +
  • prado : basic PRADO javascript framework based on jQuery
    • +
  • bootstrap : Bootstrap front-end framework
    • +
  • effects : visual effects based on jQueryUI
    • +
  • ajax : ajax and callback related based on jQuery
    • +
  • validator : widgets validation
  • logger : javascript logger and object browser
    • -
  • datepicker : datepicker control
    • -
  • colorpicker : colorpicker control
    • +
  • datepicker : TDatepicker control
    • +
  • colorpicker : TColorPicker control
  • dragdrop : basic support for "drag and drop" control
  • dragdropextra : extra support for "drag and drop" controls
    • -
  • slider : slider control
    • +
  • slider : TSlider control
  • keyboard : software keyboard control
    • -
  • tabpanel : tabpanel control
    • +
  • tabpanel : TTabPanel control
    • +
  • inlineeditor : TInPlaceTextBox. control
  • activedatepicker : ajax version of the datepicker control
  • activefileupload : ajax version of the fileupload control
    • -
  • accordion : accordion control
    • -
  • htmlarea : tinymce control
    • +
  • accordion : TAccordion control
    • +
  • ratings : TRatingList control
    • +
  • htmlarea : tinyMCE version 3 editor
    • +
  • htmlarea4 : tinyMCE version 4 editor
    • +
  • prototype : prototype javascript framework (only for compatibility with old custom controls)
    • +
  • dragdrop : compatibility package for old, prototype-based drag&drop controls
    • +
  • dragdropextra : compatiblity package for old, prototype-based drag&drop controls
    • +
  • autocomplete : compatibility package for prototype-based TAutoComplete control

The dependencies for each library are automatically resolved. Components diff --git a/demos/quickstart/protected/pages/Advanced/es/Scripts1.page b/demos/quickstart/protected/pages/Advanced/es/Scripts1.page deleted file mode 100755 index 96ab7760..00000000 --- a/demos/quickstart/protected/pages/Advanced/es/Scripts1.page +++ /dev/null @@ -1,96 +0,0 @@ - - -

Developer Notes for prototype.js

-This guide is based on the -Developer Notes for prototype.js by Sergio Pereira. - -

What is that?

-

-In case you haven't already used it, prototype.js is a - JavaScript library written by Sam Stephenson. - This amazingly well thought and well written piece of standards-compliant code takes a lot of - the burden associated with creating rich, highly interactive web pages that characterize the Web 2.0 off your back. -

- -

- If you tried to use this library recently, you probably noticed that documentation is not one - of its strongest points. As many other developers before me, I got my head around prototype.js by - reading the source code and experimenting with it. I thought it would be nice to take notes while - I learned and share with everybody else. -

-

- As you read the examples and the reference, developers familiar with the Ruby - programming language will notice an intentional similarity between Ruby's - built-in classes and many of the extensions implemented by this library. -

- - -

Using the $() function

-

- The $() function is a handy shortcut to the all-too-frequent document.getElementById() function - of the DOM. Like the DOM function, this one returns the element that has the id passed as an argument. -

- -

- Unlike the DOM function, though, this one goes further. You can pass more than one id and - $() will return an Array object with - all the requested elements. The example below should illustrate this. -

- -<com:TClientScript UsingClientScripts="prado" /> -
-

This is a paragraph

-
- -
-

This is another paragraph

-
- - - - - - -

- Another nice thing about this function is that you can pass either the id string or the element object itself, - which makes this function very useful when creating other functions that can also take either form of argument. -

- -

Using the $F() function

- -

- The $F() function is a another welcome shortcut. It returns the value of any field input control, - like text boxes or drop-down lists. The function can take as argument either the element id or the element object itself. -

- - - - - - - - diff --git a/demos/quickstart/protected/pages/Advanced/es/Scripts2.page b/demos/quickstart/protected/pages/Advanced/es/Scripts2.page deleted file mode 100755 index 5d88b065..00000000 --- a/demos/quickstart/protected/pages/Advanced/es/Scripts2.page +++ /dev/null @@ -1,253 +0,0 @@ - -

DOM Events and Javascript

- -

Basic event handling

- -

The syntax for working with events looks like the code below.

- - -Event.observe(element, name, observer, [useCapture]); - - -

Assuming for a moment that we want to observe when a link was clicked, -we could do the following:

- - -// <a id="clicker" href="http://foo.com">Click me</a> -Event.observe('clicker', 'click', function(event) -{ - alert('clicked!'); -}); - - -

If we wanted to get the element that fired the event, we'd do this:

- - -Event.observe('clicker', 'click', function(event) -{ - alert(Event.element(event)); -}); - - -

Observing keystrokes

- -

If we wanted to observe keystrokes for the entire document, we could do the following:

- - -Event.observe(document, 'keypress', function(event) -{ - if(Event.keyCode(event) == Event.KEY_TAB) - alert('Tab Pressed'); -}); - - -

And lets say we wanted to keep track of what has been typed :

- - -Event.observe('search', 'keypress', function(event) -{ - Element.update('search-results', $F(Event.element(event))); -}); - - -

Prototype defines properties inside the event object for some -of the more common keys, so feel free to dig around in Prototype to -see which ones those are.

- -

A final note on keypress events; If you'd like to detect a -left click you can use Event.isLeftClick(event).

- -

Getting the coordinates of the mouse pointer

- -

Drag and drop, dynamic element resizing, games, and -much more all require the ability to track the X and Y location of -the mouse. Prototype makes this fairly simple. The code below tracks -the X and Y position of the mouse and spits out those values into -an input box named mouse.

- - -Event.observe(document, 'mousemove', function(event) -{ - $('mouse').value = "X: " + Event.pointerX(event) + - "px Y: " + Event.pointerY(event) + "px"; -}); - - -

If we wanted to observe the mouse location when it was -hovering over a certain element, we'd just change the document argument to -the id or element that was relevant.

- -

Stopping Propagation

- -

Event.stop(event) will stop the propagation of an event .

- -

Events, Binding, and Objects

- -

Everything has been fairly straight forward so far, but things -start getting a little trickier when you need to work with events in -and object-oriented environment. You have to deal with binding and funky -looking syntax that might take a moment to get your head around.

- -

Lets look at some code so you can get a better understanding of what I'm talking about.

- -EventDispenser = Class.create(); -EventDispenser.prototype = -{ - initialize: function(list) - { - this.list = list; - - // Observe clicks on our list items - $$(this.list + " li").each(function(item) - { - Event.observe(item, 'click', this.showTagName.bindEvent(this)); - }.bind(this)); - - // Observe when a key on the keyboard is pressed. - // In the observer, we check for - // the tab key and alert a message if it is pressed. - Event.observe(document, 'keypress', this.onKeyPress.bindEvent(this)); - - // Observe our fake live search box. When a user types - // something into the box, the observer will take that - // value(-1) and update our search-results div with it. - Event.observe('search', 'keypress', this.onSearch.bindEvent(this)); - - Event.observe(document, 'mousemove', this.onMouseMove.bindEvent(this)); - }, - - // Arbitrary functions to respond to events - showTagName: function(event) - { - alert(Event.element(event).tagName); - }, - - onKeyPress: function(event) - { - var code = event.keyCode; - if(code == Event.KEY_TAB) - alert('Tab key was pressed'); - }, - - onSearch: function(event) - { - Element.update('search-results', $F(Event.element(event))); - }, - - onMouseMove: function(event) - { - $('mouse').value = "X: " + Event.pointerX(event) + - "px Y: " + Event.pointerY(event) + "px"; - } -} - -

Whoa! What's going on here? Well, we've defined our a -custom class EventDispenser. We're going to be using this class -to setup events for our document. Most of this code is a -rewrite of the code we looked at earlier except this time, we -are working from inside an object.

- -

Looking at the initialize method, we can really see how -things are different now. Take a look at the code below:

- -// Observe clicks on our list items -$$(this.list + " li").each(function(item) -{ - Event.observe(item, 'click', this.showTagName.bindEvent(this)); -}.bind(this)); - - -

We've got iterators, binding and all sorts of stuff going on. -Lets break down what this chunk of code is doing.

- -

First we are hunting for a collection of elements based on -it's CSS selector. This uses the Prototype selector function $$(). -After we've found the list items we are dealing with we send -those into an each iteration where we will add our observers.

- - -Event.observe(item, 'click', this.showTagName.bindEvent(this)); - - -

Now looking at the code above, you'll notice the bindEvent function. -This takes the method before it showTagName and treats it as the -method that will be triggered when, in this case, -someone clicks one of our list items.

- -

You'll also notice we pass this as an argument to the bindEvent function. -This simply allows us to reference the object in context EventDispenser -inside our function showTagName(event). If the showTagName function -requires additional parameters, you can attach them to the later parameters of bindEvent. For example

- -this.showTagName.bindEvent(this, param1, param2); - -//where the showTagName function is defined as -showTime : function (event, param1, param2) { ... } - - -

Moving on, you'll see bind(this) attached to our iterator function. -This really has nothing to do with events, it is only here to allow me to -use this inside the iterator. If we did not use bind(this), I could not -reference the method showTagName inside the iterator.

- -

Ok, so we'll move on to looking at our methods that actually get -called when an event occurs. Since we've been dealing with showTagName, lets look at it.

- - -showTagName: function(event) -{ - alert(Event.element(event).tagName); -} - - -

As you can see, this function accepts one argument--the event. -In order for us to get the element which fired the event we need to -pass that argument to Event.element. Now we can manipulate it at will.

- -

This covers the most confusing parts of our code. The text above is also -relevant to the remaining parts of our code. If there is anything about -this you don't understand, feel free to ask questions in the forum.

- -

Removing Event Listeners

- -

This one threw me for a loop the first time I tried to use it. -I tried something similar to what I did in the Event.observe -call with the exception of using stopObserving, but nothing seemed -to change. In other words, the code below does NOT work.

- - -$$(this.list + " li").each(function(item) -{ - Event.stopObserving(item, 'click', this.showTagName); -}.bind(this)); - - -

What's the deal here? The reason this does not work is because there -is no pointer to the observer. This means that when we passed this.showTagName -in the Event.observe method before hand, we passed it as an -anonymous function. We can't reference an anonymous function -because it simply does not have a pointer.

- -

So how do we get the job done? All we need to do is give the -observing function a pointer, or the jargon free version: Set a variable -that points to this.showTagName. Ok, lets change our code a bit.

- - -this.showTagObserver = this.showTagName.bindEvent(this); - -// Observe clicks on our list items -$$(this.list + " li").each(function(item) -{ - Event.observe(item, 'click', this.showTagObserver); -}.bind(this)); - - -

Now we can remove the event listeners from our list like this:

- -$$(this.list + " li").each(function(item) -{ - Event.stopObserving(item, 'click', this.showTagObserver); -}.bind(this)); - - - diff --git a/demos/quickstart/protected/pages/Advanced/id/Scripts1.page b/demos/quickstart/protected/pages/Advanced/id/Scripts1.page deleted file mode 100755 index 51535de1..00000000 --- a/demos/quickstart/protected/pages/Advanced/id/Scripts1.page +++ /dev/null @@ -1,86 +0,0 @@ - - -

Catatan Pengembang untuk prototype.js

-Bimbingan ini didasarkan pada -Catatan Pengembang untuk prototype.js oleh Sergio Pereira. - -

Apa itu?

-

-Dalam hal Anda tidak pernah menggunakannya, prototype.js adalah librari - JavaScript yang ditulis oleh Sam Stephenson. - Pemikiran yang hebat ini dan kode sesuai-standar yang ditulis dengan baik mengambil banyak beban terkait dengan pembuatan halaman web sangat interaktif dan kaya yang mengkarakterkan Web 2.0 di belakang Anda. -

- -

- Jika Anda baru saja mencoba menggunakan librari ini, Anda mungkin mencatat bahwa dokumentasi bukanlah salah satu titik yang terkuat. Seperti banyak pengembang lain sebelum saya, saya mempelajari prototype.js dengan membaca kode sumber dan melakukan percobaan denganya. Saya pikir akan baik jika mengambil catatan selama saya mempelajari dan berbagi dengan orang lain. -

-

- Setelah Anda membaca contoh dan referensi, para pengembang yang terbiasa dengan bahasa pemrograman Ruby akan mencatat kesamaan maksud antara kelas built-in Ruby dan banyak ekstensi diimplementasikan oleh librari ini. -

- - -

Menggunakan fungsi $()

-

- Fungsi $() adalah jalan pintas yang siap digunakan untuk fungsi yang semua-terlalu-sering document.getElementById() terhadap DOM. Seperti fungsi DOM, fungsi ini mengembalikan elemen yang id-nya dikirimkan sebagai sebuah argumen. -

- -

- Tidak seperti fungsi DOM, bagaimanapun juga, yang satu ini melampauinya. Anda dapat mengirimkan lebih dari satu id dan - $() akan mengembalikan obyek Array dengan semua elemen yang diminta. Contoh di bawah seharunya menggambarkan ini. -

- -<com:TClientScript UsingClientScripts="prado" /> -
-

This is a paragraph

-
- -
-

This is another paragraph

-
- - - - - - -

- Hal baik lainnya dari fungsi ini adalah bahwa Anda bisa mengirimkan baik string id ataupun elemen obyek itu sendiri, yang menjadikan fungsi ini sangat berguna ketika membuat fungsi lain yang juga mengambil bentuk argumen. -

- -

Menggunakan fungsi $F()

- -

- Fungsi $F() adalah jalan pintas penyambutan lainnya. Ia mengembalikan nilai dari setiap kontrol input field, seperti kotak teks atau daftar drop-down. Fungsi bisa diambil sebagai argumen baik elemen id ataupun elemen obyek itu sendiri. -

- - - - - - - - diff --git a/demos/quickstart/protected/pages/Advanced/id/Scripts2.page b/demos/quickstart/protected/pages/Advanced/id/Scripts2.page deleted file mode 100755 index 80277628..00000000 --- a/demos/quickstart/protected/pages/Advanced/id/Scripts2.page +++ /dev/null @@ -1,214 +0,0 @@ - -

Event DOM dan Javascript

- -

Penanganan event dasar

- -

Sintaks untuk bekerja dengan event terlihat seperti kode di bawah.

- - -Event.observe(element, name, observer, [useCapture]); - - -

Menganggap untuk saat ini kita ingin mengamati sebuah link yang diklik, kita dapat melakukan yang berikut:

- - -// <a id="clicker" href="http://foo.com">Click me</a> -Event.observe('clicker', 'click', function(event) -{ - alert('clicked!'); -}); - - -

Jika kita menginginkan untuk mendapatkan elemen yang memicu event, kita melakukan ini:

- - -Event.observe('clicker', 'click', function(event) -{ - alert(Event.element(event)); -}); - - -

Mengamati tekanan tombol

- -

Jika kita ingin mengamati tekanan tombol untuk seluruh dokumen, kita dapat melakukan yang berikut:

- - -Event.observe(document, 'keypress', function(event) -{ - if(Event.keyCode(event) == Event.KEY_TAB) - alert('Tab Pressed'); -}); - - -

Dan katakanlah kita ingin melacak apa yang telak diketikan:

- - -Event.observe('search', 'keypress', function(event) -{ - Element.update('search-results', $F(Event.element(event))); -}); - - -

Prototipe mendefinisikan properti di dalam obyek event untuk beberapa dari tombol yang lebih umum, maka jangan ragu-ragu untuk mencari di sekitar Prototype guna melihat yang mana saja itu.

- -

Catatan terakhir pada event tekanan tombol; Jika Anda ingin mendeteksi klik kiri, Anda bisa menggunakan Event.isLeftClick(event).

- -

Mendapatkan koordinat dari penunjuk mouse

- -

Tarik dan jatuhkan, pengukuran ulang elemen dinamis, permainan, dan lebih banyak lagi, semuanya memerlukan kemampuan untuk melacak lokasi X dan Y dari mouse. Prototipe menjadikan hal ini cukup sederhana. Kode di bawah melacak posisi X dan Y dari mouse dan memindahkan nilainya ke dalam kotak input bernama mouse.

- - -Event.observe(document, 'mousemove', function(event) -{ - $('mouse').value = "X: " + Event.pointerX(event) + - "px Y: " + Event.pointerY(event) + "px"; -}); - - -

Jika kita ingin mengamati lokasi mouse saat ia melewati elemen tertentu, cukup ubah argumen dokumen ke id atau elemen yang relevan.

- -

Menghentikan Propagasi

- -

Event.stop(event) akan menghentikan propagasi sebuah event .

- -

Event, Penyatuan, dan Obyek

- -

Sejauh ini semuanya sudah jelas, tapi sesuatu mulai menjadi sedikit lebih rumit ketika Anda perlu bekerja dengan event dalam lingkungan obyek-terorientasi. Anda harus berhadapan dengan penyatuan dan sintaks yang terlihat aneh yang memerlukan beberapa waktu bagi Anda untuk mengetahuinya.

- -

Mari kita lihat pada beberapa kode agar Anda bisa mendapatkan pengertian yang lebih baik atas apa yang sedang saya bicarakan.

- -EventDispenser = Class.create(); -EventDispenser.prototype = -{ - initialize: function(list) - { - this.list = list; - - // Amati klik pada item list kita - $$(this.list + " li").each(function(item) - { - Event.observe(item, 'click', this.showTagName.bindEvent(this)); - }.bind(this)); - - // Amati saat tombol pada keyboard ditekan. - // Dalam pengamat, kita memeriksa - // tombol tab dan memunculkan pesan jika ditekan. - Event.observe(document, 'keypress', this.onKeyPress.bindEvent(this)); - - // Amati kotak pencarian kita yang palsu. Ketika pengguna mengetik - // sesuatu ke dalam kotak, pengamat akan mengambil nilai (-1) itu - // dan memutakhirkan hasil pencarian div dengannya. - Event.observe('search', 'keypress', this.onSearch.bindEvent(this)); - - Event.observe(document, 'mousemove', this.onMouseMove.bindEvent(this)); - }, - - // Fungsi bebas untuk merespon event - showTagName: function(event) - { - alert(Event.element(event).tagName); - }, - - onKeyPress: function(event) - { - var code = event.keyCode; - if(code == Event.KEY_TAB) - alert('Tab key was pressed'); - }, - - onSearch: function(event) - { - Element.update('search-results', $F(Event.element(event))); - }, - - onMouseMove: function(event) - { - $('mouse').value = "X: " + Event.pointerX(event) + - "px Y: " + Event.pointerY(event) + "px"; - } -} - -

Wah! Apa yang terjadi di sini? Kita telah mendefinisikan kelas kustom kita EventDispenser. Kita akan menggunakan kelas ini untuk menyiapkan event untuk dokumenkita. Banyak dari kode ini ditulis ulang yang kita lihat di awal kecuali kali ini, kita bekerja dari dalam sebuah obyek.

- -

Melihat metode initialize, sebenarnya kita dapat melihat bagaimana sesuatu menjadi berbeda sekarang. Lihat kode di bawah ini:

- -// Observe clicks on our list items -$$(this.list + " li").each(function(item) -{ - Event.observe(item, 'click', this.showTagName.bindEvent(this)); -}.bind(this)); - - -

Kita mendapatkan iterator, penyatuan dan semua hal lainnya. Mari kita rinci apa yang dikerjakan kode ini.

- -

Pertama kita memburu koleksi elemen berdasarkan selektor CSS. Ini menggunakan fungsi selektor Prototipe $$(). -Setelah kita menemukan daftar item kita berhadapan dengan apa yang kita kirim ke dalam setiap iterasi di mana kita akan menambahkan pengamat kita.

- - -Event.observe(item, 'click', this.showTagName.bindEvent(this)); - - -

Sekarang, melihat kode di atas, Anda akan mencatat fungsi bindEvent. Ini mengambil metode sebelumnya showTagName dan memperlakukannya sebagai metode yang akan dipicu ketika seseorang mengklik salah satu dari item daftar kita.

- -

Anda juga akan mencatat bahwa kita mengirimkan ini sebagai argumen ke fungsi bindEvent. -Ini membolehkan kita untuk mereferensi obyek dalam konteks EventDispenser -di dalam fungsi showTagName(event) kita. Jika fungsi showTagName memerlukan parameter tambahan, Anda melampirkannya ke parameter terakhir dari bindEvent. Sebagai contoh

- -this.showTagName.bindEvent(this, param1, param2); - -//di mana fungsi showTagName didefinisikan seperti -showTime : function (event, param1, param2) { ... } - - -

Selanjutnya, Anda akan melihat bind(this) yang dilampirkan ke fungsi iterator. -Ini sama sekali tidak berkaitan dengan event, ia berada di sini untuk membolehkan saya menggunakan this di dalam iterator. Jika kita tidak menggunakan bind(this), saya tidak bisa mereferensi metode showTagName di dalam iterator.

- -

Ok, kita berlanjut untuk melihat metode kita yang sebenarnya dipanggil saat terjadi event. Karena kita sudah berhadapan dengan showTagName, mari kita lihat itu.

- - -showTagName: function(event) -{ - alert(Event.element(event).tagName); -} - - -

Seperti yang Anda lihat, fungsi ini menerima satu argumen--event. -Agar kita mendapatkan elemen yang memicu event kita perlu mengirimkan argumen ke Event.element. Sekarang kita dapat memanipulasinya kapan saja.

- -

Ini mencakup bagian yang paling membingungkan dari kode kita. Teks di atas juga relevan untuk bagian sisa dari kode kita. Jika ada sesuatu mengenai ini yang tidak Anda mengerti, jangan ragu-ragu untuk mengajukan pertanyaan dalam forum.

- -

Menghapus Pendengar Event

- -

Yang satu ini melontarkan saya dari lingkaran untuk pertama kali saya mencoba menggunakannya. -Saya mencoba sesuatu yang mirip dengan apa yang saya lakukan dalam pemanggilan Event.observe dengan kekecualian penggunaan stopObserving, tapi tidak ada yang berubah. Dengan kata lain, kode di bawah ini TIDAK bekerja.

- - -$$(this.list + " li").each(function(item) -{ - Event.stopObserving(item, 'click', this.showTagName); -}.bind(this)); - - -

Apa yang terjadi di sini? Alasan ini tidak bekerja karena tidak ada penunjuk ke pengamat. Ini berarti bahwa ketika kita mengirimkan this.showTagName dalam metode Event.observe sebelumnya, kita mengirimkannya sebagai fungsi anonim. Kita tidak bisa mereferensi fungsi anonim karena ia tidak mempunyai penunjuk.

- -

Lalu bagaimana kita yakin pekerjaan diselesaikan? Semua yang kita perlukan adalah memberikan fungsi mengamati penunjuk, atau kelompok versi bebas: Setel variabel yang mengarah ke this.showTagName. Ok, mari kita ubah kode kita sedikit.

- - -this.showTagObserver = this.showTagName.bindEvent(this); - -// Amati klik pada item list kita -$$(this.list + " li").each(function(item) -{ - Event.observe(item, 'click', this.showTagObserver); -}.bind(this)); - - -

Sekarang kita bisa menghapus pendengar event dari daftar kita seperti ini:

- -$$(this.list + " li").each(function(item) -{ - Event.stopObserving(item, 'click', this.showTagObserver); -}.bind(this)); - - - diff --git a/demos/quickstart/protected/pages/Controls/HtmlArea4.page b/demos/quickstart/protected/pages/Controls/HtmlArea4.page index 1fa33424..17c87e18 100755 --- a/demos/quickstart/protected/pages/Controls/HtmlArea4.page +++ b/demos/quickstart/protected/pages/Controls/HtmlArea4.page @@ -1,6 +1,6 @@ -

THtmlArea4

+

THtmlArea4

diff --git a/demos/quickstart/protected/pages/Controls/Markdown.page b/demos/quickstart/protected/pages/Controls/Markdown.page index d7cc00c6..0285ed32 100644 --- a/demos/quickstart/protected/pages/Controls/Markdown.page +++ b/demos/quickstart/protected/pages/Controls/Markdown.page @@ -1,6 +1,6 @@ -

TMarkdown

+

TMarkdown

diff --git a/demos/quickstart/protected/pages/Database/ViewsArUpdate.page b/demos/quickstart/protected/pages/Database/ViewsArUpdate.page index 5dd084c4..2df1d3d7 100644 --- a/demos/quickstart/protected/pages/Database/ViewsArUpdate.page +++ b/demos/quickstart/protected/pages/Database/ViewsArUpdate.page @@ -1,6 +1,6 @@

Views - AR Classes Update

- +

Usually when you use Active Records Classes to interact with your Data Base you also build some proper views to handle them. To save every element of your views in your Data Base @@ -9,9 +9,9 @@ Thats why Prado offers an automatic mechanism to update your views from your AR Classes and vice versa.

-

Updating views from AR Classes

+

Updating views from AR Classes

-

Instead of assign each attribute in your AR Class to your view controls like this:

+

Instead of assign each attribute in your AR Class to your view controls like this:

$student = AR_Student::finder()->findByPk(1); $this->name->Text = $student->name; @@ -20,7 +20,7 @@ $this->gender->Text = $student->gender; $this->average->Text = $student->average; -

You can do the same as follows:

+

You can do the same as follows:

$student = AR_Student::finder()->findByPk(1); @@ -28,8 +28,8 @@ $this->tryToUpdateView($student); -

Updating AR Classes from views

-

Instead of assign each attribute in your views to your AR Classes like this:

+

Updating AR Classes from views

+

Instead of assign each attribute in your views to your AR Classes like this:

$student = new AR_Student(); $student->name = $this->name->Text; @@ -39,7 +39,7 @@ $student->average = $this->average->Text; $student->save(); -

You can do the same as follows:

+

You can do the same as follows:

$student = new AR_Student(); diff --git a/demos/quickstart/protected/pages/Fundamentals/Pages.page b/demos/quickstart/protected/pages/Fundamentals/Pages.page index 58f4f06d..3e03a24c 100755 --- a/demos/quickstart/protected/pages/Fundamentals/Pages.page +++ b/demos/quickstart/protected/pages/Fundamentals/Pages.page @@ -15,7 +15,7 @@ A form submission is called postback if the submission is made to the pag TPage has a IsPostBack property exposing whether the current request being handled is the first request for this page or the consequence of a postback.

-

CallBack

+

CallBack

A callback is a special form submission that, instead of requiring a full page reload on the browser, gets executed in the background through an ajax call. So, a callback is considered a postback too, but not vice versa.
diff --git a/demos/quickstart/protected/pages/GettingStarted/CommandLine.page b/demos/quickstart/protected/pages/GettingStarted/CommandLine.page index 3619d3d9..9e919212 100644 --- a/demos/quickstart/protected/pages/GettingStarted/CommandLine.page +++ b/demos/quickstart/protected/pages/GettingStarted/CommandLine.page @@ -110,22 +110,22 @@ PostRecord#1

-

Creating Active Record Classes

-

+

Creating Active Record Classes

+

In the blog demo project, we need to create two Active Record classes, UserRecord and PostRecord, to represent data records in the users and posts tables, respectively. Active Record classes must extend from the base class ActiveRecord, and must define property names that matches with the field names of the corresponding table.

-

+

To better organize our directories, we create a new directory protected/database to hold the class files. We also modify our application configuration by inserting the following lines. It is equivalent to adding the directory protected/database to PHP include_path, which allows us to use the classes without explicitly including them.

- + -

+

At the prompt, enter the following two commands to create UserRecord and PostRecord classes:

@@ -135,7 +135,7 @@ At the prompt, enter the following two commands to create UserRecord an >> generate posts Application.database.PostRecord -

+

Here we used the namespace format again to specify the classes to be created. The path Application.database.UserRecord indicates that we want the UserRecord class file to be protected/database/UserRecord.php.

diff --git a/demos/quickstart/protected/pages/GettingStarted/Installation.page b/demos/quickstart/protected/pages/GettingStarted/Installation.page index 956f53c2..f59eed70 100755 --- a/demos/quickstart/protected/pages/GettingStarted/Installation.page +++ b/demos/quickstart/protected/pages/GettingStarted/Installation.page @@ -13,7 +13,7 @@ The minimum requirement by PRADO is that the Web server support PHP 5.3.3. PRADO PRADO can be installed as a standalone package or using composer

-

Standalone package

+

Standalone package

  1. Go to pradosoft.com to grab the latest version of PRADO.
  2. Unpack the PRADO release file to a Web-accessible directory. @@ -28,7 +28,7 @@ If you encounter any problems with the demo applications, please use the PRADO r

    -

    Composer install

    +

    Composer install

    1. If you don't have installed composer already, install it globally: diff --git a/demos/quickstart/protected/pages/GettingStarted/Upgrading32.page b/demos/quickstart/protected/pages/GettingStarted/Upgrading32.page index e2378ed5..7e630488 100644 --- a/demos/quickstart/protected/pages/GettingStarted/Upgrading32.page +++ b/demos/quickstart/protected/pages/GettingStarted/Upgrading32.page @@ -1,6 +1,6 @@ -

      Upgrading from v3.2

      +

      Upgrading from v3.2

      @@ -17,7 +17,7 @@ We summarize in the following the most significant changes in v3.3 to help devel

      -

      Basic Prototype to jQuery javascript porting

      +

      Basic Prototype to jQuery javascript porting

      The number one rule on writing jQuery javascript code is to read the jQuery documentation. Porting code from Prototype to jQuery needs some effort: here's a basic lookup table to port existing code:

      @@ -168,7 +168,7 @@ The number one rule on writing jQuery javascript code is to read the PRADO specific code changes

      PRADO Porting prado to jQuery some method signatures has changed, or have been adapted: @@ -207,7 +207,7 @@ Porting prado to jQuery some method signatures has changed, or have been adapted -

      Specific controls changes

      +

      Specific controls changes

      Some Prado controls were based on specific extensions of the Prototype + Scriptaculous javascript framework, and they have been deprecated now that jQuery has become the primary js framework in PRADO. PRADO 3.3 introduces jQuery-based counterpart for these controls and encourage everyone to port their code to the new controls, but the old controls are still supposed to work with some minor annoyance: diff --git a/demos/quickstart/protected/pages/GettingStarted/Wsat.page b/demos/quickstart/protected/pages/GettingStarted/Wsat.page index 3d07e6f2..a76ca163 100644 --- a/demos/quickstart/protected/pages/GettingStarted/Wsat.page +++ b/demos/quickstart/protected/pages/GettingStarted/Wsat.page @@ -1,5 +1,5 @@ -

      Web Site Administration Tool

      +

      Web Site Administration Tool

      Web Site Administration Tool (WSAT) is a development tool which allows you to perform several tedious tasks of a PRADO project in a GUI fashion. Its inspired in both Asp.Net - Web Site Administration Tool and Yii's Gii. @@ -12,12 +12,12 @@

      -

      Requirements

      +

      Requirements

      To use WSAT, you need to add in your project configuration file: application.xml, in the services section the wsat service like follows: - + ... @@ -25,7 +25,7 @@

      -

      Usage

      +

      Usage

      Then you are ready to go to: http://localhost/yoursite/index.php?wsat=TWsatLogin and doing so you should see the following page: @@ -36,7 +36,7 @@ is part of a basic security system to avoid undesirable persons to use this tool.

      -

      Active Record classes generation

      +

      Active Record classes generation

      In order to generate AR classes you need to go to: http://localhost/divermania/index.php?wsat=TWsatGenerateAR by clicking the proper links in the welcome page. Then you should see the following page: diff --git a/demos/quickstart/protected/pages/JuiControls/Home.page b/demos/quickstart/protected/pages/JuiControls/Home.page index 7c0c065f..f997e573 100644 --- a/demos/quickstart/protected/pages/JuiControls/Home.page +++ b/demos/quickstart/protected/pages/JuiControls/Home.page @@ -1,9 +1,9 @@ -

      Jui Controls (jQuery UI)

      +

      Jui Controls (jQuery UI)

      Jui controls are the PRADO port of the standard jQuery UI widgets. They can be used as standard Active Controls, but will automatically load the needed jQuery-UI javascript libraries.

      -

      Options

      +

      Options

      The Options property of PRADO Jui controls is used to pass options to the underlying javascript object. Each subproperty set on Options will be translated to a javascript property added to the object. The complete list of options available for each widget is availble at jQuery-UI's API Documentation.

      @@ -24,7 +24,7 @@ jQuery-UI's Resizable adds an handl />       -

      Events

      +

      Events

      jQuery-UI widgets offers a lot of events that PRADO can hook up and trasmit to the serverside using a callback request. Event available for PRADO Jui controls inherits their names from their jQuery-UI counterparts, prefixed with "On". Jui controls doesn't make use of the AutoPostback property anymore, but only triggers a callback when an event handler is associated to the corresponding event. @@ -42,7 +42,7 @@ jQuery's Draggable allows a target /> -

      PRADO Jui interactions controls

      +

      PRADO Jui interactions controls

      Jui interactions adds basic mouse-based interactions to elements like moving, resizing or sorting. PRADO Jui interactions controls applies there interactions to a TActivePanel For informations of the specific options of each interaction, follow jQuery-UI Interaction API Documentation for the specific interaction. @@ -74,7 +74,7 @@ For informations of the specific options of each interaction, follow jQuery-UI I

      2. -

      PRADO Jui widgets controls

      +

      PRADO Jui widgets controls

      • TJuiProgressbar diff --git a/demos/quickstart/protected/pages/JuiControls/Interactions.page b/demos/quickstart/protected/pages/JuiControls/Interactions.page index 2b48da68..b2be141f 100644 --- a/demos/quickstart/protected/pages/JuiControls/Interactions.page +++ b/demos/quickstart/protected/pages/JuiControls/Interactions.page @@ -1,12 +1,12 @@ -

        Jui interactions controls

        +

        Jui interactions controls

        Jui interactions adds basic mouse-based interactions to elements like moving, resizing or sorting. PRADO Jui interactions controls applies these interactions to a TActivePanel For informations of the specific options of each interaction, follow jQuery-UI Interaction API Documentation for the specific interaction.

        -

        TJuiDraggable

        +

        TJuiDraggable

        - jQuery UI API

        @@ -22,7 +22,7 @@ The panel can be moved using the mouse, and eventually dropped over a -

        TJuiDroppable

        +

        TJuiDroppable

        - jQuery UI API

        @@ -37,7 +37,7 @@ When a TJuiDraggable
        -

        TJuiResizable

        +

        TJuiResizable

        - jQuery UI API

        TJuiResizable is an extension to TActivePanel based on jQuery-UI's Resizable interaction. @@ -52,7 +52,7 @@ A small handle is shown on the bottom right corner of the panel, that permits th -

        TJuiSelectable

        +

        TJuiSelectable

        - jQuery UI API

        TJuiSelectable is an extension to TActivePanel based on jQuery-UI's Selectable interaction. @@ -67,7 +67,7 @@ A small handle is shown on the bottom right corner of the panel, that permits th -

        TJuiSortable

        +

        TJuiSortable

        - jQuery UI API

        TJuiSortable is an extension to TActivePanel based on jQuery-UI's Sortable interaction. diff --git a/demos/quickstart/protected/pages/JuiControls/Widgets.page b/demos/quickstart/protected/pages/JuiControls/Widgets.page index 63c6aa32..5bf8b083 100644 --- a/demos/quickstart/protected/pages/JuiControls/Widgets.page +++ b/demos/quickstart/protected/pages/JuiControls/Widgets.page @@ -1,5 +1,5 @@ -

        Jui widgets controls

        +

        Jui widgets controls

        Jui widgets are complex controls built on the foundations of jQuery effects and jQueryUI interactions. PRADO Jui widgets controls can be divided in two groups: @@ -11,7 +11,7 @@ For informations of the specific options of each widget, follow jQuery-UI Widget

        -

        TJuiProgressbar

        +

        TJuiProgressbar

        -         jQuery UI API

        @@ -26,7 +26,7 @@ The panel takes the aspect of a progressbar ranging from a value of 0 to the val
        -

        TJuiAutoComplete

        +

        TJuiAutoComplete

        -         jQuery UI API

        @@ -50,7 +50,7 @@ When a suggestion is selected the OnSuggestionSelected event is raised, -

        TJuiDialog

        +

        TJuiDialog

        -         jQuery UI API

        @@ -72,7 +72,7 @@ The buttons may contain a callback that will be fired when they are clicked. -

        TJuiDatePicker

        +

        TJuiDatePicker

        -         jQuery UI API

        -- cgit v1.2.3