fluid-work IRC Logs-2012-04-04

[04:02:37 CDT(-0500)] <kasper> Mr. Bosmon! are you still alive?

[09:04:43 CDT(-0500)] <jhung> jvass, jameswy: an interesting article on the creation and design of Flupboard for iPhone. http://craigmod.com/journal/digital_physical/

[09:16:25 CDT(-0500)] <Daniel_> any mentors online?

[09:17:36 CDT(-0500)] <anastasiac> jameswy, any ETA on wireframes for the AfA metadata stuff?

[09:19:02 CDT(-0500)] <jameswy> anastasiac: Anytime if you want to look at my screen or at the repo; sometime this morning for an early copy on the wiki; and by EOD tomorrow for all the strings.

[09:22:55 CDT(-0500)] <jhung> Hi Daniel_

[09:23:15 CDT(-0500)] <jhung> I'm one of the mentors for the HTML5 Image Editor project

[09:23:28 CDT(-0500)] <jhung> Anything I can help you with?

[09:23:50 CDT(-0500)] <Daniel_> hey jon, I'm ready to submit my proposal

[09:24:06 CDT(-0500)] <Daniel_> Do i put my resume into google to or do i mail that to you?

[09:24:51 CDT(-0500)] <jhung> Resume + Cover letter is emailed to us. The application / proposal goes to the GSoC site, Daniel_

[09:25:56 CDT(-0500)] <Daniel_> ok thats cool. Do I send it straight to you or via the info email adress

[09:27:20 CDT(-0500)] <jhung> To info email address and CC justin_o and I (so 3 copies).

[09:28:24 CDT(-0500)] <Daniel_> ok got it

[09:28:38 CDT(-0500)] <jhung> great. Any thing else?

[09:28:45 CDT(-0500)] <Daniel_> nope

[09:28:52 CDT(-0500)] <Daniel_> thanks for the help jon

[09:29:08 CDT(-0500)] <jhung> No problem Daniel. Good luck!

[09:32:42 CDT(-0500)] <kasper_> Bosmon: ping

[10:07:34 CDT(-0500)] <avtar> jhung, Justin_o: http://code.google.com/p/js-test-driver/

[10:09:39 CDT(-0500)] <Justin_o> avtar: thanks

[10:11:20 CDT(-0500)] <jhung> This graphic made me happy. Thanks Microsoft! http://paulirish.com/wp-content/uploads/2011/09/browserlineupin20191.jpg

[11:14:04 CDT(-0500)] <asteig> Hello.

[11:15:39 CDT(-0500)] <jhung> hello asteig.

[11:38:05 CDT(-0500)] <Justin_o> Bosmon: I'm having a bit of a problem trying to test something. Basically I have a component that renders out other components as fluid renderer decorators. This seems to be working fine. However I'm a few levels up in integrating components into parents now. I need to get access to this low level comment that was rendered out, to trigger a click. I've had to access this component through something like subcompoent["**-renderer-component-0

[11:38:06 CDT(-0500)] <Justin_o> This had been working, but now i'm getting failures because the numbering can be different from run to run. Is there any better way to access these lower level compoennts?

[13:30:00 CDT(-0500)] <asteig> Can any GSoC mentor tell me the best way to submit two proposals? The website gives me space to submit one proposal to the organization as a whole.

[13:30:52 CDT(-0500)] <asteig> I'm interested in working on either the HTML5 image editor or colinclark's musical instruments.

[13:34:23 CDT(-0500)] <jhung> asteig: I am looking into this. fluid-everyone: does anyone else know?

[13:36:42 CDT(-0500)] <ashesh21> asteig: open the LU GSoC page from the link in the accepted organizations page (alternatively, use this link http://www.google-melange.com/gsoc/org/google/gsoc2012/learningu) and click on the submit proposal button

[13:37:14 CDT(-0500)] <ashesh21> once you've submitted one proposal, go to the page again and click on submit proposal

[13:37:21 CDT(-0500)] <ashesh21> and you can submit another one there

[13:37:23 CDT(-0500)] <ashesh21>

[13:38:03 CDT(-0500)] <asteig> Awesome, thanks ashesh21!

[13:38:30 CDT(-0500)] <ashesh21> No problems

[13:38:47 CDT(-0500)] <jhung> thanks.

[13:39:40 CDT(-0500)] <ashesh21> now regarding my own query, i need some guidance regarding what to research regarding epub readers and what kind of a solution is exactly required for the web based ePub reader project

[13:40:13 CDT(-0500)] <ashesh21> can any of the mentors throw some light on this please?

[13:40:20 CDT(-0500)] <greggy> yura: ^

[13:48:06 CDT(-0500)] <Justin_o> fluid-everyone: no community meeting today, if you have any suggestions for topics you'd like to cover or to see covered please let me know.

[14:14:46 CDT(-0500)] <NickMayne> hey chaps

[14:23:13 CDT(-0500)] <NickMayne> Hey chaps, with the inline editing, how can i trun the selector in to a 'h1'

[14:23:18 CDT(-0500)] <NickMayne> it doesnt seem to work

[14:26:19 CDT(-0500)] <NickMayne> trun = turn*

[14:30:29 CDT(-0500)] <Bosmon> Justin_o - you shouldn't try to access these components by name

[14:30:36 CDT(-0500)] <Bosmon> YOu should instead use the renderer utility functions

[14:30:43 CDT(-0500)] <Justin_o> Bosmon: okay.. what function is that

[14:31:17 CDT(-0500)] <Bosmon> They are at the head of RendererUtilities.js

[14:31:25 CDT(-0500)] <Bosmon> In particular fluid.renderer.getDecoratorComponents

[14:31:57 CDT(-0500)] <Bosmon> NickMayne - do you just get the first h1, or do you find it doesn't work at all?

[14:32:10 CDT(-0500)] <NickMayne> doesnt find at all

[14:32:23 CDT(-0500)] <Bosmon> Fascinating...

[14:32:30 CDT(-0500)] <NickMayne> If I put a class of flc-inlineEdit-text on the h1... or div, it works

[14:33:54 CDT(-0500)] <NickMayne> Hmmm I dont have that js file!

[14:36:05 CDT(-0500)] <NickMayne> Do I need it?

[14:36:46 CDT(-0500)] <Bosmon> NickMayne - so you are configuring the selectors.text option?

[14:36:58 CDT(-0500)] <NickMayne> Yes

[14:37:10 CDT(-0500)] <Bosmon> Perhaps you can send a little code snippet showing how you have this set up?

[14:37:22 CDT(-0500)] <Bosmon> I'll be looking at your jquery issues this afternoon...

[14:38:34 CDT(-0500)] <NickMayne> http://pastie.org/3728900

[14:38:40 CDT(-0500)] <NickMayne> Promise

[14:38:44 CDT(-0500)] <NickMayne> hehe

[14:41:15 CDT(-0500)] <Justin_o> Bosmon: thanks.. i'm looking at fluid.renderer.getDecoratorComponents now.. so it returns an object with keys that look like **-renderer-component-0 still.. is that correct.. there's no way to be able access it straight from the original ID.

[14:41:17 CDT(-0500)] <Justin_o> ?

[14:45:41 CDT(-0500)] <Bosmon> Hi NickMayne - inadvertently, I managed to demonstrate the same issue

[14:45:49 CDT(-0500)] <Bosmon> It looks like what is happening is that you are configuring the wrong selectors block

[14:46:01 CDT(-0500)] <NickMayne> argh!! am i?

[14:46:06 CDT(-0500)] <Bosmon> That is, you are probably putting "h1" in the block of selectors which goes to the undo widget, not to the main control itself

[14:46:17 CDT(-0500)] <Bosmon> It's desperately easy to do, if you are just modifying the demo code

[14:46:26 CDT(-0500)] <NickMayne> yup!

[14:46:32 CDT(-0500)] <NickMayne> What do I need to change?

[14:46:47 CDT(-0500)] <Bosmon> So, for example, like this:

[14:46:48 CDT(-0500)] <Bosmon> fluid.inlineEdit(".demoSelector-inlineEdit-container-caption", {

[14:46:48 CDT(-0500)] <Bosmon> selectors: {

[14:46:48 CDT(-0500)] <Bosmon> text: "h1",

[14:46:48 CDT(-0500)] <Bosmon> },

[14:46:58 CDT(-0500)] <Bosmon> The selectors block that targets the widget itself is at top level

[14:47:17 CDT(-0500)] <NickMayne> ah

[14:47:18 CDT(-0500)] <Bosmon> I think we can say there is a "moral bug" in the demo since the variable holding the selectors block is poorly named

[14:47:24 CDT(-0500)] <Bosmon> So I will put in a fix for that

[14:47:35 CDT(-0500)] <Bosmon> To make it clear that this is just the set of selectors for the undo subwidget

[14:50:23 CDT(-0500)] <NickMayne> yay it works!!!

[14:50:31 CDT(-0500)] <NickMayne> For the undo widget?

[14:51:38 CDT(-0500)] <Bosmon> yes

[17:14:41 CDT(-0500)] <NickMayne> Hey Bosmon

[17:14:57 CDT(-0500)] <Bosmon> Hey there NickMayne

[17:15:18 CDT(-0500)] <NickMayne> I have noticed when you edit a piece of content, the undo button falls out side of the div

[17:16:14 CDT(-0500)] <Bosmon> Render-wise, or DOM-wise?

[17:16:16 CDT(-0500)] <NickMayne> So you end up with somethign like this <div><div>content</div><a href='#'>Edit</a><div><a href='#'>Undo</a>

[17:16:25 CDT(-0500)] <NickMayne> Renderwise....

[17:16:36 CDT(-0500)] <NickMayne> well both i guess

[17:16:57 CDT(-0500)] <NickMayne> I would expect it to look like this..... <div><div>content</div><a href='#'>Edit</a><a href='#'>Undo</a><div>

[17:17:05 CDT(-0500)] <Bosmon> Yes, it's true - unless you make a container yourself to store it, it will fall outside it

[17:17:21 CDT(-0500)] <Bosmon> I guess it all depends on which of the two divs are the ones you hit with your "text" selector and which with the container

[17:17:45 CDT(-0500)] <NickMayne> True.

[17:18:39 CDT(-0500)] <NickMayne> But it doesnt seem right

[17:18:49 CDT(-0500)] <NickMayne> The Edit button is automagically generated....

[17:18:57 CDT(-0500)] <NickMayne> So is the undo buttons....

[17:20:03 CDT(-0500)] <Bosmon> Yes, but they are generated by different processes : P

[17:20:18 CDT(-0500)] <Bosmon> So, it looks like the undo renderer will append to the overall "container" you have chosen for the parent inlineEdit control

[17:20:57 CDT(-0500)] <NickMayne> So how can you make the Edit button do the same?

[17:25:38 CDT(-0500)] <Bosmon> Whereas the edit button is always positioned as the following sibling node in the DOM to the text itself

[17:25:47 CDT(-0500)] <Bosmon> You want the edit button to go outside?

[17:26:09 CDT(-0500)] <Bosmon> If you want different behaviour, you can implement your own "displayModeRenderer"

[17:26:25 CDT(-0500)] <Bosmon> You can see the default one at line 732 in InlineEdit.js for guidance

[17:26:45 CDT(-0500)] <Bosmon> If this were an IoC-era component, it would be a lot easier - but you can see that all the raw materials are there for you

[17:26:56 CDT(-0500)] <Bosmon> In particular you want your own implementation of fluid.inlineEdit.setupTextEditButton

[17:27:40 CDT(-0500)] <Bosmon> This is at least part of our era of "universally public setup functions" so you can call all the same initialisation as the standard renderer

[17:29:06 CDT(-0500)] <NickMayne> Wow.... completely plugable

[17:29:10 CDT(-0500)] <NickMayne> Like it!

[17:29:18 CDT(-0500)] <NickMayne> Just checkign now...

[17:29:35 CDT(-0500)] <Bosmon> Hah... this is part of our 19th-century steam-driven model of pluggability : P

[17:29:43 CDT(-0500)] <Bosmon> We have far more awesomely powerful schemes these days....

[17:30:01 CDT(-0500)] <Bosmon> Looking at this code there does seem to be a bit of an inconsistency

[17:30:04 CDT(-0500)] <NickMayne> I wanan see you guys plug your new stuff in!

[17:30:15 CDT(-0500)] <Bosmon> The "setupTextEditButton" appends the edit button immediately after the text control

[17:30:23 CDT(-0500)] <NickMayne> Yup!

[17:30:36 CDT(-0500)] <Bosmon> But it seems that immediately following this, on line 739, the button is moved to form part of the "displayModeRenderer" container

[17:30:59 CDT(-0500)] <Bosmon> Which by default seems to be set as a span wrapping the "viewEl"

[17:31:28 CDT(-0500)] <NickMayne> Im sure there was a reason it was done this way

[17:31:46 CDT(-0500)] <Bosmon> It's always possible

[17:32:14 CDT(-0500)] <Bosmon> Anyway, if you implement your own "displayModeRenderer" you can take complete control of this process

[17:32:28 CDT(-0500)] <Bosmon> Regardless of the mental oddities of the original implementors : P

[17:33:18 CDT(-0500)] <NickMayne> There are alot of quirks im finding

[17:33:27 CDT(-0500)] <NickMayne> little things i guess

[17:33:30 CDT(-0500)] <Bosmon> Do make JIRAs for everything you find

[17:34:01 CDT(-0500)] <Bosmon> I'm just rushing to the bank just now, but I'll start on your jquery issues when I get back

[17:34:06 CDT(-0500)] <Bosmon> And anything else you may have come up with : P

[17:36:54 CDT(-0500)] <NickMayne>

[17:36:57 CDT(-0500)] <NickMayne> Thanks man

[17:37:00 CDT(-0500)] <NickMayne> Oh

[17:37:03 CDT(-0500)] <NickMayne> Tooltips!!!

[17:37:14 CDT(-0500)] <NickMayne> Need to raise one for that... bit of a major one that!

[18:09:49 CDT(-0500)] <NickMayne> Bosmon: 1 more for ya! http://issues.fluidproject.org/browse/FLUID-4691

[18:09:52 CDT(-0500)] <NickMayne> Night dude