Author Archives: 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/

Testing Team

Testing Team Meeting – May 04 2012

QUnit 1.6.0 was released, featuring a stable composite addon, a few bug fixes and enhancements. More details in the changelog.

swarm.jquery.org is now running TestSwarm 1.0.0.

Jenkins integration is now done via node-testswarm, making improvements a lot easier and moving configurations into the individual projects. That makes them also a lot less dependent on Jenkins itself.

TestSwarm-BrowserStack is now using the TestSwarm 1.0.0 API, removing the dependency on auto-increment IDs. Its also gotten better at dealing with BrowserStack queue limits, making more efficient use of their service. The module now has more documentation, making it easier to use for other projects.

Krinkle wrote Automated Distributed Continuous Integration for JavaScript, outlining how to combine all these various projects into one whole automation setup.

jQuery Mobile Team

jQuery Mobile Team Meeting – May 03 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”

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.

link 1.1.1 Planning

link Pull requests

link PhoneGap blinky transitions

link Fixed jumping into place on transition w/scroll

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?

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!
  • Overflow regions - overthrow.js, be very defensive here to not break platforms
  • Carousel?
  • Pull in autocomplete from UI?
  • Pull in spinner from UI?
  • Pull in progressbar from UI?
  • Light calendar picker?

link Infrastructure

###Migration to Grunt (Bender)

  • Migration to Grunt in progress
  • Sort out Test / TestSwarm issues
  • Redirects for Branch Preview / Test to new server (per D. Heberden)

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?
Testing Team

Testing Team Meeting – Apr 27 2012

QUnit’s composite addon is now using the new callback registration mechanism, making it a lot more compatible with other code using those callbacks. Rerun links to open the individual testsuite.

The QUnit website is coming together, with a docpad-based repo at https://github.com/jquery/qunitjs.com. Contributions welcome! For now this is deployed via GitHub pages at qunitjs.com, but will soon migrate to the WordPress-based deployment that all other jQuery properties will use.

TestSwarm 1.0 is basically done, but still waits for updates on BrowserStack and Jenkins integrations. Once those are done, TestSwarm 1.0 will be official. In the meantime, we’ve revived the @TestSwarm Twitter account.

jQuery Core Team

jQuery Core Team Meeting – Apr 23 2012

April 23, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, rwaldron, timmywil, gibson042, sindresorhus, gnarf, jaubourg
Time: Noon ET

Official Agenda:

new team member – gibson042

Triage

  • http://goo.gl/fbZD3
  • Need a sweep of bugs and assign to 1.8
  • Please look at tickets related to rewrites if you’re doing one
  • Dave will ping people on specific tickets if needed

1.8

Beta schedule?

  • Need solid final release by end of June
  • Work backwards from there
  • Beta?
  • RC? Want a month given the changes

Unit tests need to work better – Dave will ping jzaefferer

Ready to land animations?

CCAO – can we land the Sizzle CCAO changes as-is? (Timmy says yes)

  • mostly quoting of args … not sure of the size impact
  • could commit to a branch and have CCAO submodule that?

Timmywil has first cut at Sizzle changes

jQuery.quickReady – land it now? (yep)

Documentation

  • New interfaces like quickReady?
  • Animation hooks Tween etc.
  • Other things needing docs?

Blogs and messaging (Dave)

  • Deprecation — goo.gl/Vzaxa (team only)
  • Size and “bloat”, call for participation on CCAO

Build process

  • code will used shared_var
  • Use “grunt watch” to auto-build

gnarf may try to move Trac to a new server