Differences

This shows you the differences between two versions of the page.

Link to this comparison view

project:faq [2012/07/16 12:34]
mwittemann
project:faq [2015/04/17 13:57] (current)
ecker [Community]
Line 18: Line 18:
 ==== Who is behind this project? ==== ==== Who is behind this project? ====
  
-qooxdoo was initiated and is maintained by [[:project:developers#initiator_and_maintainer|1&1]], the worldbiggest web hosting company. There is a team of full-time [[:project:developers#core_developers|core developers]] as well as many committers and contributors.+qooxdoo was initiated and is maintained by [[:project:developers#initiator_and_maintainer|1&1]], one of the world'leading web hosts. There is a team of full-time [[:project:developers#core_developers|core developers]] as well as many committers and contributors.
  
 ==== Will it stay Open Source? ==== ==== Will it stay Open Source? ====
  
-Yes. Always has, always will. It is a true Open Source project: standard licensing, contributor-friendly, public code repositories, public bug tracking and roadmap planning.+Yes. Always has, always will. It is a true Open Source project: standard OSS licensing, public code repositories, public bug tracking, contributor-friendly.
  
  
Line 31: Line 31:
 ==== Is it enterprise-ready? ==== ==== Is it enterprise-ready? ====
  
-Yes. Its solid programming model and tooling allows for creating large-scale applications. To get an idea, see [[:community:real_life_examples#gmx_webmaillarge-scale_qooxdoo_app|GMX.com]] or other user-contributed [[:community:real_life_examples|examples]].+Yes. Its solid programming model and tooling allows for creating large-scale applications. To get an idea, see some user-contributed [[:community:real_life_examples|examples]] (even if that's only the tip of an iceberg).
  
  
Line 37: Line 37:
 ==== Where do I get support? ==== ==== Where do I get support? ====
  
-Use the general [[:community#mailing_lists]]. Many active users as well as the full-time core [[:project:developers|developers]] try to answer all your questions. There is no commercial support currently available, but there are several companies listening to the mailing list to offer qooxdoo-related contracting.+Use the general [[:community#mailing_lists|mailing list]]. Many active users as well as the core [[:project:developers|developers]] try to answer all your questions. There is no commercial support currently available, but there are several companies listening to the mailing list to offer qooxdoo-related contracting.
  
 ==== Is there a qooxdoo book? ==== ==== Is there a qooxdoo book? ====
  
-While several books contain sections on qooxdoo or references to it, you cannot buy a printed book just about qooxdoo. Use the [[http://manual.qooxdoo.org/current/|qooxdoo manual]] instead with its approx. 400 pages. It's available for free: as an online HTML version and a PDF to download.+While several books contain sections on qooxdoo or references to it, there is only one printed book which is specifically about qooxdoo. Unfortunately it's now outdated because it was written towards qooxdoo v1.4, at a time when only (what we call now) qx.Desktop existed: //qooxdoo - Develop Rich Internet Applications (RIA) with qooxdoo//. Therefore we recommend the [[http://manual.qooxdoo.org/current/|qooxdoo manual]] instead with its approx. 400 pages. It's maintained by the core team and available for free: as an online HTML version and a PDF to download.
  
 ===== Technical ===== ===== Technical =====
Line 47: Line 47:
 ==== Which browsers are supported? ==== ==== Which browsers are supported? ====
  
-A qooxdoo application runs in [[:docs:1.1:requirements#client|all major web browsers]] with identical look & feel.+A qooxdoo application runs in [[http://manual.qooxdoo.org/current/|all major web browsers]]. For a typical qx.Desktop application that means: with identical look & feel.
  
 ====  Does it come with a server? ==== ====  Does it come with a server? ====
  
-No. If you already have an existing backend that serves HTTP (or HTTPS) requests, it's probably fine to continue using it. //Optionally// qooxdoo offers several [[:docs:1.1:RPC|RPC servers]] for an elegant client-server communication. BTW, during development of your client application the local file system often is sufficient, without the need to use a real server. +No. If you already have an existing backend that serves HTTP (or HTTPS) requests, it's probably fine to continue using it. //Optionally// qooxdoo offers several [[http://manual.qooxdoo.org/current/pages/communication/rpc_server_writer_guide.html|RPC servers]] for an elegant client-server communication. BTW, during development of your client application the local file system often is sufficient, without the need to use a real server.
  
 ==== What languages and technologies do I need to know? ==== ==== What languages and technologies do I need to know? ====
  
-Not many. qooxdoo features regular object-oriented GUI programming without requiring knowledge of low-level web technologies. No HTML, no CSS, no DOM. Just JavaScript. Even non-JavaScript programmers get easily familiar with qooxdoo's OO capabilities and its tool chain.+Not many. qooxdoo features regular object-oriented GUI programming without requiring knowledge of low-level web technologies. Even non-JavaScript programmers get easily familiar with qooxdoo's OO capabilities and its tool chain. 
 + 
 +But it also depends on the app domain you choose: for higher-level qx.Desktop apps it typically is: No HTML, no CSS, no DOM. Just JavaScript. For lower-level apps such as qx.Mobile and particularly qx.Website it is also about directly leveraging HTML, CSS and the DOM. 
  
  
Line 63: Line 65:
 ==== Isn't it just another JavaScript library? ==== ==== Isn't it just another JavaScript library? ====
  
-No. It's also not just a "library", but a "framework". It is much more comprehensive than a typical JS library like jQuery or Prototype. qooxdoo's main focus is on creating full-featured rich internet applications (RIAs), so it comes with a large set of high-quality widgets and features a powerful, platform-independent tool chain. But due to some recent advancements it is now also possible to leverage qooxdoo as a [[:docs:1.1#low_level_framework|low-level library]] for extending traditional HTML documents.+No. Well, it depends ...   
 + 
 +For creating qx.Desktop or qx.Mobile apps it is much more comprehensive than a typical JS library like jQuery. It's also not just a "library", but a "framework"it comes with a large set of high-quality widgets and features a powerful, platform-independent tool chain.  
 + 
 +For creating rather DOM-oriented qx.Website solutions, though, it is also possible to leverage qooxdoo as a [[:docs:1.1#low_level_framework|low-level library]].
  
 ==== I'm familiar with jQuery. How does it compare? ==== ==== I'm familiar with jQuery. How does it compare? ====
Line 74: Line 80:
 ==== Are visual GUI builders available? ==== ==== Are visual GUI builders available? ====
  
-Only to some extent. There is no official GUI builder that comes with the framework. But there are some community-driven attempts to create such GUI builders. These contributions may have different objectives and may only work with legacy qooxdoo code, so YMMV. If you're interested, have a look at some of the following implementations: [[http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/TartanBlueprint/|Tartan Blueprint]] or [[http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/qooxit/|qooxit]] for some fairly recent attempts. [[http://jsQt.org|jsQt]] for a Qt Designer based solution. Older attempts include [[:contrib:project#weida|Weida]] (browser-based, contributed), [[http://qxtransformer.org/a/qxtransformer.org/qxtransformer/pqc|PyQooxCard]] (part of the [[http://qxtransformer.org|QxTransformer]] project) or [[https://sourceforge.net/projects/qxrad/|GUI RAD for qooxdoo]]. A commercial solution is [[http://www.codegear.com/products/delphi/php|Delphi for PHP]] from Borland/CodeGear (frontend largely qooxdoo-based). qooxdoo's built-in [[http://manual.qooxdoo.org/current/pages/application/inspector.html|Inspector]] is a sophisticated debugging tool rather than a GUI builder, but it might help nonetheless as it allows to manipulate a running qooxdoo user interface.+There is no official GUI builder that comes with the framework. But there are some community-driven attempts to create such GUI builders. 
 +<html><!--These contributions may have different objectives and may only work with legacy qooxdoo code, so YMMV. If you're interested, have a look at some of the following implementations: [[http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/TartanBlueprint/|Tartan Blueprint]] or [[http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/qooxit/|qooxit]] for some fairly recent attempts. [[http://jsQt.org|jsQt]] for a Qt Designer based solution. Older attempts include [[:contrib:project#weida|Weida]] (browser-based, contributed), [[http://qxtransformer.org/a/qxtransformer.org/qxtransformer/pqc|PyQooxCard]] (part of the [[http://qxtransformer.org|QxTransformer]] project) or [[https://sourceforge.net/projects/qxrad/|GUI RAD for qooxdoo]]. A commercial solution is [[http://www.codegear.com/products/delphi/php|Delphi for PHP]] from Borland/CodeGear (frontend largely qooxdoo-based). qooxdoo's built-in [[http://manual.qooxdoo.org/current/pages/application/inspector.html|Inspector]] is a sophisticated debugging tool rather than a GUI builder, but it might help nonetheless as it allows to manipulate a running qooxdoo user interface.--></html>
  
  
  
  
 +<html><!--
 ==== Any alternatives to the JavaScript-based programming model? ==== ==== Any alternatives to the JavaScript-based programming model? ====
  
 Yes, several. Java-oriented are [[http://tomsondev.bestsolution.at/2009/12/17/qxwt-1-0-0-0-released/|QxWT]], which provides a qooxdoo wrapper for GWT, or the [[http://eclipse.org/rap|Eclipse Rich Ajax Platform]] (RAP). An XML-based UI description is featured by [[http://qxtransformer.org|QxTransformer]]. A visual RAD solution is [[http://www.codegear.com/products/delphi/php|Delphi for PHP]]. See some  Yes, several. Java-oriented are [[http://tomsondev.bestsolution.at/2009/12/17/qxwt-1-0-0-0-released/|QxWT]], which provides a qooxdoo wrapper for GWT, or the [[http://eclipse.org/rap|Eclipse Rich Ajax Platform]] (RAP). An XML-based UI description is featured by [[http://qxtransformer.org|QxTransformer]]. A visual RAD solution is [[http://www.codegear.com/products/delphi/php|Delphi for PHP]]. See some 
 [[:docs:general:development_platforms|more solutions]]. [[:docs:general:development_platforms|more solutions]].
 +--></html>
 ===== Community ===== ===== Community =====
  
-==== How do I correct/change/extend the homepage? ==== +Please get involved and participateCheck out **[[:community:contribution]]**!
- +
-The homepage is a Wiki, that allows you to easily modify its content. You are welcome to contribute. See [[:documentation#wiki_informations|here]] for more information. +
- +
-==== Where to look for and file bug reports? ==== +
- +
-Use [[http://bugzilla.qooxdoo.org|bugzilla]].  +
- +
-==== Are you interested in contributing? ==== +
- +
-Absolutely. You are invited to become a fellow developer and contributor to the project. There is an infrastructure for [[:contrib|contributions]], which allows for easily setting up, developing, releasing a project and for collaborating on it. +
- +
-==== Other sources of information? ==== +
- +
-Wanna [[:community#meeting_people|meet people]]? Wanna [[:community#social_networks|connect to people]] via social networks? Presentation [[:community#presentations|slides]] are also available. Subscribe to [[:community#feeds|feeds]]. Enjoy some [[:community#reallife_examples|real-life examples]] from other qooxdoo users. Become a member of the [[:community]]!+