Merge branch 'master' of https://github.com/unify/qooxdoo

Author: mcdit

.gitignore

@@ -10,6 +10,7 @@ qooxdoo/component/inspector/source/script
 qooxdoo/component/inspector/build
 qooxdoo/component/inspector/test
 qooxdoo/component/inspector/api
+qooxdoo/component/apiviewer/source/script
 qooxdoo/documentation/manual/build
 qooxdoo/application/feedreader/inspector
 qooxdoo/application/demobrowser/build

qooxdoo/application/demobrowser/source/class/demobrowser/demo/virtual/ListWithFilter.js

@@ -0,0 +1,135 @@
+/* ************************************************************************
+
+   qooxdoo - the new era of web development
+
+   http://qooxdoo.org
+
+   Copyright:
+     2004-2009 1&1 Internet AG, Germany, http://www.1und1.de
+
+   License:
+     LGPL: http://www.gnu.org/licenses/lgpl.html
+     EPL: http://www.eclipse.org/org/documents/epl-v10.php
+     See the LICENSE file in the project's top-level directory for details.
+
+   Authors:
+     * Martin Wittemann (martinwittemann)
+     * Christian Hagendorn (chris_schmidt)
+
+************************************************************************ */
+
+/**
+ * @tag filter
+ */
+qx.Class.define("demobrowser.demo.virtual.ListWithFilter",
+{
+  extend : qx.application.Standalone,
+
+  members :
+  {
+    main: function()
+    {
+      this.base(arguments);
+
+      // create the data
+      var rawData = [];
+      for (var i = 0; i < 8; i++) {
+        rawData.push(i);
+      }
+      var data = new qx.data.Array(rawData);
+
+      // create the widget
+      var list = new qx.ui.list.List(data);
+
+      // add the widgets to the document
+      this.getRoot().add(list, {left: 10, top: 80});
+
+      // create the delegates for the filter
+      var delegateOdd = {};
+      delegateOdd.filter = function(data) {
+        return parseInt(data) % 2 == 1;
+      };
+      var delegateEven = {};
+      delegateEven.filter = function(data) {
+        return parseInt(data) % 2 == 0;
+      };
+
+      var filterNameLabel = new qx.ui.basic.Label("init");
+      this.getRoot().add(filterNameLabel, {left: 10, top: 290});
+      var options = {
+        converter: function(data) {
+          if (data == delegateEven) {
+            return "Show only even numbers."
+          } else if (data == delegateOdd) {
+            return "Show only odd numbers."
+          }
+          return "Show all numbers."
+        }
+      };
+      list.bind("delegate", filterNameLabel, "value", options);
+
+
+      /* ***********************************************
+       * Controlls: Do only work on the data array
+       * ********************************************* */
+      var addItemButton = new qx.ui.form.Button("Add an item");
+      addItemButton.setWidth(120);
+      this.getRoot().add(addItemButton, {left: 130, top: 80});
+      addItemButton.addListener("execute", function() {
+        data.push(data.length);
+      }, this);
+
+      var removeItemButton = new qx.ui.form.Button("Remove an item");
+      removeItemButton.setWidth(120);
+      this.getRoot().add(removeItemButton, {left: 130, top: 115});
+      removeItemButton.addListener("execute", function() {
+        data.pop();
+      }, this);
+
+      var logDataButton = new qx.ui.form.Button("Write data to log");
+      logDataButton.setWidth(120);
+      this.getRoot().add(logDataButton, {left: 130, top: 150});
+      logDataButton.addListener("execute", function() {
+        // open the console
+        qx.log.appender.Console.show();
+        // push the data in the console
+        this.info(data.toString());
+      }, this);
+
+      var changeFilterButton = new qx.ui.form.Button("Odd / Even filter");
+      changeFilterButton.setWidth(120);
+      this.getRoot().add(changeFilterButton, {left: 130, top: 185});
+      changeFilterButton.addListener("execute", function() {
+        list.getDelegate() == delegateOdd ? list.setDelegate(delegateEven) : list.setDelegate(delegateOdd);
+      }, this);
+
+      var removeFilterButton = new qx.ui.form.Button("Remove filter");
+      removeFilterButton.setWidth(120);
+      this.getRoot().add(removeFilterButton, {left: 130, top: 220});
+      removeFilterButton.addListener("execute", function() {
+        list.setDelegate(null);
+      }, this);
+
+      var reverseButton = new qx.ui.form.Button("Reverse order");
+      reverseButton.setWidth(120);
+      this.getRoot().add(reverseButton, {left: 130, top: 255});
+      reverseButton.addListener("execute", function() {
+        data.reverse();
+      }, this);
+
+
+       /* ***********************************************
+        * DESCRIPTIONS
+        * ********************************************* */
+       // List Selection sync description
+       var description = new qx.ui.basic.Label();
+       description.setRich(true);
+       description.setWidth(200);
+       description.setValue(
+         "<b>Filtered List</b><br/>"
+         + "List showing numbered items, bound to a data array."
+       );
+       this.getRoot().add(description, {left: 20, top: 10});
+    }
+  }
+});

qooxdoo/application/demobrowser/source/demo/virtual/ListWithFilter.html

@@ -0,0 +1,10 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+  <script type="text/javascript" src="../helper.js"></script>
+</head>
+<body>
+
+</body>
+</html>

qooxdoo/documentation/manual/source/pages/development/profiling.rst

@@ -3,7 +3,7 @@
 Profiling Applications
 **********************
 
-qooxdoo has build in a cross-browser, pure JavaScript profiler. If the profiler is enabled, each call of a method defined by qooxdoo's class declaration can be measured. The profiler is able to compute both the total own time and the call count of any method.
+qooxdoo has built-in a cross-browser, pure JavaScript profiler. If the profiler is enabled, each call of a method defined by qooxdoo's class declaration can be measured. The profiler is able to compute both the total own time and the call count of any method.
 
 Since the profiler is implemented in pure JavaScript, it is totally cross-browser and works on any supported browser.
 
@@ -12,14 +12,20 @@ Since the profiler is implemented in pure JavaScript, it is totally cross-browse
 How to enable the Profiler
 ==========================
 
-Basically set the variant ``qx.aspects`` to ``on`` and be sure to include the class `qx.dev.Profile <http://api.qooxdoo.org/#qx.dev.Profile>`_. The class should be included before other classes.
+Basically set the variant ``qx.aspects`` to ``on`` and be sure to include the class `qx.dev.Profile <http://api.qooxdoo.org/#qx.dev.Profile>`_. The class should be included before other classes. The easiest way to achieve that is to extend the ``profiling`` helper job in a job that creates your application. For example, to enable profiling in the source version of your app, go to the ``"jobs"`` section of your config.json, and add ::
+
+  "source-script" : {
+    "extend" : [ "profiling" ]
+  }
+
+
 
 .. _pages/profiling#how_to_use_the_profiler:
 
 How to use the Profiler
 =======================
 
-The profiler can be controlled either hard-wired in the application code (like the demo browser does for instance) or interactively using a JavaScript shell like FireBug for Firefox or DebugBar for IE.
+The profiler can be controlled either hard-wired in the application code, or interactively using a JavaScript shell like FireBug for Firefox or DebugBar for IE.
 
 Profiling a certain action:
 

qooxdoo/documentation/manual/source/pages/getting_started.rst

@@ -20,6 +20,7 @@ Tutorials
    tutorials/tutorial-part-3
    tutorials/tutorial-part-4-1
    tutorials/tutorial-part-4-2
+   tutorials/tutorial-part-4-3
 
 .. _index#sdk:
 

qooxdoo/documentation/manual/source/pages/gui_toolkit/window_management.rst

@@ -1,5 +1,5 @@
 Window Management
-============
+=================
 
 Window is a widget used to show dialogs or to realize a MDI (Multiple Document Interface) applications. Windows can only be added to ``qx.ui.window.Desktop`` widgets, or to widgets which implement the ``qx.ui.window.IDesktop`` interface.  
 
@@ -69,5 +69,5 @@ Related documentation
 
 
 Demos and API
------
+-------------
 To find out more, you can check the `desktop demo <http://demo.qooxdoo.org/1.2.x/demobrowser/index.html#widget~Desktop.html>`_ and the `API reference <http://demo.qooxdoo.org/1.2.x/apiviewer/index.html#qx.ui.window>`_. 

qooxdoo/documentation/manual/source/pages/tutorials/tutorial-part-3.rst

@@ -12,22 +12,22 @@ Pre-Evaluation
 
 First, we need to specify what's the data we need to transfer. For that, we need to take a look what tasks our application can handle:
 
-1. Show the friends timeline for a specific user.
+1. Show the public twitter timeline.
 2. Post a tweet.
 
-So it's clear that we need to fetch the friends timeline (that's how it is called by twitter), and we need to post a message to twitter. It's time to take a look at the `twitter API <http://apiwiki.twitter.com/Twitter-API-Documentation>`_ so that we know what we need to do to communicate with the service.
+So it's clear that we need to fetch the public timeline (that's how it is called by twitter), and we need to post a message to twitter. It's time to take a look at the `twitter API <http://apiwiki.twitter.com/Twitter-API-Documentation>`_ so that we know what we need to do to communicate with the service.
 But keep in mind that we are still on a website so we can't just send some ``POST`` or ``GET`` requests due to cross-site scripting restrictions. The one thing we can and should do is take advantage of JSONP. If you have never heard of JSONP, take some time to read the `article on ajaxian <http://ajaxian.com/archives/jsonp-json-with-padding>`_ to get further details.
 
 .. _pages/tutorials/tutorial-part-3#creating_the_data_access_class:
 
 Creating the Data Access Class
 ==============================
 
-Now, that we know how we want to communicate, we can tackle the first task, fetching the friends timeline. twitter offers a `JSONP service for that <http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-friends_timeline>`_ which we can use. Luckily, twitter also takes care of the login process on the server side so we don't need to bother with that in the client. The following URL returns the friends timeline wrapped in a JavaScript method call (that's what JSONP is about):
+Now, that we know how we want to communicate, we can tackle the first task, fetching the public timeline. twitter offers a `JSONP service for that <http://dev.twitter.com/doc/get/statuses/public_timeline>`_ which we can use. Luckily, there is no login process on the server side so we don't need to bother with that in the client. The following URL returns the public timeline wrapped in a JavaScript method call (that's what JSONP is about):
 
 ::
 
-  http://twitter.com/statuses/friends_timeline.json?callback=methodName
+  http://api.twitter.com/1/statuses/public_timeline.json?callback=methodName
 
 Now we know how to get the data from twitter. Its time for us to go back to the qooxdoo code. It is, like in the case of the UI, a good idea to create a separate class for the communication layer. Therefore, we create a class named ``TwitterService``. We don't want to inherit from any advanced qooxdoo class so we extend straight from ``qx.core.Object``. The code for that class should looks like this:
 
@@ -59,7 +59,7 @@ Now it's time to get this method working. But how do we load the data in qooxdoo
 ::
 
   if (this.__store == null) {
-    var url = "http://twitter.com/statuses/friends_timeline.json";
+    var url = "http://api.twitter.com/1/statuses/public_timeline.json";
     this.__store = new qx.data.store.Jsonp(url, null, "callback");
     // more to do
   } else {

qooxdoo/documentation/manual/source/pages/tutorials/tutorial-part-4-1.rst

@@ -3,6 +3,11 @@
 Tutorial Part 4.1: Form Handling
 ********************************
 
+.. note::
+
+    This tutorial is outdated! twitter changed its API and does not allow basic authentication anymore. Still, the qooxdoo part is valid and worth trying even if you can not access you friends timeline anymore.
+
+
 In the previous steps of this tutorial, we :doc:`laid the groundwork <tutorial-part-1>` for a Twitter client application, gave it a :doc:`neat UI <tutorial-part-2>` and implemented a :doc:`communication layer <tutorial-part-3>`. One thing this application still lacks is a nice way for users to input their Twitter user name and password in order to post a status update. Fortunately, qooxdoo comes with a :doc:`forms API </pages/gui_toolkit/ui_form_handling>` that takes the pain out of creating form elements and handling user input.
 
 Before we get started, make sure you're working on the version of the Twitter tutorial application tagged with `"Step 3" in the GitHub repository <http://github.com/wittemann/qooxdoo-tutorial/tree/Step3>`_. This includes the posting part of the communication layer that we'll be using in this tutorial.