Provide loader logic for browser variant builds (BZ#2290)

[qx-bug-importer]

Thomas Herchenroeder (@thron7) wrote:

Currently, when browser-specific builds are created, there is no functionality available to pick the right one for a particular client.

This functionality only requires a coars engine detection and should be added, either in the form of a specialized index.html with embedded Javascript, or a separate loader script. In either way, the correct variant script would then be loaded.

assigned to Thomas Herchenroeder (@thron7)

[qx-bug-importer]

Andreas Ecker (@ecker) wrote:

Yes, it is really a pity that that we lack promoting such (often unparalleled?) features to the typical users. There simply seem to be too many powerful features available but a bit buried in either framework or tool chain.

Well, so much for a Friday evening framework blues. Sorry 'bout that. ;-) Anyway, let's try to address one cool qooxdoo feature after the other.

On a more technical side note, browser detection and switching is often rather done on a webserver level ((e.g. Apache, typically based on the user agent string). This allows for a client-specific content delivery without first detecting clients in the browser. The server-side option of browser switching should be addressed by proper documentation in the wiki by the time client-side detection is in place (i.e. this bug is resolved).

[qx-bug-importer]

Sebastian Werner (@swernerx) wrote:

There is also a lot more missing. Really interesting is the GWT video regarding "Deferred Binding". Their loading mechnism really sounds great as it offer support for different variant sets, output platforms, languages in one system and also cares about build times and this way also fix cache-related issues:

http://www.youtube.com/watch?v=nvti32k4xyU

[qx-bug-importer]

Sebastian Werner (@swernerx) wrote:

The best way IMHO is to have some kind of redirection HTML file which is generated by the build system.

In my current survey to support different kind of platforms it is also required to have different HTML files for the various platforms. This means that some kind of single-HTML file which just loads the correct JS file is not enough.

[qx-bug-importer]

Andreas Ecker (@ecker) wrote:

Alex, could you start with a simple includer script, maybe just adding that to the wiki? A more advanced solution may not be targeted very soon, so you may want to get yourself unassigned afterwards.

[qx-bug-importer]

Alexander Steitz (@asteitz) wrote:

Not in the time frame of the 0.8.3 release. Moving on to 0.9

[qx-bug-importer]

Sebastian Werner (@swernerx) wrote:

It might be too specific to limit this to variants. I am currently more thinking of a mutation/set selector which combines different other aspects of a build as well e.g. languages, variants, settings, application class, themes, etc. Maybe it's better to solve this the big way.

[qx-bug-importer]

Andreas Ecker (@ecker) wrote:

mass renaming of 0.9 target to 1.0 (for issues with status "NEW")

[qx-bug-importer]

Alexander Steitz (@asteitz) wrote:

Moving on to target 1.0.1

[qx-bug-importer]

Alexander Steitz (@asteitz) wrote:

accepting

[qx-bug-importer]

Alexander Steitz (@asteitz) wrote:

I've just committed a basic startup script as starting point to the qooxdoo-contrib repository under Bugs/2290.

== Open issues == The startup script assumes that the generator fills out the JS file to load. This has to be done by the generator since the filenames of the different browser variants are free choosable.

Passing this bug to Thomas for tool chain support.

[qx-bug-importer]

Andreas Ecker (@ecker) wrote:

moved to target 1.0.2

[qx-bug-importer]

Thomas Herchenroeder (@thron7) wrote:

This has been solved with the Feature Configuration Editor (bug#4985). The corresponding manual section [1] gives an example how to achieve something like this bug's intent in a custom index.html. But with the shift to feature detection, it seems almost impossible to solve this in a generic way, ie. provide a full feature detection in the loader, and then choose a built script the matches the found feature set, or matches it as closely as possible.

[1] http://manual.qooxdoo.org/1.5.x/pages/application/featureconfigeditor.html#loading-a-specific-variant