r955 - branches/dev/spinner
Author: rdworth Date: Tue Nov 18 18:25:00 2008 New Revision: 955 Added: branches/dev/spinner/ - copied from r953, /trunk/ Log: Created dev/spinner branch as of trunk rev953
r954 - branches/dev
Author: rdworth Date: Tue Nov 18 18:23:28 2008 New Revision: 954 Added: branches/dev/ Log: Created new dev branches folder for plugins in pre-release/alpha development
Progressbar Options: min, max, value
I'd like to propose the addition of three options for progressbar: min, max value. Right now, progressbars always range from 0 to 100, and the only value you can set is the percentage via the progress method. User's should be able to define the range to fit their needs. Examples: - Someone is working their way through a 5 step process. I would want my range to be 1-5. - An app is parsing a 50k string. I would want my range to be 0-50k. User's should also be able to define the current value.
Trimming the ui parameter
One of our design goals with the jQuery UI API is to not have multiple ways of doing something, to keep things simple. There are two properties often included in the ui parameter in callback functions I propose removing, as they're duplicative: ui.element (same as $(this)) ui.options (options should be get and set through the api - .pluginname("option", key, value)) Both may have been needed before when we weren't (yet) consistent with $(this) and being able to get and set all options through the
r953 - branches/experimental/demos/functional/templates branches/experimental/tests branches/expe...
Author: rdworth Date: Mon Nov 17 18:55:25 2008 New Revision: 953 Modified: branches/experimental/demos/functional/templates/ui.autocomplete.html branches/experimental/demos/functional/templates/ui.colorpicker.html branches/experimental/demos/functional/templates/ui.magnifier.html branches/experimental/tests/autocomplete.html branches/experimental/tests/datepicker.html branches/experimental/tests/grid.html branches/experimental/tests/grid.js branches/experimental/tests/gridmodel-local.js branches/experimental/tests/gridmodel.html
r952 - trunk/ui
Author: scott.gonzalez Date: Mon Nov 17 18:22:30 2008 New Revision: 952 Modified: trunk/ui/ui.progressbar.js Log: Progressbar: Removed text method. Modified: trunk/ui/ui.progressbar.js ============================================================================== --- trunk/ui/ui.progressbar.js (original) +++ trunk/ui/ui.progressbar.js Mon Nov 17 18:22:30 2008 @@ -137,7 +137,7 @@ var percent = Math.round(this.percentState); if (this.options.range && !this.options.text)
r951 - trunk/ui
Author: scott.gonzalez Date: Mon Nov 17 17:54:45 2008 New Revision: 951 Modified: trunk/ui/effects.core.js trunk/ui/effects.highlight.js trunk/ui/ui.accordion.js Log: Various: Fixed #3596: Removed references to jQuery for .noConflict() compatibility. Modified: trunk/ui/effects.core.js ============================================================================== --- trunk/ui/effects.core.js (original) +++ trunk/ui/effects.core.js Mon Nov 17 17:54:45 2008 @@ -183,8 +183,8 @@ */ // We override
r922 - trunk/themes/default
Author: kbwood.au Date: Wed Nov 12 05:22:28 2008 New Revision: 922 Modified: trunk/themes/default/ui.all.css Log: Fixed 3261, 3307, 3513, 3521. Refactored datepicker CSS to allow full functionality. Modified: trunk/themes/default/ui.all.css ============================================================================== --- trunk/themes/default/ui.all.css (original) +++ trunk/themes/default/ui.all.css Wed Nov 12 05:22:28 2008 @@ -55,121 +55,199 @@ } -/* Datepicker */ +/*datepicker*/ /* Main Style
issue with sortable('toArray') with v1.6.2
I just updated to fix a bug with 1.5.2, and I got o undefined at ui.sortable.js line 85: items.each(function() { ret.push($(this).attr(o.attr || 'id')); }); that's just after updating to 1.6.x from 1.5.x I'm using sortable on a <ul> where each li has custom id attribute: $("ul.productPlatforms").sortable({update: pageController.callbacks.onSortableDrop}); onSortableDrop : function(e, ui){ var result = $("ul.productPlatforms").sortable('toArray'); var callback = function(){} $.post(saveSortUrl, {keys
r950 - trunk/ui
Author: scott.gonzalez Date: Mon Nov 17 05:58:53 2008 New Revision: 950 Modified: trunk/ui/ui.progressbar.js Log: Progressbar: Removed identifier, element, textElement from the ui object in callbacks. Modified: trunk/ui/ui.progressbar.js ============================================================================== --- trunk/ui/ui.progressbar.js (original) +++ trunk/ui/ui.progressbar.js Mon Nov 17 05:58:53 2008 @@ -192,10 +192,7 @@ ui: function() { return { - identifier:
Progressbar text Method
I'd like to propose the removal of the text method for progressbar, since it can be accomplished just as easily by setting the text option. $(el).progressbar('option', 'text', 'some value');
r949 - trunk/ui
Author: scott.gonzalez Date: Mon Nov 17 05:56:28 2008 New Revision: 949 Modified: trunk/ui/ui.progressbar.js Log: Progressbar: Removed textClass option. Modified: trunk/ui/ui.progressbar.js ============================================================================== --- trunk/ui/ui.progressbar.js (original) +++ trunk/ui/ui.progressbar.js Mon Nov 17 05:56:28 2008 @@ -56,7 +56,6 @@ width: 0, overflow: 'hidden' }) - .addClass(options.textClass)
Progressbar textClass Option
Why does progressbar have a textClass option? If the user wants to have multiple progressbars on the page with different text styles, they can easily apply a class to the main element and write their CSS rules appropriately.
r948 - trunk/ui
Author: scott.gonzalez Date: Sun Nov 16 17:16:34 2008 New Revision: 948 Modified: trunk/ui/ui.progressbar.js Log: Progressbar: Removed references to jQuery for compatibility with .noConflict(). Modified: trunk/ui/ui.progressbar.js ============================================================================== --- trunk/ui/ui.progressbar.js (original) +++ trunk/ui/ui.progressbar.js Sun Nov 16 17:16:34 2008 @@ -92,7 +92,7 @@ self._animate(); } else
r947 - trunk/ui
Author: scott.gonzalez Date: Sun Nov 16 16:21:36 2008 New Revision: 947 Modified: trunk/ui/ui.progressbar.js Log: Progressbar: Refactored creation of elements on init. Removed propagate method; using trigger instead. Fixed appending background text element. Added $.ui.progressbar.uuid; used for identifier instead of timestamp + random number. Fixed updating of text to also update the background text. Removed default for unused addClass option. Modified: trunk/ui/ui.progressbar.js ==============================================================================
r946 - branches/experimental/tabbable
Author: scott.gonzalez Date: Sat Nov 15 05:59:23 2008 New Revision: 946 Modified: branches/experimental/tabbable/ui.core.js Log: Tabbable: Temporary proxy of $.attr. Modified: branches/experimental/tabbable/ui.core.js ============================================================================== --- branches/experimental/tabbable/ui.core.js (original) +++ branches/experimental/tabbable/ui.core.js Sat Nov 15 05:59:23 2008 @@ -1,5 +1,16 @@ (function($) { +// temporary hack to proxy $.attr +//
r945 - branches/experimental/tabbable
Author: scott.gonzalez Date: Sat Nov 15 05:54:10 2008 New Revision: 945 Modified: branches/experimental/tabbable/ui.core.js Log: Tabbable: Potential improvement for getTabIndex(). Modified: branches/experimental/tabbable/ui.core.js ============================================================================== --- branches/experimental/tabbable/ui.core.js (original) +++ branches/experimental/tabbable/ui.core.js Sat Nov 15 05:54:10 2008 @@ -4,6 +4,13 @@ ? 'tabIndex' : 'tabindex');
r944 - branches/experimental/tabbable
Author: scott.gonzalez Date: Sat Nov 15 05:49:32 2008 New Revision: 944 Modified: branches/experimental/tabbable/ui.core.js Log: Tabbable: Cleanup. Modified: branches/experimental/tabbable/ui.core.js ============================================================================== --- branches/experimental/tabbable/ui.core.js (original) +++ branches/experimental/tabbable/ui.core.js Sat Nov 15 05:49:32 2008 @@ -1,19 +1,20 @@ (function($) { - -var normalizedTabindex = ($.browser.msie && parseInt($.browser.version,
r943 - branches/experimental/tabbable
Author: scott.gonzalez Date: Sat Nov 15 05:47:32 2008 New Revision: 943 Modified: branches/experimental/tabbable/ui.core.js Log: Tabbable: Applied patch from Colin/Alex. Modified: branches/experimental/tabbable/ui.core.js ============================================================================== --- branches/experimental/tabbable/ui.core.js (original) +++ branches/experimental/tabbable/ui.core.js Sat Nov 15 05:47:32 2008 @@ -1,34 +1,35 @@ (function($) { - -function getTabIndex(element)
r942 - trunk/themes/default
Author: kbwood.au Date: Sat Nov 15 04:08:55 2008 New Revision: 942 Modified: trunk/themes/default/ui.all.css Log: Rollback changes for datepicker. This means 3261, 3307, 3513, 3521 are problems again. Modified: trunk/themes/default/ui.all.css ============================================================================== --- trunk/themes/default/ui.all.css (original) +++ trunk/themes/default/ui.all.css Sat Nov 15 04:08:55 2008 @@ -55,200 +55,123 @@ } -/*datepicker*/ +/* Datepicker */ /* Main
ThemeRoller CSS framework class naming conventions
While transitioning our widgets to use framework classes, we should probably change the class naming conventions to something more scalable than they currently are. For example, the state classes currently look like this: .ui-default-state .ui-hover-state .ui-active-state They should probably be this: .ui-state-default .ui-state-hover .ui-state-active Same with icons, which are currently like this: .ui-arrow-right-default .ui-arrow-right-hover .ui-plus-default and should probably have an "icon" naming
r941 - in trunk: tests ui
Author: scott.gonzalez Date: Fri Nov 14 20:29:08 2008 New Revision: 941 Modified: trunk/tests/core.js trunk/ui/ui.core.js Log: Core: Fixed #3562: Modify .removeAttr() to work on ARIA properties in FF2. Modified: trunk/tests/core.js ============================================================================== --- trunk/tests/core.js (original) +++ trunk/tests/core.js Fri Nov 14 20:29:08 2008 @@ -56,12 +56,23 @@ module('jQuery extensions'); test("attr - aria", function() { - expect(4); + expect(6);
wysiwyg editor
What's the best wysiwyg editor in your opinion?<br clear="all"> -- Eduardo Lundgren Software Engineer Liferay, Inc. Enterprise. Open Source. For Life.
1.7 Proposal - Password Widget
Hey folks, On the main UI list I've just posted details about my new widget, the password widget (http://groups.google.com/group/jquery-ui/ browse_thread/thread/4ed3a6d773ce87de). At the moment, it's actually almost pretty much completed, however I understand I've missed the boat on 1.6, so I'd like to put it forward for 1.7. The password widget works by attaching itself to a input password field, like so: jQuery(":password").password(); It then attaches a progress bar to below the password area
autocomplte: visual test, remote, gone?
Hi, I'm currently looking into a few autocomplete issues and wonder why all the remote tests from the visual test (experimental/tests/visual/autocomplete/) are gone. Any idea? Jörn
Menu planning update
Just an FYI that we've updated the menu wiki page with extended visual designs and recommendations for additional features (check/radio options, dividers, etc.). http://jqueryui.pbwiki.com/Menu Thanks, Maggie
Plugins for the future
There is a lot of requests for two plugins into jQuery UI, that is not listed on our wiki yet. A Carousel: <a href="http://sorgalla.com/projects/jcarousel/examples/static_controls.html">http://sorgalla.com/projects/jcarousel/examples/static_controls.html</a> <a href="http://sorgalla.com/projects/jcarousel/examples/static_multiple.html">http://sorgalla.com/projects/jcarousel/examples/static_multiple.html</a> Cycle plugin: <a href="http://malsup.com/jquery/cycle/int.html">http://malsup.com/jquery/cycle/int.html</a>
r940 - branches/experimental/ui
Author: joern.zaefferer Date: Fri Nov 14 07:21:20 2008 New Revision: 940 Modified: branches/experimental/ui/ui.autocomplete.js Log: autocomplete: fixed #3585 Modified: branches/experimental/ui/ui.autocomplete.js ============================================================================== --- branches/experimental/ui/ui.autocomplete.js (original) +++ branches/experimental/ui/ui.autocomplete.js Fri Nov 14 07:21:20 2008 @@ -212,6 +212,9 @@ if ( !value ) { return [""];
r939 - in branches/experimental: tests ui
Author: joern.zaefferer Date: Fri Nov 14 06:41:35 2008 New Revision: 939 Modified: branches/experimental/tests/autocomplete.js branches/experimental/ui/ui.autocomplete.js Log: autocomplete: fixed #3168 Modified: branches/experimental/tests/autocomplete.js ============================================================================== --- branches/experimental/tests/autocomplete.js (original) +++ branches/experimental/tests/autocomplete.js Fri Nov 14 06:41:35 2008 @@ -132,3 +132,20 @@ equals(
r938 - branches/experimental/tests
Author: joern.zaefferer Date: Fri Nov 14 06:40:51 2008 New Revision: 938 Modified: branches/experimental/tests/autocomplete.html branches/experimental/tests/autocomplete.js Log: autocomplete: fixed testsuite (missing elements in html file, invalid comparison of functions) Modified: branches/experimental/tests/autocomplete.html ============================================================================== --- branches/experimental/tests/autocomplete.html (original) +++ branches/experimental/tests/autocomplete.html Fri
r937 - in branches/experimental: tests ui
Author: joern.zaefferer Date: Fri Nov 14 06:29:21 2008 New Revision: 937 Modified: branches/experimental/tests/autocomplete.js branches/experimental/ui/ui.autocomplete.js Log: autocomplete: added tests for #3581 and fixed it: user specified values for delay and max are now always preferred over "intelligent" defaults Modified: branches/experimental/tests/autocomplete.js ============================================================================== --- branches/experimental/tests/autocomplete.js (original)
r936 - branches/experimental/tests
Author: joern.zaefferer Date: Fri Nov 14 06:03:59 2008 New Revision: 936 Modified: branches/experimental/tests/autocomplete.js Log: autocomplete: formatting in test Modified: branches/experimental/tests/autocomplete.js ============================================================================== --- branches/experimental/tests/autocomplete.js (original) +++ branches/experimental/tests/autocomplete.js Fri Nov 14 06:03:59 2008 @@ -50,7 +50,6 @@ $('<input id="autocomplete_dis">').autocomplete().autocomplete("destroy").autocomplete().remove();
r935 - trunk/tests
Author: kbwood.au Date: Fri Nov 14 05:32:12 2008 New Revision: 935 Modified: trunk/tests/datepicker.js Log: Added tests for daylight savings problems - only show up in specific timezones. Modified: trunk/tests/datepicker.js ============================================================================== --- trunk/tests/datepicker.js (original) +++ trunk/tests/datepicker.js Fri Nov 14 05:32:12 2008 @@ -1240,6 +1240,88 @@ equals(alt.val(), '', 'Alt field range - alt - enter/pgdn/ctrl+end');
r934 - trunk/ui
Author: kbwood.au Date: Fri Nov 14 05:28:58 2008 New Revision: 934 Modified: trunk/ui/ui.datepicker.js Log: Fixed 3395, 3512, 3537, 3560, 3566. Problems with daylight saving cutover. Moved prompt to below controls. Corrected month/year spacing for multiple months. Modified: trunk/ui/ui.datepicker.js ============================================================================== --- trunk/ui/ui.datepicker.js (original) +++ trunk/ui/ui.datepicker.js Fri Nov 14 05:28:58 2008 @@ -251,12 +251,6 @@
Versioning ThemeRoller - moving forward
With the upcoming changes to the TR framework styles, re-classing of widgets, and changing the icons to sprites (which will require additional elements in the widgets), we are going to be making changes that won't work with previous versions of UI. Should the current version of ThemeRoller's CSS be frozen with 1.6 and have a different CSS version for each release of UI? Should we make a clean break for 1.7 where ThemeRoller will only be compatible moving forward but not backward? How about adding
r933 - branches/experimental/autotest branches/experimental/coverflow branches/experimental/demos...
Author: rdworth Date: Thu Nov 13 19:00:16 2008 New Revision: 933 Modified: branches/experimental/autotest/jquery.useraction.js branches/experimental/autotest/ui.testmouse.js branches/experimental/coverflow/ui.coverflow.js branches/experimental/demos/functional/templates/ui.colorpicker.html branches/experimental/tests/visual/colorpicker.html branches/experimental/tests/visual/keyboard_selection.html branches/experimental/tests/visual/menu/menu.html branches/experimental/ui/ui.autocomplete.js branches/experimental/ui/ui.colorpicker.js
r932 - trunk/ui
Author: david.bolter Date: Thu Nov 13 08:24:44 2008 New Revision: 932 Modified: trunk/ui/ui.accordion.js Log: refactored keyboard handling to a switch statement for clarity. Modified: trunk/ui/ui.accordion.js ============================================================================== --- trunk/ui/ui.accordion.js (original) +++ trunk/ui/ui.accordion.js Thu Nov 13 08:24:44 2008 @@ -106,18 +106,18 @@ var currentIndex = this.options.headers.index(e.target); var toFocus = false;
r931 - in trunk: tests ui
Author: david.bolter Date: Thu Nov 13 07:51:09 2008 New Revision: 931 Modified: trunk/tests/accordion.js trunk/ui/ui.accordion.js Log: Added accordion keyboard and ARIA support, and tests. Mozilla needs this for website. (partial review: Scott González, fix for 3553) Modified: trunk/tests/accordion.js ============================================================================== --- trunk/tests/accordion.js (original) +++ trunk/tests/accordion.js Thu Nov 13 07:51:09 2008 @@ -129,4 +129,22 @@
Whitespace
Hey everyone, as you might remember, we recently had the discussion wether we should remove whitespace on empty lines or keep it. This email is <b>not</b> about deciding to go for one of them, but about something that hurts much more: In the past, there have been many commits that actually consisted of the following changes: 1) Changes to non-empty lines (normal changes, additions, removals) 2) Adding/removing whitespace on lines, without modifying something else on that particular line. Whenever
Removing the copyright information in the UI headers
Hi everyone, as a inbetween solution between the current confusing copyright information in file headers and the better solution to have a foundation as copyright holder (which we don't have yet), the team leads agreed that it makes sense to simply remove the information from all js file headers for now. <b>This is not a change to any of your copyrights</b> - it's just a visual representation change. Every code you've written and commited still is copyrighted by you, and always viewable using the
Next Page