fluid-work IRC Logs-2011-07-25

[08:47:47 CDT(-0500)] <kasper> Justin_o: ping
[08:48:19 CDT(-0500)] <Justin_o> kasper: hello
[08:49:24 CDT(-0500)] <kasper> Justin_o: I'm trying to send out a suggestion to the list on what environments we should support in collectionspace .. having FF doing an almost monthly release is making things a lot more complicated for us
[08:49:43 CDT(-0500)] <kasper> Justin_o: I checked the yahoo a-grade list, and saw that they no longer list OS types
[08:49:44 CDT(-0500)] <kasper> http://developer.yahoo.com/yui/articles/gbs/
[08:50:46 CDT(-0500)] <kasper> Justin_o: .. which is kind of annoying, because we used to base our supported OS' on this .. now we actually have to think
[08:53:39 CDT(-0500)] <kasper> anyways, I'm wondering what your experience is with difference in behaviors across OS' are .. Reason I'm asking is that I'm considering whether it would make sense for us to omit minor versions on eg. macOS'.. so we just support macOSX 10.x rather than eg. 10.7
[08:54:18 CDT(-0500)] <Justin_o> kasper: funny i just sent an e-mail about that to the fluid-work list on friday
[08:54:47 CDT(-0500)] <Justin_o> so the argument that some people have been making is that variations across OS's are rare/minor
[08:55:15 CDT(-0500)] <Justin_o> yahoo i think said that they would do specific testing across browsers for issues that do come up, but it can be a bit risky
[08:55:39 CDT(-0500)] <Justin_o> for us we haven't yet taken a stance for our upcoming release, we'll be thinking about it more after Infusion 1.4 is out
[08:55:49 CDT(-0500)] <huslage> Yong is working on the network
[08:55:54 CDT(-0500)] <Justin_o> huslage: thanks
[08:56:27 CDT(-0500)] <Justin_o> kasper: so in the past yahoo would have probably had both Mac OS versions listed, and then dropped the old one on their next update
[08:56:59 CDT(-0500)] <kasper> Justin_o: ok, cool .. I agree that it seems pretty risky to say we support eg. firefox 4 .. but only test it on windows, and not any mac version
[08:57:21 CDT(-0500)] <kasper> Justin_o: would you mind forwarding me your mail, so I can see your thoughts on this?
[08:57:41 CDT(-0500)] <Justin_o> kasper: yes... that's true.. but the question is also, whose bug is that then anyways.. is it ours or is it Mozilla's for making their browser different
[08:58:01 CDT(-0500)] <Justin_o> kasper: sure.. i didn't really say much though, more so just mentioned the situation
[08:58:15 CDT(-0500)] <Justin_o> kasper: what is your browser support looking like by the way?
[08:58:41 CDT(-0500)] <kasper> Justin_o: well.. it's kind of outdated as FF5 hit the shelves just as we started QA
[08:58:51 CDT(-0500)] <kasper> but: http://wiki.collectionspace.org/display/collectionspace/Testing+Tasks+1.8
[09:00:43 CDT(-0500)] <Justin_o> kasper: so what we've decided for FF4 is to not support it anymore..
[09:00:55 CDT(-0500)] <Justin_o> since FF has moved to a chrome like system of pushing updates automatically
[09:01:43 CDT(-0500)] <kasper> Justin_o: ahh cool, I didn't realize they pushed them automatically.. that certainly makes life a bit easier
[09:02:12 CDT(-0500)] <Justin_o> kasper: yah.. basically everyone over here ended up getting FF5 pushed to them
[09:02:55 CDT(-0500)] <Justin_o> kasper: and i think that's the way they will go moving forward too
[09:05:02 CDT(-0500)] <Justin_o> FF4 didn't last very long, and I think colinclark was saying that 6 will be out pretty shortly too
[09:05:35 CDT(-0500)] <kasper> Justin_o: yeah – FF6 mid august, FF7 late sept, and FF8 early oct
[09:05:53 CDT(-0500)] <kasper> oooops, november was FF8
[09:05:54 CDT(-0500)] <Justin_o> kasper: i think they're trying to catch up to Chrome in version numbers
[09:05:58 CDT(-0500)] <kasper> haha
[09:06:21 CDT(-0500)] <kasper> well.. it's pretty uncool to have a FF3.6 trying to compete with IE9 and Chrome12
[09:06:36 CDT(-0500)] <kasper> (or whatever version chrome is at)
[09:06:42 CDT(-0500)] <Justin_o> haha, yah..
[09:07:34 CDT(-0500)] <Justin_o> kasper: by the way.. i wanted to point you at this jira plugin if you hadn't seen it yet
[09:07:35 CDT(-0500)] <Justin_o> http://www.atlassian.com/en/software/bonfire
[09:07:56 CDT(-0500)] <Justin_o> we haven't got it working yet, so you may want to hold off a bit, but i think it will be useful when it's all up and running
[09:10:43 CDT(-0500)] <kasper> Justin_o: wow, that looks awesome
[09:11:07 CDT(-0500)] <kasper> Justin_o: I'd love to hear about your experience with it, once you get it up and running properly
[09:11:45 CDT(-0500)] <Justin_o> kasper: sure no problem.. i'll try to send some information a long.. not sure when we'll get it up though.. i think we had to file a ticket with atlassian for something or other...
[09:20:45 CDT(-0500)] <lahabana> harriswong: hi Have you got a few minutes?
[09:21:00 CDT(-0500)] <harriswong> lahabana: sure.
[09:21:15 CDT(-0500)] <lahabana> harriswong: it's about the renderer
[09:21:24 CDT(-0500)] <lahabana> I've got 2 questions
[09:22:15 CDT(-0500)] <harriswong> lahabana: please ask. Though I might not be the best person to ask when it comes to the renderer...
[09:22:18 CDT(-0500)] <lahabana> first I've got a shared model between 2 components and one uses a renderer autoBinded to the model
[09:22:26 CDT(-0500)] <lahabana> ho ok
[09:22:57 CDT(-0500)] <harriswong> ok
[09:23:24 CDT(-0500)] <lahabana> my problem is that I've got an event that modifies the model in the component but strangely my view (in the other component) doesn't update
[09:23:39 CDT(-0500)] <lahabana> do you want to have a look at the code?
[09:24:38 CDT(-0500)] <harriswong> sure can you put it on pastebin or jsfiddle please?
[09:25:16 CDT(-0500)] <lahabana> sure I'll commit it on gitHub cause it's quite big
[09:26:13 CDT(-0500)] <harriswong> lahabana: sure.
[09:26:57 CDT(-0500)] <lahabana> https://github.com/lahabana/videoPlayer/tree/FLUID-4297
[09:27:10 CDT(-0500)] <lahabana> https://github.com/lahabana/videoPlayer/tree/FLUID-4297
[09:28:12 CDT(-0500)] <lahabana> harriswong the interesting files are: videoplayer.js and videoPlayer_controller.js
[09:28:36 CDT(-0500)] <lahabana> let me find the lines number
[09:28:53 CDT(-0500)] <harriswong> great thanks
[09:29:35 CDT(-0500)] <lahabana> https://github.com/lahabana/videoPlayer/blob/FLUID-4297/js/VideoPlayer.js#L62-67
[09:29:55 CDT(-0500)] <lahabana> so that's the modelchange by the other component
[09:30:02 CDT(-0500)] <lahabana> I've check it works well
[09:31:08 CDT(-0500)] <lahabana> https://github.com/lahabana/videoPlayer/blob/FLUID-4297/js/VideoPlayer_controllers.js#L31-117
[09:31:20 CDT(-0500)] <lahabana> and here is the other component using a renderer
[09:31:35 CDT(-0500)] <lahabana> the play button stops the video without anyproblem
[09:32:14 CDT(-0500)] <lahabana> the console.log line 112-114 gives a logical state of the model
[09:32:42 CDT(-0500)] <lahabana> however the view (a checkbox) doesn't update when I click on the video
[09:33:28 CDT(-0500)] <lahabana> harriswong: I was thinking that maybe it was an issue with the applier
[09:34:25 CDT(-0500)] <lahabana> but I tried to specify in the rendererOptions an applier but it didnn't change anything
[09:41:00 CDT(-0500)] <harriswong> can you point me to the code where the clicking on the video would update the checkbox view?
[09:41:44 CDT(-0500)] <harriswong> i only see the volumebutton being binded in the controller code
[09:42:01 CDT(-0500)] <harriswong> binded to click i mean
[09:46:57 CDT(-0500)] <lahabana> well
[09:47:05 CDT(-0500)] <lahabana> it is autoBinded
[09:47:12 CDT(-0500)] <lahabana> and that works
[09:48:36 CDT(-0500)] <lahabana> l70 links the renderer to the model
[09:54:55 CDT(-0500)] <harriswong> sorry, i am not too sure that's happening for you. Does fluid-everyone knows what the problem could be for lahabana? ^
[09:55:07 CDT(-0500)] <harriswong> why*
[09:55:21 CDT(-0500)] <lahabana> why?
[09:55:31 CDT(-0500)] <lahabana> well it seems it is working
[09:55:56 CDT(-0500)] <lahabana> cause when I click on the play checkbox it plays or pause the video
[09:56:16 CDT(-0500)] <lahabana> which is linked to the model in the videoPlayer component
[09:56:18 CDT(-0500)] <harriswong> i missed a word in my sentense, i meant "i am not too sure why* that's happening..."
[09:59:49 CDT(-0500)] <lahabana> ho ok
[09:59:51 CDT(-0500)] <anastasiac> lahabana, I'm just having a look at your code. What you want is for the controller to update when the VideoPlayer itself changes the model's "play" state, is that right?
[10:00:07 CDT(-0500)] <lahabana> yes exactly
[10:01:06 CDT(-0500)] <anastasiac> ok, forgive my questions, I'm just catching up: The controller itself successfully starts and stops the video, and also clicking on the video successfully starts and stops it, but it's just the display of the checkbox that's not working? is that right, labahana?
[10:01:50 CDT(-0500)] <lahabana> yes
[10:02:57 CDT(-0500)] <anastasiac> this is odd, the page doesn't display properly at all for me. I'm using FF5 in MacOSX, lahabana - that should work, right?
[10:03:31 CDT(-0500)] <lahabana> there's a problem on FF5 I think
[10:03:36 CDT(-0500)] <lahabana> chrome works well
[10:04:04 CDT(-0500)] <anastasiac> ah, ok, Safaris works.
[10:04:35 CDT(-0500)] <lahabana> it's a security thing I think that prevents downloading from something...
[10:04:44 CDT(-0500)] <lahabana> having figured it out yet
[10:05:01 CDT(-0500)] <lahabana> *haven't
[10:05:59 CDT(-0500)] <anastasiac> ok, lahabana, I'm having a look. Appliers can be tricky to pass around and share (sometimes you think you're sharing the same Applier, but it turns out you've unknowningly created a copy) so that's what I'm going to investigate
[10:06:18 CDT(-0500)] <lahabana> ok
[10:06:24 CDT(-0500)] <lahabana> if it can help you
[10:06:47 CDT(-0500)] <lahabana> just before having the renderer I was already sharing the applier like now
[10:06:51 CDT(-0500)] <lahabana> and it was working
[10:11:18 CDT(-0500)] <Justin_o> harriswong: hello.. wondering if you can give me a quick update about what you're working on
[10:12:04 CDT(-0500)] <harriswong> Justin_o: i am working on FLUID-4339
[10:14:32 CDT(-0500)] <Justin_o> harriswong: cool.. thanks.. how's it going?
[10:23:19 CDT(-0500)] <harriswong> Justin_o: by firing uio refresh when on click and update, it would potentially fix the problem except on one particular font. This problem also seems to be the related to click and apply on FullPreview. After applying my fix, the comic font would still fail while all the other ones work. cindyli suggested me that the problem could be somewhere else then, and now i am trying to find out where that problem
[10:23:19 CDT(-0500)] <harriswong> I am thinking it could be the settingStore that's overwriting the settings after it's saved.
[10:26:13 CDT(-0500)] <Justin_o> harriswong: that seems like a likely place, i think the fatpanel updates from the settings store directly.. unless that's been changed
[10:26:43 CDT(-0500)] <Justin_o> harriswong: also, wondering how far you got with the bit of pretesting in ATutor
[10:41:28 CDT(-0500)] <harriswong> Justin_o: The uploader seems to be working in ATutor. The copy i got was from colinclark's FLUID-3787 branch(i think) Currently, I can upload files no problem to the server. I haven't tested the error handler part yet. I should probably test it again with the master branch though.. Also, I don't know if it's worth adding a note that if they are implementing the uploader with PHP, the php.ini
[10:41:28 CDT(-0500)] <harriswong> upload_max_filesize needs to be adjusted otherwise it could be pretty confusing trying to figure out why it is not working.
[10:44:38 CDT(-0500)] <Justin_o> harriswong: yah.. i think it should be added somewhere in the uploader docs... not sure where though, colinclark and anastasiac might have some thoughts on that
[10:45:43 CDT(-0500)] <anastasiac> harriswong, providing information in the docs that will help avoid confusion is always a good idea
[10:48:57 CDT(-0500)] <anastasiac> lahabana, the problem is that the renderer's autobinding isn't two-way: your model will automatically be updated with the UI widget changes, but it doesn't go the other way: your UI widget won't automatically be updated when the model changes. You'll need to do a "refreshView" on modelChanged
[10:49:31 CDT(-0500)] <anastasiac> clearly, this is not well documented I'll have to fix that
[10:49:33 CDT(-0500)] <lahabana> ho ok
[10:49:39 CDT(-0500)] <lahabana> thx a lot
[10:49:41 CDT(-0500)] <anastasiac> np
[10:49:59 CDT(-0500)] <lahabana> and I'm really stupid cause when I tried the renderer I noticed that
[10:50:11 CDT(-0500)] <lahabana> also anastasiac I've got another thing I'm wondering
[10:50:37 CDT(-0500)] <lahabana> I wanted to add some decorators to my current protoTree
[10:50:49 CDT(-0500)] <lahabana> but I can't find the syntax without ID
[10:51:09 CDT(-0500)] <lahabana> I mean : {ID: "my-menu",
[10:51:09 CDT(-0500)] <anastasiac> ah, hm, good question
[10:51:09 CDT(-0500)] <lahabana> value: "Cheeses",
[10:51:10 CDT(-0500)] <lahabana> decorators: {
[10:51:10 CDT(-0500)] <lahabana> type: "addClass",
[10:51:10 CDT(-0500)] <lahabana> classes: "fl-listmenu fl-activemenu"
[10:51:32 CDT(-0500)]

[10:54:48 CDT(-0500)] <anastasiac> lahabana, I'm guessing that you need to add a "valuebinding" key for your current value binding, and add the "decorators" key as a sibling to that, e.g.
[10:54:51 CDT(-0500)] <anastasiac> playButton: {
[10:54:51 CDT(-0500)] <anastasiac> valuebinding: ".flc-videoPlayer-controller-play",
[10:54:51 CDT(-0500)]

<anastasiac> decorators:

Unknown macro: {...}

[10:54:52 CDT(-0500)] <anastasiac> },
[10:55:02 CDT(-0500)] <lahabana> anastasiac: btw you were right it's working fine with a refreshView thx
[10:55:08 CDT(-0500)] <anastasiac> glad it works
[10:55:19 CDT(-0500)] <lahabana> ok thx
[10:55:28 CDT(-0500)] <anastasiac> let me know if that doesn't work, lahabana
[10:55:38 CDT(-0500)] <lahabana> ok
[10:55:52 CDT(-0500)] <lahabana> while you're here I've 2 other small questions
[10:55:57 CDT(-0500)] <lahabana> (sorry )
[10:56:14 CDT(-0500)] <lahabana> so the first one is about conditionnal decorators
[10:56:25 CDT(-0500)] <lahabana> I'm sure I've seen some documentation about it
[10:56:43 CDT(-0500)] <lahabana> but I can't find it anymore have you got an idea of where it is?
[10:58:25 CDT(-0500)] <lahabana> anastasiac: just found it was indeed in the expander part
[10:58:43 CDT(-0500)] <anastasiac> lahabana, good, glad you found it.
[10:58:54 CDT(-0500)] <lahabana> I'm just wondering can u put an expander in the middle of a protoTree?
[11:01:39 CDT(-0500)] <Justin_o> jessm: are we having a decapod meeting today? and if so by which means?
[11:02:01 CDT(-0500)] <anastasiac> lahabana, an expander can take the place of one node of a tree, and you can have non-expanders for other nodes, so for example you could use an expander for the play button, but leave the captions button as it is now. Is that what you meant?
[11:02:20 CDT(-0500)] <lahabana> anastasiac: cause what I actually need is to change classes or names of the html markup do I have to use a jQuery decorator on an onClick? or is it better to use a conditionnal expander
[11:02:21 CDT(-0500)] <jessm> Justin_o: ah, good question – we are schedule to
[11:02:25 CDT(-0500)] <jessm> let me try to ping them
[11:02:41 CDT(-0500)] <lahabana> anastasiac: yes it was my question thx
[11:02:53 CDT(-0500)] <Justin_o> jessm: thanks
[11:03:07 CDT(-0500)] <jessm> Justin_o: skype
[11:03:21 CDT(-0500)] <jessm> fluid-everyone: decapod call on skype
[11:03:25 CDT(-0500)] <Justin_o> okay
[11:03:27 CDT(-0500)] <Justin_o> thanks
[11:03:31 CDT(-0500)] <jessm> let me know to add you
[11:03:31 CDT(-0500)] <anastasiac> lahabana, changing class names in response to user input might best be done in whatever event handler you have attached to the event
[11:03:57 CDT(-0500)] <jameswy> jessm: Ready to be added.
[11:04:11 CDT(-0500)] <anastasiac> lahabana, are you thinking of something like changing the visible appearance of something to go with a state change?
[11:04:35 CDT(-0500)] <lahabana> yes but I've just realized I could simply use the proper CSS selectors
[11:05:04 CDT(-0500)] <lahabana> but for accessibility text though?
[11:05:53 CDT(-0500)] <anastasiac> lahabana, I think you'd still want to make that change in your event handler - that way, the tex will be updated any time the state changed - regardless of what triggered the change
[11:05:56 CDT(-0500)] <lahabana> I should deal with that in an modelChanged ?
[11:06:23 CDT(-0500)] <lahabana> ok
[11:11:45 CDT(-0500)] <lahabana> anastasiac: one last question and after I promise I'll leave you alone
[11:12:15 CDT(-0500)] <anastasiac> no, and please don't leave me alone. Your questions are very informative for me - they tell me what someone new to the renderer needs to know
[11:12:23 CDT(-0500)] <anastasiac> sorry, "no problem", not "no"
[11:12:55 CDT(-0500)] <lahabana> how does the fluid decorator works with IoC now?
[11:13:25 CDT(-0500)] <lahabana> ho ok then thx
[11:14:35 CDT(-0500)] <lahabana> anastasiac: If you remember my code I've got those 2 components (captionner and controllers) that wait for an event called onCreateXXXXcontainer to begin their instantiation
[11:15:02 CDT(-0500)] <lahabana> anastasiac: if I understood well the fluid decorator is quite made for those kind of things no?
[11:16:29 CDT(-0500)] <anastasiac> lahabana, not sure I understand the question. Are you just double-checking if decorators will work in this scenario, or are you suggesting something different?
[11:16:45 CDT(-0500)] <lahabana> I'm double checking
[11:17:17 CDT(-0500)] <lahabana> anastasiac, and I'm not sure how to actually use that decorator in a IoC context
[11:18:18 CDT(-0500)] <anastasiac> lahabana, I think the two are pretty independent, and should co-exist just fine. Your renderer decorator should work fine, regardless of whether or not the component is IoC-ified
[11:18:25 CDT(-0500)] <lahabana> anastasiac: to be short and clear: I would like to replace my 2 events by decorators
[11:18:29 CDT(-0500)] <anastasiac> ah
[11:19:16 CDT(-0500)] <lahabana> so in the defaults function should I put into the component section the component that will be in the decorator?
[11:19:26 CDT(-0500)] <lahabana> or not?
[11:19:46 CDT(-0500)] <anastasiac> hm. ok, let me think about that for a sec
[11:20:59 CDT(-0500)] <anastasiac> lahabana, first, you mean replace two event handlers, right? and specifically which two?
[11:21:27 CDT(-0500)] <lahabana> onCreateControllerContainer, onCreateCaptionContainer
[11:21:36 CDT(-0500)] <lahabana> in the videoPlayer Component
[11:22:56 CDT(-0500)] <lahabana> (they are fired l150-161 of js/videoplayer.js)
[11:23:44 CDT(-0500)] <anastasiac> got it, ok, I see what you're doing now... hm... pondering...
[11:24:26 CDT(-0500)] <lahabana> if I understood well the fluid decorator is made to avoid those kind a walkaround
[11:25:01 CDT(-0500)] <anastasiac> lahabana, I'm not sure that renderer decorators are really intended for that...
[11:25:29 CDT(-0500)] <anastasiac> ok first, there would be a simpler way than having those two specific events: you could simply have both of those subcomponents create on your "onReady"event
[11:25:59 CDT(-0500)] <lahabana> true
[11:27:21 CDT(-0500)] <lahabana> thx anastasiac
[11:27:22 CDT(-0500)] <anastasiac> lahabana, where were you thinking of putting these new decorators? what would they decorate?
[11:27:58 CDT(-0500)] <lahabana> flc-videoPlayer-captionArea and flc-videoPlayer-controller
[11:28:08 CDT(-0500)] <lahabana> I'm sorry I got to go
[11:28:18 CDT(-0500)] <lahabana> thanks a lot for your help
[11:28:57 CDT(-0500)] <anastasiac> k, np
[11:59:58 CDT(-0500)] <michelled> colinclark: I know the new build scripts require a newer version of rhino then I've got - is there a particular version? how did you get ant to use the correct version?
[12:00:10 CDT(-0500)] <colinclark>
[12:00:14 CDT(-0500)] <colinclark> one sec
[12:00:23 CDT(-0500)] <colinclark> but check the lib directory in the meantime
[12:02:33 CDT(-0500)] <colinclark> Okay, sorry
[12:02:38 CDT(-0500)] <colinclark> So, Rhino should be in the repo now
[12:02:45 CDT(-0500)] <colinclark> Which I know Justin_o wasn't too happy with--me adding more binaries to Git
[12:02:55 CDT(-0500)] <colinclark> but it seemed like the easiest way to solve the problem we had in the past
[12:03:02 CDT(-0500)] <colinclark> where we had no clue which version of Rhino was being loaded
[12:03:13 CDT(-0500)] <colinclark> The key to getting it to work, and which I should have made some note about...
[12:03:30 CDT(-0500)] <colinclark> is that you need to disable any older versions of Rhino fetched by fetch.xml
[12:03:36 CDT(-0500)] <michelled> I'm thinking we've needed a readme in the build scripts directory for a long time now
[12:03:40 CDT(-0500)] <colinclark> Yeah
[12:03:45 CDT(-0500)] <colinclark> Shall I go ahead and draft something now?
[12:03:52 CDT(-0500)] <michelled> that would be great
[12:03:57 CDT(-0500)] <colinclark> I'm already working on the main readme and release notes
[12:04:01 CDT(-0500)] <colinclark> literally as we speak
[12:04:07 CDT(-0500)] <michelled>
[13:04:27 CDT(-0500)] <harriswong> cindyli: in UIOptions.css line 51, .fl-uiOptions select#textFont option.comic..., is that being used anywhere?
[13:05:13 CDT(-0500)] <cindyli> harriswong: heidi_ might know better of your question
[13:05:30 CDT(-0500)] <harriswong> cindyli; thx
[13:05:41 CDT(-0500)] <cindyli> np
[13:23:22 CDT(-0500)] <Bosmon> Hi cindyli - thanks for all your hard work on Friday, after the merge we are on the final stretch now...
[13:23:29 CDT(-0500)] <Bosmon> Are you looking at Justin_o's munging code today?
[13:23:37 CDT(-0500)] <cindyli> yes, Bosmon
[13:24:36 CDT(-0500)] <cindyli> it seems lots of options need to be munged
[13:24:39 CDT(-0500)] <Bosmon> Great
[13:24:42 CDT(-0500)] <Bosmon> Yes, almost all of them
[13:24:47 CDT(-0500)] <Bosmon> Actually.... ALL of them
[13:24:54 CDT(-0500)] <cindyli> aha
[13:25:14 CDT(-0500)] <Bosmon> I'm not actually sure that there is a single option which is "in the right place" in terms of what our users might expect
[13:25:17 CDT(-0500)] <Bosmon> Perhaps there are some
[13:25:25 CDT(-0500)] <Bosmon> What is your feeling?
[13:27:04 CDT(-0500)] <Justin_o> Bosmon: just wanted to know what your thoughts were on the options munging.. will there need to be framework changes?
[13:27:08 CDT(-0500)] <Justin_o> for 1.4 that is
[13:27:20 CDT(-0500)] <cindyli> i feel it might be hard to make all the options configurable
[13:28:14 CDT(-0500)] <Bosmon> I guess we will need to draw a line somewhere - clearly "all" of them are configurable, if the user can somehow "guess" what path they are at
[13:28:35 CDT(-0500)] <Bosmon> But my feeling is that at least options which are directed targeted at UIOptions, UIEnhancer, and options which are template paths should be simply configurable
[13:28:40 CDT(-0500)] <Bosmon> Does that seem reasonable?
[13:29:45 CDT(-0500)] <cindyli> yes, Bosmon
[13:31:54 CDT(-0500)] <colinclark> What are you referring to when you say "options munging?"
[13:32:13 CDT(-0500)] <Bosmon> colinclark - Justin_o has written some code which right now only operates for FatPanel
[13:32:44 CDT(-0500)] <Bosmon> I think our final stretch on UIOptions work consists of fixing this up so it works again, also works more fully, and also does the same work for all of the UIOptions configurations we deliver
[13:33:23 CDT(-0500)] <Bosmon> Justin_o - I guess it's a grey issue whether this counts as "framework changes"
[13:33:35 CDT(-0500)] <Bosmon> It should be ok if we can make something that is just "moderately reusable" just for UIOptions
[13:33:59 CDT(-0500)] <Bosmon> Perhaps we can even use a part of colinclark's ModelTransformations, but I don't think we really need the full power of it
[13:34:16 CDT(-0500)] <Bosmon> So we could get away with a much simpler kind of configuration just for this use case, and pick up the pieces later for 1.5
[13:34:16 CDT(-0500)] <Justin_o> Bosmon: okay.. so the code changes would only be inside of UI Options?
[13:34:25 CDT(-0500)] <Bosmon> Justin_o - that's what I'm proposing now
[13:34:44 CDT(-0500)] <Justin_o> Bosmon: okay... and what will the effecct be on Infusion 1.5
[13:34:55 CDT(-0500)] <Justin_o> meaning what will we be able to keep vs throw away
[13:35:09 CDT(-0500)] <Bosmon> Well... we will be able to keep some of the "ideas" perhaps
[13:35:39 CDT(-0500)] <harriswong> cindyli: i have a question
[13:35:49 CDT(-0500)] <Bosmon> We've never advertised that users of the framework can do their own options munging in any case
[13:36:04 CDT(-0500)] <Bosmon> This has so far just been a thing we have done ourselves to help them out in specific cases
[13:36:15 CDT(-0500)] <cindyli> sure, harriswong
[13:39:24 CDT(-0500)] <cindyli> Bosmon: would the code changes be only inside UI Options? it will also be in ui enhancer i think
[13:39:38 CDT(-0500)] <cindyli> so that page enhancer is able to pass the options to ui enhancer
[13:41:37 CDT(-0500)] <harriswong> cindyli: i want to confirm that we shouldn't need to call that.events.onUIOptionsRefresh.fire(); when "save" is clicked right?
[13:41:58 CDT(-0500)] <cindyli> no, should not, harriswong
[13:46:30 CDT(-0500)] <michelled> Justin_o: is there a jira I should be working off for the toc issue when there are no headings on the page?
[13:46:34 CDT(-0500)] <michelled> or should I create one?
[13:47:28 CDT(-0500)] <Justin_o> michelled: i don't think there is one yet
[13:50:13 CDT(-0500)] <colinclark> anastasiac and jessm, I've made some more tweaks to the README and Release Notes for Infusion 1.4
[13:50:18 CDT(-0500)] <colinclark> and pushed them up to the project repo
[13:50:52 CDT(-0500)] <colinclark> So your FLUID-4251 pull request is now resolved, anastasiac
[13:51:01 CDT(-0500)] <anastasiac> cool, thanks colinclark
[13:51:03 CDT(-0500)] <colinclark> Any last edits or feedback before I close this issue?
[13:51:09 CDT(-0500)] <anastasiac> I'll have a look
[13:55:26 CDT(-0500)] <anastasiac> colinclark, your changes seem fine, only stylistic thoughts. I'd recommend a final review of the known issues list after testing, of course.
[13:55:40 CDT(-0500)] <colinclark> What are your stylistic thoughts?
[13:56:51 CDT(-0500)] <anastasiac> in the readme on line for, put a space between control and --; and I'd keep the 'and' and puncuation in the list of things included on lines 8-10.
[13:56:59 CDT(-0500)] <anastasiac> line "four"
[13:57:13 CDT(-0500)] <colinclark> Em dashes never have spaces between them and their surrounding text
[13:57:50 CDT(-0500)] <colinclark> As for punctation in lists, we might be best to agree to disagree
[13:57:59 CDT(-0500)] <colinclark> And in Infusion 1.5, you can put them back in
[13:58:42 CDT(-0500)] <anastasiac> well, I might argue with "never", and I'm happy to disagree. As I said, they're stylistic thoughts only.
[14:09:56 CDT(-0500)] <colinclark> Hi, can someone give me a list of all the places where UI Options exists?
[14:10:05 CDT(-0500)] <colinclark> In other words, all related demos, examples, etc.
[14:10:22 CDT(-0500)] <colinclark> I'm just trying to update them all to link to the new, generated FSS themes with !important in them
[14:10:34 CDT(-0500)] <colinclark> I'm thinking anastasiac or cindyli or michelled might know best
[14:12:20 CDT(-0500)] <michelled> colinclark: there are the three demos inside demos/uiOptions
[14:12:58 CDT(-0500)] <michelled> there are two integration examples - the sakai one uses UIO and the uPortal one uses UIE
[14:13:43 CDT(-0500)] <michelled> there is a manual test SomeKindOfNews
[14:14:25 CDT(-0500)] <michelled> and of course the three templates in the components directory
[14:14:41 CDT(-0500)] <michelled> and you might want to take a look at the unit tests too
[14:15:10 CDT(-0500)] <anastasiac> colinclark, I'm in the process of moving the manual test SomeKindOfNews into the demos folder, replacing the three individual demos (http://issues.fluidproject.org/browse/FLUID-4351)
[14:15:15 CDT(-0500)] <michelled> colinclark: I think that's it - am I missing anything anastasiac, cindyli?
[14:15:23 CDT(-0500)] <colinclark> waiwaiwait
[14:15:33 CDT(-0500)] <colinclark> Tell me the bananas are not becoming an official demo!
[14:15:43 CDT(-0500)] <cindyli> michelled: u got them all
[14:16:39 CDT(-0500)] <anastasiac> colinclark, we can certainly tidy the page up; maybe jameswy can provide some suggestions. The change was his request
[14:17:22 CDT(-0500)] <colinclark> Okay, so I'm sorry that I haven't been following these decisions very closely
[14:17:36 CDT(-0500)] <colinclark> I am a pretty solid -1 against moving the SomeKindOfNews out of the manual tests folder
[14:17:48 CDT(-0500)] <colinclark> We intentionally made it as a test for ourselves
[14:17:52 CDT(-0500)] <colinclark> demos involve a design process
[14:17:56 CDT(-0500)] <colinclark> they involve some craft
[14:18:05 CDT(-0500)] <colinclark> anastasiac, I appreciate all the work you've done with making that test page
[14:18:11 CDT(-0500)] <colinclark> it's been immensely, immensely useful
[14:18:36 CDT(-0500)] <colinclark> but your bananas might not be the best public showcase for our flagship component
[14:18:41 CDT(-0500)] <colinclark> maybe?
[14:19:32 CDT(-0500)] <anastasiac> My understanding is that the current full-page demos are inadequate because they don't offer an context. jameswy and justin wanted a "page" that the full-page ui options could be used with. They suggested using the SomeKindOfNews. I'm happy to work on this with any sample page, be it an all-new one or a "dignification" of the test page
[14:19:46 CDT(-0500)] <colinclark> Okay
[14:20:27 CDT(-0500)] <colinclark> hilarious use of the word "dignification," btw, anastasiac
[14:20:29 CDT(-0500)] <colinclark>
[14:20:44 CDT(-0500)] <anastasiac> it could use some
[14:30:56 CDT(-0500)] <colinclark> jameswy and I just had a quick strategy session
[14:31:11 CDT(-0500)] <colinclark> We both agree that awesomeness is key for showing off UI Options
[14:31:26 CDT(-0500)] <colinclark> he's going to do the work of putting together a UIO demo
[14:31:29 CDT(-0500)] <colinclark> and we'll block on it
[14:35:08 CDT(-0500)] <Bosmon4> Speaking of awesomeness, I managed to get our content simplification demo to a kind of quarter-awesome state on Friday
[14:35:28 CDT(-0500)] <Bosmon4> I ran into a bit a stumbling block using the CSS opacity strategy which suggests we will have to do some somewhat more complex stuff
[14:40:16 CDT(-0500)] <colinclark> that's great
[14:40:30 CDT(-0500)] <Bosmon4> The big problem is that CSS opacity unconditionally inherits
[14:40:33 CDT(-0500)] <Bosmon4> Even if the style doesn't
[15:31:36 CDT(-0500)] <heidi_> harriswong sorry i missed yr earlier msg. you can remove that style, i believe it's now in fss-text.css
[15:31:57 CDT(-0500)] <harriswong> thanks heidi_