Author Archives: builder

Testing Team

Testing Team Meeting – Jun 01 2012

Second QUnit meeting happened on Thursday. The focus was on triaging all existing tickets. In the process we closed a few as invalid, fixed two with actual code changes, and clarified a few other.  Documentation tickets will be handled once the qunitjs.com site is a little further. Once module filtering and their visual display is improved, 1.7.0 is ready for release.

jQuery Mobile Team

jQuery Mobile Team Meeting – May 31 2012

  • Attending: Todd Parker, John Bender, Mat Marquis, Gabriel Schulhof, Jasper de Groot, Anne-Gaelle Colom, Jason Scott

link General Updates

link Todd

link Ghislain Seguin

  • Download builder now outputs structure + theme files based on new meta data
  • Working on decoupling basic components like touch, orientation, throttledresize

link John Bender

  • Grunt work is done

link Gabriel Schulhof

  • Fixed #4423 ( initial page has dialogHashKey ) need to talk about it.
  • Merged custom-select-via-popup - Need to talk about progressive enhancement.
  • Fixed popup screen sizing issues.
  • Issue #4340 ( slow lists ) need to talk with gseguin.

link Jasper de Groot

link Anne-Gaelle Colom

  • Will meet Richard about the new docs in XML format that follows the UI standard

link Jason D Scott

link Open dev questions

Issue #4340 - do we need to blur() all links anymore now that gseguin has added the link tracking? https://github.com/jquery/jquery-mobile/blob/master/js/jquery.mobile.navigation.js#L1267 I’ve tried with that line commented out and the problem from #1840 (which caused the above line to be added) did not re-occur - Improvement: 37.7% on my N900 78.9% on my desktop Chrome 20 29.4% on my desktop Firefox 12

BlackBerry 7.1 Transitions https://github.com/jquery/jquery-mobile/issues/4001 documentation about -webkit-backface-visibility: hidden;

Auto-scroll expandibles - Todd to test https://github.com/jquery/jquery-mobile/pull/3520#issuecomment-5702502

Opera mini bug - text focus https://github.com/jquery/jquery-mobile/issues/4311#issuecomment-5733560

link PhoneGap blinky transitions

Scott's recent fix for blinking in PhoneGap seems to be pretty solid, though I've see a few reports that some issues remain. Since PG is a big deal, we should probably accelerate 1.1.1 for release in the next 2-3 weeks. https://github.com/jquery/jquery-mobile/issues/3768 https://github.com/jquery/jquery-mobile/issues/4024

link Fixed toolbars / updatePagePadding / header and content switched

Many related issues

link Re-enhancement after manipulation

buttonMarkup() and/or controlgroup() https://github.com/jquery/jquery-mobile/issues/4317 https://github.com/jquery/jquery-mobile/issues/3635 Gabriel can have a look at these

link Button/form consistency

https://github.com/jquery/jquery-mobile/issues/4098#issuecomment-5469381 new PR + test page (Jasper) Test box-sizing border-box on WP: jsbin.com/emaziy/ (Todd) do we want form elements in toolbars to default to mini with option to override?

PR #4385 Should we add styles to protect buttons from a: basic styles? https://github.com/jquery/jquery-mobile/issues/3444 Cascade issue bar link colors + reorder pseudo classes TR issue #73 - links in bar not themable, always same as JQM default theme (Tyler Benziger)

buttons wrap on BB5 and IE7, buttons leave a gap on probably all other browsers depending on available width - Jasper

link 2.3 nav issues

The back button doesn’t work in 2.x in some situations. The proposed fix is a revert back to the old timeout based prevention but doesn’t prevent the popstate triggered navigation like the previous version did. https://github.com/jquery/jquery-mobile/issues/3980 https://github.com/jquery/jquery-mobile/compare/1.1-stable...3980-fix?w=1

link 1.1.1 Planning

Open issues: https://github.com/jquery/jquery-mobile/issues?milestone=14&state=open

link 1.2 Features

Issues: https://github.com/jquery/jquery-mobile/issues?milestone=13&page=1&state=open

link Read-only lists

New styling including removal smaller font-size and padding of ui-li-static for 1.2 #4347

link Grid widget?

have the framework adding the ui-block classes (same as navbar widget) data attribute # columns

link start="2">
  • Other
    • <

    • Donation page
    jQuery Core Team

    jQuery Core Team Meeting – May 25 2012

    May 21, 2012
    Minutes (Notes) of the meeting of jQuery
    Location: #jquery-meeting on Freenode
    Attending: DaveMethvin, gibson042, mikesherov, rwaldron, Krinkle, scott_gonzalez
    Time: Noon ET

    Official Agenda:

    Unit test failures

    JHP for serving – land it?

    • Need to coordinate with testswarm – Krinkle?
    • Can’t land until swarm issues are resolved

    Need update to README to reflect current build process

    Manual modularity

    effects – gibson042

    jaubourg can do ajax part?

    Can we deprecate Boolean attrHooks? — probably not

    Compat repo for deprecated/removed stuff?

    • Separate plugins including compressed versions
    • Combined plugin with everything
    • “Debug” version with console.warn msgs?
    • We can host these on code.jquery.com

    Documentation

    • Deprecations – dave created tickets, will finish docs
    • Animation hooks Tween etc. — gnarf can you outline?
    • Other things needing docs?

    Remaining 1.8 items

    FYI: wycats trying to get standards to help our selector impl

    jQuery Mobile Team

    jQuery Mobile Team Meeting – May 24 2012

    link Download builder

    link jQM Modularity

    • I’ve heard a bunch of questions recently about how monolithic the library is. I know we’ve done a lot of decoupling work internally and now have the download builder which will help quite a bit.

    • Modularity questions: how much make we break things up for consumption:

      • Only want utilities like touch events, zoom fix, orientation (not yet?)
      • Want a specific subset of widgets and transitions (yes)
      • Only want certain widgets, no nav model (yes)
      • Only want nav model/transitions, no widgets or CSS framework (yes)

    • I’d like to do some analysis for LOE and see if we should focus on this for 1.3.

    • All modules use $.mobile - requires core

    • Also jQ core dependencies to consider - tree shaking to see how much we use

    • What is core? What is a module?

    link Timing

    1.1.1 rc1 - conference? 1.2.0 alpha/beta - conference?

    Need to discuss this more as we get closer.

    link Test suite

    John Bender - use grunt and now Phantom on swam.jquery.com More stable, consistent, and easy to debug Once we get test swarm running, we’ll be able to test in multiple browsers - that is the next priority for Bender

    link Open dev questions

    Auto-scroll expandibles - Todd to test https://github.com/jquery/jquery-mobile/pull/3520#issuecomment-5702502

    Opera mini bug - text focus https://github.com/jquery/jquery-mobile/issues/4311#issuecomment-5733560

    link Multi-view (tablet) layout Q’s from Sven

    • Quick update:

    I'm sort of done with my new multiview version. Some minor stuff left to do, but I worked out the main obstalces in tapping into JQM navigation and urlHistory to handle all panel transitions. I tested in IE8 and on iPad iOS 3 yesterday, which both worked, so I'm pretty happy with it. I will try to finish up in the next couple of weeks and set up a new multiview demo, too.

    The plugin now only requires 4 changes in JQM. If you have the time and any idea how I could get by without changing the following, I'd try to work this into multiview to stay "JQM tweak free" (I could also do a pull request on Github with the changes, if that's easier than via email...

    Thanks & best regards,

    Sven

    • JQM changes:
    1. createHandler - cleanform function = need to add an if-clause to prevent JQM from dropping active class on the wrong page.
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    		 
        ...
     
        if ( $to.parents('.ui-page-active').length == 0  && $from.parents('.ui-page-active').length == 0 ) {                    
     
               $from.closest(':jqmData(wrapper="true")').removeClass( $.mobile.activePageClass );    
     
               return;
     
                }
     
        ...
     
        $from
     
              .removeClass( $.mobile.activePageClass + " out in reverse " + name )
    1. urlHistory - store pageContainer in URL history
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    		 
        ....
     
        addNew: function( url, transition, title, pageUrl, role, pageContainer ) {
     
        ...
     
           urlHistory.stack.push( {url : url, transition: transition, title: title, pageUrl: pageUrl, role: role, pageContainer: pageContainer } );
     
        ...
     
        $.mobile.changePage(
     
        ...
     
           if( !historyDir ) {
     
               urlHistory.addNew( url, settings.transition, pageTitle, pageUrl, settings.role, settings.pageContainer );
     
                }
    1. transitionPages - promise.done(function() - add if-clause to prevent removing the wrapper page
    1
    2
    3
    4
    5
    6
    7
    8
    9
    		 
        if( fromPage ) {
     
               if ( $(fromPage).jqmData('internal-page') != true && (fromPage).jqmData('data-dom-cache') != true ) {
     
                       fromPage.data( "page" )._trigger( "hide", null, { nextPage: toPage } );
     
                        }
     
                }
    1. Plugin init - $.extend - set a flag to allow deeplinking on panels
    1
    2
    3
    4
    5
    6
    7
    8
    9
    		 
        // if hashchange listening is disabled or there's no hash deeplink, change to the first page in the DOM
     
        if ( !$.mobile.hashListeningEnabled || !$.mobile.path.stripHash( location.hash ) || $( window.location.hash ).closest('div:jqmData(role="panel")').length > 0 ) {
     
              $('html').data("deep", window.location.hash);
     
              $.mobile.changePage( $.mobile.firstPage, { transition: "none", reverse: true, changeHash: false, fromHashChange: true } );
     
               }

    link 1.1.1 Planning

    link Pull requests

    link PhoneGap blinky transitions

    link Fixed toolbars / updatePagePadding / header and content switched

    • Many related issues

    link Re-enhancement after manipulation

    link Button/form consistency

    • Should we add styles to protect buttons from a: basic styles?

    • https://github.com/jquery/jquery-mobile/issues/3444

    • PR #4385 commit 8509d57

    • Cascade issue bar link colors + reorder pseudo classes (also PR #4385)

    • TR issue #73 - links in bar not themable, always same as JQM default theme (Tyler Benziger)

    link 2.3 nav issues

    link 1.2 Features

    Issues: https://github.com/jquery/jquery-mobile/issues?milestone=13&page=1&state=open

    link Read-only lists

    • New styling including removal smaller font-size and padding of ui-li-static for 1.2 #4347

    link 1.3 Features

    ###Fetchlink - Needs API design

    ###Tabs - standalone widget or just a fetchlink demo?

    ###Library modularity?

    ###Themes: Multiple active states

    • Support active state per swatch instead of a global active (Tyler - LOE?)
    • If we make it a full button state class (.ui-btn-active-a) what to do with ui-focus box-shadow color?

    ###Grid widget?

    • have the framework adding the ui-block classes (same as navbar widget) data attribute # columns

    link 1.future

    Prioritize and start sequencing the next few releases for the remainder of the year

    • Tablet responsive layout patterns - YES!

    • Overflow regions - overthrow.js, be very defensive here to not break platforms

    • Performance optimizations to speed up rendering and interactions, enhancement - if you’re building a dynamic app, writing out the enhanced markup directly instead of starting with basic then enhancing via create makes more sense

    • Slider lag (look at UI?)

    • Pre-enhance markup

    • Carousel?

    • Pull in autocomplete from UI?

    • Pull in position from UI?

    • Pull in progressbar from UI?

    • Light calendar picker?

    • Scan wiki/feature-request and jQuery forum/ideas for interesting new features

    link Infrastructure

    ###Migration to Grunt (Bender) Migration to Grunt in progress - JS and CSS only, not docs or zip because they aren’t public targets. Need to check with team on this. DONE

    link Sort out Test / TestSwarm issues

    • Migrated existing tests to Phantomjs. Need to setup multiple jquery versions. Fixing existing build issues. Soon.

    link Redirects for Branch Preview / Test to new server (per D. Heberden)

    • Looking into this.

    link Plugin site requirements

    • Package JSON file for our plugins

    link UI Integration

    • Test port of mobile TR framework onto a UI widget (TBD) as a POC - Scott/Mat
    • Download builder - status of UI’s tool?

    link 3rd Party Widgets

    • Think about how to curate semi-official widgets that we recommend to offload some of the dev work. Bender wants to think about how to register and init widgets to make this easier.

    link ThemeRoller - 3rd party tools

    • All sorts of web apps or software tools may want to integrate ThemeRoller functionality - how to make this as seamless as possible w/o hooking in too deeply?

    • Current idea: Support a lightweight round trip theme solution that lets a 3rd party tool have a button that would launch TR in a new window/iframe. This could either be a default TR theme (Create new theme) or it could support editing by pushing in a theme (via the import mechanism) so the theme would appear in TR, ready for modification. In TR, allow the Download button to be customized in appearance (Save to App X + icon) and the 3rd party tool would write a handler to manage the manipulation and saving of the TR output on their side. We'd just provide the hooks in and out so this would be a new API for developers to use TR without forking it and making a custom build.

    • Tyler needs to do more work on the versioning side of things to support this. The guys from Codiqa have volunteered to help with some of the engineering and to be the test case for this to help us work out the kinks. This would launch as an open platform and others tools can help participate in shaping this as we go.

    • Help test the new ThemeRoller versioning: http://jquerymobile.com/themeroller-test/

    link Download builder

    jQuery Mobile Team

    jQuery Mobile Team Meeting – May 17 2012

    link jQM Modularity

    • I’ve heard a bunch of questions recently about how monolithic the library is. I know we’ve done a lot of decoupling work internally and now have the download builder which will help quite a bit.

    • Modularity questions: how much make we break things up for consumption:

      • Only want utilities like touch events, zoom fix, orientation (not yet?)
      • Want a specific subset of widgets and transitions (yes)
      • Only want certain widgets, no nav model (yes)
      • Only want nav model/transitions, no widgets or CSS framework (yes)

    • I’d like to do some analysis for LOE and see if we should focus on this for 1.3.

    • All modules use $.mobile - requires core

    • Also jQ core dependencies to consider - tree shaking to see how much we use

    • What is core? What is a module?

    link Team

    • Adobe changes - Kin
    • New committers - Jason and Jasper
    • More people to add to the team?

    link Timing

    • 1.1.1 beta - conference?

    • 1.2.0 alpha - conference?

    • Need to discuss this more as we get closer.

    ##Popups

    link Open dev questions

    1
    		 
      .ui-li-static { background-image: none; }

    link Git current issue

    • event.html in 1.1-stable needs resolving.

    link 1.1.1 Planning

    link Pull requests

    link PhoneGap blinky transitions

    link Button/form consistency

    link 2.3 nav issues

    link 1.2 Features

    link Read-only lists

    • New styling including removal smaller font-size and padding of ui-li-static for 1.2 #4347

    • Changes to discuss

      • Modal overlay screen - default to none, only show if data-overlay-theme option is set to a swatch letter✓
      • Remove "Fade" as an option and just fade in overlay screen if one is specified, CSS override of keyframes if needed✓
      • Popup container - inherits the theme from the parent page by default, data-theme attr can be set to a swatch letter or to "none" to have the container have an invisible background (just won't write in the ui-content-a/b/c class)✓
      • Popup won't have any padding by default to let widgets like lists (menus), photos, etc. be edgeless. To add padding, recommend people add the "ui-content" class to the popup wrapper add the standard 15px of page padding or write custom styles as needed
      • Corner classes are a bit tricky with nested edgeless elements. Ex. if a inset list is inside a popup, will the corners look ok?
      • Popup transition. Use the same fallback mechanism as the dialogs >> create a utility that is used for both dialogs and popups. Factor out the mechanism (which is currently inline inside a function in navigation.js) into a public function: degradedTransition = $.mobile.maybeDegradeTransition( originalTransition ); It need not be public - but the little dance it does with looking up the transition in a hash of fallbacks is kind of important, and I don't want to copy/paste that code into popup.✓
      • Add an example of how to add a close button, like dialog, false by default = data-close-btn=”true”. Note that if we add this, we’ll also need a data-close-btn-text=”Close popup” option for accessibility and a11y. https://github.com/jquery/jquery-mobile/issues/4267#issuecomment-5492106
        • Q: Dialog doesn’t have an option currently to not write in the close button, add this feature there for consistency? Probably
      • The custom select should also be ported over to use popup as part of 1.2. Need to create a ticket. Any other widgets that could be ported over? - https://github.com/jquery/jquery-mobile/issues/4329

    link 1.3 Features

    link Library modularity?

    link Themes: Multiple active states

    • Support active state per swatch instead of a global active (Tyler - LOE?)

    link 1.future

    • Prioritize and start sequencing the next few releases for the remainder of the year
    • Tablet responsive layout patterns - YES!
    • Decoupling things to use standalone (touch events, vmouse, etc.)
    • Overflow regions - overthrow.js, be very defensive here to not break platforms
    • Performance optimizations to speed up rendering and interactions, enhancement - if you’re building a dynamic app, writing out the enhanced markup directly instead of starting with basic then enhancing via create makes more sense
    • Slider lag (look at UI?)
    • Pre-enhance markup
    • Carousel?
    • Pull in autocomplete from UI?
    • Pull in position from UI?
    • Pull in progressbar from UI?
    • Light calendar picker?

    link Infrastructure

    ###Migration to Grunt (Bender)

    • Migration to Grunt in progress - JS and CSS only, not docs or zip because they aren’t public targets. Need to check with team on this. DONE

    link Sort out Test / TestSwarm issues

    • Migrated existing tests to Phantomjs. Need to setup multiple jquery versions. Fixing existing build issues. Soon.

    link Redirects for Branch Preview / Test to new server (per D. Heberden)

    • Looking into this.

    link Plugin site requirements

    • Package JSON file for our plugins

    link UI Integration

    • Test port of mobile TR framework onto a UI widget (TBD) as a POC - Scott/Mat
    • Download builder - status of UI’s tool?

    link 3rd Party Widgets

    • Think about how to curate semi-official widgets that we recommend to offload some of the dev work. Bender wants to think about how to register and init widgets to make this easier.

    link ThemeRoller - 3rd party tools

    • All sorts of web apps or software tools may want to integrate ThemeRoller functionality - how to make this as seamless as possible w/o hooking in too deeply?

    • Current idea: Support a lightweight round trip theme solution that lets a 3rd party tool have a button that would launch TR in a new window/iframe. This could either be a default TR theme (Create new theme) or it could support editing by pushing in a theme (via the import mechanism) so the theme would appear in TR, ready for modification. In TR, allow the Download button to be customized in appearance (Save to App X + icon) and the 3rd party tool would write a handler to manage the manipulation and saving of the TR output on their side. We'd just provide the hooks in and out so this would be a new API for developers to use TR without forking it and making a custom build.

    • Tyler needs to do more work on the versioning side of things to support this. The guys from Codiqa have volunteered to help with some of the engineering and to be the test case for this to help us work out the kinks. This would launch as an open platform and others tools can help participate in shaping this as we go.

    • Help test the new ThemeRoller versioning: http://jquerymobile.com/themeroller-test/

    link Download builder

    jQuery UI Team

    jQuery UI Team Meeting – May 16 2012

    • Back to green in TestSwarm :-)
    • Finished accessibility updates for tooltip.
    • Finished accessibility updates for autocomplete.
    • Working on new documentation.
      • Using a new process documented on the planning wiki.
      • Documentation is written in XML, then converted to HTML via XSLT.
      • Generated HTML is then published to WordPress using grunt-wordpress.
    • Working on new api.jquery.com site first, then moving on to api.jqueryui.com.
    • Landed new animation API for tabs.
      • Uses new show and hide options.
      • Common API among many widgets.
    • Planning 1.9m8 release this week.
    jQuery Core Team

    jQuery Core Team Meeting – May 14 2012

    May 14, 2012
    Minutes (Notes) of the meeting of jQuery
    Location: #jquery-meeting on Freenode
    Attending: DaveMethvin, mikesherov, rwaldron, timmywil, gnarf
    Time: Noon ET

    Official Agenda:

    1.8

    Need to knock down the list of remaining 1.8 items

    Manual modularity

    • Allow build without effects, ajax, css even?
    • Opened a ticket: http://bugs.jquery.com/ticket/11767
    • gnarf will look at animation modularity
    • jaubourg can do ajax part?
    • dave will look at grunt

    Documentation

    • Deprecations – dave created tickets
    • Animation hooks Tween etc. — gnarf can you outline?
    • Other things needing docs?

    Size and “bloat”, call for participation on CCAO

    mikesherov asks: what browser “versions” do we support?

    Bug triage meeting Thursday 8pm eastern time #jquery-dev

    • all the cool kids will attend
    jQuery Mobile Team

    jQuery Mobile Team Meeting – May 10 2012

    link Download builder

    • http://jquerymobile.com/download-builder/

    • https://github.com/jquery/jquery-mobile-builder

    • Open issues: none, 4 reported and closed

    • Include default theme + structure theme - create issue because we only include default, not structure

    • Plans for wider beta since we've run this by our alpha testers for the last 2 weeks

    • Need to test more internally:

    • Modularity questions: how much make we break things up for consumption:

      • Want a specific subset of widgets and transitions (yes)
      • Only want certain widgets, no nav model (yes)
      • Only want nav model/transitions, no widgets or CSS framework (yes)
      • Only want utilities like touch events, zoom fix, orientation (not yet?)
      • How to define mobile “core”

    • CREATE ISSUE: multiple button CSS

    • CREATE ISSUE: generate structure CSS in addition version with theme

    link Code indentation

    • I am ready now to work on the docs code indentation to make it 2 spaces. Would it be ok to just update master and not cherry-pick into 1.1-stable?

    • As it will take several days, I'd rather target 1.2 and have it all completed for that, while if I cherry-pick, some pages of the stable version would get updated before others and we'd inconsistent code layout.

    • So is it ok to only update master for now? I could have a standard comment for it to easily track them if we then wanted to update stable before 1.2 is out? If we go for that, do you have a suggestion for what this comment should be? [docs indent]?

    • Decision: make changes in master only for 1.2, don’t cherry pick into 1.1-stable but we may have merge conflicts on whitespace. Wait until 1.2-beta (or RC), than tackle this.

    link 1.1.1 Planning

    link Pull requests

    link New members:

    • Jasper, Codiqa guys - look for people to help us

    link PhoneGap blinky transitions

    ###Fixed jumping into place on transition w/scroll

    1
    2
    3
    4
    5
    		 
        $('a').click(function () {
     
          $('html, body, .ui-page').animate({ scrollTop: 0 }, 0);
     
        });
    • This works best either when data-transition is set to either none or fade. Hope this helps someone with this issue.

    link Persistent toolbar with fixed

    link Button/form consistency

    link 2.3 nav issues

    link The href monkeying issue

    • We’ve seen several issues coming in that are related to that. # on iOS
      • remove this

    link 1.2 Features

    link Read-only lists

    • New styling including removal smaller font-size and padding of ui-li-static for 1.2 #4347

    *Changes to discuss

    • Modal overlay screen - default to none, only show if data-overlay-theme option is set to a swatch letter
    • Remove "Fade" as an option and just fade in overlay screen if one is specified, CSS override of keyframes if needed
    • Popup container - inherits the theme from the parent page by default, data-theme attr can be set to a swatch letter or to "none" to have the container have an invisible background (just won't write in the ui-content-a/b/c class)
    • Popup won't have any padding by default to let widgets like lists (menus), photos, etc. be edgeless. To add padding, recommend people add the "ui-content" class to the popup wrapper add the standard 15px of page padding or write custom styles as needed
    • Corner classes are a bit tricky with nested edgeless elements. Ex. if a inset list is inside a popup, will the corners look ok?
    • Popup transition. Use the same fallback mechanism as the dialogs >> create a utility that is used for both dialogs and popups. Factor out the mechanism (which is currently inline inside a function in navigation.js) into a public function: degradedTransition = $.mobile.maybeDegradeTransition( originalTransition ); It need not be public - but the little dance it does with looking up the transition in a hash of fallbacks is kind of important, and I don't want to copy/paste that code into popup.✓
    • Add an example of how to add a close button, like dialog, false by default = data-close-btn=”true”. Note that if we add this, we’ll also need a data-close-btn-text=”Close popup” option for accessibility and a11y. https://github.com/jquery/jquery-mobile/issues/4267#issuecomment-5492106
      • Q: Dialog doesn’t have an option currently to not write in the close button, add this feature there for consistency? Probably
    • The custom select should also be ported over to use popup as part of 1.2. Need to create a ticket. Any other widgets that could be ported over? - https://github.com/jquery/jquery-mobile/issues/4329

    link Listview: autodividers

    link 1.3 Features

    link Themes: Multiple active states

    • Support active state per swatch instead of a global active (Tyler - LOE?)

    link 1.future

    Prioritize and start sequencing the next few releases for the remainder of the year

    • Tablet responsive layout patterns - YES!
    • Decoupling things to use standalone (touch events, vmouse, etc.)
    • Overflow regions - overthrow.js, be very defensive here to not break platforms
    • Performance optimizations to speed up rendering and interactions, enhancement - if you’re building a dynamic app, writing out the enhanced markup directly instead of starting with basic then enhancing via create makes more sense
    • Slider lag (look at UI?)
    • Pre-enhance markup
    • Carousel?
    • Pull in autocomplete from UI?
    • Pull in position from UI?
    • Pull in progressbar from UI?
    • Light calendar picker?

    link Infrastructure

    ###Migration to Grunt (Bender)

    • Migration to Grunt in progress - JS and CSS only, not docs or zip because they aren’t public targets. Need to check with team on this.

    link Sort out Test / TestSwarm issues

    • hopefully next week we’ll get this going

    link Redirects for Branch Preview / Test to new server (per D. Heberden)

    • Looking into this.

    link Plugin site requirements

    • Package JSON file for our plugins

    link UI Integration

    • Test port of mobile TR framework onto a UI widget (TBD) as a POC - Scott/Mat
    • Download builder - status of UI’s tool?

    link 3rd Party Widgets

    • Think about how to curate semi-official widgets that we recommend to offload some of the dev work. Bender wants to think about how to register and init widgets to make this easier.

    link ThemeRoller - 3rd party tools

    • All sorts of web apps or software tools may want to integrate ThemeRoller functionality - how to make this as seamless as possible w/o hooking in too deeply?

    • Current idea: Support a lightweight round trip theme solution that lets a 3rd party tool have a button that would launch TR in a new window/iframe. This could either be a default TR theme (Create new theme) or it could support editing by pushing in a theme (via the import mechanism) so the theme would appear in TR, ready for modification. In TR, allow the Download button to be customized in appearance (Save to App X + icon) and the 3rd party tool would write a handler to manage the manipulation and saving of the TR output on their side. We'd just provide the hooks in and out so this would be a new API for developers to use TR without forking it and making a custom build.

    • Tyler needs to do more work on the versioning side of things to support this. The guys from Codiqa have volunteered to help with some of the engineering and to be the test case for this to help us work out the kinks. This would launch as an open platform and others tools can help participate in shaping this as we go.

    • Help test the new ThemeRoller versioning: http://jquerymobile.com/themeroller-test/