fluid-work IRC Logs-2013-11-01

[07:09:24 CDT(-0500)] <colinclark> Hey kasparnet, do the acceptance tests all pass for you on Windows?

[07:09:54 CDT(-0500)] <colinclark> On your 32 bit version?

[07:09:59 CDT(-0500)] <kasparnet> colinclark: yeah

[07:10:09 CDT(-0500)] <colinclark> like right now they do?

[07:10:49 CDT(-0500)] <colinclark> I was reading through them on Windows, as I get ready for my "ditch font size" pull request

[07:11:10 CDT(-0500)] <colinclark> How come this one, which seems to be testing the SPI handler among other things, is named "os_gnome"? https://github.com/colinbdclark/windows/blob/master/tests/AcceptanceTests.js#L326

[07:11:35 CDT(-0500)] <colinclark> is it just a cut and paste sort of thing, or are these tests actually cross-platform somehow?

[07:12:55 CDT(-0500)] <kasparnet> they are... we have the inverse transformations from pilot 1

[07:13:03 CDT(-0500)] <kasparnet> so they should actually work

[07:18:19 CDT(-0500)] <chrispetsos> Justin_o: hi, do you spare some time for a question?

[07:28:51 CDT(-0500)] <colinclark> kasparnet: OOOH, I get it. "os_gnome" is the preference set name, and you're actually reverse-transforming from app-specific on GNOME to common terms to Windows

[07:28:52 CDT(-0500)] <colinclark> nice

[07:29:06 CDT(-0500)] <kasparnet> yeah, exactly

[07:49:27 CDT(-0500)] <Justin_o> chrispetsos: sorry I'm away today. Maybe cindyli will be able to help you.

[07:50:15 CDT(-0500)] <cindyli> chrispetsos: what's the problem

[07:52:32 CDT(-0500)] <chrispetsos> cindyli: hi, it's not a particular problem, i'd just ask for a recommendation on something

[07:53:30 CDT(-0500)] <chrispetsos> cindyli: basically, i've created a new reusable adjuster which i have used twice, you can see a demo here, http://160.40.60.238/prefsEditors/demos/adjustersPilots2/ (temp link)

[07:54:08 CDT(-0500)] <cindyli> looks great

[07:55:24 CDT(-0500)] <chrispetsos> cindyli: what i want to do now is to use this adjuster for a composite one, http://wiki.fluidproject.org/download/attachments/34570511/adjusters-for2ndpilots.pdf, scroll all the way down, at the

[07:55:34 CDT(-0500)] <chrispetsos> cindyli: "Magnifier location follows:"

[07:56:11 CDT(-0500)] <cindyli> i see it

[07:56:22 CDT(-0500)] <chrispetsos> cindyli: till now we have been using the repeatingSelector method for these, I wanted to ask if we could some way use the composite panel you have been working on

[07:57:07 CDT(-0500)] <chrispetsos> cindyli: The reason for this is not to maintain the markup in two different places

[07:57:23 CDT(-0500)] <chrispetsos> cindyli: so, do you have a suggestion on how that could be implemented?

[08:01:16 CDT(-0500)] <cindyli> yes, we should be able to use composite panel for this. the only thing needs attention is, each of these "follows" has a different label icon. if you are thinking to use css to achieve that, the customized css can be passed in as an option in aux schema

[08:05:39 CDT(-0500)] <cindyli> chrispetsos: anastasiac found a bug yesterday (http://issues.fluidproject.org/browse/FLUID-5203) that options from subpanels are not handled properly in some cases. So, you may have problem implementing what you want by using composite panels with the current infusion lib in gpii repo. we will update the gpii infusion once all major issues with composite panels are addressed.

[08:10:03 CDT(-0500)] <chrispetsos> cindyli: ok, so it would be better if i used the "repeatingSelector" method for the time being

[08:10:14 CDT(-0500)] <cindyli> yes, chrispetsos

[08:10:33 CDT(-0500)] <chrispetsos> ok cindyli thanks

[08:10:39 CDT(-0500)] <cindyli> anytime, chrispetsos

[10:21:53 CDT(-0500)] <anastasiac> yzen, regarding the pageBuilder stuff, one thing that's not clear to me at all is: what are the general circumstances in which someone would want to configure the pageBuilder in some way other than the default, and how should they go about doing that? (ok, that's two things)

[10:22:46 CDT(-0500)] <anastasiac> if you have thought, yzen, could you add them to the etherpad?

[10:22:47 CDT(-0500)] <yzen> anastasiac: so for example if you want to add a top level component on the page, like sidebar or header or configure it

[10:23:22 CDT(-0500)] <yzen> since page builder contains all components, the options, or new components must be passed as the options to the page builder

[10:23:45 CDT(-0500)] <anastasiac> and where would I do the work of adding a new sidebar?

[10:24:26 CDT(-0500)] <yzen> anastasiac: so that would be done through a config file

[10:24:47 CDT(-0500)] <anastasiac> modifications of an existing config file, or a new one? and how would I tell the page builder about the new file?

[10:26:35 CDT(-0500)] <yzen> so changes would be in a tenant specific config file for example:

[10:26:35 CDT(-0500)] <yzen> https://github.com/collectionspace/ui/tree/master/src/main/webapp/tenants/lifesci/config

[10:26:39 CDT(-0500)] <yzen> app layer handles the overlay

[10:26:46 CDT(-0500)] <yzen> e.g. loads the correct config for a tenant

[10:26:52 CDT(-0500)] <yzen> if there is one

[10:27:02 CDT(-0500)] <yzen> otherwise the ones in default directory are used{color}

[10:28:27 CDT(-0500)] <anastasiac> yzen, do you know if this kind of tenant-specific configuration (in general) is already documented somewhere on their wiki?

[10:28:47 CDT(-0500)] <yzen> anastasiac: i would hope so, I mean it's not on our list is it ?

[10:28:57 CDT(-0500)] <anastasiac> no, thanks goodness!

[10:29:03 CDT(-0500)] <yzen> k

[10:29:05 CDT(-0500)] <anastasiac> ok, I'll look around there

[13:17:08 CDT(-0500)] <cindyli> hi Bosmon

[14:27:26 CDT(-0500)] <anastasiac> cindyli, I just wanted to double-check with you: Before we introduced composite panels, we had the two links controls checkboxes in one panel; two preferences in one panel. We still support that, right?

[14:28:17 CDT(-0500)] <cindyli> yes, we do, anastasiac

[14:28:26 CDT(-0500)] <anastasiac> ok, thanks cindyli

[14:28:28 CDT(-0500)] <cindyli> np