Page Comparison

[08:32:57 CDT(-0500)] <Justin_o> heidi_: hello
[08:33:10 CDT(-0500)] <heidi_> hey Justin_o
[08:33:28 CDT(-0500)] <Justin_o> i pushed a minor change to my github account for your 4150 branch
[08:34:06 CDT(-0500)] <Justin_o> it just adds some labels to the columns so they are easier to distinguish when in single col layout
[08:34:40 CDT(-0500)] <heidi_> Justin_o okay thanks - how should i merge them in?
[08:34:59 CDT(-0500)] <Justin_o> you would fetch from my repo, then do a merge into your branch
[08:35:03 CDT(-0500)] <Justin_o> so for example
[08:35:09 CDT(-0500)] <Justin_o> git fetch justin
[08:35:42 CDT(-0500)] <Justin_o> git checkout FLUID-4150
[08:35:54 CDT(-0500)] <Justin_o> git merge justin/heidi-FLUID-4150
[08:35:59 CDT(-0500)] <Justin_o> I think something like that should do it
[08:36:06 CDT(-0500)] <Justin_o> hopefully there's no conflicts
[08:37:08 CDT(-0500)] <heidi_> ok i'll try thatnow
[08:38:42 CDT(-0500)] <Justin_o> heidi_: thanks... did you have a chance to look at the focus stuff yesterday?
[08:38:45 CDT(-0500)] <heidi_> i have to commit my changes first... so when i'm done i'll do that
[08:38:54 CDT(-0500)] <heidi_> not yet - on the list for today
[08:39:34 CDT(-0500)] <heidi_> Justin_o when aligning stuff for linear, do you think the elements themselves should move to say, the right, or just the text within them
[08:39:53 CDT(-0500)] <heidi_> i think the former
[08:47:23 CDT(-0500)] <Justin_o> heidi_: i think i agree with that
[08:47:30 CDT(-0500)] <Justin_o> the former, that is
[08:47:42 CDT(-0500)] <heidi_> Justin_o did we figure out a good name for the linear width style?
[08:47:52 CDT(-0500)] <Justin_o> i'm not sure.. did you see my later suggestions
[08:48:01 CDT(-0500)] <Justin_o> i can't quite remember what they were now..
[08:48:05 CDT(-0500)] <Justin_o> i'll check the logs
[08:48:41 CDT(-0500)] <Justin_o> heidi_: so what do you think of these
[08:48:45 CDT(-0500)] <Justin_o> fl-container-linearflex
[08:48:46 CDT(-0500)] <Justin_o> fl-container-linear100
[08:49:24 CDT(-0500)] <heidi_> Justin_o i don't think container works here cos the width affects every element, not just the container div
[08:49:44 CDT(-0500)] <Justin_o> heidi_: hmm.. just the block level elements right?
[08:49:49 CDT(-0500)] <heidi_> ya
[08:49:53 CDT(-0500)] <Justin_o> okay...
[08:49:58 CDT(-0500)] <Justin_o> hmm i'll keep thinking
[08:50:04 CDT(-0500)] <heidi_> yeah it's tricky!
[08:50:09 CDT(-0500)] <Justin_o> by the way.. with the grid example you have
[08:50:35 CDT(-0500)] <Justin_o> i feel like the individual cells were already linearized.. and it would have been nicer if they were just moved into a single column
[09:05:18 CDT(-0500)] <heidi_> Justin_o check now
[09:05:23 CDT(-0500)] <Justin_o> heidi_ okay
[09:05:24 CDT(-0500)] <heidi_> i'm going to try merging your changes now too
[09:05:28 CDT(-0500)] <Justin_o> heidi_: thanks
[09:05:40 CDT(-0500)] <heidi_> k that worked, i'll push that too
[09:07:38 CDT(-0500)] <Justin_o> heidi_: thanks.. got it.. i'm not sure the centre alignment is working
[09:07:55 CDT(-0500)] <heidi_> Justin_o so i think mostly what's left is making the alignments work properly and go through and fix what looks weird or changes unexpectedly
[09:07:59 CDT(-0500)] <heidi_> Justin_o yep that's next
[09:08:47 CDT(-0500)] <heidi_> and also right now just the text is aligning, not the containers
[09:09:19 CDT(-0500)] <Justin_o> heidi_: what did we say we wanted to do about that?
[09:09:28 CDT(-0500)] <heidi_> Justin_o align the containers
[09:09:39 CDT(-0500)] <heidi_> makes sense right?
[09:10:00 CDT(-0500)] <Justin_o> heidi_: i was just playing with this latest version you have, and it probably doesn't make sense for the unifrom width option
[09:10:07 CDT(-0500)] <Justin_o> since centring will have no effect
[09:10:41 CDT(-0500)] <heidi_> Justin_o yeah aligning the containers doesn't affect full width stuff. hmm
[09:11:18 CDT(-0500)] <Justin_o> heidi_: i guess we should try to think about how people will want to use this stuff
[09:11:31 CDT(-0500)] <heidi_> i wonder if these two types of alignment should be separate. i.e. just use the existing text-align styles and then the container alignment as an alternative to the full width
[09:12:13 CDT(-0500)] <Justin_o> heidi_: seems reasonable
[09:12:35 CDT(-0500)] <heidi_> Justin_o i'm afraid of making linearizing too complex and hard to use
[09:12:57 CDT(-0500)] <heidi_> it shouldn't be, but still have lots of options
[09:12:59 CDT(-0500)] <heidi_> hm
[09:13:02 CDT(-0500)] <Justin_o> heidi_: i would agree with that.. i am starting to worry about that too
[09:18:23 CDT(-0500)] <Justin_o> heidi_: i'm kind of feeling right now like a user would have to change a lot of classes to get things the way they want
[09:19:06 CDT(-0500)] <heidi_> Justin_o i wonder if we should have a default class that has everything in it (widht, alignment) in addition to the existing separated classes
[09:21:44 CDT(-0500)] <Justin_o> heidi_: this might be the same thing.. i was thinking that fl-layout-linear would remain and force everything to the left, but then you could have other versions that forced it to the right, or didn't change the alignment
[09:21:52 CDT(-0500)] <Justin_o> how does that compare with what you were thinking
[09:21:53 CDT(-0500)] <Justin_o> ?
[09:21:56 CDT(-0500)] <heidi_> Justin_o i think layout-align shouldn't do any text-aligning... just align the containers
[09:22:10 CDT(-0500)] <Justin_o> heidi_: okay
[09:22:37 CDT(-0500)] <heidi_> Justin_o hm, i wonder what that idea (yours) would look like in practice
[09:22:56 CDT(-0500)] <heidi_> cos the width issue too
[09:23:21 CDT(-0500)] <Justin_o> you mean it wouldn't matter if they set the width to 100%
[09:23:43 CDT(-0500)] <Justin_o> ?
[09:23:52 CDT(-0500)] <heidi_> right now we basically have 1) fl-layout-linear that strips styles 2) fl-layout-linearwidth or whatever that makes things uniform width 3)fl-layout-align-x that aligns containers
[09:24:18 CDT(-0500)] <heidi_> so our ideal default would be to use all 3
[09:25:03 CDT(-0500)] <Justin_o> heidi_: do the alignments have to have !importants?
[09:25:13 CDT(-0500)] <heidi_> i think so
[09:25:55 CDT(-0500)] <Justin_o> heidi_: and we aren't going to worry about text-alignment anymore, or we will have to add those as well?
[09:26:20 CDT(-0500)] <heidi_> Justin_o not sure, what do you think? it might be weird to align everything right and not the text itself
[09:26:31 CDT(-0500)] <heidi_> meaning maybe both is best
[09:26:49 CDT(-0500)] <Justin_o> heidi_: hard to say.. i guess it really depends on what it is
[09:26:50 CDT(-0500)] <heidi_> in the one layout-align style
[09:27:13 CDT(-0500)] <Justin_o> so for the grid example i think it would be fine to leave it centred even when the container is left aligned..
[09:27:16 CDT(-0500)] <Justin_o> maybe that's just me though
[09:27:32 CDT(-0500)] <Justin_o> jameswy: any thoughts on this?
[09:27:55 CDT(-0500)] <jameswy> Justin_o: Where should I start reading?
[09:28:21 CDT(-0500)] <Justin_o> jameswy: i guess you can start around 10:23
[09:30:18 CDT(-0500)] <heidi_> jameswy did you get a chance to look at the manual-tests/html/fss-linearize.html in my github? i just updated it again
[09:31:38 CDT(-0500)] <Justin_o> heidi_: i'm showing it to him now
[09:31:43 CDT(-0500)] <heidi_> cool
[09:31:50 CDT(-0500)] <Justin_o> heidi_, jameswy skype?
[09:31:56 CDT(-0500)] <heidi_> ya
[09:44:56 CDT(-0500)] <heidi_> Justin_o okay i'm going to try to get alignments working. chat after yr meeting!
[10:47:06 CDT(-0500)] <Justin_o> heidi_: hello, back now
[10:51:34 CDT(-0500)] <heidi_> ok
[10:51:42 CDT(-0500)] <Justin_o> any luck with the alignments
[10:51:54 CDT(-0500)] <Justin_o> i'm wondering if we can really get around that without using floats
[10:52:38 CDT(-0500)] <heidi_> Justin_o yeah or abs positioning. hmmmph
[10:54:03 CDT(-0500)] <Justin_o> heidi_: i think floating everything might work...
[10:54:51 CDT(-0500)] <Justin_o> i'm not sure abs positioning would work.. since we'd have to know where to put everything wouldn't we
[10:54:55 CDT(-0500)] <heidi_> Justin_o floating yah, but not everything...
[10:55:14 CDT(-0500)] <Justin_o> heidi_: i guess this is another reason why everything had a 100% width before
[10:55:21 CDT(-0500)] <heidi_> haha yes
[10:56:38 CDT(-0500)] <Justin_o> heidi_: i floated everything to the right.. it looks awful
[10:56:45 CDT(-0500)] <Justin_o> even the table linearized
[10:56:52 CDT(-0500)] <heidi_> yeah we'd have to pick out things to float
[10:57:23 CDT(-0500)] <heidi_> man, what do you think about forcing 100% width. i really liked having the option to not do that, but it seems to be causing trouble
[10:58:25 CDT(-0500)] <Justin_o> heidi_: yes.. it's true.. i guess if we can make it work we should try not to.. but i'm not sure we should implent something that only works some of the time
[10:58:41 CDT(-0500)] <Justin_o> meaning that sometimes the linearization will make things unreadable...
[10:58:53 CDT(-0500)] <Justin_o> then we should stick with forcing 100% width instead
[10:59:19 CDT(-0500)] <Justin_o> i'm also starting to think we should move the linearization stuff into it's ownfile
[10:59:21 CDT(-0500)] <Justin_o> own file
[10:59:30 CDT(-0500)] <Justin_o> and renaming to fl-linear
[10:59:30 CDT(-0500)] <heidi_> let's try the float thing, and if it's inconsistent we can give up on that
[10:59:37 CDT(-0500)] <Justin_o> heidi_: okay
[10:59:52 CDT(-0500)] <heidi_> not a bad idea... a lot of stuff in fss-layout should be moved out i think
[11:00:18 CDT(-0500)] <Justin_o> heidi_: yes.. we should also go through later and see what stuff should be dropped and moved into that community gallery spot instead..
[11:00:23 CDT(-0500)] <heidi_> ya
[11:01:17 CDT(-0500)] <thealphanerd> Hi guys
[11:01:55 CDT(-0500)] <thealphanerd> harriswong: was it you who said you could point me in the direction of the google documentation
[11:04:09 CDT(-0500)] <harriswong> thealphanerd: yes hi. http://www.booki.cc/gsocstudentguide/_v/1.0/writing-a-proposal/
[11:04:16 CDT(-0500)] <thealphanerd> !!!
[11:04:17 CDT(-0500)] <thealphanerd>
[11:05:22 CDT(-0500)] <harriswong> thealphanerd: You can also check the wiki here: http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents
[11:05:44 CDT(-0500)] <thealphanerd> thanks harris... I appreciate the help
[11:06:41 CDT(-0500)] <harriswong> thealphanerd: you are welcome
[11:09:12 CDT(-0500)] <Justin_o> heidi_: so i tried floating all the block level elements that you had for the fl-layout-width-100 plus the inputs and imgs
[11:09:38 CDT(-0500)] <Justin_o> it looked okay on the sample website, but not really on the other pages.. one problem is that the widths are all messed up
[11:09:45 CDT(-0500)] <heidi_> hm
[11:10:16 CDT(-0500)] <heidi_> Justin_o widths for?
[11:11:28 CDT(-0500)] <Justin_o> for example the border under the h1 was much shorter.. the column widths all collapsed down to the width of the contetns
[11:12:15 CDT(-0500)] <heidi_> ah right
[11:15:41 CDT(-0500)] <colinclark> mlam: Here's the branch I created for the options transformation bug in Uploader: https://github.com/colinbdclark/infusion/tree/FLUID-4174
[11:15:46 CDT(-0500)] <colinclark> With correctly failing tests
[11:16:02 CDT(-0500)] <colinclark> Bosmon and I will put together a solution tomorrow, if all goes well
[11:16:04 CDT(-0500)] <mlam> cool, i'll take a look
[11:16:12 CDT(-0500)] <mlam> thanks!
[11:16:22 CDT(-0500)] <colinclark> Is your branch for the fileTypes stuff all up to date based on our conversation?
[11:17:33 CDT(-0500)] <mlam> Yes, it is, except that I didn't use the fluid.find function
[11:18:32 CDT(-0500)] <mlam> the fluid.find() returns the first match in an object, but in my case, I needed to continue iterating through to find more possible matches.
[11:18:41 CDT(-0500)] <colinclark> ah, okay
[11:18:48 CDT(-0500)] <colinclark> how come?
[11:18:58 CDT(-0500)] <colinclark> I guess I should just go look at your algorithm
[11:19:11 CDT(-0500)] <colinclark> Okay, so consider the fileTypes stuff done from your end
[11:19:24 CDT(-0500)] <colinclark> I'll take care of merging it into the project repo
[11:19:31 CDT(-0500)] <colinclark> once I've fixed my buig
[11:21:28 CDT(-0500)] <colinclark> mlam: Is the ErrorHandler branch ready to go now, too?
[11:22:01 CDT(-0500)] <mlam> It's just that some file types share the same MIME type
[11:22:06 CDT(-0500)] <mlam> ok, t hanks colin
[11:22:12 CDT(-0500)] <mlam> yes, the error handler branch is ready to go too.
[11:22:28 CDT(-0500)] <mlam> I'll have to do a fresh merge again since there were some framework changes last night
[11:24:55 CDT(-0500)] <colinclark> ok
[11:25:43 CDT(-0500)] <colinclark> mlam: One other bit of code review for the MimeTypeCompatibility.js file, if you have time to look at it
[11:26:08 CDT(-0500)] <colinclark> We should probably your fileTypeTransformer into a swfUpload-specific namespace and file
[11:26:09 CDT(-0500)] <mlam> Yes, I have time
[11:26:17 CDT(-0500)] <colinclark> Am I correct in assuming that you only need it in two cases:
[11:26:27 CDT(-0500)] <colinclark> 1. The user is using the old options format
[11:26:44 CDT(-0500)] <colinclark> 2. They are potentially delivering the Flash version of the Uploader?
[11:27:10 CDT(-0500)] <mlam> Yes, that's right
[11:27:10 CDT(-0500)] <colinclark> Looking at the code and the comment above it, it seems like fluid.uploader.fileTypeTransfomer is specific to swfUpload
[11:27:42 CDT(-0500)] <colinclark> I guess maybe I'm stretching that argument, since ostensibly we supported the SWFUpload format for file types in the HTML5 strategy for Infusion 1.3 and 1.3.1
[11:27:48 CDT(-0500)] <colinclark> even thought it didn't actually work
[11:28:29 CDT(-0500)] <colinclark> I'm not quite sure where the right place to put it is...
[11:28:36 CDT(-0500)] <colinclark> We use it in the SWFUploadStrategy
[11:28:48 CDT(-0500)] <colinclark> but then we also use it in the UploaderCompatibility-Infusion1.3.js file
[11:29:03 CDT(-0500)] <mlam> Would there be another case where we would need to add to this file?
[11:29:15 CDT(-0500)] <colinclark> I don't know
[11:29:24 CDT(-0500)] <colinclark> I can't think of one off-hand
[11:31:46 CDT(-0500)] <colinclark> mlam: I think I'd vote for moving this code into the FlashUploaderSupport.js
[11:32:47 CDT(-0500)] <colinclark> and placing it into the swfUploadStrategy "namespace"
[11:33:08 CDT(-0500)] <mlam> I'm up for that. I guess we can always pull t his functionality out into a separate file again if other mime type transformations are ever needed
[11:34:03 CDT(-0500)] <colinclark> sure
[11:34:15 CDT(-0500)] <mlam> Ok, sounds good. I can make the changes
[11:34:16 CDT(-0500)] <colinclark> or if there are other types of transformations that are strategy-specific, they might go there
[11:34:35 CDT(-0500)] <colinclark> One of my goals is to try to keep all the Flash-related code in one place so that people who don't want to deliver the Flash version can just not include a file.
[11:36:24 CDT(-0500)] <mlam> Ok makes sense
[11:47:18 CDT(-0500)] <heidi_> Justiin_o even with full width the logo stays left
[11:47:21 CDT(-0500)] <heidi_> hm
[11:47:26 CDT(-0500)] <heidi_> Justin_o
[11:48:06 CDT(-0500)] <Justin_o> heidi_: ah
[11:48:26 CDT(-0500)] <Justin_o> i guess because there's no text alignment for that
[11:50:13 CDT(-0500)] <colinclark> mlam: Other than that, I've taken one last look at the code and it's awesome
[11:50:25 CDT(-0500)] <colinclark> sorry it took so long to get in
[11:50:40 CDT(-0500)] <mlam> colinclark: np I'm just glad to have it finished and working well
[11:50:51 CDT(-0500)] <colinclark> nice work, mlam
[11:50:54 CDT(-0500)] <mlam> ...and coded well
[11:50:56 CDT(-0500)] <mlam> thanks!
[11:51:06 CDT(-0500)] <colinclark> it is all those things
[11:51:35 CDT(-0500)] <heidi_> Justin_o let's make some decisions for the sake of wrapping this up! let's enforce 100% width for now and come back to it later if we have time?
[11:51:50 CDT(-0500)] <heidi_> fix up the other stuff, and move on
[11:52:02 CDT(-0500)] <heidi_> tabs and grid
[12:01:07 CDT(-0500)] <Justin_o> heidi_: when you say wrap it up for now you mean.. immediately or for 1.4?
[12:01:39 CDT(-0500)] <heidi_> Justin_o yeah for today, then come back to it if there's time before the release to nit pick keeping the width + aligning. what do you think?
[12:03:02 CDT(-0500)] <Justin_o> heidi_: seems practical
[12:03:28 CDT(-0500)] <Justin_o> since it had already set the width to 100%, I think we can get away with leaving it like that
[12:03:46 CDT(-0500)] <heidi_> Justin_o cool i'll make the changes now, and work on fixing tabs and grid
[12:03:54 CDT(-0500)] <Justin_o> heidi_: thanks
[12:04:04 CDT(-0500)] <Justin_o> can you push that change up to your github repo
[12:04:20 CDT(-0500)] <Justin_o> also i'll have to go to that OCGS meeting soon
[12:08:43 CDT(-0500)] <arun197> colinclark: Hi! did you have a closer look at the mail I sent you
[12:09:03 CDT(-0500)] <heidi_> Justin_o okay cool. btw, do you know what's up with the "sliding door" buttons ?
[12:09:46 CDT(-0500)] <anastasiac> jhung, updated the docs architecture designs page to be the new home for your designs, and moved the older designs into a child page:
[12:09:47 CDT(-0500)] <anastasiac> http://wiki.fluidproject.org/display/fluid/Documentation+Architecture+Designs
[12:09:56 CDT(-0500)] <anastasiac> and i added a TOC to make finding particular pages easier
[12:11:20 CDT(-0500)] <Justin_o> heidi_: not sure actually...
[12:11:31 CDT(-0500)] <heidi_> k
[12:13:29 CDT(-0500)] <Justin_o> heidi_: where did those come from?
[12:13:37 CDT(-0500)] <heidi_> Justin_o fss demo
[12:14:09 CDT(-0500)] <heidi_> i think... checking
[12:14:34 CDT(-0500)] <heidi_> Justin_o ah maybe mobile, that makes sense
[12:15:59 CDT(-0500)] <heidi_> Justin_o from tests/framework-tests/fss/html/3.fss.layout.advanced.html
[12:46:04 CDT(-0500)] <jhung> anastasiac: sorry I didn't see your message.
[12:46:15 CDT(-0500)] <jhung> thanks for doing that anastasiac! It looks good!
[13:05:50 CDT(-0500)] <harriswong> Justin_o: I think this is ready to get a pull request: http://issues.fluidproject.org/browse/FLUID-4164.
[13:33:30 CDT(-0500)] <Justin_o> harriswong: thanks for the pull request
[13:33:47 CDT(-0500)] <Justin_o> heidi_: thanks for letting me know where the buttons came from
[13:34:13 CDT(-0500)] <Justin_o> I don't seem to see them here though
[13:34:14 CDT(-0500)] <Justin_o> http://build.fluidproject.org/infusion/tests/framework-tests/fss/html/3.fss.layout.advanced.html
[13:34:28 CDT(-0500)] <heidi_> Justin_o search for "sliding"
[13:34:35 CDT(-0500)] <heidi_> it's white text. i dunno what the deal is with it
[13:35:53 CDT(-0500)] <Justin_o> ah
[13:36:09 CDT(-0500)] <harriswong> justin_o: when would you be free to chat about 1.5.2 upgrade?
[13:36:13 CDT(-0500)] <Justin_o> heidi_: i guess this page is just broken
[13:36:23 CDT(-0500)] <Justin_o> harriswong: you want to chat now
[13:36:47 CDT(-0500)] <harriswong> justin_o: ok
[13:47:30 CDT(-0500)] <heidi_> Justin_o getting kinda burnt out on linearizing. i pushed most recent changes. wanna take a look? some stuff still not aligning. gonna spend the rest of the day on checking out focus and reset and maybe other stuff
[14:02:52 CDT(-0500)] <Justin_o> hey heidi_ sorry.. was chatting with harriswong
[14:03:01 CDT(-0500)] <Justin_o> o
[14:03:09 CDT(-0500)] <Justin_o> i'll take a look at the linearization stuff
[14:03:20 CDT(-0500)] <Justin_o> curious to know what you think of the focus and reset stuff
[14:03:25 CDT(-0500)] <heidi_> cool
[14:03:45 CDT(-0500)] <heidi_> Justin_o btw, the space between tabs is from margin-left:0
[14:03:49 CDT(-0500)] <heidi_> not sure how to get around that one
[14:06:31 CDT(-0500)] <Justin_o> heidi_ ah okay.. that's interesting.. did they have a negative margin before?
[14:06:41 CDT(-0500)] <heidi_> Justin_o wasn't set i don't think!
[14:08:50 CDT(-0500)] <Justin_o> heidi_: the <a> have a -5 left margin
[14:08:58 CDT(-0500)] <heidi_> aha
[14:09:06 CDT(-0500)] <heidi_> weird
[14:09:11 CDT(-0500)] <Justin_o> set by .fl-tabs li a
[14:09:31 CDT(-0500)] <heidi_> is it over-riding the margin set elsewhere?
[14:09:33 CDT(-0500)] <heidi_> strange..
[14:10:16 CDT(-0500)] <Justin_o> hmm.. not that i can see
[14:17:20 CDT(-0500)] <heidi_> Justin_o how do i name one of your branches justin-FLUID-zzzz
[14:17:21 CDT(-0500)] <heidi_> ?
[14:17:32 CDT(-0500)] <heidi_> git branch -b ?
[14:19:33 CDT(-0500)] <Justin_o> heidi_: you've already checked it out?
[14:33:51 CDT(-0500)] <Justin_o> anastasiac, colinclark, jessm: wondering where we are at with the README
[14:34:02 CDT(-0500)] <colinclark> Justin_o: The ball is my court, I think
[14:34:11 CDT(-0500)] <colinclark> I was going to do a quick edit of what anastasiac had in her fork
[14:34:13 CDT(-0500)] * anastasiac is experience deja-vu
[14:34:15 CDT(-0500)] <Justin_o> i'm just wondering because i'm looking at harriswong's pull request and wondering if i should be updating it now with the info about the new version of jquery ui
[14:34:22 CDT(-0500)] <colinclark> I say let's get it in regardless
[14:34:28 CDT(-0500)] <colinclark> and I'll edit it once it's in the project repo
[14:34:34 CDT(-0500)] <colinclark> anastasiac's last round of edits were awesome
[14:34:37 CDT(-0500)] <anastasiac> should I just go ahead and push it?
[14:34:40 CDT(-0500)] <colinclark> anastasiac: yes
[14:34:42 CDT(-0500)] <anastasiac> k
[14:34:45 CDT(-0500)] <colinclark> as long as Justin_o approves
[14:35:01 CDT(-0500)] <Justin_o> anastasiac: i don't remember what it looks like
[14:35:30 CDT(-0500)] * anastasiac is recalling the JIRA so she knows which branch its in
[14:37:08 CDT(-0500)] <anastasiac> Justin_o, it's in my FLUID-4120 branch - there's now a ReleaseNotes as well as the README
[14:37:14 CDT(-0500)] * anastasiac also reminding herself of the content
[14:38:07 CDT(-0500)] <Justin_o> anastasiac: thanks.. i'll take a look at your repo
[14:39:53 CDT(-0500)] <Justin_o> anastasiac: two questions
[14:40:03 CDT(-0500)] <Justin_o> 1) should the release notes be kept up to date as we work
[14:40:42 CDT(-0500)] <Justin_o> 2) when we actually release, what will happen with the "What are we working on now" section in the readme
[14:47:44 CDT(-0500)] <colinclark> Justin_o: That seems like a reasonable approach
[14:50:16 CDT(-0500)] <arun197> colinclark: Hi Thanks for the mail. Learning the fluid infusion framework.
[14:50:36 CDT(-0500)] <colinclark> arun197: Cool, that sounds great
[14:50:37 CDT(-0500)] <arun197> colinclark: Give me few hours time. I ll come up with something with infusion framework on mind
[14:50:44 CDT(-0500)] <colinclark> sure
[14:50:50 CDT(-0500)] <colinclark> go for it
[14:51:08 CDT(-0500)] <arun197> colinclark: yup! on a great note
[14:52:55 CDT(-0500)] <heidi_> arun197 i took a shot at writing an intro to infusion, not sure if it'll help guide you a bit: http://wiki.fluidproject.org/display/fluid/Developer+Introduction+to+Infusion+Framework
[14:53:13 CDT(-0500)] <colinclark> ooh, this is cool
[14:53:19 CDT(-0500)] <colinclark> I hadn't seen that, heidi_
[14:53:26 CDT(-0500)] <Justin_o> heidi_: so for the branch thing.. i think you can do git checkout NameOfBranch
[14:53:34 CDT(-0500)] <heidi_> colinclark still might need work, but hopefully it helps!
[14:53:40 CDT(-0500)] <Justin_o> where NameOfBranch would just be something like FLUID-xxxx
[14:53:41 CDT(-0500)] <arun197> heidi_: Awesome. thanks a ton
[14:54:13 CDT(-0500)] <Justin_o> heidi_: if you want it to have a different name in your repo though.. i think you'll have to rename it after
[14:54:25 CDT(-0500)] <heidi_> arun197 the 'types of components' section needs more attention... but it's a start!
[14:54:28 CDT(-0500)] <Justin_o> alternatively.. you can do git checkout justin/nameOfBranch
[14:54:40 CDT(-0500)] <Justin_o> then do git checkout -b yourNameOfbranch
[14:55:09 CDT(-0500)] <arun197> heidi_: cool! Will make note of it
[14:55:14 CDT(-0500)] <heidi_> cool thanks Justin_o so i can do git checkout to just look at it, and name a branch of my own with it if i want to make changes
[14:55:26 CDT(-0500)] <arun197> heidi_: I shall get back to you!
[14:56:17 CDT(-0500)] <heidi_> arun197 yes let me know if it helps or if some things are still fuzzy. you'll also see the 'creating a component' page is in progress. but if you search the wiki for 'how to create a component' there's another rough tutorial
[14:58:08 CDT(-0500)] <arun197> heidi_: Yup okay
[14:58:50 CDT(-0500)] <anastasiac> Justin_o, short answers to your questions: 1) good question. 2) We should update it to reflect plans for next release
[14:58:52 CDT(-0500)] <Justin_o> heidi_: yep
[14:58:55 CDT(-0500)] <anastasiac> longer answers:
[14:59:24 CDT(-0500)] * anastasiac tries to remember what the long answers were
[15:04:39 CDT(-0500)] <jhung> anastasiac: I've uploaded some revised images for the API page. See here: http://wiki.fluidproject.org/display/fluid/Documentation+Architecture+Designs#DocumentationArchitectureDesigns-ComponentAPIpageexample
[15:05:02 CDT(-0500)] <anastasiac> jhung, thanks - I did see some of them. it's looking much better
[15:05:07 CDT(-0500)] <anastasiac> I'll take a closer look in a bit
[15:06:33 CDT(-0500)] <jhung> anstasiac: Thanks! In particular I'm wondering if we can handle the deprecation notes a bit better (see hideAnimation under the Progress mock-up).
[15:09:38 CDT(-0500)] <anastasiac> so Justin_o, we identified two ways to deal with the 'release notes' 1) leave it as-is until we're about to release, or 2) update it as we go in prep for the next release
[15:10:14 CDT(-0500)] <anastasiac> personally, I think that the release notes that is present in "trunk" would be fine to be kept up-to-date as we go - then it would more accurately reflect the current code base
[15:10:55 CDT(-0500)] <anastasiac> but we should put a caveat next to the version number, like "pending" or "expected release date: early May" since 1.4 (for example) is not actually out yet
[15:11:45 CDT(-0500)] <anastasiac> The "what are we working on" should give the reader of the README an idea of what things are currently in flux in the "trunk", I think, so after a release, update to the roadmap for the next release
[15:11:52 CDT(-0500)] <anastasiac> does that make sense, Justin_o?
[15:12:05 CDT(-0500)] <Justin_o> anastasiac: i wonder if we just want to have the version number as 1.4-SNAPSHOT or something like it is in the rest of the code
[15:12:12 CDT(-0500)] <anastasiac> good idea
[15:12:27 CDT(-0500)] <anastasiac> we'd clean it up before the release
[15:12:34 CDT(-0500)] <Justin_o> anastasiac: yep
[15:12:43 CDT(-0500)] <anastasiac> and we should probably update release notes in the branch before we merge it into trunk
[15:12:47 CDT(-0500)] <anastasiac> since it's still for 1.3.1
[15:12:58 CDT(-0500)] <Justin_o> anastasiac: yes please
[15:13:11 CDT(-0500)] <anastasiac> ok, I'll do that now, and run it by you one last time before merging
[15:13:28 CDT(-0500)] <Justin_o> anastasiac: thanks.. i'm about to leave for the day though, but i can take a look at it tomorrow
[15:13:35 CDT(-0500)] <anastasiac> sure
[15:17:26 CDT(-0500)] <arun197> heidi_: stuck halfway on creating a component. you have any other tutorial link for that?
[15:18:02 CDT(-0500)] <heidi_> arun197 yep it's not done. you can try this tutorial http://wiki.fluidproject.org/display/fluid/How+to+Create+a+Fluid+Component
[15:18:34 CDT(-0500)] <arun197> thanks
[15:28:34 CDT(-0500)] <anastasiac> colinclark and Justin_o, back when we talked about creating the release notes file, we talked about moving away from the downloadable zip files on the website, and using github instead. First: did I understand that correctly, and if so: second: would that be the plan for 1.4, or post-1.4?
[15:29:07 CDT(-0500)] <Justin_o> anastasiac: can't exactly remember
[15:29:10 CDT(-0500)] <colinclark> I don't know that we really even want to encourage downloading zip files for 1.4 and beyond
[15:29:13 CDT(-0500)] <colinclark> What do you guys think?
[15:29:16 CDT(-0500)] <colinclark> Is the Builder enough?
[15:29:32 CDT(-0500)] <Justin_o> colinclark: i guess if they want the tests they will need to get it from github
[15:30:05 CDT(-0500)] <anastasiac> I like the idea of just the builder and github, and no more zip files
[15:32:49 CDT(-0500)] <Justin_o> anastasiac: and they can get zip files from github if they really want it
[15:33:06 CDT(-0500)] <Justin_o> they just wont get the infusionAll and war files
[15:33:06 CDT(-0500)] <anastasiac> right
[15:35:35 CDT(-0500)] <anastasiac> cindyli and jamon: I just tried to download something using the builder, and I got an error message "Cannot create cache directory"
[15:35:41 CDT(-0500)] <anastasiac> is this a known issue?
[15:36:14 CDT(-0500)] <cindyli> anastasiac: seems like a permission issue
[15:36:55 CDT(-0500)] <anastasiac> yes, perhaps. Not good. It means that if there isn't already a cached version of the requested configuration, the user can't download. jamon, any ideas?