fluid-work IRC Logs-2011-04-13

[08:40:52 CDT(-0500)] <heidi_> Justin_o this is interesting stuff: http://html5boilerplate.com/
[08:48:14 CDT(-0500)] <Justin_o> heidi_: yes... i had looked at that when gary sent the styles along
[08:48:40 CDT(-0500)] <Justin_o> heidi_: which parts did you find most interesting
[08:53:02 CDT(-0500)] <anastasiac> heidi_, I'm wondering if you could look at a couple of FSS docs draft pages, let me know if you think they make sense
[08:53:11 CDT(-0500)] <anastasiac> they're pretty short
[08:54:22 CDT(-0500)] <heidi_> Justin_o their style.css page is an interesting variation on a reset/base file.
[08:54:36 CDT(-0500)] <heidi_> i've not seen this before in css either: @media all and (orientation:landscape)
[08:54:44 CDT(-0500)] <heidi_> anastasiac for sure!
[08:55:10 CDT(-0500)] <anastasiac> heidi_: http://wiki.fluidproject.org/display/fluid/FSS+Advanced+Layout+-+Widgets and http://wiki.fluidproject.org/display/fluid/FSS+Advanced+Layout+-+Icons
[08:57:30 CDT(-0500)] <anastasiac> and, heidi_, in case you're curious, another set of pages: http://wiki.fluidproject.org/display/fluid/FSS+Columns+-+Equal-width+columns%2C+fixed-width+container
[08:58:42 CDT(-0500)] <heidi_> anastasiac i think one other thing to add for widgets is there are some icons in FSS for it ... not sure to what extent... but might want to add to example. toggle icons come to mind
[08:59:11 CDT(-0500)] <anastasiac> heidi_, yes, I was hoping to extend the page a bit with info on icons
[08:59:45 CDT(-0500)] <anastasiac> given what you've learned recently about icons and widgets, heidi_, do you think these pages explain them adequately (notwithstanding your previous comment)?
[09:02:35 CDT(-0500)] <heidi_> anastasiac maybe expanding on this statement "These controls are typically implemented using an <img>, but this is often implemented inaccessibly." might be good. just mentioning alt text
[09:02:44 CDT(-0500)] <heidi_> and why this one is better
[09:05:00 CDT(-0500)] <anastasiac> heidi_, sounds like a good idea
[09:06:03 CDT(-0500)] <heidi_> anastasiac looks good!
[09:06:12 CDT(-0500)] <anastasiac> heidi_, thanks for the feedback
[09:07:35 CDT(-0500)] <heidi_> anastasiac column layout is good... for equal width ex, should it be fl-container-700 instead of fl-container-950 ?
[09:07:58 CDT(-0500)] <anastasiac> heidi_, quite likely good catch
[09:08:02 CDT(-0500)] <heidi_> the h3 is different too
[09:08:40 CDT(-0500)] <heidi_> with all the examples i think that top part just has to be sure to match up
[09:08:59 CDT(-0500)] <heidi_> equal width flex
[09:09:58 CDT(-0500)] <anastasiac> heidi_, yes - eventually we'll have a component that extracts a single blob of markup and uses it for both the demo and the explanation - right now it's manual, and hence error prone
[09:10:16 CDT(-0500)] <heidi_> cool
[09:10:53 CDT(-0500)] <heidi_> anastasiac yeah i really like how you've done this. each thing on its own page, with clear explanation, demo, code example
[09:11:38 CDT(-0500)] <anastasiac> heidi_, thanks - that's the goal: more examples, more useful examples: things people could actually cut-and-paste to get themselves started; and both the demo and the explanation on the same page
[09:12:01 CDT(-0500)] <heidi_> big improvement
[09:34:32 CDT(-0500)] <heidi_> Justin_o there's another clearfix choice from boilerplate as well we should take a look at. i'll paste it into the jira
[09:35:59 CDT(-0500)] <heidi_> also http://www.yuiblog.com/blog/2010/09/27/clearfix-reloaded-overflowhidden-demystified/
[09:49:43 CDT(-0500)] <Justin_o> heidi_: thanks
[09:50:26 CDT(-0500)] <heidi_> Justin_o the boiler plate hide styles are awesome so i'm going to add those to fss-layout and prob deprecate fl-offscreen-hidden
[09:50:47 CDT(-0500)] <Justin_o> heidi_: i've pushed up some more changes to FLUID-3880 https://github.com/jobara/infusion/tree/FLUID-3880
[09:51:08 CDT(-0500)] <heidi_> the style that matches with our current fl-offscreen-hidden is their equivalent to "image replacement" which makes more sense, and other styles for hiding or visually hiding things
[09:51:10 CDT(-0500)] <Justin_o> they add the scoped focus styling back onto a bunch of html pages can you quickly double check it and make sure i didn't miss anything
[09:51:16 CDT(-0500)] <Justin_o> some pages didn't need it
[09:51:24 CDT(-0500)] <heidi_> Justin_o ok i'll check it over
[09:52:03 CDT(-0500)] <Justin_o> heidi_: thanks..
[09:52:46 CDT(-0500)] <Justin_o> heidi_: interesting.. can you update the names or we can think of that later.. i remember thinking they weren't very clear.. for the hidden stuff
[09:52:58 CDT(-0500)] <heidi_> Justin_o yeah we'll fss-ize the names
[10:10:08 CDT(-0500)] <Justin_o> heidi_: sounds good
[10:33:36 CDT(-0500)] <anastasiac> fluid-everyone: did we settle on a new url for stand-up? was it https://connect.ocad.ca/r87258683/ or https://connect.ocad.ca/fluid-work/ ?
[10:33:40 CDT(-0500)] <anastasiac> jessm: ^
[10:35:21 CDT(-0500)] <anastasiac> ok, we're using the old york room for today
[11:46:01 CDT(-0500)] <Justin_o_> anastasiac: for tomorrow.. i think harris has https://connect.ocad.ca/fluid-work/ setup
[11:46:22 CDT(-0500)] <anastasiac> Justin_o, yes, I was able to connect to it today.
[11:46:35 CDT(-0500)] <anastasiac> I'll email the list with that info, and maybe change the wiki page
[11:51:55 CDT(-0500)] <Justin_o_> anastasiac: thanks.. do you think we need to run a test of it first?
[11:52:33 CDT(-0500)] <anastasiac> Maybe we could try it for the dev meeting this afternoon? Or would that be asking too much of it?
[12:38:54 CDT(-0500)] <jessm> sorry to miss standup y'all
[12:39:34 CDT(-0500)] <jessm> anastasiac: sorry for the delay in responding – but my emails stands I +1 fluid-work in connect.ocad.ca
[12:55:19 CDT(-0500)] <thealphanerd> hey justin_o: my arc just showed up 0o0o0o0o0o
[13:32:32 CDT(-0500)] <heidi_> Justin_o FLUID-4181 is ready for your review... assigned to you, when you have time. going to look at 3880 now
[13:34:06 CDT(-0500)] <michelled> fluid-everyone: anyone want to be skyped into the dev meeting?
[13:40:15 CDT(-0500)] <heidi_> michelled yes please
[14:06:12 CDT(-0500)] <anky> Justin_o: hi
[14:06:48 CDT(-0500)] <anky> Justin_o: i had been working on the MediaWiki theme design, and had to discuss certain things over it
[14:59:39 CDT(-0500)] <Justin_o> anky: hello
[15:00:25 CDT(-0500)] <anky> hi Justin_o
[15:01:16 CDT(-0500)] <anky> wanted to discuss some ideas with you
[15:03:20 CDT(-0500)] <Justin_o> anky: sure, what's up
[15:03:38 CDT(-0500)] <anky> can you please take a look at this http://www.evernote.com/pub/ankurdnana/gsoc#n=5517a35e-68e4-474b-a67a-9882c833a210&amp;b=5e92c921-31fc-477d-8c1b-a06cd0256330
[15:08:10 CDT(-0500)] <cindyli> Bosmon2: have time to answer a question on autoInit?
[15:08:34 CDT(-0500)] <anky> Justin_o: this is like my rough notes over the design of the theme, i am going to make the final theme mockup tonight, hence needed to discuss on these ideas
[15:08:53 CDT(-0500)] <Justin_o> anky: okay..
[15:09:00 CDT(-0500)] <Justin_o> just finishing up reading it
[15:10:07 CDT(-0500)] <anky> ok, its rough so ignore the incompleteness and the raw nature
[15:13:33 CDT(-0500)] <heidi_> anastasiac ... so for the creating a component page. i wrote a bit on creator functions and i'm wondering if we should have a separate place for that now that i should switch it to the new way
[15:13:57 CDT(-0500)] <anastasiac> heidi_, good point - it does seem like we'll need to change that
[15:13:57 CDT(-0500)] <heidi_> it'd make sense to still explain, since the majority of our components still use this way
[15:14:10 CDT(-0500)] <heidi_> but prob not in this tutorial
[15:14:12 CDT(-0500)] <anastasiac> yes, we should explain it, but it would be a "side" page
[15:14:20 CDT(-0500)] <anastasiac> not this tutorial
[15:14:32 CDT(-0500)] <heidi_> okay. i'll make it a subpage for now and we can move it
[15:14:36 CDT(-0500)] <anastasiac> thanks
[15:15:10 CDT(-0500)] <Justin_o> anky: hello.. so i'm wondering if write now things are a bit abstract, maybe with the project
[15:15:45 CDT(-0500)] <Justin_o> anky: meaning there's no real direction in what the content of the pages will be
[15:16:12 CDT(-0500)] <Justin_o> anky: do you have something in mind for that?
[15:16:42 CDT(-0500)] <anky> Justin_o: i have also been working on making a simple theme with FSS and UI options to test them
[15:17:06 CDT(-0500)] <Justin_o> anky: that's a good idea
[15:17:13 CDT(-0500)] <anky> Justin_o: there are some problems in it, but would soon get ove them
[15:18:20 CDT(-0500)] <anky> Justin_o: almost done with implementing the FSS in mediawiki theme
[15:18:45 CDT(-0500)] <Justin_o> anky: how are you finding the fss so far?
[15:19:00 CDT(-0500)] <anky> Justin_o: also, i am working on a live installation, ankuranand.in/mediawiki(not working right now), so would be able to test the installation also
[15:19:28 CDT(-0500)] <anky> Justin_o: i have understood fss-text, fss-layout
[15:19:52 CDT(-0500)] <anky> yet to go to fss-layout advanced, and just a rough idea of fss-theme
[15:20:53 CDT(-0500)] <Justin_o> anky: not sure if i mentioned this before, but FSS is undergoing some changes http://wiki.fluidproject.org/display/fluid/FSS+1.4+-+1.5+Roadmap
[15:21:24 CDT(-0500)] <Justin_o> so in your notes that you sent along, you made it sound like UI Options would only be for the focused reading mode? Is that correct?
[15:22:38 CDT(-0500)] <anky> Justin_o: no, it would be for everything, but as you go in the reading option, it slides down on the side automatically, for others you have to activate it
[15:23:51 CDT(-0500)] <Justin_o> Interesting... in this mode, would the changes be global or just for the focused reading?
[15:25:27 CDT(-0500)] <anky> i imagined it to be just for the reading mode, but now that you just pointed it, i am in a little dillema over this
[15:26:22 CDT(-0500)] <Bosmon2> cindyli: Sure
[15:26:42 CDT(-0500)] <anky> Justin_o: what would you suggest ? i think we can give the user an option like - "keep the changes"
[15:27:15 CDT(-0500)] <Justin_o> anky: i think you'd have to make it really clear that the changes in one mode don't affect the presentation in another mode
[15:27:29 CDT(-0500)] <Justin_o> anky: i'm not sure it's actually necessary to have the two
[15:27:40 CDT(-0500)] <Justin_o> but i might have to see the mockups first
[15:28:10 CDT(-0500)] <anky> ya i am on them, would get to you with them asap
[15:28:18 CDT(-0500)] <cindyli> your autoinit example has
[15:28:18 CDT(-0500)]

[15:28:18 CDT(-0500)] <cindyli> the container specifies ".flc-rendererComponent", is there a way to use that.locate("a-selector")? however, the "that" does not yet exist
[15:28:29 CDT(-0500)] <cindyli> Bosmon2: as above
[15:28:46 CDT(-0500)] <Justin_o> you might just be able to have the one global ui options. why were you thinking of having two? I'm curious to know what your thoughts are
[15:28:54 CDT(-0500)]

<Bosmon2> If the subcomponent is configured via IoC, you can use the notation

Unknown macro: {parentComponent}

.dom.selectorName

[15:29:14 CDT(-0500)] <cindyli> ic
[15:29:14 CDT(-0500)] <Bosmon2> Hint: The subcomponent should be configured via IoC
[15:29:34 CDT(-0500)] <cindyli> thx, Bosmon2
[15:30:16 CDT(-0500)] <Bosmon2> Again, in the absence of good documentation on this, looking at some of JURA's CSpace code, although you may need his help to find out where to look
[15:30:40 CDT(-0500)] <anky> Justin_o: no, i was not thinking about having 2 UI options, i wanted to make the content focussed , the UI options would remain the same, only that the sidebar, navigation panels, search bar, all would fade away(darken,dim etc) to give the user focussed content
[15:31:21 CDT(-0500)] <cindyli> thx, Bosmon2.
[15:32:56 CDT(-0500)] <anky> Justin_o: the idea would not change anything about the UI options, but would only make the content focussed
[15:36:25 CDT(-0500)] <Justin_o> anky: I think the idea of the focused content is pretty good
[15:37:18 CDT(-0500)] <heidi_> Justin_o is there a way to make an InfusionAll.js out of the current trunk?
[15:37:36 CDT(-0500)] <Justin_o> anky: I don't necessarily think you need just one ui options.. you could go with the two.. just make sure it is clear to the user that they are different
[15:37:45 CDT(-0500)] <Justin_o> heidi_: sure
[15:37:51 CDT(-0500)] <Justin_o> but you have to use the command line
[15:37:52 CDT(-0500)] <anky> Justin_o: thanks. what about the use of color shades which i have mentioned ??
[15:38:09 CDT(-0500)] <Justin_o> heidi_: you can run the ant build scripts
[15:38:29 CDT(-0500)] <Justin_o> anky: let me double check that... that was for the nav?
[15:38:33 CDT(-0500)] <heidi_> Justin_o k, i don't know much about it - is there a guide in the wiki?
[15:39:00 CDT(-0500)] <Justin_o> heidi_: are you making a custom build.. or just want the infusion all?
[15:39:05 CDT(-0500)] <anky> Justin_o: nav + search results
[15:39:09 CDT(-0500)] <heidi_> Justin_o just infusion all
[15:40:20 CDT(-0500)] <anky> Justin_o: check out http://aarronwalter.com/blog/ , it maked the idea of using shades in search results more clear
[15:41:25 CDT(-0500)] <Justin_o> anky: it's probably better to keep things that are on the same level the same shade... also some of those shades are a bit hard to read... also with the different shades it makes some parts look more important than others...
[15:42:15 CDT(-0500)] <Justin_o> if you are just trying to break them up a bit, you might be able to get away with different colours
[15:42:43 CDT(-0500)] <anky> Justin_o: different colors sometimes hurts the eyes, even if you chose them too subtle
[15:43:33 CDT(-0500)] <Justin_o> anky: this is true
[15:43:45 CDT(-0500)] <Justin_o> which article were you refering to from the blog you posted
[15:44:16 CDT(-0500)] <anky> Justin_o: no article, just the overall arrangement of the blogs
[15:44:24 CDT(-0500)] <anky> like you can see the color shade as you scroll
[15:45:52 CDT(-0500)] <anky> Justin_o: also, i feel the user would on the first hand understand the color scheme wrong(maybe take colors:importance, color:how recent etc ), but then i guess the user would understand the color code eventually
[15:46:45 CDT(-0500)] <anky> but then, it can be a test feature, i m not too sure about using colors in search results myself, but it sure would work in navigation sidebars, breadcrumbs etc
[15:47:42 CDT(-0500)] <Justin_o> anky: yes.. i'm not saying colour would be a good options.. just something else that may work.. i think you'd have to be careful about that too.. As for the blog post, i think it works there because the colours are representative of age, so they add to the heirarchy of the content. in the nave if items are on the same level.. they should appear the same
[15:48:00 CDT(-0500)] <Justin_o> i think i missed the search results part.. so i'll go take a peak at that
[15:48:47 CDT(-0500)] <Justin_o> anky: is there an example of the search results with the shading?
[15:49:04 CDT(-0500)] <anky> Justin_o: no not right now
[15:49:15 CDT(-0500)] <Justin_o> ah okay..
[15:49:21 CDT(-0500)] <Justin_o> so it might make sense for the search results
[15:49:28 CDT(-0500)] <Justin_o> just make sure that the text is still easy to read
[15:50:15 CDT(-0500)] <Justin_o> anky: you might be interested in looking through wcag 2.0 guidlines on colour contrast http://www.w3.org/TR/WCAG20/
[15:50:25 CDT(-0500)] <anky> Justin_o: the search results with shading is actually a bit tough to get the shades, the visual appeal and to get the whole thing working, it would need a lot of iterations
[15:50:52 CDT(-0500)] <Justin_o> anky: okay.. i think then don't worry about the shading then..
[15:52:18 CDT(-0500)] <anky> Justin_o: also, had to discuss the idea of using HTML5, i know about HTML5, worked a bit on it
[15:53:07 CDT(-0500)] <anky> Justin_o: also i wanted to talk about CSS3, but its already on the cards, so would ask you later about what all to do there(once i am done with this work as of now )
[15:53:46 CDT(-0500)] <Justin_o> anky: sure no problem
[15:54:06 CDT(-0500)] <Justin_o> anky: anything else you wanted to chat about now?
[15:55:09 CDT(-0500)] <anky> Justin_o: just about HTML5 in the theme
[15:56:06 CDT(-0500)] <anky> if you can see the notes, there are some issues according to wikimedia, but they are getting fixed
[15:57:23 CDT(-0500)] <anky> Justin_o: if you are busy, we can have this discussion later, i don need it for the next day atleast
[15:57:40 CDT(-0500)] <Justin_o> anky: okay.. i was just looking over the wikimedia page
[15:57:48 CDT(-0500)] <Justin_o> i guess you are wondering if you should be using it or not?
[15:57:55 CDT(-0500)] <anky> Justin_o: ya
[15:58:28 CDT(-0500)] <anky> and there are no live examples other that MDN
[15:58:44 CDT(-0500)] <Justin_o> anky: i guess it's up to you.. at the moment the FSS doesn't have any default stylings or resets for any of the new html5 tags.. although those may be added by 1.4.. not sure about that yet though...
[15:59:43 CDT(-0500)] <Justin_o> I think for now you don't have to worry about using it too extensively.. although it may be interesting if you have time... I can't remember off hand which browsers you were going to test with
[15:59:50 CDT(-0500)] <Justin_o> do they all support html5 though
[16:00:30 CDT(-0500)] <anky> i would just tell you
[16:02:08 CDT(-0500)] <Justin_o> anky: okay... well don't worry too much about html5 at the moment then
[16:02:34 CDT(-0500)] <anky> Justin_o: other that firefox 3.6, all of them do, and even fx -3.6 updated version does
[16:02:53 CDT(-0500)] <anky> Justin_o: ya, it can always be added later, the core components would anyways remain the same
[16:03:02 CDT(-0500)] <Justin_o> anky: okay... so you might want to add in a few tags here and there as needed then
[16:03:40 CDT(-0500)] <anky> Justin_o: ya, i guess i would do HTML5 later, and by then the issues would also be resolved
[16:05:21 CDT(-0500)] <anky> Justin_o: one more thing, the 4 basic functionalities i have shown, do you think its right ? because its like the core of my design
[16:07:06 CDT(-0500)] <Justin_o> anky: I think you didn't speak a lot about your us of UI Options, but maybe there isn't much to say.
[16:07:26 CDT(-0500)] <Justin_o> I guess i'd be curious in knowing which contrasts and etc you'll support
[16:08:36 CDT(-0500)] <anky> Justin_o: ya, actually i havent studied much about UI options, just went through the basics, but i don think there is anything that UI options would do to my deigns
[16:08:44 CDT(-0500)] <anky> *designs
[16:09:03 CDT(-0500)] <Justin_o> anky: okay
[16:09:20 CDT(-0500)] <Justin_o> anky: can you quickly summarize your 4 basic functions again
[16:09:33 CDT(-0500)] <anky> 1. Navigation
[16:09:42 CDT(-0500)] <anky> 2. Reading
[16:09:50 CDT(-0500)] <anky> 3. Editing content
[16:09:57 CDT(-0500)] <anky> 4. User Management
[16:10:16 CDT(-0500)] <Justin_o> number 4 is your Settings Management from the evernote?
[16:10:35 CDT(-0500)] <anky> Justin_o: ya
[16:10:42 CDT(-0500)] <Justin_o> anky: yep i think that's fine
[16:11:10 CDT(-0500)] <anky> (the idea is that they are disjoint, user doing one functionality would usually not do anything to the other )
[16:11:22 CDT(-0500)] <Justin_o> you mean at the same time?
[16:11:23 CDT(-0500)] <anky> is why i came up with the focussed content idea
[16:11:27 CDT(-0500)] <Justin_o> ah okay
[16:11:32 CDT(-0500)] <Justin_o> what about edit?
[16:11:51 CDT(-0500)] <Justin_o> will you have a focussed mode for that too?
[16:12:21 CDT(-0500)] <anky> Justin_o: ya it should be there
[16:12:35 CDT(-0500)] <Justin_o> anky: cool.. i'm interested to see how it will all look
[16:12:36 CDT(-0500)] <anky> because the user is focussed on the content then too
[16:14:08 CDT(-0500)] <anky> Justin_o: same, i am very excited to make the focus feature work seamlessly, nothing very drastic for the user
[16:15:34 CDT(-0500)] <Justin_o> anky: yes.. if you can get it right.. i think it would be very good
[16:16:35 CDT(-0500)] <anky> Justin_o: hmmmm
[16:16:54 CDT(-0500)] <Bosmon2> anastasiac: Could you give me an idea about the plan re. the old docs site and the new one?
[16:17:09 CDT(-0500)] <anastasiac> Bosmon2: <sigh>
[16:17:15 CDT(-0500)] <Bosmon2> So, for example, if I wanted to document the new (in 1.4) "priority" option for events
[16:17:26 CDT(-0500)] <Bosmon2> Should I go ahead and add this to the "old" page documenting "Infusion Event System"?
[16:18:21 CDT(-0500)] <anastasiac> eventually (e.g. circa 1.5) we'll have an all-new docs space which will supercede both the new an old confluence spaces, so my original plan of migrating all of our docs into the new space seems a bit pointless now, so I'd say yes, just add it to the existing docs, with an indication that it's new for 1.4
[16:18:33 CDT(-0500)] <Bosmon2> Ok
[16:18:40 CDT(-0500)] <Bosmon2> But what form will our docs take for 1.4?
[16:18:51 CDT(-0500)] <Bosmon2> Are we planning to direct people to the union of the old and new sites?
[16:19:02 CDT(-0500)] <anastasiac> we're continuing with confluence, yes
[16:19:40 CDT(-0500)] <Bosmon2> Well, if we are planning to get rid of the entire docs space, do you think it makes sense to simply "axe" our "new Confluence space" entirely?
[16:19:47 CDT(-0500)] <Bosmon2> And just fold all the pages back into the old namesapce?
[16:20:00 CDT(-0500)] <Bosmon2> I feel the current setup would be confusing to users who come at it in the 1.4 timeframe
[16:21:16 CDT(-0500)] <anastasiac> Bosmon2, yes, that does make sense. I'll try to find the time to move the pages before the 1.4 release
[16:21:22 CDT(-0500)] <Bosmon2> Ok, that's cool
[16:21:31 CDT(-0500)] <Bosmon2> I can start migrating back my new pages then?
[16:21:39 CDT(-0500)] <Bosmon2> And it's ok to create any further new pages in the old space?
[16:22:22 CDT(-0500)] <anastasiac> Bosmon2, if you'd like to help migrate pages, feel free! and yes, create new pages in the old space.
[16:22:29 CDT(-0500)] <Bosmon2> Ok cool, thanks
[16:22:44 CDT(-0500)] <anastasiac> Bosmon2, if you do move any function api pages, please take care to ensure they're still readable. The new space has custom styles, etc
[16:23:25 CDT(-0500)] <Bosmon2> Ok
[16:23:32 CDT(-0500)] <Bosmon2> Is there anything in particular I should look out for?
[16:23:50 CDT(-0500)] <Bosmon2> Rather, any particular changes I need to make to the headers of pages for example, when I migrate them?
[16:24:34 CDT(-0500)] <anastasiac> Bosmon2, I haven't tried, so I'm not sure what might happen
[16:24:39 CDT(-0500)] <Bosmon2> ok
[16:24:51 CDT(-0500)] <Bosmon2> Well, I'll probably leave function API pages alone, in any case
[16:25:12 CDT(-0500)] <Bosmon2> I'll be mainly writing and moving guides to "framework areas", such as autoInit, IoC and renderer components
[16:25:32 CDT(-0500)] <anastasiac> sounds good
[16:26:51 CDT(-0500)] <Bosmon2> btw, are you seeing that the "sidebar" on the wiki seems to be broken?
[16:26:59 CDT(-0500)] <Bosmon2> That is, on our main Confluence
[16:27:07 CDT(-0500)] <Bosmon2> Although the navigation links work, it never updates to show the current page
[16:27:16 CDT(-0500)] <Bosmon2> For me, right now, it is stuck showing "Fluid Infusion"
[16:27:35 CDT(-0500)] <Bosmon2> Oh wait, never mind
[16:27:45 CDT(-0500)] <Bosmon2> I just misunderstood its visual idiom