• Shortcuts : 'n' next unread feed - 'p' previous unread feed • Styles : 1 2

» Publishers, Monetize your RSS feeds with FeedShow:  More infos  (Show/Hide Ads)


Date: Friday, 11 Apr 2014 15:04

Welcome. For a list of tasks accomplished during the last working week, use this bugzilla query.

Have a great weekend.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 04 Apr 2014 14:36

Welcome to a weekly status update.

Progress in pointer Branch

We’ve made good progress in the pointer branch and are very excited about the result. If you are curious, now it’s time for you to get started! Thanks in advance for your support.

Check out the pointer branch and build your app with it. If you have any error, make sure to read the preliminary release notes for qooxdoo 4.0, which holds more information on what API changed. Don’t worry about the long list of API changes. Only a few changes are to the public API (in the list the terms in bold). Your app would be affected if it uses this public API; you would have to adjust the terms in your code.

The majority of changes is to protected API, i.e. it could only affect you if you derived from framework classes (e.g. for creating custom widgets). Usually the renaming is straightforward, e.g. “Mouse” into “Pointer”, or “Click” into “Tap”. Of course, the qooxdoo migration job is going to list all (possible) names in your code that should be renamed.

Anyway, your existing and future qooxdoo apps will benefit from the input-device independence. The event API should also be quite consistent in terms of naming, so it’d be some pleasure to work with. Take the chance to get your feedback included before we merge the branch into master. The earlier the better, particularly well ahead before we ship the next release. Depending on your feedback and our own ongoing testing, we plan to merge the branch into master within a week’s span.

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

Have a nice weekend.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 28 Mar 2014 14:24

Work continued with a strong focus on Pointer Events, which we blogged about recently for status and details. It is going to provide excellent event support independent of the input device. Great foundation for your universal, multi-platform qooxdoo apps.

For a complete list of tasks accomplished during the last two working weeks, use this bugzilla query.

C U.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Thursday, 20 Mar 2014 15:03

During recent weeks, pointer events have been the dominating topic in the framework team, as we already teasered in the weekly blog post some weeks ago. With this post, we want to give you a deeper insight into this topic.

The Challenge

qooxdoo features three GUI toolkits: desktop, mobile and website. Connected to these domains are the main input devices: mouse for desktop / website and touch for mobile. In detail, this means that desktop / website widgets register mouse event listeners and mobile widgets register touch event listeners. So using one type of app with another input device is at best not optimal. For that reason, we already added emulation layers for mouse on touch devices and touch on PCs. But transforming one event model to another is error prone and simply doesn’t feel natural. Another way to get the optimal user experience would be to listen to both types of event for each widget, but making that change takes a lot of effort without providing an ideal solution.

Pointer to the rescue

Luckily, some clever guys at Microsoft already recognized this issue and came up with a W3C spec named Pointer Events, which tackles this problem. The main idea of this spec is to offer a unified event, independent of the input device. In an ideal world, we would simply use these events and everyone would be happy. But every web developer knows that we don’t live in an ideal world and we have to support browsers that don’t implement the spec. In fact, it’s only IE10+ which already has support for native pointer events.

Pointer Spec in a nutshell

In a nutshell, the spec is based on mouse events and maps all input devices to pointer events. It extends the mouse event type with additional information like the id of the pointer for multi pointer devices. So as a developer familiar with mouse events, you will feel comfortable with pointer events as well because most of the events are equal at first sight, like pointerdown, pointermove or pointerover. For more details, take a look at the spec.

What we already did

Having pointer events in mind, the task was clear: offer pointer events for our GUI toolkits. That means adding event handlers for the website and desktop / mobile layer, bringing these events to the widgets and changing every widget so it listens to pointer events instead of mouse / touch events. After that, change every app we ship with the SDK to use pointer events as well. If we slow down a bit and take a step back, the most important things to consider here are the event layers which fire the pointer events. So here is a listing of the newly added pointer events:

  • pointerover
  • pointerout
  • pointermove
  • pointerdown
  • pointerup
  • pointercancel

If you have the spec in mind, you will see that this list does not contain all events it mentions. But these are the most important events we need for widgets so we kept the list as small as possible. This is one of the reasons we don’t like to call this implementation a polyfill, even if in most areas it’s well-aligned with the spec and is quite broad in scope.
All the events mentioned above have one thing in common: They are atomic. The click event for example is not atomic because it is generated by a sequence of other events. But click is also closely connected to the mouse so to achieve our goal, we needed something input device independent here as well.

Gestures on top

But click is not the only combined event we know. Think of tap, swipe, or rotate in the mobile world. So we introduced another set of new events which can be grouped as gestures:

  • tap
  • longtap
  • swipe
  • rotate
  • pinch
  • track

All these events should work with either mouse or touch. Of course, for rotate and pinch, you need more than one pointer, which is not possible using a mouse.

What’s still missing

There are still some challenges left for us to tackle. One obvious thing is scrolling as there is no mouse wheel or scroll bar on mobile devices. Most of the algorithms relying on hover events are to be refactored e.g. Drag & Drop, quick selection for lists and tooltips. Last but not least, we need to add some manual pages explaining why, how and when to use use these events.

Give it a try

While we continue to complete this event layer, we would like to invite you to take a look at the changes so far. Check out our demo apps we built based on the pointer branch and let us know what you think.

Author: "Martin Wittemann" Tags: "Development, Feature Highlight, Mobile, ..."
Comments Send by mail Print  Save  Delicious 
Date: Monday, 17 Mar 2014 10:07

As we have been working on larger topics recently, such as input device independence via pointer events or embracing JS tooling via GruntJS, there hasn’t been much feedback in the form of weekly blog posts. We’ll get back to you with more details once we are to feature the upcoming milestones and achievements.

In the meantime, here’s a list of tasks accomplished during the last two working weeks, straight from bugzilla, with many others currently in progress. C U.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 28 Feb 2014 16:30

Welcome to the weekly status update.

Bugzilla cleanup

As most of you know, the qooxdoo project has quite a long history, and so has its bugzilla and many of the issues in it. As we have been moving to a more agile development process we have set out for exciting advancements this year. Thus we plan to better handle and clean up the existing bugzilla issues. We want to have and provide a clear view on what’s important and be even more transparent to you what will probably be fixed and what most likely not.

In a first step we are going to move those open issues to RESOLVED – LATER, whose last comment is older than a year. BTW, we plan on doing such maintenance steps periodically. There will be other steps to handle the large number of issues (including many that are rather outdated or unlikely enhancements). We just wanted to inform you about upcoming bug updates. If we move or modify a bug of yours during this process, and you’re still interested in it, feel free to comment or reopen. Just give us feedback why you still think this is important. Thanks for your support.

HtmlArea now a contrib

We accomplished bug #7918 this week, which was about moving the HtmlArea components into a separate repository and adding it to the regular contrib catalog. If you happen to use the framework from its Git master and you use the HtmlArea, make sure you update your code to include component as the contrib.

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

Bye.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 21 Feb 2014 15:01

We’ve been busy working on various issues, some of them mentioned in the last weekly status updates. For or a complete list of tasks accomplished during the recent working week, use this bugzilla query.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 14 Feb 2014 15:50

Welcome to a weekly wrap-up of dev activities.

Pointing out Pointers

We started one of the next big advancements of the framework: Introduction of input device independent events. In the end qooxdoo apps – be it desktop, mobile or website – are supposed to work fine independent of the actual input device (mouse, finger, etc.).

We’ve added a meta bug with some dependent bugs, which hold some more details on that topic and its implementation process. All the development will be done in a feature branch named “pointer”. Before we merge the feature over to master, we will let you know.

Mobile Improvements

Check out the recent blog post on Mobile: Back navigation, Console. It contains some handy new features when creating mobile apps.

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

Bye.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 14 Feb 2014 15:49

Here are some improvements for mobile apps.

Back navigation in Routing

We enhanced qx.application.Routing by adding a back() method.

It navigates the application to the last known path(s), including all hash states. The logic inside the back() method detects route cycles and removes them automatically from routing history.

Example: Lets say you navigate from one page to another (denoted as >> below). If you then call back() it will take you back to the previous page in the original page flow, not just to the previous page of the chronological page history:

Page A >> Page B >> Page C >> Page B >> routing.back() >> Page A

This is the typical behavior users expect from an actual mobile app. Of course, you can still implement whatever page flow and history support you need. But the new feature is a huge help when creating a working page flow in your mobile apps. For a real life example that already includes the new back navigation feature, have a look at the qx.Mobile Showcase source code.

Console in Mobile Apps

Debugging on mobile devices may be difficult, because you don’t have access to a regular JavaScript console. Therefore, one often had to use remote debugging tools like WeInRe or Adobe Shadow.

Now the mobile framework contains a built-in console. Originally it was meant to provide a console for legacy browsers (you might recall pressing “F7″ in qx.Desktop apps). This built-in, basic console is now also available on mobile devices. For writing messages to it, please use qx.log.Logger.

If you trigger a longtap event on the navigation bar, the qx.log.appender.Console will appear on screen. Check this feature out, at the Mobile Showcase.

Stay tuned for more advancements in developing mobile apps for all kind of devices.

Author: "Christopher Zündorf" Tags: "Development, Mobile"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 07 Feb 2014 16:36

Welcome to the weekly status update.

Forms Updated

We updated the form component and its included validation for qx.Desktop. The invalid messages are usually shown in tooltips. As soon as the form gets validated and is detected as invalid, the first invalid tooltip will be shown to signal the user something is wrong. Take a look at a form demo to see the new behavior.

IE8: Regression in mouse events

We recently found a regression that affects the 3.0.2 and 3.5 releases: In Internet Explorer 8, the methods qx.event.type.Mouse.getDocumentLeft and getDocumentTop will return NaN, which unfortunately breaks the custom scroll bars in qx.Desktop. If your applications are affected you may want to switch to the branch_3_5_x branch of the Git repository or apply a patch from the commit that contains the fix.

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

Bye.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 31 Jan 2014 13:52

Welcome to another weekly status update. Lots of practical improvements have been made recently.

Improved Touch Events for IE 10+

The class qx.module.event.TouchHandler was enhanced to calculate the rotation out of MSPointerEvents. This means the method getRotation() of qx.event.type.Touch now returns the polyfilled rotation angle. This makes it possible to rotate objects even on MSPointerEvent-based browsers (IE10, IE on Windows Phone 8).

You can try the rotation feature with Internet Explorer 10+ or Windows Phone 8 inside the qx.Mobile Showcase.

qx.Mobile Forms with new scroll-to-input logic

The scroll-to-input logic of a qx.Mobile Form was normalized and improved for all platforms. The logic was different for each supported platform or did not even work reliably (e.g. Android). The new qooxdoo-driven logic scrolls the surrounding scroll container to the focused input element, thus keeping it in view as long as the virtual keyboard is active.

Along with this feature we added a new SCSS theming variable to change the focused border color: $input-active-border-color

If you work on the latest snapshots, please add this variable to your _styles.scss and define a suitable value.

Try this feature at the qx.Mobile Showcase.

Progress on qx.Website

We continue to keep a focus on qx.Website and improved the API of the Traversing module. We extended all static methods e.g. getDocument or isWindow to also allow a selector or collection as argument to check.

Updated Editor

Some of you might have already noticed the misplaced cursor in the editor of the Playground or Tutorial apps. A recent update of the external code editor ACE fixed that issue.

Dynamic form

The qooxdoo form and its renderer has been extended to be more dynamic. This means we added the possibility to remove items from a form and added an event to notify any subscriber of such changes. This event is used in all renderers we offer to update the views already rendered, which makes it possible to update the form after rendering. Take a look at two simple demos, a qx.Desktop demo, the other a qx.Mobile demo. Both use the same form class and benefit from those enhancements.

Custom decorator mixins

With the qooxdoo 3.0 release, we changed the way decorators work. Since that, we often heard the question how to write custom decorator mixins. Thus we extended the manual with a demo to make that clear. Hope that info is helpful.

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

Have a nice weekend.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 24 Jan 2014 20:37

Welcome to the weekly status update.

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

qooxdoo 3.5 Presentation

We host an in-house presentation here at 1&1 for each new qooxdoo release. This time our colleagues got to know about major features of qooxdoo 3.5. We figured the slides might be interesting to you as well, so we put them online:

qooxdoo 3.5 by Martin Wittemann




Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 17 Jan 2014 16:55

Welcome back to the first weekly status update in 2014. Hope you also had a great holiday season. And Happy New Year to all of you!

The core team members returned from vacation recently, so we’re back now to continue to work on your favorite JS framework. 2013 has seen some great achievements, and we’re eager to make 2014 another exciting year for qooxdoo. We’re looking forward to your ongoing support, your input and engagement. Lets make it a fantastic year for the framework and web technologies in general – in all of qooxdoo’s application domains Website, Mobile, Desktop and Server, as well as its Tooling.

Bugfixes

Since the last report end of last year, quite a number of tasks could already be accomplished. For a complete list since Dec 20, 2013, use this bugzilla query.

Enriched touch events by deltaX and deltaY

We improved the touchmove event, by calculating the delta values in relation to the touch position on touchstart. If you call getDelta() on qx.event.type.Touch you receive a native array with all active touches, providing their distance and their movement axis, x/y respectively:

{axis: "x", identifier: 1, x: -34, y: 0}

That’s it for now. C U again next week.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 20 Dec 2013 13:10

Welcome to the weekly status update.

Updated BusyIndicator Spinner

We updated the qx.Mobile Busy Indicator for being resolution independent. Instead of using an image, we now display a CSS-based graphic for indicating the progress. The spinner is also customizable through our theming system:

$spinner-border-thickness: rem(3);
$spinner-border-color: white;
$spinner-size: rem(14);

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

As this will be the last status update for this year, we wish you a nice weekend and a Happy New Year!

Author: "Martin Wittemann" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 13 Dec 2013 16:35

Welcome to the weekly status update.

qooxdoo 3.5 released

As you have certainly seen, the framework shipped with many improvements and exciting new features. Check out the new release, get familiar with the new features, sent us your feedback, and let other users or potential new users know about the things you like most. Thanks.

Workaround for pySCSS compiler

We recognized a potential problem in qx.Mobile 3.5 within the generated qx.Mobile themes Indigo and Flat. The generated CSS has a leading SCSS import statement, which might cause some issues within your mobile application.

In some cases (e.g. if you use @font-face), it might be possible that this statement will not be ignored by the browser. The browser tries to import a non-existing mixins.css and throws a 404 error.

If you discover that problem in your app, choose one out of the three following solutions:

  1. Switch to branch 3_5_x or master. We removed the unnecessary import statement there already.
  2. Remove the first line @import "../../../scss/mixins"; in the file qooxdoo/framework/source/resource/qx/mobile/scss/common/_mixins.scss of your qx.Mobile project.
  3. Use the original Ruby-based SASS compiler, and integrate it as the manual suggests modifying the watch-scss job inside your app-specific config.json.

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

Have a nice weekend.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Tuesday, 10 Dec 2013 14:50

 

We are happy to announce a new release of the framework, qooxdoo 3.5.

Many thanks go to the entire community for making this happen: the team of core developers, 1&1 as the supporting company, all contributors and users who brought in their suggestions and improvements.

qooxdoo 3.5

qooxdoo 3.5 is another landmark in the framework’s ongoing evolution of being a universal JavaScript framework. The current release introduces such highlights as a lightweight widget set for websites and it embraces an ever-growing ecosystem for JavaScript tooling.

 

qx.Website

The website-oriented part of qooxdoo had already become an enterprise-grade solution for developers to enhance their websites with dynamic functionality. One frequent request was the need for “low-level widgets”.

So we added a qx.Website Widgets library that provides a set of lightweight UI components ready to be integrated into any web project. These widgets use the same collection API paradigm as qx.Website itself, so they can be be initialized and customized in just a few lines of code. Each widget can also be configured using HTML data attributes so that a website’s UI can be defined entirely in (server-generated) HTML and initialized with only a single line of JavaScript.

For the initial release, the library contains the following components: Button, Calendar, Rating, Slider, Tabs, Accordion. More will be added in the coming months – let us know which UI components you would find useful.

Please note that the Widgets module is considered experimental, i.e. the API can still change. We expect it to be finalized for the next major release, your input is appreciated.

The addition of new qx.Website modules necessitated a redesign of the qx.Website API Viewer‘s navigation.

Modules are arranged in groups and a filter box can be used to narrow down the list of methods. Thanks to the responsive UI, the API Viewer works well on phones and tablets, too.

 

qx.Mobile

When specifically targeting smartphones or tablets, qooxdoo’s mobile GUI toolkit continues to be the perfect choice. Many improvements went into the qooxdoo 3.5 release that emphasize its capabilities to let you create elaborate mobile apps.

One of the most challenging features in a multi-device world is proper application scaling. qx.Mobile now enables you to easily adjust the scale of your qx.Mobile app (or even let your users do so), simply by changing the root font size.

This is made possible by the built-in themes that are now fully resolution-independent. In technical terms this means that relative units are being used throughout the themes instead of absolute pixel units. No matter how small or large your font settings are, the mobile widgets will scale accordingly.

qx.Mobile is built upon CSS-based themes, backed by the popular SCSS precompiling technology. We took the chance to consolidate and improve the themes provided by the framework. For instance, we expose many widget style variables to the main SCSS file of a theme. Modifying colors or using linear gradients becomes trivial. It is now even easier to create your very own custom theme.

So-called “flat” designs became popular on mobile operating systems recently. In leveraging the new capabilities for custom themes, we created and shipped a new “Flat” theme.

Support for Windows Phone 8 and Internet Explorer 11 has been enhanced. The modern IEs 10 and 11 now take advantage of native scrolling, providing a much smoother user experience. Multi-touch handling was also added for those browsers, based on pointer events. Target those emerging device classes (hybrid devices, convertibles, etc.) with your qx.Mobile app.

Besides fixes and improvements throughout qx.Mobile many existing widgets were enhanced. To pick just one example, the mobile Carousel can now host a large number of pages due to its pagination overflow handling.

 

Tooling

We introduced experimental Grunt support. Grunt.js is a popular task runner based on Node.js. The features of the qooxdoo toolchain nicely blend with Grunt. We’ve begun to leverage Grunt’s ecosystem of plugins and combine the best of Grunt with the best of the qooxdoo Generator.

For newly created qooxdoo apps all Generator jobs are now also available through a Grunt frontend. For instance, instead of writing generate.py source you can now use grunt source, too.

In order to use it in your existing app take a look at the Gruntify existing apps section in the manual. Grunt offers a huge number of Grunt Plugins waiting to be utilized. Go ahead and read our Grunt manual page to find out about the possibilities and what we are aiming for.

 

Check it out!

qooxdoo 3.5 is available for download. Check out the detailed release notes and the manual. Watch the code repository on GitHub.

The qooxdoo 3.5 release comes with many substantial improvements and exciting new features. In fact about 190 bugfixes and enhancements made it into the release.

Thanks

Many thanks from the core developers to the community of contributors and users. Please help to spread the news, get people excited about the latest releases, and show them how to deploy qooxdoo as a truly universal JavaScript framework.

Enjoy! :-)

 

Author: "Andreas Ecker" Tags: "Announcements, Release"
Comments Send by mail Print  Save  Delicious 
Date: Tuesday, 10 Dec 2013 14:34

A new maintenance release of the framework is available.

qooxdoo 3.0.2 includes about 60 bugfixes over the previous qooxdoo 3.0.1 release.

As a patch release qooxdoo 3.0.2 is fully backwards-compatible to the previous versions. Nothing needs to be changed in your existing apps if they are based on either qooxdoo 3.0 or 3.0.1. When upgrading from an older version you can migrate directly to 3.0.2.

Download qooxdoo 3.0.2, checkout the detailed release notes and the manual.

Many thanks from the core developers to the community, particularly for reporting issues and your help in improving the framework.


Author: "Andreas Ecker" Tags: "Announcements, Release"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 06 Dec 2013 16:12

We are in the rampdown for the …

Upcoming Releases

They are planned to ship next week. It is about a maintenance release qooxdoo 3.0.2. And a larger release that introduces areas that were not part of qooxdoo 3.0: for instance, a lightweight widget set for qx.Website and a qooxdoo toolchain to embrace Grunt.js.

While those new features will see further improvement and are not meant for production yet (but certainly for your feedback!), this significant landmark of the framework will go by the name qooxdoo 3.5.

We appreciate any of your support while working towards the new releases, particularly reporting issues of your apps built against the framework master or of the latest online devel demos. Thanks!

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

Stay tuned.

Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Friday, 29 Nov 2013 15:51

Welcome to a weekly status update.

Website Widgets

A couple of days ago we blogged about Introducing qx.Website Widgets. These are to complement the existing qx.Website component, a fully-featured DOM library, allowing developers to enrich websites with dynamic features. The “low-level widgets” are easy to integrate with just a few lines of code but also fully customizable for any site design. This great new feature set will ship as experimental with the upcoming qooxdoo release.

Release Rampdown

For the upcoming joint release of qooxdoo 3.1 and 3.0.2 we’ve settled the code freeze and rampdown phase to December, 04 – 09 2013. This means during this time we will thoroughly test the software and only core members should make pushes to the Github repo.

We appreciate any of your support while working towards the new releases, particularly reporting issues of your apps (built against the framework master) or the online devel demos.

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

Bye.


Author: "Andreas Ecker" Tags: "Activity Reports"
Comments Send by mail Print  Save  Delicious 
Date: Wednesday, 27 Nov 2013 16:15

Since its initial release with qooxdoo 2.0, the qx.Website component has steadily grown and matured into a fully-featured DOM library, allowing developers to enrich websites with dynamic features. One frequent request we’ve heard from projects using qx.Website is the need for “low-level widgets”, meaning prefab UI components that are easy to integrate with just a few lines of code but also fully customizable so they can be adapted to any site design.

That’s why the upcoming qooxdoo release will ship with a new qx.Website module: q-ui.js, a.k.a. “qx.Website Widgets”, a library of UI elements including components such as Calendar, Slider and Accordion.

Key features of the qx.Website Widgets library include:

  • Uses the same well-known programming paradigms as qx.Website and other DOM manipulation libraries:  Widgets are wrapped in Array-like collections (inheriting from qxWeb so all qx.Website Core methods are supported). Widget methods generally return the collection to support call chaining.
  • Easy customization using CSS and mustache.js templates
  • Widgets can be created either entirely in JavaScript or be configured using HTML data attributes, e.g. for HTML generated on the server.

Demos

The new Website Widget Browser application contains demos for all currently available widgets, while the recently made-over qx.Website API Viewer provides all the information you need to integrate them into your website projects.

Give them a try, and let us know what you think via the usual channels – blog comment, mailing list, Facebook or Twitter. Just keep in mind this new feature is still considered experimental – the API can and probably will change, possibly taking into account your input.

Next steps

In the weeks and months following the December release, we plan to stabilize the qx.Website Widgets API, add new widgets and improve support for legacy browsers. From a framework perspective, our goal will be to leverage qx.Website as a foundation for the higher-level UI toolkits (qx.Desktop and qx.Mobile), consolidating and unifying the technology stack where appropriate. This will make it even easier for you to create universal apps for any or all domains of Website, Mobile and Desktop.

 

Author: "Daniel Wagner" Tags: "Development, Technical"
Comments Send by mail Print  Save  Delicious 
Next page
» You can also retrieve older items : Read
» © All content and copyrights belong to their respective authors.«
» © FeedShow - Online RSS Feeds Reader