Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do you manage the ui-layout of an Ember.js app?
    primarykey
    data
    text
    <p>I am looking for options to manage the ui-layout of an ember application I am currently working on.</p> <p>The application has to be very flexible (configurable) when it comes to the ui-layout - so having layout-containers with regions like "top", "left", "center", "right" and "bottom" which can be nested whould be a good fit (thats how most layout-managers manage layout).</p> <p>I found a few solutions, but am somehow undecided:</p> <ol> <li><p><a href="http://developer.yahoo.com/yui/layout/" rel="noreferrer">yui2-layout-manager</a> (<a href="http://developer.yahoo.com/yui/examples/layout/page_layout_source.html" rel="noreferrer">Demo</a>) Seems a bit old/clunky, successor, yui3-layoutmanager, is in "planning" stage since months (years?)</p></li> <li><p><a href="http://layout.jquery-dev.net/" rel="noreferrer">jquery-ui-layout</a> (<a href="http://layout.jquery-dev.net/demos/complex.html#" rel="noreferrer">Demo</a>) Looks a bit bloated. Codebase is not public: As it seems the project-owner does not want it to be too public(?) (from what i read in the google-group, someone asked why its not on github...)</p></li> <li><p><a href="http://dojotoolkit.org/" rel="noreferrer">dojotoolkit</a> (<a href="http://dojotoolkit.org/documentation/tutorials/1.6/dijit_layout/demo/appLayout.html" rel="noreferrer">Demo</a>) Seems quit a bit "obtrusive" </p></li> </ol> <p>All in all no solution feels "good" to me and I wonder if I should better write the layout-managing-logic myself. What do you think? </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload