fluid-work IRC Logs-2008-12-01

Owned by Fluid IRC Log Bot
Last updated: Dec 01, 2008Version comment
6 min read

[08:16:17 EST(-0500)] * Justin_o (n=Justin@142.150.154.101) has joined #fluid-work
[09:17:05 EST(-0500)] * jessm (n=Jess@c-76-19-199-61.hsd1.ma.comcast.net) has joined #fluid-work
[09:21:56 EST(-0500)] <jessm> 'morning Bosmon & Justin_o
[09:22:11 EST(-0500)] <Justin_o> good morning
[09:22:46 EST(-0500)] <Justin_o> jessm: hope you had a good thanksgiving
[09:22:58 EST(-0500)] <jessm> Justin_o: i did!
[09:23:36 EST(-0500)] <Justin_o> that's good... did you go shopping on friday?
[09:24:03 EST(-0500)] <jessm> Justin_o: i was doing my best to reinvigorate the global economy – short shopping trip – big sales!
[09:25:29 EST(-0500)] <Justin_o> thank you for doing your part for the global economy (smile)
[09:25:45 EST(-0500)] <Justin_o> I hear that sales are really good
[09:26:14 EST(-0500)] <jessm> Justin_o: yeah, it looked bleak on the streets, but I was in downtown, not in a mall and I think there's going to be a lot of online shopping this year
[09:27:55 EST(-0500)] <Justin_o> very true, online shopping is easier and cheaper
[09:36:00 EST(-0500)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[09:36:27 EST(-0500)] * anastasiac (n=team@142.150.154.160) has joined #fluid-work
[09:37:00 EST(-0500)] <jessm> 'morning anastasiac – how's Home Depot?!
[09:37:19 EST(-0500)] <anastasiac> 'morning jessm
[09:37:25 EST(-0500)] <anastasiac> Home Depot is getting richer and richer (smile)
[09:37:59 EST(-0500)] <anastasiac> we bough 6 range hoods and 30 feet of countertop
[09:38:05 EST(-0500)] <anastasiac> among other things
[09:38:31 EST(-0500)] <jessm> wow!
[09:38:36 EST(-0500)] <jessm> incredible volume
[09:45:46 EST(-0500)] * clown (n=clown@guiseppi.atrc.utoronto.ca) has joined #fluid-work
[09:48:46 EST(-0500)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[10:33:12 EST(-0500)] * michelled (n=team@142.150.154.197) has joined #fluid-work
[10:36:25 EST(-0500)] * athena7 (n=athena7@adsl-99-162-190-42.dsl.wlfrct.sbcglobal.net) has joined #fluid-work
[10:55:47 EST(-0500)] * phiggins (n=dante@74.11.156.6) has joined #fluid-work
[11:28:46 EST(-0500)] * lessthanzero (n=FatalRem@CPE001ff342457c-CM001ac352aefc.cpe.net.cable.rogers.com) has joined #fluid-work
[11:35:39 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[12:14:22 EST(-0500)] * phiggins (n=dante@74.11.156.6) has joined #fluid-work
[12:26:00 EST(-0500)] <clown> anyone: okay, I'm too lazy to look it up: what is the difference between the CSS selector [foo=bar] and [foo~=bar]? if you know off the top of your head, thanks in advance.
[12:29:58 EST(-0500)] * ecochran (n=ecochran@dhcp-169-229-212-28.LIPS.Berkeley.EDU) has joined #fluid-work
[12:34:15 EST(-0500)] <clown> well, i'm no longer lazy and looked up the answer. [foo=bar] means "attribute value for 'foo' exactly matches 'bar'", whereas [foo~=bar] means "attribute value for 'foo' contains 'bar'".
[12:34:54 EST(-0500)] <clown> eg. [foo=bar] will match <div for="bar" ...>
[12:35:30 EST(-0500)] <clown> eg. [foo~=bar] will match <div foo="snafu bar baz" ...>
[12:57:07 EST(-0500)] * phiggins (n=dante@74.11.156.6) has joined #fluid-work
[13:45:28 EST(-0500)] * apetro (n=apetro@74.11.156.6) has joined #fluid-work
[14:09:38 EST(-0500)] * michelled (n=team@142.150.154.197) has left #fluid-work
[14:11:47 EST(-0500)] * phiggins (n=dante@c-71-229-123-70.hsd1.fl.comcast.net) has joined #fluid-work
[16:29:18 EST(-0500)] <athena7> colin last week you'd linked me to an implementation of refresh(): http://fluid.pastebin.com/m3cfadb30
[16:29:31 EST(-0500)] <colinclark> athena7: Yep. Did it work for you?
[16:29:37 EST(-0500)] <athena7> do i need to copy that code into my javascript, or is the refresh method already available using that code?
[16:30:38 EST(-0500)] <athena7> i wasn't quite sure what to do with it when i got around to testing
[16:31:46 EST(-0500)] <colinclark> That method was added to Reorderer in Infusion 0.5, if I remember correctly.
[16:32:01 EST(-0500)] <colinclark> So you can just invoke it whenever you've modified the DOM.
[16:32:10 EST(-0500)] <athena7> hm, ok
[16:32:18 EST(-0500)] <athena7> it didn't seem to be working
[16:32:24 EST(-0500)] <colinclark> Interesting.
[16:32:40 EST(-0500)] <athena7> i'll try it again though
[16:32:49 EST(-0500)] <colinclark> Give it a shot. Let me know if it doesn't work.
[16:32:50 EST(-0500)] <athena7> so i'd just want to call "reorderer.refresh();"?
[16:33:02 EST(-0500)] <colinclark> It's an instance method...
[16:33:13 EST(-0500)] <colinclark> so if you init your Reorderer like this:
[16:33:22 EST(-0500)] <colinclark> var myReorderer = fluid.reorderLayout(...);
[16:33:29 EST(-0500)] <colinclark> You'll call myReorderer.refresh();
[16:33:58 EST(-0500)] <athena7> ok
[16:34:33 EST(-0500)] <athena7> nope, not getting it to work
[16:34:34 EST(-0500)] <athena7> hm.
[16:35:08 EST(-0500)] <athena7> is it likely to matter that we're using the columns/modules properties to set up the reorderer?
[16:35:26 EST(-0500)] <colinclark> I don't think so, no.
[16:35:42 EST(-0500)] <colinclark> Do you have a URL to uPortal trunk where it's being initialized?
[16:36:24 EST(-0500)] <athena7> the code itself? http://fluid.pastebin.com/m4f468bf7
[16:36:36 EST(-0500)] <colinclark> awesome
[16:36:42 EST(-0500)] <colinclark> That should do it.
[16:36:48 EST(-0500)] <colinclark> reorderer.refresh() whenever the DOM changes.
[16:37:33 EST(-0500)] <athena7> ok
[16:37:48 EST(-0500)] <athena7> so i tried calling that when a new column is added to the layout
[16:37:57 EST(-0500)] <athena7> and it is being called presumably, since the debug statement after it prints out
[16:38:09 EST(-0500)] <athena7> but i still can't drag anything into the new column
[16:38:46 EST(-0500)] <athena7> i double checked and the new column does have a class of "portal-page-column-inner"
[16:39:08 EST(-0500)] <athena7> any debugging steps you'd recommend?
[16:54:19 EST(-0500)] <colinclark> athena7: Sorry, missed your questions.
[16:54:22 EST(-0500)] <colinclark> let me catch up
[16:54:30 EST(-0500)] <athena7> sure (smile)
[17:40:44 EST(-0500)] * clown (n=clown@guiseppi.atrc.utoronto.ca) has left #fluid-work
[17:41:46 EST(-0500)] * jessm (n=Jess@c-76-19-199-61.hsd1.ma.comcast.net) has joined #fluid-work
[18:02:44 EST(-0500)] * phiggins (n=dante@c-71-229-123-70.hsd1.fl.comcast.net) has joined #fluid-work
[18:49:29 EST(-0500)] * Everett (n=Mirc4Lif@fctnnbsc16w-156034216002.pppoe-dynamic.nb.aliant.net) has joined #fluid-work
[18:56:07 EST(-0500)] * Everett (n=Mirc4Lif@fctnnbsc16w-156034216002.pppoe-dynamic.nb.aliant.net) has joined #fluid-work
[19:00:31 EST(-0500)] <Everett> Good evening
[19:00:53 EST(-0500)] <Everett> Can anyone tell me if Fluid supports a keyrepeat event trigger?
[19:01:03 EST(-0500)] <colinclark> Everett: Hey, how are you doing?
[19:01:07 EST(-0500)] <colinclark> I was just writing some code for you.
[19:01:27 EST(-0500)] <Everett> Oh, wonderful
[19:01:29 EST(-0500)] <colinclark> I just got it working and was about to send it off.
[19:01:39 EST(-0500)] <Everett> Thank you very much for your help with that.
[19:01:44 EST(-0500)] <colinclark> It was fun.
[19:02:00 EST(-0500)] <Everett> I think it's an essential part of having an ARIA web-chat.
[19:02:17 EST(-0500)] <colinclark> In short, if I understand what you need, you basically need to track key presses and store a bit of state.
[19:02:20 EST(-0500)] <Everett> It would allow for navigating the message history one message at a time without leaving the input field
[19:02:41 EST(-0500)] <Everett> Verymuch like Windows Messenger and JAWS using the tilda
[19:02:49 EST(-0500)] <colinclark> Cool, that makes sense.
[19:02:54 EST(-0500)] <colinclark> I'll email you the code.
[19:03:00 EST(-0500)] <colinclark> Since IRC is a drag for posting code snippets.
[19:03:21 EST(-0500)] <colinclark> It's just a sketch; you'll want to fill it in with more specifics. But it gives you the basic structure, anyway.
[19:03:28 EST(-0500)] <Everett> Particularily if you are using AT.
[19:03:35 EST(-0500)] <colinclark> I bet.
[19:03:43 EST(-0500)] <Everett> I haven't used IRC for 8 years until just now.
[19:03:57 EST(-0500)] <colinclark> Glad you were able to find us okay.
[19:04:07 EST(-0500)] <colinclark> I hadn't used IRC in a long time until I started on Fluid.
[19:04:31 EST(-0500)] <Everett> Do you know of anyone testing Fluid against Orca and Firefox?
[19:04:44 EST(-0500)] <colinclark> Not so far, no.
[19:05:17 EST(-0500)] <colinclark> I'd be curious how it goes. Orca's a fair bit further along than JAWS when it comes to ARIA support.
[19:05:26 EST(-0500)] <colinclark> I suspect we've got a lot of rough edges, too.
[19:06:13 EST(-0500)] <Everett> Aaron Leventhal and Will Walker (manages Orca) are interested in testing it against fluid, dojo, yahoo and google.
[19:06:34 EST(-0500)] <Everett> Once I get my Orca machine back up and running I may do some testing.
[19:06:34 EST(-0500)] <colinclark> Yeah, that makes a lot of sense.
[19:06:49 EST(-0500)] <colinclark> I think some of the Dojo folks have done some degree of testing with Orca.
[19:06:58 EST(-0500)] <Everett> That's good to know.
[19:06:58 EST(-0500)] <colinclark> That would be great.
[19:07:09 EST(-0500)] <colinclark> In the meantime, it's good to have you on the channel.
[19:07:20 EST(-0500)] <Everett> I think the tweaking will need to be on the Orca end. So much easier to get changes to Orca than to WE or JAWS.
[19:07:31 EST(-0500)] <colinclark> yes, definitely.
[19:07:39 EST(-0500)] <colinclark> Would you also put NVDA into that category?
[19:07:43 EST(-0500)] <colinclark> Do they share code at all?
[19:08:45 EST(-0500)] * jessm (n=Jess@c-76-19-199-61.hsd1.ma.comcast.net) has joined #fluid-work
[19:08:45 EST(-0500)] <Everett> No, I don't think they share code. They go about things quite differently. As I understand it NVDA uses MSAA and COM automation whereas Orca uses AT-SPI, a gnome AT framework
[19:09:43 EST(-0500)] <colinclark> Yes, that makes sense.
[19:10:13 EST(-0500)] <Everett> No, I don't think they share code. They go about things quite differently. As I understand it NVDA uses MSAA and COM automation whereas Orca uses AT-SPI, a gnome AT frameworkThe furstrating thing is that Orca is coded in py which is complicated to use for the blind. I think there may be a couple of good editors. py is really strangely dependent on indentation.
[19:10:32 EST(-0500)] <colinclark> Yes, Python's whitespace would be a challenge.
[19:12:05 EST(-0500)] <Everett> Well, thanks for the code and I'll let you know if I have any other questions. If you have any parts of Fluid that you would be most interested to see tested against Orca send me a list or perhaps some sites that implement those particular widgets.
[19:12:13 EST(-0500)] <colinclark> Sounds great.
[19:12:19 EST(-0500)] <Everett> ok, later
[19:12:21 EST(-0500)] <colinclark> I'll respond to your other email tomorrow when I get some time.
[23:03:45 EST(-0500)] * apetro (n=apetro@74.11.156.6) has joined #fluid-work