(10:43:09 AM) davidserduke: rworth: are there any pages in the docs that you feel are pretty updated?
(10:45:28 AM) xover [n=xover@pounder.neutri.no] entered the room.
(10:46:27 AM) davidserduke: looking at UI/Draggables it appears the methods section is updated but the demo is using the API and code
(10:47:53 AM) rworth: davidserduke: I don't have a good feel anymore
(10:50:48 AM) davidserduke: ok
(10:51:48 AM) davidserduke: i'm going to head out for my first meeting. I think I'll be able to continue reviewing the code while I'm in it. I should be back in a couple hours I hope then be around for at least a few more hours working
(10:52:35 AM) davidserduke: if anyone is able to make some changes to the UI/Guidelines page make a comment here and/or update the team wiki page
(10:52:41 AM) davidserduke is now known as davidserduke_awa
(1:00:00 PM) ***rworth sees that davidserduke just said he's going to ;)
(1:00:11 PM) rworth: davidserduke: go ahead
(1:00:11 PM) davidserduke: heh
(1:00:22 PM) davidserduke: will do. i'll let you know when i have something to review
(2:00:38 PM) davidserduke: rworth: when you get a chance if you could check setters/getters section of the UI/Guidelines to see if it is ok
(2:01:23 PM) ***rworth looks
(2:01:32 PM) davidserduke: i think i might have to document $().data() because I don't see it in the core documentation atm
(2:01:44 PM) davidserduke: do you think that is where it should go? jQuery Core?
(2:02:10 PM) rworth: it's in internals
(2:02:19 PM) davidserduke: the internals one is jquery.data()
(2:02:22 PM) davidserduke: which is a bit different
(2:02:29 PM) rworth: oh, you're right
(2:02:38 PM) rworth: I noticed yesterday that the new one wasn't documented yet
(2:02:52 PM) davidserduke: i'll do that next
(2:02:56 PM) rworth: umm, yeah, I guess core
(2:03:04 PM) davidserduke: k
(2:03:13 PM) davidserduke: look ok?
(2:03:22 PM) rworth: still reading
(2:05:26 PM) rworth: davidserduke: maybe say $(...).data() function instead of $.data()? otherwise it confuses with jQuery.data()
(2:05:38 PM) davidserduke: yeah, definitely
(2:05:46 PM) rworth: other than that, looks good
(2:06:13 PM) davidserduke: k, i'll move on to data next then come back
(2:06:42 PM) rworth: k
(2:17:15 PM) scott_gonzalez: is someone handling the docs for dialog?
(2:19:06 PM) rworth: not at the moment
(2:19:26 PM) rworth: we should add a section on the wiki for people to claim modules
(3:00:34 PM) c_t [n=c_t@e178001175.adsl.alicedsl.de] entered the room.
(3:01:18 PM) rworth: c_t: welcome
(3:01:36 PM) c_t: hi
(3:02:23 PM) davidserduke: ok, i just finished a somewhat decent version of the $().data() and $().removeData() functions
(3:03:37 PM) rworth: davidserduke: looks great
(3:03:58 PM) ***rworth crowns davidserduke the documentation wiz
(3:04:04 PM) davidserduke: rworth: so the only stubbed out section of the Guidelines appears to be the plugin.add, etc
(3:04:05 PM) davidserduke: lol
(3:04:13 PM) davidserduke: a dubious honor :)
(3:05:21 PM) davidserduke: rworth: in any case, can you give me quick any tips on plugin.add, call, css, and hasScroll? I can look at the code but a quick flyby from you would help me a lot
(3:05:58 PM) rworth: davidserduke: I'd leave those for Paul (or at least until he gets back). Let's start going through plugins. Would you mind making a list on the sprint-docs page and we can start calling them
(3:07:20 PM) davidserduke: rworth: ok, i do have another hopefully quick question. what is the delineation between something in ui.plugin.js and ui.plugin.ext.js
(3:07:34 PM) davidserduke: do those need to be documented separately?
(3:08:42 PM) rworth: davidserduke: that's a good question. The ext ones being in their own file allow you to have a stripped down/simple version of the plugin by just leaving out one file
(3:09:14 PM) davidserduke: makes sense
(3:09:29 PM) rworth: I think that'll depend on whether or not the package/download manager gives you the option
(3:09:46 PM) davidserduke: so document them together for now?
(3:09:48 PM) rworth: otherwise someone can just look inside the file and see what's in it
(3:09:54 PM) rworth: Unless it's packed of course
(3:10:00 PM) rworth: yeah
(3:10:03 PM) davidserduke: k
(3:10:11 PM) rworth: but let's bring this up with Paul
(3:14:26 PM) rworth: **General Reminder** all: when you create a UI ticket, set the component field to 'UI' and put the plugin name in square brackets at the beginning of the summary
(3:28:53 PM) davidserduke: i set up a section on the sprint/docs where people can sign up for a section. I'm not sure if scott_gonzalez was signing up for dialog or not
(3:29:30 PM) scott_gonzalez: I justed wanted to inform whoever it is that there are new, undocumented, options
(3:29:38 PM) davidserduke: ahh ok
(3:29:44 PM) davidserduke: i won't pencil you in then :)
(3:30:16 PM) scott_gonzalez: ...if I ever finish coding them :-P
(3:30:20 PM) davidserduke: heh
(3:30:40 PM) davidserduke: i think i'll sign myself up for draggables and see how I do with that
(3:31:23 PM) rworth: davidserduke: I'll do the draggables unit test writing at the same time. We can collaborate
(3:32:00 PM) davidserduke: k. i probably won't start for about an hour
(3:32:06 PM) rworth: k
(3:32:08 PM) davidserduke: i'll let you know when i'm on it
(3:33:14 PM) davidserduke: i need to grab something to eat. hopefully back in about an hour
(3:33:31 PM) davidserduke left the room (quit: "ChatZilla 0.9.81 [Firefox 2.0.0.12/2008020121]").
(3:59:22 PM) ***rworth away for 30min
(4:22:08 PM) pbakaus [n=paulbaka@p5799EF86.dip.t-dialin.net] entered the room.
(4:22:42 PM) pbakaus: hey everyone
(4:23:44 PM) pbakaus: davidserduke_awa: could you give me a note when you come back? I wanted to talk to you about the guidelines
(4:26:01 PM) braeker_ left the room (quit: "ircN 8.00 for mIRC (20080313) - www.ircN.org").
(4:30:34 PM) ***rworth is back
(4:33:26 PM) pbakaus: welcome back :)
(4:37:55 PM) rworth: thanks :)
(4:48:17 PM) c_t left the room (quit: Remote closed the connection).
(5:05:26 PM) davidserduke_awa is now known as davidserduke
(5:05:49 PM) davidserduke: i'm semi back atm
(5:06:04 PM) rworth: davidserduke: I guess you missed Paul
(5:06:04 PM) davidserduke: pbakaus: back if you are around
(5:06:28 PM) scott_gonzalez: Paul's gone for the night
(5:06:33 PM) davidserduke: any idea what he wanted?
(5:06:48 PM) scott_gonzalez: nope
(5:07:15 PM) scott_gonzalez: although, I do know something important for the guidelines
(5:07:30 PM) davidserduke: yeah?
(5:07:56 PM) scott_gonzalez: all the comments about stuff like this: jQuery.data(DOMelement, "ui-draggable")
(5:08:02 PM) scott_gonzalez: needs to become: jQuery.data(DOMelement, "draggable")
(5:08:08 PM) scott_gonzalez: (drop the ui- prefix)
(5:08:34 PM) scott_gonzalez: check out the dev sprint wiki page
(5:08:36 PM) scott_gonzalez: first section
(5:08:38 PM) davidserduke: hmm, the ui- is what is currently in the code. dd that jsut change>
(5:08:43 PM) davidserduke: ahh k
(5:08:57 PM) scott_gonzalez: yeah, just changed two minutes ago
(5:09:18 PM) pbakaus left the room (quit: Read error: 104 (Connection reset by peer)).
(5:11:06 PM) davidserduke: k, that change is made
(5:13:00 PM) davidserduke: rworth: ok, i'm going to start doc'ing draggables. i think i have about 2 hrs before my next meeting
(5:13:22 PM) davidserduke: course first i have to learn it :)
(5:16:49 PM) rworth: davidserduke: Sounds good. I have to go for about 2 hrs. So I'll be back around when you leave ;)
(5:17:12 PM) davidserduke: haha! have fun :)
(5:20:27 PM) pbakaus [n=paulbaka@p5799EF86.dip.t-dialin.net] entered the room.
(5:20:41 PM) davidserduke: welcome back :)
(5:22:25 PM) davidserduke: pbakaus: btw, i'm here if you still need to talk to me. if not, sleep well
(5:28:03 PM) Miksago: heyas
(5:28:49 PM) davidserduke: hi
(5:29:26 PM) Miksago: so what are we doing?
(5:29:37 PM) davidserduke: in documentation?
(5:29:47 PM) davidserduke: i'm working on draggables atm
(5:39:55 PM) Miksago: i think i'll go shiny side up
(5:40:29 PM) davidserduke: you get a nice rainbow that way when the light hits it just right
(5:40:48 PM) davidserduke: so... any chance you understand this plugins.add start/stop code?
(5:40:54 PM) davidserduke: it looks like getter/setters
(5:41:03 PM) davidserduke: sort of
(5:41:13 PM) Miksago: hmm..
(5:41:17 PM) Miksago: lemme
(5:41:32 PM) Miksago: see.. draggables you said?
(5:41:45 PM) davidserduke: yeah, although i suspect that code is for any plugin
(5:42:27 PM) davidserduke: i wrote the UI/Guidelines getters/setters using $(...).data() but looking at this code i suspect there is more to it than that
(5:42:43 PM) davidserduke: that's probably what paul wanted to talk to me about heh
(5:43:19 PM) Miksago: suppose i should svn sync before opening the file
(5:45:52 PM) davidserduke: hmm, ok i sort of see how this works
(5:46:34 PM) davidserduke: it's an automatic getter and setter for the actually draggable object
(5:47:27 PM) davidserduke: so you can have something with various options then when you click to drag it the css can completely change to reflect the options and get set back when you drop
(5:52:40 PM) Miksago: hmmm.
(5:54:37 PM) davidserduke: i'm not sure i understand why there is draggable code in ui.mouse.js
(5:55:55 PM) davidserduke: actually it looks like it's just firing events so i guess if the draggable code isn't included those will just be ignored
(5:56:27 PM) pbakaus left the room (quit: ).
(5:56:57 PM) Miksago: there is a mouse event called drag
(5:57:02 PM) davidserduke: seems a bit of an odd way to set it up
(5:57:46 PM) Miksago: that's because multiple plugins may use drag
(5:58:35 PM) davidserduke: yeah i can see that
(5:58:45 PM) davidserduke: and it makes sense, but
(5:59:10 PM) davidserduke: i'd think the namespace should be like mouseup.mouse
(5:59:14 PM) davidserduke: not mouseup.draggable
(5:59:32 PM) Miksago: talk to rworth or paul about it
(5:59:50 PM) davidserduke: i think i'm just going to go ahead and start writing some simple demos for the wiki
(6:00:06 PM) davidserduke: paul is sleeping. rworth said he'd be back in another hour or so
(6:00:31 PM) davidserduke: i'm sure there is a good reason for everything. it's just i'm not sure what it is yet hehe
(6:06:30 PM) Miksago: k
(6:06:39 PM) Miksago: i'm gunna start working on toolbars
(6:06:43 PM) Miksago: (again)
(6:54:08 PM) ajtrichards [i=mrpink@78.150.47.181] entered the room.
(7:08:28 PM) ajtrichards left the room (quit: ).
(8:13:43 PM) neojp [n=chatzill@190.42.179.65] entered the room.
(8:34:53 PM) rworth: I'm back :)
(8:38:26 PM) digitalspaghetti [i=digitals@drupal.org/user/88490/view] entered the room.
(9:10:47 PM) digitalspaghetti is now known as ds|zzz
(9:11:18 PM) ThrushAAX [n=Thrush@dhcp-41-17.njit.edu] entered the room.
(9:54:47 PM) davidserduke: rworth: back again
(9:57:35 PM) davidserduke: gah, i'm wrestling with some wiki problem where I can't get more than one example to work on the draggables wiki page. i've done it on other pages though!
(9:58:50 PM) rworth: davidserduke: hmm
(9:59:52 PM) davidserduke: for some reason it will only run the document ready code for the last example
(9:59:55 PM) davidserduke: weird...
(10:01:09 PM) davidserduke: hmm, actually it's just failing on the first one when i have 3 examples
(10:12:09 PM) davidserduke left the room (quit: Read error: 104 (Connection reset by peer)).
(10:13:53 PM) davidserduke [n=chatzill@adsl-71-131-8-173.dsl.sntc01.pacbell.net] entered the room.
(10:14:56 PM) davidserduke: so sad, sometimes i forget my own rule #1. if something weird is happening reboot
(10:16:04 PM) davidserduke: luckily firefox crashed on me and forced me to so now i can move on heh
(10:16:18 PM) rworth: heh
(10:53:07 PM) neojp left the room (quit: "ChatZilla 0.9.81 [Firefox 2.0.0.12/2008020121]").
(11:09:51 PM) braeker_ [n=braeker@189.70.117.168] entered the room.
(11:22:48 PM) davidserduke left the room (quit: "ChatZilla 0.9.81 [Firefox 2.0.0.12/2008020121]").
(12:50:50 AM) Miksago left the room (quit: Read error: 104 (Connection reset by peer)).
(12:51:37 AM) Miksago [n=miksago@124-171-35-236.dyn.iinet.net.au] entered the room.
(1:46:10 AM) Byron [n=byron@125-238-204-252.broadband-telecom.global-gateway.net.nz] entered the room.
(2:02:24 AM) Byron is now known as Byron54
(2:48:10 AM) Byron54 left the room.
(3:19:27 AM) antares [n=antares@82.193.101.94.ipnet.kiev.ua] entered the room.
(3:44:17 AM) antares left the room (quit: Read error: 104 (Connection reset by peer)).
(3:45:06 AM) antares [n=antares@82.193.101.94.ipnet.kiev.ua] entered the room.
(4:00:38 AM) antares left the room (quit: Read error: 104 (Connection reset by peer)).
(4:00:53 AM) antares_ [n=antares@82.193.101.94.ipnet.kiev.ua] entered the room.
(4:13:26 AM) antares_ left the room (quit: "kernel trap").
(4:16:18 AM) pbakaus [n=paulbaka@p5799E32D.dip.t-dialin.net] entered the room.
(4:36:56 AM) pbakaus left the room (quit: ).
(4:37:05 AM) pbakaus [n=paulbaka@p5799E32D.dip.t-dialin.net] entered the room.
(4:39:32 AM) pbakaus is now known as paulBakaus
(4:39:56 AM) paulBakaus is now known as sdfsdf
(4:42:20 AM) sdfsdf left the room (quit: ).
(4:43:02 AM) p_bakaus [n=paulbaka@p5799E32D.dip.t-dialin.net] entered the room.
(6:01:14 AM) ds|zzz is now known as digitalspaghetti
(8:07:40 AM) xover: Where is the documentation being worked on? Live edits on the wiki page, or is there a master in SVN somewhere? Any form of staging going on?
(8:10:47 AM) Miksago: braeker_, rworth ^^
(8:11:14 AM) xover: I see p_bakaus and davidserduke are the only two with assigned docs tasks.
(8:11:44 AM) xover: Hmm. It's probably too early yet in the `merki time zones.
(8:11:52 AM) p_bakaus: I have a doc task assigned? ugh
(8:11:54 AM) Miksago: paul's out for food
(8:11:56 AM) p_bakaus: lol
(8:11:57 AM) Miksago: or was
(8:12:02 AM) xover: heh heh
(8:12:04 AM) ***p_bakaus is now out for food
(8:12:10 AM) Miksago: lolwat.
(8:13:13 AM) rworth: xover: all documentation is on the wiki
(8:13:35 AM) rworth: xover: staging is on the wiki too ;)
(8:14:16 AM) xover: Yeah, but is the document edited live, or is there a separate staging copy that gets moved to the live docs after review; or some workflow like that?
(8:14:25 AM) rworth: xover: it's all live
(8:14:31 AM) xover: Coolio.
(8:15:34 AM) rworth: xover: After the realease we'll probably segment future docs (1.6, 1.7) so that we don't step on current docs during dev
(8:16:55 AM) xover: Any thoughts along the lines of separating API Reference type documentation from End User / User Manual type documentation?
(8:18:28 AM) xover: It's just… I found the unit tests page for .dialog() easier to understand then the docs qua docs for it.
(8:20:16 AM) xover: And I speculate that it's because the latter is somewhat of a hybrid between pure API reference and end user docs.
(8:20:35 AM) xover: Anyways, I digress… :-)
(8:26:56 AM) xover: rworth: You the one coordinating docs? Should I feel free to jump in and do some minor editing?
(8:27:27 AM) xover: (specifically, adding some undocumented options to the .dialog() page based on the unit tests for it)
(8:28:59 AM) rworth: xover: I'm glad you found the unit test page easy to understand. :) I think in a lot of ways, it will always play that role (at least for developers). Unit tests are like that - great examples.
(8:29:35 AM) rworth: xover: and yes, the full docs is sort of a hybrid, but it should be complete. There isn't anything that shouldn't go in there
(8:30:25 AM) rworth: xover: feel free, yes. Jump in. Make changes. And I'm glad you're finding (as I have) that the unit test page is a great test of the docs themselves.
(8:30:45 AM) xover: Ah, will do.
(8:31:14 AM) xover: Also, I suspect the unit tests are much much easier to get the developers to write, than actual documentation.
(8:32:30 AM) rworth: And when they're done, the docs are half done (at least the API reference portion)
(8:32:42 AM) xover: Yeah.
(8:33:02 AM) Miksago: xover: be sure to check out the demo viewer when it's finished
(8:33:03 AM) xover: And they help probably as much with coming up with functional demos.
(8:33:13 AM) xover: Miksago: URL?
(8:33:30 AM) Miksago: it's the functional demos
(8:33:58 AM) Miksago: demo viewer is sorta with in the demo's group
(8:33:59 AM) rworth: Yeah, I wonder if we won't do some sharing there. The functional demos are almost slimmed down unit tests with a little better presentation
(8:34:21 AM) Miksago: rworth: soon really good presentation :D
(8:34:28 AM) rworth: :)
(8:34:48 AM) Miksago: i need more coffee.
(8:35:05 AM) Miksago: though i think i should go for tea..
(8:35:06 AM) Miksago: bbs
(8:43:12 AM) Miksago: back
(8:43:20 AM) xover: wb
(8:43:34 AM) Miksago: cheers
(8:44:31 AM) brianpeiris_away is now known as brianpeiris
(8:46:58 AM) xover: rworth: Did I take you to imply you were the one who put together the .dialog() unit test page?
(8:48:42 AM) xover: In any case, looking at it with an eye to completing the docs for .dialog(), I note that the subsections don't have a test for default behaviour.
(8:49:14 AM) xover: e.g. all the tests under draggable explicitly set the property.
(8:49:26 AM) xover: Ditto for at least a few others.
(8:49:47 AM) Miksago: uh, xover do you know what to run to run the tests?
(8:50:06 AM) digitalspaghetti: morning folks
(8:50:20 AM) xover: Miksago: Assume I'm clueless and have no idea what I'm doing. You won't be offby much, I assure you. :-)
(8:50:22 AM) Miksago: wait.
(8:50:32 AM) Miksago: sorry, i'm stupid. i didn't click the links
(8:50:33 AM) xover: `morning.
(8:51:29 AM) digitalspaghetti: so what needs to be done at the moment?
(8:52:36 AM) xover: digitalspaghetti: For Docs, it looks like the answer is “Everything, except the UI/Guidelines”, but I may very well be wrong.
(8:53:06 AM) ***Miksago has tried to keep the keynotes up to date
(8:53:18 AM) Miksago: however, people haven't assigned roles/jobs.
(8:54:20 AM) digitalspaghetti: well if there is any code stuff to work on (the other channels are quite quiet just now)
(8:54:57 AM) rworth: anyone can grab a section of docs to review/update
(8:55:07 AM) rworth: just add your name to the wiki to keep from duplicating
(8:55:27 AM) xover: digitalspaghetti: If you want code-related, perhaps unit tests? Since they seem very very usefull for everything from docs to dev to examples.
(8:55:30 AM) rworth: xover: yeah, I did the dialog and draggable test pages. I'm not sure I understand your last question, about default behavior?
(8:55:43 AM) javam [n=pc@78.160.64.35] entered the room.
(8:55:44 AM) digitalspaghetti: yea, i can write some tests, or some demos
(8:56:00 AM) rworth: digitalspaghetti: demos seems to have a lot of help. I could use some help in test
(8:56:31 AM) xover: rworth: The section for the draggable option doesn't have a test where draggable is left at default; all four tests explicitly set it.
(8:56:46 AM) digitalspaghetti: cool rworth, i'll make sure my trunk is up to date. I think I grabbed the dev.jquery one instead of the google code one, i better grab that so i have my write permissions
(8:57:08 AM) xover: rworth: Mainly I noticed because I came at it from the docs side; I was trying to see what it's default value actually was.
(8:57:54 AM) rworth: xover: no, the default test is simply calling .draggable()
(8:58:13 AM) xover: right
(8:58:19 AM) rworth: that is, it's a test of the default options, and that it can be called (and functional) without any explicit options
(8:59:21 AM) xover: Put another way: I may be on crack, but I noticed the .draggable() test up in the default section wasn't repeated down in the draggable section.
(8:59:34 AM) xover: And the fact that I noticed means that for some reason I /expected/ it to be there.
(8:59:49 AM) xover: Not that that necessarily means anything except that my brain works in weird ways. :-)
(9:00:47 AM) xover: Feel free to summarily disregard any and all such observations from my deranged mind. :-)
(9:03:29 AM) digitalspaghetti: rworth, ok i've grabbed the google code copy, so i've got my write access, where do you want me to start?
(9:35:45 AM) xover: Hmm. How do you represent an option that can take both Number and Array as arguments in the docs?
(9:36:03 AM) xover: The MW template doesn't make that obvious.
(9:36:51 AM) rworth: digitalspaghetti: let's talk in #jquery-sprint-test
(9:36:57 AM) xover: Ah. “Number, Array" seems to be the syntax. Nevermind.
(10:15:49 AM) xover: @@FIXME: Figure out the Options for the overlay option to .dialog();
(10:16:59 AM) scott_gonzalez: xover: overlay is a CSS hash
(10:17:13 AM) scott_gonzalez: any settings you want to use for the overlay div of a modal dialog
(10:18:59 AM) xover: Hmm.
(10:19:33 AM) xover: Is the “CSS hash” documented anywhere?
(10:21:09 AM) digitalspaghetti: xover, what OS/Language you on?
(10:21:11 AM) rworth: scott_gonzalez: I noticed you're making a lot of API consistency changes. Thanks! :)
(10:21:19 AM) digitalspaghetti: i'm getting some weird unicode chars here
(10:21:38 AM) rworth: scott_gonzalez: be sure to let us know if/when any docs need to be updated, if you need help
(10:21:39 AM) xover: digitalspaghetti: On IRC? Yeah, sorry; force of habit. I'm sending raw UTF-8 on IRC.
(10:21:53 AM) scott_gonzalez: yup, that's gonna need to be tested :-P
(10:21:57 AM) xover: (which not all IRC clients cope with very well)
(10:22:32 AM) scott_gonzalez: I'm not sure if any of the test suites bind to events
(10:22:52 AM) scott_gonzalez: I'm about to bring it up in the test channel once I'm done reviewing some code
(10:22:58 AM) rworth: k
(10:23:05 AM) digitalspaghetti: the test suite doesn't work with sliders :/
(10:23:25 AM) digitalspaghetti: i've just committed the start of it, but it doesn't produce sliders
(10:23:42 AM) ***xover punts on overlay for now...
(10:24:24 AM) scott_gonzalez: xover: sorry, wasn't paying attention to this channel - standard .css() call
(10:33:56 AM) xover: scott_gonzalez: Thanks. I'll try to figure out how to document it on my next pass through the page (working on updating the docs for .dialog() based on the unit tests page).
(10:34:12 AM) scott_gonzalez: ok
(10:35:01 AM) scott_gonzalez: maybe to give a better idea, the most common use would be something like: $(el).dialog({ modal: true, overlay: { backgroundColor: '#000', opacity: 0.5 } })
(10:38:41 AM) xover: Hmm. Following that trail leads me to .css(), which says map', which further leads to name/value as String/String or Number.
(10:39:10 AM) xover: Are the various properties you can use there from the W3C DOM spec? Or the CSS spec, possibly?
(10:39:26 AM) scott_gonzalez: yeah, any valid CSS property
(10:39:52 AM) scott_gonzalez: height, width, color, overflow, etc.
(10:40:31 AM) xover: Yeah, but the unit tests use backgroundColor and the CSS property would be background-color. Where is that mapping actually defined? Is the former a jQuery thing? A general JavaScript thing?
(10:41:31 AM) xover: Or does one of the W3C CSS or DOM specs say "The CSS property 'foo-bar' is exposed in JavaScript/DOM as 'fooBar'"?
(10:42:02 AM) xover: Oh, hey; this wouldn't be the "W3C Selectors API" thing, would it?
(10:44:57 AM) neojp [n=chatzill@190.42.179.65] entered the room.
(10:46:10 AM) scott_gonzalez: backgroundColor is defined in jQuery
(10:46:26 AM) scott_gonzalez: because if you use background-color as a JavaScript property name, you must quote it
(10:46:44 AM) scott_gonzalez: so you can do {backgroundColor: "blue"} or {"background-color": "blue"}
(10:47:41 AM) xover: Hmm. Ok, so the difference is simply that jQuery has defined some convenience names? e.g. I can say "plain CSS properties + see .css() for convenience names"?
(10:51:09 AM) p_bakaus: [announcement]: the draggable option dragPrevention is no changed to 'cancel', please update the appropriate docs
(10:53:16 AM) scott_gonzalez: xover: see current discussion in #jquery-sprint-dev
(10:53:49 AM) xover: thanks
(10:54:01 AM) scott_gonzalez: you're welcome
(10:56:00 AM) rworth: p_bakaus: thanks. Done
(10:59:22 AM) digitalspaghetti left the room (quit: " HydraIRC -> http://www.hydrairc.com <- IRC with a difference").
(11:00:59 AM) xover: scott_gonzalez: Take a look at the overlay' option on <http://docs.jquery.com/UI/Dialog/dialog>. Ignoring my awkward prose, does that description look ok (at least factually correct)?
(11:02:06 AM) scott_gonzalez: I would remove the first and third sentences
(11:02:15 AM) scott_gonzalez: the overlay is automatically produced when modal is set to true
(11:02:31 AM) scott_gonzalez: it's just that by default it's transparent with 100% opacity
(11:02:43 AM) xover: Hmm.
(11:03:03 AM) scott_gonzalez: because it's just <div class="ui-dialog-overlay" />
(11:03:18 AM) xover: But you can have overlay even when modal is false?
(11:03:30 AM) scott_gonzalez: you can specify it, but it won't do anything
(11:03:55 AM) xover: Hmm. So overlay' should perhaps be documented as part of the modal option?
(11:04:18 AM) scott_gonzalez: I'm not sure what the plan is for dependent options
(11:04:26 AM) scott_gonzalez: maybe you should ask rworth and p_bakaus about that
(11:04:44 AM) scott_gonzalez: there are other options too, like dragStart, drag, dragStop are all dependent on draggable being set to true
(11:05:43 AM) xover: Hmm. Those seem to be missing unit tests.
(11:06:20 AM) scott_gonzalez: indeed, I added them yesterday
(11:06:29 AM) scott_gonzalez: also resizeStart, resize, resizeStop
(11:07:00 AM) rworth: xover: modal option should mention overlay, sure. But the options should stay in alpha-order and be documented each on their own
(11:07:52 AM) xover: Ok. I'll try to come up with some way to indicate the dependant relationship in prose.
(11:08:30 AM) xover: Anyone working on adding unit tests for the resize/drag options?
(11:09:01 AM) rworth: xover: I'm doing dialog unit tests. I'll add those
(11:09:09 AM) scott_gonzalez: not sure, rworth is in charge of tests and should know about the new options, but I'll make an announcement in the tests channel just in case
(11:15:16 AM) xover: (modal and overlay both updated)
(11:23:56 AM) franciscallo [n=RT-TEY@adsl-75-30-180-214.dsl.pltn13.sbcglobal.net] entered the room.
(12:00:05 PM) xover: Ok, .dialog()'s options documentation is now updated with all the options that're currently in uiTest. dialog (i.e not the new drag*/resize*).
(12:01:12 PM) xover: Will have a go at Draggable next, if that's not too advanced for me.
(12:03:30 PM) xover: Hmm. I should probably check with davidserduke on that first.
(12:08:53 PM) rworth: xover: Since he's not around, I say go for it
(12:09:48 PM) xover: Will do.
(12:10:21 PM) xover: Mostly I'm just doing mechanical translation from the unit tests pages, so there shouldn't be any significant edit conflicts or similar anyway.
(12:15:40 PM) braeker_ left the room (quit: "ircN 8.00 for mIRC (20080313) - www.ircN.org").
(12:23:27 PM) ***rworth eats lunch
(12:34:00 PM) scott_gonzalez: xover: dialog looks fine
(12:34:25 PM) xover: scott_gonzalez: Thanks.
(12:41:23 PM) erh [i=eburhan@88.251.17.237] entered the room.
(12:42:59 PM) ThrushAAX: I assume you guys know that the zIndex option is missing on the dialog page?
(12:47:24 PM) xover: ThrushAAX: No. Thanks!
(12:48:24 PM) ThrushAAX: np, just had a question about it in #jquery-ui, and I checked the docs and it was missing
(12:48:54 PM) xover: That's because it's missing from the unit test page. rworth: You'll fix, perhaps?
(1:28:27 PM) rworth: xover: yes. thanks
(1:43:08 PM) erh left the room.
(1:59:46 PM) p_bakaus: [announcement] draggable option cursorAt now also accepts an array in the format [left, top]
(2:12:58 PM) xover: p_bakaus: Docs updated for [top, left] syntax.
(2:13:08 PM) p_bakaus: great, thanks
(2:13:21 PM) p_bakaus: I have a special task
(2:13:38 PM) p_bakaus: could someone document the snap plugin? (actually, I don't know if I did it already)
(2:14:12 PM) xover: There is a snap plugin? :-)
(2:14:24 PM) neojp: snap was a plugin?
(2:14:31 PM) neojp: or an extension?
(2:15:20 PM) p_bakaus: it's a extension for draggables
(2:16:48 PM) p_bakaus: it seems I documented it already :)
(2:17:14 PM) xover: Well there you go then. :-)
(2:38:21 PM) kswedberg [n=kswedber@c-71-205-185-23.hsd1.mi.comcast.net] entered the room.
(2:38:30 PM) rworth: The king has returned!
(2:38:36 PM) kswedberg: hahaha!
(2:38:43 PM) ***rworth bows
(2:38:53 PM) kswedberg: rworth: oh, stop it.
(2:38:57 PM) rworth: ok ;)
(2:39:04 PM) kswedberg: :)
(2:39:05 PM) rworth: glad you could join us
(2:39:34 PM) rworth: I actually haven't been around too much in -docs today. Been busy with test and dev
(2:39:46 PM) kswedberg: thx. glad to be here.
(2:39:51 PM) rworth: Take a look at the wiki page to find a section no one has snagged yet
(2:39:52 PM) kswedberg: cool deal.
(2:39:56 PM) kswedberg: will do
(2:40:22 PM) kswedberg: btw. I pulled down the latest svn last night, but couldn't get the ui/apps/ stuff running because it was looking for /ui/current/... am I doing something wrong?
(2:40:37 PM) rworth: no, that's beyond rotted
(2:40:59 PM) rworth: the new stuff is in ui/demos/real-world
(2:41:41 PM) rworth: p_bakaus: you planning on resurrecting the 1.0 app?
(2:42:05 PM) kswedberg: ah. ok. good to know. thought I was losing my mind. ;) on to the wiki!
(2:42:38 PM) rworth: kswedberg: A lot of people have been using the docs side-by-side with the unit tests, to ensure coverage+clarity. I recommend this, if it works for you
(2:43:02 PM) rworth: the unit tests are in ui/tests/uiTest.*
(2:43:33 PM) kswedberg: beautiful. thanks!
(2:43:33 PM) p_bakaus: rworth: you mean the image gallery?
(2:43:46 PM) rworth: kswedberg: of course they're still being written, so there may not be one for you (yet)
(2:44:01 PM) rworth: p_bakaus: yeah. kswedberg was just asking about it, caus it's pointing to /ui/current
(2:44:02 PM) kswedberg: rworth: k. no prob.
(2:48:08 PM) rworth: Anyone have an idea how we might document which options can be set after initialization?