*** You have joined channel #concourse
*** Users on #concourse: technomancy @evilchelu 
*** #concourse modes: +sn
*** #concourse was created on Saturday 2006/06/17 11:06:12 AM
*** Fullmoon_mobile (n=Fullmoon@chello080108092034.22.11.vie.surfer.at) has
    joined channel #concourse
<evilchelu> yo yo yo
<evilchelu> :)
*** evilchelu (n=evil@89.136.147.205) has changed mode for #concourse to +oo
    Fullmoon_mobile technomancy
<technomancy> go team!
<Fullmoon_mobile> Hey there :) Sorry for letting you hang..
<technomancy> no worries; we can still rock this contest
<evilchelu> :>
<technomancy> Fullmoon_mobile: got a copy checked out running?
<Fullmoon_mobile> I am on my way ;)
<evilchelu> i'll commit soon the meeting form
<technomancy> excellent
<Fullmoon_mobile> Though I do not know for how I long I can carry on, my
		 girlfriend proposed that we go out at the evening, to get our
		 minds off that... fight we had, and she would be super-mad if
		 I would cancel -- but there are still some hours left
<technomancy> if you need to go, i'll understand
<technomancy> just make *sure* you check in first!!! =D
<Fullmoon_mobile> Sure - I just does not want to make even more akward than
		 they are already
*** Fullmoon (n=Fullmoon@chello080108092034.22.11.vie.surfer.at) has joined
    channel #concourse
<technomancy> wups, forgot to add a file; you'll need to svn up
<Fullmoon> Here is the screenshot:
	   http://www.slash7.com/railsday/freckle_sneak_sm.png
<Fullmoon> Looks suspicious
<technomancy> hmmm...
<technomancy> our name is better
<technomancy> our spectate isn't updating. =(
<Fullmoon> Checked out and got it working - what are you guys doing at the
	   moment?
<evilchelu> hm, should i commit all yui or only the calendar?
<evilchelu> i'm commiting the meeting form thing
<technomancy> Fullmoon: i was thinking you could do the invitation emails
<Fullmoon> Will do
<Fullmoon> technomancy: And what are you working on atm?
<technomancy> there's an invite method in the user class
<technomancy> i'm working on getting noncontinuous ranges working so we can do
	      math with peoples' times
<technomancy> adding methods to the range class; much fun
<technomancy> we haven't set up any actionmailer stuff at all yet
<Fullmoon> I will have a look at it :)
<evilchelu> i just commited the meeting form!
<evilchelu> update and check it out :)
<technomancy> basically User#invite needs to send an email based on whether
	      they are a new user (inviting them to create an account) or an
	      existing user (inviting them to specify their time on a certain
	      meeting)
<technomancy> evilchelu: sweet!
<evilchelu> i'll get to removing the sidebar now
<technomancy> kewl
<Fullmoon> There is no controller for the user login yet, right?
<evilchelu> there is, account
<technomancy> it was generated by acts_as_authenticated
<technomancy> totally dig this calendar widget; it looks awesome
<evilchelu> technomancy, take a look in the meeting_controller to see if it's
	    bad what i did in new
<technomancy> will do
<technomancy> evilchelu: good stuff; just need to add an error message if the
	      save fails
<evilchelu> cool :)
<evilchelu> i was thiking those might be in the model or something
<evilchelu> wasn't sure
<technomancy> oh, you're right
<technomancy> it already shows the errors
<technomancy> cool
<evilchelu> i quite like how the form turned out with fieldsets and all that
<evilchelu> :)
<technomancy> yeah, dig the fieldsets
<technomancy> i just learned about fieldsets like a month ago
<evilchelu> heh
<technomancy> could you style the flash[:error] messages?
<evilchelu> they aren't?
<evilchelu> oh, the inside of them
<evilchelu> oh crap
<evilchelu> i'm on it :)
<technomancy> curious: why are list and index separate actions in the meeting
	      controller?
<evilchelu> i have no idea, it's stuck in my brain from using scaffolding
<evilchelu> ...
<technomancy> i'm going to move list to index unless there are objections
<technomancy> heh, all right
<evilchelu> :)
<technomancy> i'm seeing that the <select>s in "Timing details" are a little
	      too small
<technomancy> (i can only see "5:0" rather than "5:00"
<technomancy> )
<Fullmoon> The interface for scheduling a meeting already creates a user for
	   each entered email address, should we not keep track if a user
	   confirmed ("created") his account?
<evilchelu> technomancy, ok, will fix
*** evilchelu (n=evil@89.136.147.205) has changed mode for #concourse to +o
    Fullmoon
<technomancy> Fullmoon: i was thinking about that, but then i couldn't think
	      of a reason why i would need it
<technomancy> if you can, go ahead and make the change
<Fullmoon> I am still analyzing how everything works together, dont want to
	   break anything :)
<technomancy> ok
<Fullmoon> Then we need a way for a user that was created via that interface
	   to "sign up", right?
<Fullmoon> Or, we could provide him with a provi... um...
<technomancy> actually, if the user was created by the invitation process,
	      they should be able to just log in
<Fullmoon> Damn - my english sucks, wait a sec
<evilchelu> with what pass?
<technomancy> signup is for creating accounts that don't exist
<Fullmoon> With a password that we create?
<technomancy> yeah, there's already a random password created when the new
	      account is made
<Fullmoon> And the user can change later, that we we would spare him "signin
	   up"
<technomancy> exactly
<technomancy> seems more convenient that way
<evilchelu> ya, you can spam people easier that way :D
<evilchelu> kiddin' :)
<technomancy> heh
<evilchelu> waaa, our spectate is down :/
<Fullmoon> Got it now :)
<Fullmoon> evilchelu: Do you want html mail, plain or both?
<technomancy> oh, one problem--right now the invite method doesn't have any
	      way of knowing the password; i'll add that in
<evilchelu> Fullmoon, i think plain will do, don't you?
<Fullmoon> evilchelu: Yes, me too
<technomancy> i vote for plain
<evilchelu> omg, unanimous vote!
<Fullmoon> technomancy: I should be able to simple call "self.password", since
	   it is created before invite is called
<technomancy> Fullmoon: oh yeah, that should do it actually since it's in the
	      same request and the unhashed version is still in memory
<technomancy> good call
<technomancy> our test-to-code ratio is getting low; i'll see if i can spruce
	      up the functional tests
<Fullmoon> technomancy: Should we pass the controller to the actionmailer
	   instance in order to retrieve an login url (unclean imho), or
	   should I use a fixed uri?
<technomancy> can we generate the uri and pass that by itself?
<technomancy> url_for might do the trick
<Fullmoon> technomancy: we could also pass the url too, but we would still
	   need to pass it to User#invice
<Fullmoon> *invite
<Fullmoon> I will take care of that
<technomancy> oh, activerecord can't do url_for?
<technomancy> hmmm
<Fullmoon> technomancy: Only ActionController
<Fullmoon> ideas?
<technomancy> i'd say just go fixed at that point
<Fullmoon> Sure
<technomancy> it's just the login url, right? a single thing that's not likely
	      to be renamed
<Fullmoon> I will point it to localhost:3000/account/login/, so that the juri
	   can test it without hassle, okay?
<evilchelu> hmm
<technomancy> no, just do "/account/login"
<technomancy> the browser will add the hostname
<evilchelu> technomancy, you don't have / in email
<evilchelu> :)
<technomancy> what?
<evilchelu> this is for email, right?
<evilchelu> what people get in their email to login
<Fullmoon> Yes
<technomancy> oh... duh
<technomancy> sorry
<technomancy> not thinking
<evilchelu> :)
<technomancy> damn
<technomancy> i guess we better pass it through all the way from the
	      controller then
<Fullmoon> Ok!
<technomancy> fixed path is not bad; fixed hostname+path is problematic
<Fullmoon> or we could be $evil ;)
<technomancy> heh; that's points off
<Fullmoon> I was just kidding :)
<technomancy> of course
<evilchelu> so, have a config var or smth?
<technomancy> oh, you could set a constant in environment.rb, i suppose
<Fullmoon> That sounds not bd
<technomancy> or LOGIN_URI ||= something in ApplicationController
<evilchelu> ya, and put a big thingy in the readme... if you're host is not
	    localhost:3000, change this
<evilchelu> and then default to localhost:3000 so it works out of the box on
	    webrick and mongrel
<Fullmoon> I could make a login_url instance variable for Meeting
<evilchelu> s/you're/your/
<Fullmoon> technomancy: I do not  think ApplicationController is accessible
	   from ActionMailer
<technomancy> i think if you set a constant in applicationcontroller, you'd be
	      able to access it
<technomancy> ApplicationController::LoginUri
<Fullmoon> technomancy: I will try that
<technomancy> that's the cleanest solution i can think of
<technomancy> i don't want the judges to have to manually set it because they
	      will be really sick of doing stuff like that by the time they
	      reach our app. =)
<evilchelu> well, if they're on webrick... and we default to localhost:3000 as
	    Fullmoon suggested, they might not have to
<technomancy> oh, that's true
<technomancy> i guess both solutions would work just fine
<technomancy> evilchelu: what are you working on now?
<evilchelu> removed the sidebar and moved that stuff to navbar
<evilchelu> was about to commit
<technomancy> cool
<evilchelu> so, we don't show anything to users without accounts?
<technomancy> just the login and signup pages
<technomancy> oh, and the faq
<evilchelu> hm, not friendly enough
<technomancy> how about we change the routes so all the account/ actions don't
	      need to specify the controller?
<technomancy> localhost:3000/signup, localhost:3000/login, etc
<Fullmoon_mobile> technomancy: already did that
<technomancy> cool
<evilchelu> hah :)
<technomancy> evilchelu: not friendly enough, huh?
<technomancy> what do you think we should change?
<evilchelu> as a not user, i'd like to see something without an account
<technomancy> like a demo, or an actual meeting?
<evilchelu> dunno
<evilchelu> whatever, doesn't matter now
<evilchelu> :)
<evilchelu> ignore me
<evilchelu> so, i should start on that show and register_times page then
<technomancy> that would be great
<technomancy> i think it would be cool to have a demo
<evilchelu> but, i'll go grab some food and redbull first
<technomancy> but after we get it working... =)
<evilchelu> exactly :)
<technomancy> caffiene! yaye!
<evilchelu> yeh, my thing. since i can't stand coffee
* technomancy is a tea guy
<technomancy> though i had coffee this morning since it gets the caffiene into
	      your system faster than tea. =)
<evilchelu> i'm used to not sleeping tho
<technomancy> the trick with coffee is you add cream and sugar until you like
	      it
<technomancy> eventually it works. =)
<evilchelu> bleh
<technomancy> it just ends up tasting like candy
<evilchelu> :))
<evilchelu> ok, so i fixed that select padding things
<technomancy> great
<evilchelu> ok, i'll skip the next 30 minutes, just let me know if you find
	    interface bugs
<technomancy> aye
<Fullmoon> Commited
<Fullmoon> technomancy: on what are you working currently? where could I help?
<technomancy> oh, sorry; i was taking a break
<technomancy> let's see.... tests for the mailer would be awesome
<technomancy> another thing would be to make sure users trying to log in have
	      JS enabled
<Fullmoon> will do
<technomancy> cool
<Fullmoon> currently many tests break, do you know that?
<technomancy> yes, but i think they all break because of things that aren't
	      implemented yet
<technomancy> which is as it should be imho
<Fullmoon> I will look in the two other cases
<technomancy> which are they? i might have a fix that hasn't been checked in
	      yet
<Fullmoon>  1) Error:
<Fullmoon> test_create(MeetingControllerTest):
<Fullmoon> NoMethodError: You have a nil object when you didn't expect it!
<Fullmoon> The error occured while evaluating nil.>
<Fullmoon>
	   /Users/Fullmoon/Webs/concourse/config/../app/models/meeting.rb:34:in
	   `validate'
<technomancy> i've got that one covered
<Fullmoon>  5) Failure:
<Fullmoon> test_status(MeetingTest) [./test/unit/meeting_test.rb:17]:
<Fullmoon> <:open> expected but was
<Fullmoon> <:ready>.
<technomancy> ah, that is also not yet implemented
<technomancy> it's just not marked as such; i will mark it
<Fullmoon> Very nice :)
<technomancy> can you write some new tests for the invitation code?
<evilchelu> back!
<technomancy> cool
<technomancy> ready to roll on meeting/show?
<evilchelu> indeed
<evilchelu> :)
<evilchelu> hm, when adding the current user to the attendances shouldn't he
	    also be added as being available for the whole period?
<technomancy> evilchelu: good question
<technomancy> i think it could go either way
<evilchelu> ok, no biggie
<evilchelu> another one: when we store the times for a user, because of time
	    range, we'll have a lot of ranges for each user, right?
<evilchelu> one for each day
<technomancy> at least one for each day
<technomancy> i'm working on a NoncontinuousRange class
<evilchelu> right
<evilchelu> oh
<technomancy> that will be how we store the time ranges
<evilchelu> i trust you on that one :)
<technomancy> i should have an initial version checked in soon
<technomancy> the first question, i guess is how do we get the range data to
	      the server
<technomancy> do we make ajax calls every time the selection changes?
<technomancy> or do we store the range as JS variables and post it when they
	      hit "save" or something
<evilchelu> hm
<evilchelu> as the saying goes, it could go either way :)
<technomancy> i think the first one is more convenient for the user, but it
	      may be more difficult to implement
<technomancy> i like the idea of not having to save explicitly
<evilchelu> why would it be more difficult?
<evilchelu> rails makes ajax easy, so they say :)
<technomancy> i speak from ignorance. =)
<technomancy> if it's easy, go for it; i think it's the better option
<evilchelu> ok, so, i'm not sure how the interface to add a range will be tho
<technomancy> you mean how you to post the values?
<evilchelu> no, UI
<technomancy> oh, right
<evilchelu> oh, i know
<evilchelu> so, we have days as columns
<evilchelu> for each column, the user can enter time slices
<technomancy> using the yahoo calendar widget, or no?
<evilchelu> i think not
<evilchelu> since we already have the dates
<technomancy> so a block of divs then?
<evilchelu> ya
<evilchelu> just like google calendar
<evilchelu> days as columns
<technomancy> so we would show a week at a time?
<technomancy> and then have links to go forward/back a week?
<evilchelu> well, i think we should restrict the admin so he doesn't choose a
	    too big of a range
<evilchelu> or something
<technomancy> hmmm
<technomancy> let me propose an alternative and you can tell me if it's sane
<evilchelu> no, i'd rather have it in a scrolling div
<evilchelu> so we don't need pagination
<evilchelu> ok, shoo
<evilchelu> shoot
<technomancy> have that same yahoo calendar widget off to one side with only
	      the valid dates active
<technomancy> when you click on a date, it brings up a long div for the day
<evilchelu> you can select multiple dates in that too
<technomancy> then you could drag and drop to specify the ranges
<evilchelu> so the user could click all his dates
<technomancy> oh, that would be cool
<evilchelu> so we'd get more vertical divs
<evilchelu> but, the problem with that is that you don't see everything
<evilchelu> i mean, you don't see other people's status
<technomancy> i think you could still do the colorization based on other
	      peoples' status
<evilchelu> oh, maybe we could have that calendar and have everything already
	    selected
<technomancy> or in the vertical div that represents the day, you could have
	      two columns
<evilchelu> with a toggle, select all/select none
<technomancy> first column you toggle on/off the hours you can make it
<technomancy> second column indicates how many others can attend
<technomancy> (using either numbers or the darkness of the color)
<evilchelu> i didn't say it's not possible, i just think that it's much nicers
	    to be able to view all the dates at once when you decide when you
	    can go
<evilchelu> becuase... when you first see it, you'll want to see what other
	    people are doing, then you'll add yourself
<technomancy> yeah, that's true
<technomancy> perhaps we could color the dates in the calendar widget based on
	      how many people could come?
<technomancy> you wouldn't see an hour-by-hour breakdown, but it might be a
	      good compromise
<evilchelu> hm, from the docs that seems possible
<evilchelu> btw, why to the time pickers only show times after 5am?
<technomancy> ehh; sanity check? =D
<technomancy> we could do earlier, just wanted to reduce clutter
<evilchelu> uh, i didn't see any code for that
<evilchelu> i don't know who sets that
<technomancy> meeting helper
<evilchelu> that's why i'm asking :)
<evilchelu> oh, k
<evilchelu> and, what happens if start time is bigger than end time? say 23:00
	    to 03:00
<technomancy> there's already validations to stop that; you can try it and see
	      for yourself. =D
<evilchelu> oh, k
<evilchelu> so we must go home like cindirella :)
<technomancy> also for start/end dates and decide_by
<evilchelu> or however you spell that
<technomancy> yup! =)
<evilchelu> ok, so... proposed solution:
<evilchelu> have a yahoo thingy on top, with only the valid dates allowed
<evilchelu> then, as the user selects a date, a vertical div for it appears
	    below... if there are too many, a horizontal scroll will appear
<evilchelu> those day divs will show somehow info about current users coming
	    and allow the user to insert some ranges of time
<evilchelu> for the initial version, the user will only be able to select the
	    whole day
<technomancy> yeah, that sounds good
<evilchelu> i'll later add stuff like colors for the datepicker based on
	    number of people, etc. if i'm still awake :)
<technomancy> awesome
<evilchelu> but i think we should get it just working with at least 4 hours
	    before the deadline
<technomancy> yeah, i think it would be good to start with a simpler goal just
	      in the interests of getting it done before you collapse
<evilchelu> and i mean, everything working!
<evilchelu> so, we're T-7.5
<technomancy> yep
<evilchelu> we should pretty much finish everything in 2.5hours i say
<evilchelu> and then another hour to integrate and test stuff
<evilchelu> then the rest of the time, add features
<technomancy> sounds reasonable
<evilchelu> m'kaaay
<technomancy> Fullmoon: how's it coming?
<evilchelu> btw, can we add, punch and pie to the end of the emails?
<evilchelu> :D
<evilchelu> as in: "ps: punch and pie"
<Fullmoon> Wrote an simple test for mailer, now writing a test for User#invite
<technomancy> excellent
<evilchelu> not going out after all?
<Fullmoon> Not yet :)
<technomancy> wow, our spectate is up to date, but it's missing rev 19 - 27
<evilchelu> and 2-4
<evilchelu> :)
<technomancy> weird
<evilchelu> and some others
<evilchelu> ya, it sucks
<technomancy> well, it's pretty impressive considering it was written like a
	      day ago
<evilchelu> oh
<evilchelu> didn't know that :)
<evilchelu> what should happen when you edit a meeting?
<technomancy> oh, i was thinking just show the original form
<technomancy> you should be able to make changes and invite new people
<technomancy> the wording should probably be different for inviting new people
	      though
<evilchelu> hm, so the list of current people should be available too
<technomancy> oh yes, that too
<evilchelu> ok, we'll save it for later
<evilchelu> :)
<technomancy> yeah, i think i could handle that after i go to sleep
<technomancy> i'd rather have you focus on the meeting show and decide_times
<evilchelu> okaay
<evilchelu> so, how will the data be available, list of ranges per day for
	    each users?
<technomancy> ok, i've got a subclass of Array called NoncontinuousRange
<technomancy> you can treat it like [(5 .. 7), (12 .. 15)]
<technomancy> but you can also do addition and subtraction on it
<evilchelu> available times are hourly?
<technomancy> (well, you will be able to)
<technomancy> yes
<evilchelu> ok, the meeting form is with half hours
<technomancy> oh, no wait... they'll be Time object
<technomancy> s
<evilchelu> uh?
<technomancy> they need to have date/time data
<technomancy> [(2006-06-17 5:00 .. 2006-06-17 7:00) ... etc]
<technomancy> hmmm
<evilchelu> omg, i'm gonna need some helpers :)
<technomancy> or maybe it should just be an array for every day
<technomancy> how about this
<evilchelu> ya
<evilchelu> i'd like that
<technomancy> you have a hash, you put in a date, and you get out an array of
	      integer ranges
<evilchelu> i'd rather have an array of days, that each holds an array of
	    ranges
<evilchelu> ya
<technomancy> hash rather than array is ok though, right?
<Fullmoon> simple tests commited
<technomancy> awesome
<evilchelu> i think it's better, since the user will be able to select
	    noncontiguous date ranges
<technomancy> yeah, an array would make it unweildy to skip a day
<technomancy> ok, it's decided; hash of arrays of ranges
<technomancy> whew!
<technomancy> Fullmoon: cool; so can you next do a check to see if the user
	      has JS enabled?
<Fullmoon> Sure
<technomancy> excellent
<technomancy> Fullmoon: after that, maybe work on a way for users to get their
	      passwords reset and emailed to them in case they forget them
<Fullmoon> :) Yeah!
<technomancy> and after that, make it adjust based on the users' timezone, and
	      also import free/busy data, and then make it read your mind so
	      you don't have to type
<technomancy> think you can handle all that?
<technomancy> =)
<Fullmoon> first things first :)
<technomancy> ok, ok. if you say so.
<Fullmoon> evilchelu: <noscript seems to work in every browser, do you have a
	   problem with that?
<evilchelu> no
<evilchelu> it has some bugs in ie3 or ie4 tho :D
<technomancy> that sounds good; so it'll warn them that it won't work right
	      and recommend they turn on JS?
<Fullmoon_mobile> Yes
<technomancy> i was originally thinking disallowing them to log in, but i like
	      that idea better
<Fullmoon_mobile> And we need no hide-form magic
<technomancy> good stuff
<Fullmoon> I prefer it, when the user gets a link mailed to reset his
	   password, instead of mailing him a new one, or security questions
<technomancy> yeah, that's a good idea
<technomancy> have an accounts/reset_password action
<evilchelu> brb, 10-15 minutes, i need to clear my head and decide how to do
	    this show
<technomancy> but the user must provide the verification token he gets in his
	      email
<technomancy> evilchelu: see you in a few
<technomancy> Fullmoon: is that what you mean?
<Fullmoon> Yes
<technomancy> sounds good
<Fullmoon> I am just thinking what I will send him as token, without
	   introducing a new database field
<Fullmoon> Mabe a substring of a hash of the hashed password
<technomancy> heh; i was about to suggest that
<technomancy> or a substring of the salt
<technomancy> actually, the user table already has a "verification" column in
	      it
<technomancy> i added it thinking i would need it for invitations, but i
	      realized it was unnecessary
<technomancy> so you could use that, or use the salt and get rid of that
	      column
<Fullmoon> :) 10 minute break first, need something to drink
<technomancy> yeah, i need to rest my eyes too
<technomancy> baaaack!
<technomancy> and ready to rock
<evilchelu> so
<evilchelu> major mental blockage
<technomancy> ah, bad stuff
<evilchelu> i can't think of a decent UI that i think i'll actually manage to
	    finish for this
<evilchelu> and i can't figure out what to simplify
<technomancy> the originally proposed one is too complicated?
<evilchelu> and i also don't want to have a zillion add range buttons
<evilchelu> ya, i don't think i'll finish a block drawing lib at this time
<technomancy> ok, so we've got a vertical "day" div and a small calendar
<evilchelu> i'll check to see if there's something already done in the
	    available js libs
<technomancy> the day div has each half-hour marked off
<evilchelu> i know that walter zorn guy had some
<evilchelu> hal hour?
<evilchelu> half?
<evilchelu> i thought we were only doing full hours
<technomancy> each half-hour's onclick changes its color and sends an ajax
	      call to the server
<technomancy> right, full hours
<technomancy> we can just change the "length" selector then
<evilchelu> oh, so you have to click 10 dates to select 10 hours?
<technomancy> yeah
<evilchelu> i mean, 10 boxes?
<evilchelu> oooh
<evilchelu> i wasn't even considering that :)
<technomancy> it's not as intuitive as drag and drop, but it would be quicker
	      to implement
<evilchelu> i thought it would be too much work for the user
<technomancy> it's a good fallback; we can improve on it if we have time
<evilchelu> and also, i think we should batch set them, with a specific save
	    button
<technomancy> ok
<evilchelu> since maybe the user changes his mind, eh?
<technomancy> sure
<evilchelu> ok, already better :)
<evilchelu> so your lib will handle all this range mergins i suppose, right?
<technomancy> are you planning on going till you collapse, or are you planning
	      to sleep a bit and then wake up before it's over?
<evilchelu> merging
<technomancy> yeah, i think it would be way easier to handle server-side
<evilchelu> technomancy, if i sleep, i'm not waking up in time :)
<technomancy> ok, so full steam ahead! =)
<evilchelu> :>
<technomancy> one thing i'm curious about: what is chelu?
<evilchelu> ha :)
<evilchelu> so, chel means bald
<evilchelu> chelul = the bald
<evilchelu> chelu = tha bald
<technomancy> heh
<evilchelu> or something
<evilchelu> but i'm not bald
<evilchelu> long story that :)
<technomancy> maybe another time then.
<evilchelu> you won't get it then either... the final i already told you
<evilchelu> but how it got there...
<evilchelu> it's some stupid romanian play of words that somehow ended up like
	    this :)
<evilchelu> and for some reason stuck
<technomancy> thought it might be something like that
<technomancy> ok--later, when we get too tired to code, that's when we write
	      the faq
<technomancy> that'll make things interesting... =)
<evilchelu> ya, those last 4 hours :)
<Fullmoon> :)
<technomancy> the answer to every question is "chunky bacon!" =)
<evilchelu> chelu is pronounced like... keloo
<evilchelu> and it usually sounds a bit aggressive and mean over here... but
	    i'm thin and harmless. quite a chuckle :)
<Fullmoon> Nearly finished
<technomancy> rock on
<technomancy> dibs on migration #3
<technomancy> never mind, the migration didn't help
<evilchelu> technomancy, please check my latest commit
<evilchelu> i propose that as the communication for the attendance things
<technomancy> ok, taking a look
<evilchelu> that's a list i would expect to be able to get for a meeting
<evilchelu> the first things are the userids
<evilchelu> then the month-day
<technomancy> which page should i be looking at?
<evilchelu> then hour ranges
<evilchelu> the .js
<evilchelu> attendance_communication_sample.js
<evilchelu> :)
<technomancy> oh, so no html yet
<technomancy> right
<technomancy> thought you forgot to add the view files or something. =)
<evilchelu> na
<evilchelu> they're not done
<evilchelu> it seems i'm not up to full speed :)
<technomancy> ok, what is 2: and 4:?
<evilchelu> userids
<technomancy> oh, right
<technomancy> this is to list other peoples' times
<technomancy> i was thinking you were going to do specifying your own times
	      first
<evilchelu> ya, and when i post, i'll just send the part with the dates
<technomancy> it looks good; the only thing i'd change is to add in a year
	      value to the date
<evilchelu> ya, i was typing that :)
<technomancy> this is in JSON, right?
<evilchelu> ya, that's json
<technomancy> rawk on
<technomancy> looks good
<evilchelu> but i dunno how you'll turn ranges in those arrays
<technomancy> it won't be difficult
<technomancy> in terms of data a range is a two-item array; it's only in terms
	      of behaviour that they differ
<evilchelu> ok
<evilchelu> don't try to reason with me now :D
<technomancy> heh
<technomancy> in retrospect we probably should have started with this part
<evilchelu> ya
<technomancy> oh well, we'll work with what we've got
<evilchelu> anyway, too late for that now :)
<evilchelu> ok, so, i need the following: 
<evilchelu> - an action that spits that out so i can use it to render the page
<technomancy> i'll get right on it cap'n!
<evilchelu> - an action that accepts the range part so i can send the user
	    selection
<evilchelu> just the part for one user
<technomancy> for now use that data as a mock; i'll make it dynamic
<evilchelu> btw, indentation and anything doesn't matter
<technomancy> sure
<evilchelu> but, punctuation does
<evilchelu> no , after the last element
<technomancy> right
<evilchelu> so, do i need anything else?
<technomancy> good question. =)
<evilchelu> get all data, send my data
<evilchelu> oh, get my data?
<evilchelu> ya, i think i need get my data too, if we want to edit
<evilchelu> and we want to edit
<evilchelu> since that's what we basically do every time, edit
<evilchelu> and the first time we just don't have any "my data"
<technomancy> "my data" = the user's current attendance?
<evilchelu> da
<evilchelu> err
<evilchelu> ya
<technomancy> ok, can you create dummy actions for these that have static data
	      like this JS sample?
<technomancy> then i'll make them dynamic as i code more of the attendance
	      class
<evilchelu> so i can play?
<technomancy> exactly
<evilchelu> i can work around not having actions to be able to do the js
<technomancy> so we can both start where we are and work towards each other
<evilchelu> no problem
<evilchelu> damn, da = yes in romanian :) ... i'm slipping :)
<technomancy> heh
<evilchelu> ok, i'm more confident now :)
<evilchelu> i can smell the progress
<evilchelu> :D
<technomancy> oh, there's that one song, "Dragostea Din Tei" -- is that
	      Romanian?
<evilchelu> ya dude, fuckin lame song :)
<technomancy> heh; yeah. but then i know a few words of romanian.
<technomancy> "Alo. Salut."
<technomancy> =D
<evilchelu> the dudes are actually moldavian. that's a part of romania that
	    was lost to the russians a while ago and is now a separate country
<technomancy> huh; but same language
<evilchelu> ya, they still speak romanian but also russian
<evilchelu> they got funky accents tho :)
<evilchelu> ok, i'll start on this
<technomancy> i think i've got a decent to_json method for attendances; just
	      need to write a test
<technomancy> Fullmoon: hey, i've got an error with the
	      test_delivery_for_existing_user test
<technomancy> just a heads up
<Fullmoon> Will look into it
<technomancy> thanks
<evilchelu> technomancy, stop!
<evilchelu> i had an idea
<evilchelu> one sec
<Fullmoon> technomancy: Is that OK style?
<Fullmoon> return flash[:error] = "No new password set." if
	   params[:user][:password].blank?
<technomancy> that's fine; yeah
<evilchelu> wouldn't validate_length_of or something?
<Fullmoon> Also the return before? I hate nested divs
<evilchelu> already do that?
<technomancy> i think this is a special case
<evilchelu> oh, k
<technomancy> the user model can't always require the password to be reset
<evilchelu> i see
<evilchelu> doh
<Fullmoon> evilchelu: Does not works if there is already a password present,
	   or a hashed value is present, but I will look more into it
<evilchelu> :)
<technomancy> just on this action
<evilchelu> just ignore me
<evilchelu> :)
<Fullmoon> But I am afraid  I need to leave soon, so I will make it work, pass
	   tests, and write a Todo
<technomancy> awesome
<technomancy> i don't think i could have gotten to those mailer tasks
	      especially if you hadn't been around
<Fullmoon> Oh, they are easy and I am terrible slow tonight, having problems
	   to concentrate 100%
<technomancy> hey, less things for me to worry about makes a huge difference
<Fullmoon> Glad to hear :)
<technomancy> is the <noscript> warning in too?
<Fullmoon> technomancy: Not yet commited
<Fullmoon> Commited :)
<technomancy> kewl
<technomancy> have you tested the emailer stuff manually as well?
<technomancy> eg tried to follow the login links and such?
<Fullmoon> Yes
<technomancy> great
<technomancy> Fullmoon: did you see eriberri's screenshots in #caboose?
<technomancy> it's a wedding planning app
<technomancy> it looks like ours, but rather different
<Fullmoon> Not yet...
<technomancy> kickass design, though
<evilchelu> ya, nice looking :)
<technomancy> ummm... wondering if i should leak an url in #caboose
<technomancy> figure there's no harm; it's too late for anyone to be stealing
	      ideas
<Fullmoon> Ah, wedding planning
<technomancy> what do you think?
<evilchelu> they'll find bugs we'll have to fix!!!
<evilchelu> :))
<technomancy> heh
<technomancy> ok, i'll post the url
<Fullmoon> Sure :)
<technomancy> Fullmoon: going quite soon?
<Fullmoon> I am afraid so, though I want to finish this before
<technomancy> ok, right
<technomancy> evilchelu: three actions you need coded, right: my_attendance,
	      others_attendance, set_my_attendance
<technomancy> is that right?
<evilchelu> hm
<evilchelu> i think you might merge my and others
<technomancy> also, have you put up dummy data in those actions, or should i
	      go ahead and do that
<technomancy> oh yeah?
<evilchelu> ok, i need my and others to be able to display the show page
<technomancy> so just get all the attendances for a meeting, and split out
	      "my" vs "theirs" in JS?
<evilchelu> so, if you put all users in the same place and give me my user id
	    i'm set
<technomancy> ok
<evilchelu> also, some stuff like, number of days and hour limits will be
	    needed
<evilchelu> but we can add that easily
<technomancy> Fullmoon: i'm going to move the noscript warning into the
	      application layout so people will still see it after they log in
	      just in case they are in a hurry and don't read the whole page
<technomancy> ok
<Fullmoon> technomancy: Gread idea!
<evilchelu> technomancy, updated the sample data
<evilchelu> damn, i'm slow
<technomancy> ok
<technomancy> so i'll be adding two actions to the meeting controller
<evilchelu> well, only one
<evilchelu> the set one is actually the save for edit
<evilchelu> or something
<evilchelu> ya, 2 actions
<evilchelu> whatever. i'm not making sense :)
<technomancy> i renamed record_times to set_times
<technomancy> that will save the json
<technomancy> the other is attendances
<evilchelu> have you seen the latest sample?
<technomancy> to get attendances, pass in the id of the meeting
<technomancy> no, i'll take a look
<technomancy> ok, so that whole bit of JSON needs to be returned by the
	      meeting controller
<technomancy> the action named...
<Fullmoon> Finished, writing tests
<technomancy> meeting_json?
<technomancy> Fullmoon: cool!
<evilchelu> technomancy, i will put a <script src=""> in the show page to get
	    that, or we could inline it in the html
<technomancy> ah; right
<technomancy> i was thinking it needs to be ajax, but it doesn't
<evilchelu> no ajax, too sleepy for that :D
<technomancy> also, the set_times will be a non-ajax save-type action?
<evilchelu> ya
<technomancy> got it
<technomancy> Fullmoon: check in?
<Fullmoon> technomancy: let me finish the test first, just discovered an error
<technomancy> ah, i misread it as "finished writing tests", not "finished,
	      writing tests"... =)
<technomancy> big difference
<technomancy> man, i'm tired, and it's only 3:35pm here
<Fullmoon> Damn, Sqlite realls is nice for tests and dev
<Fullmoon> Especially when you need to move dev data between machines
<technomancy> yeah, i dig it
<technomancy> especially the memory testing; it's super-fast
<technomancy> kickass! i just wrote the Meeting#good_for_everyone(time)
	      method, and it was a lot simpler than I anticipated
<technomancy> not fast or elegant, but I think it works
<technomancy> course, now my brain is too fried to write a test for it
<technomancy> evilchelu: about to checkin for you, man
<evilchelu> damn
<evilchelu> i'm lagging behind
<evilchelu> :/
<evilchelu> but this second redbull is kicking in
<technomancy> i like the sound of that
<technomancy> ok, grab it
* technomancy is really bummed you can't use "!" in your commit messages...
<evilchelu> you can't?
<technomancy> commit messages without exclamation points just don't express
	      the same sentiments as well
<technomancy> well, not in bash
<technomancy> oh, you probably could if you write the commit message in your
	      editor
<evilchelu> well, set SVN_EDITOR
<evilchelu> ya
<evilchelu> but, -m "!" doesn't work?
<technomancy> nope, it's some kind of bash control char
<evilchelu> creepy
<technomancy> oh, could prolly escape it
<technomancy> if you're hella tired, i usually find taking a shower helps a
	      lot
<technomancy> just a suggestion
> 


<Fullmoon_mobile> Or a cold footbath
<technomancy> oooh... that sounds like a good idea
* technomancy runs off to find a tub of water
<technomancy> no tub.... will have to sit on the toilet with my laptop and
	      stick my feet in the bathtub
<technomancy> (kidding!)
<evilchelu> technomancy, hmm, i'm around for now
<evilchelu> the redbull worked :)
<technomancy> awesome
<technomancy> i'll get working on testing the meeting_data method
<technomancy> did you take a look at its code? about what you needed?
<evilchelu> didn't look yet
<technomancy> ok
<technomancy> no rush
<evilchelu> i'll look now
<evilchelu> well, push me, since i tend to forget :D
<technomancy> k
<technomancy> do you care about the "final" boolean?
<technomancy> or we can handle that in the view rather than in the JS
<evilchelu> uh?
<technomancy> oh... i never explained that, did i. =)
<evilchelu> btw, the meeting_data action breaks when there is no attendance
	    data
<technomancy> heh; silly me
<technomancy> will fix
<technomancy> the final boolean is there so you can specify some attendance
	      times but not say you're 100% sure yet
<evilchelu> uhhhh
<technomancy> basically, you can log on and set your time, but until everyone
	      sets the final bool, the organizer won't get the email telling
	      him to choose the time
<evilchelu> well, i think the organizer should be able to set the final stuff
	    even if not all people have decided
<technomancy> maybe that's more complicated than we need
<technomancy> yeah
<evilchelu> since you could wait forever
<technomancy> ok, i'll get rid of final
<technomancy> if there are *any* times listed in attendance, it's considered
	      that the user has specified his time
<evilchelu> okay
<Fullmoon> Committed
<technomancy> heh; i can just redefine the final method rather than rewriting
	      all the stuff that it relies on
<technomancy> i love ruby!
<Fullmoon> technomancy: What now to do? :)
<technomancy> good question
<technomancy> look at the notimplementederrors and see which one appeals to
	      you? =D
<technomancy> the big things still missing are the set_times action and the
	      decide_time action
<technomancy> if you want to take a break from coding, you could write the FAQ
<Fullmoon> I will have a look at the errors :)
<technomancy> ok. the one i'm handling right now is the test_possible_times
	      one
<technomancy> ok, the "final" attribute (for attendances) is being dropped in
	      favor of "entered?" which simply returns whether any times have
	      been specified
<Fullmoon> huh? I dont get that
<technomancy> oh, originally i had it so each attendee would have to specify
	      "these times are final" before the organizer would be able to
	      decide on a final time
<technomancy> that was a bad idea
<technomancy> but the app still needs to know which users have entered times
	      for a meeting
<technomancy> so the entered? method tells them
<Fullmoon> aah
<technomancy> evilchelu: how's the show page coming?
<evilchelu> slowly
<evilchelu> it's like i'm retarded or something
<evilchelu> :/
<technomancy> i'm about to call my wife, want to know if she can help beta
	      test. =D
<evilchelu> :))
<evilchelu> don't call yet
<technomancy> evilchelu: it doesn't help that JS is really hard to write tests
	      for
<technomancy> coding when you're tired (or drunk) is way easier with tests. =D
<evilchelu> well, there will be no tests, and the js will suck, but it'll work
<evilchelu> hooepfully
<evilchelu> erm, hopefully
<evilchelu> but i think it'll be about an hour till that happens
<evilchelu> :/
<technomancy> i think you can do it. =D
<technomancy> ok
<evilchelu> i think too, but it's pissing me off that i write it this crappy
	    :/
<evilchelu> :)
<technomancy> 2:30 there?
<evilchelu> ya
<technomancy> well take consolation in the fact that the judges are experts in
	      ruby but not JS
<technomancy> just hope madrobby isn't judge on ours. =D
<evilchelu> there's madrobby in there
<evilchelu> :D
<evilchelu> and i'm using yui stuff, not prototype!
<technomancy> he's all, "what, you didn't use scriptaculous? points off!"
<evilchelu> and i'm writing procedural js
<evilchelu> !
<technomancy> hah
<evilchelu> bleh
<evilchelu> oh well, must get it done
<evilchelu> even if we don't get style points for the js
<technomancy> any JS at all is better than i would have come up with
	      myself. =D
<evilchelu> should plan a better sleep schedule next year :)
<Fullmoon> Is there something else to do except for the tests?
<Fullmoon> I am staring blank at that screen, and dont get anything... too
	   late
<technomancy> write the faq? =D
<technomancy> doesn't take as much thought... can do it when you're tired
<technomancy> Fullmoon: err-it's not that tests need to be written. it's that
	      the NotImplementedErrors indicate actions which haven't been
	      written at all
<technomancy> mmm... stretch break time
* technomancy does jumping jacks
* technomancy jogs in place
<technomancy> evilchelu: i'm working on improving the meeting_data action
	      right now
<evilchelu> ?
<evilchelu> oh, with checks
<evilchelu> okay
<Fullmoon_mobile> How is the status on MeetingController # edit and show?
<evilchelu> i'm working on show
<technomancy> Fullmoon: you could write edit
<technomancy> it is just like new, but it needs to display the already invited
	      people
<Fullmoon_mobile> I see
<technomancy> fixed Attendance#to_json
<Fullmoon_mobile> DHH will not like the create form, he uses safari afaik ;)
<technomancy> uh oh... i can't test on safari
<technomancy> what's wrong with it?
<evilchelu> :o
<evilchelu> what did i dooooo?
<evilchelu> what doesn't work in safari?
<evilchelu> :(
<Fullmoon_mobile> The fieldset does not wrap the complete contents of it
<technomancy> warning: please use a Gecko browser. =D
<technomancy> criminy
<Fullmoon_mobile> Wait a sec, I'll make a screenshot
<evilchelu> Fullmoon_mobile, ok, try adding width: 100% in the css to fieldset
<evilchelu> or don't
<evilchelu> it'll fuckup
<evilchelu> grr
<technomancy> evilchelu: don't let this distract you; keep working on the show
	      page
<Fullmoon_mobile> http://www.lorem-ipsum.at/safariproblem.png
<Fullmoon_mobile> I can try to fix it?
<evilchelu> oooh, it's the floats, just a sec
<evilchelu> try adding class="clearfix" to all fieldsets please
<technomancy> <br style='clear: both;' /> after the calendars might make it
	      work?
<technomancy> or that
<evilchelu> technomancy, i hate those kind of brs :p
<Fullmoon_mobile> Floating the fieldset  left would work
<Fullmoon_mobile> mom, will try
<evilchelu> try the clearfix please
<technomancy> yeah, they are evil... i am not thinking
<technomancy> mom => moment, please?
<evilchelu> floating will make them as wide as the contents
<evilchelu> oh, k :)
<technomancy> what was the error you were getting on meeting_data?
<evilchelu> you were doing join on @attendances
<evilchelu> which was empty
<evilchelu> erm, nil
<evilchelu> or something
<technomancy> oh, ok
<technomancy> hmmm.... i don't remember making a change, but now attendances
	      is an empty array if there are none, so join works
<technomancy> did you make that fix?
<technomancy> because i can successfully render meeting_data for a meeting
	      that has no attendances
* technomancy smells funny
<evilchelu> no, i didn't
<technomancy> umm... ok. well if it happens again let me know the details
<evilchelu> ok
<technomancy> safari problem sorted out?
<technomancy> (man... i feel like a software manager... this is weird)
<technomancy> i love how the entire test suite takes 0.56 seconds on my
	      machine
<Fullmoon_mobile> I can make the fieldset embrace the ccontenst without using
		 a float: left; on fieldset, as well as width: 90%; to make it
		 not leave the bounds, a little bit ugly, but works in safari,
		 firefox, IE
<Fullmoon_mobile> I can not...
<technomancy> sounds good to me
<Fullmoon_mobile> I will commit it, maybe we find a nicer solution later
<technomancy> right
<technomancy> did you also start on the edit meeting action?
<Fullmoon_mobile> not yet, I could barely fix that, sorry... soo tired
<Fullmoon_mobile> at least we dont go out today 
<evilchelu> Fullmoon_mobile, didn't clearfix work?
<Fullmoon_mobile> evilchelu: No
<technomancy> Fullmoon: just checking
<evilchelu> that bastard!
<technomancy> i can handle edit after you both collapse from exhaustion
<evilchelu> so, the br didn't work eigher?
<technomancy> tbh i am amazed you can still type
<evilchelu> :)
<evilchelu> dude, i'm writing so ugly shit
<evilchelu> !!!!
* evilchelu smacks himself
<evilchelu> and i'm writing it so slooowly
<evilchelu> geez
<technomancy> take a shower; it will refresh you and you will come back with
	      renewed vigor
<evilchelu> hm
<evilchelu> in 10 mins
<Fullmoon_mobile> evilchelu: No :( The problem seems to be that the stupid
		 fieldset does not get as big as its contents, unless it is
		 floated
<evilchelu> hm, i see
<evilchelu> ok, float it, set it to 100% width, then remove the side paddings
	    and add margin-left to labels textareas and all that shit
<evilchelu> it's because those paddings that it extends the container when you
	    set width 100%
<Fullmoon_mobile> evilchelu: I figured so, but was too tired to check
<evilchelu> maybe
<evilchelu> it's better you did it
<evilchelu> safer for this hour at least
<evilchelu> just make it with % to look good at the default size
<evilchelu> :)
<evilchelu> OH!!!
<Fullmoon_mobile> Sure
<evilchelu> set the width in em
<evilchelu> calculate how many ems
<evilchelu> the big one is 60em, so just try width: 56em
<Fullmoon_mobile> Nice idea
<Fullmoon_mobile> comitted
<evilchelu> worked?
<evilchelu> sweet
<Fullmoon_mobile> i hit a wall
<evilchelu> oh
<evilchelu> i'm like... so revived
<evilchelu> some shit actually just worked!
<evilchelu> amazing, really
<Fullmoon_mobile> cani see?
<evilchelu> no :D
<evilchelu> it's just some alerts
<evilchelu> but, still
<evilchelu> i'm amazed
<evilchelu> but it's so ugly :(
<evilchelu> oh well, back to it
<technomancy> revived from the joy of getting it to work?
<evilchelu> ya
<evilchelu> :D
<Fullmoon_mobile> technomancy: I do not think i can contrubite anything more
		 :(
<technomancy> Fullmoon: no shame in sleeping now
<technomancy> you've helped a lot
<technomancy> just check in what you've got and i'll take over
<Fullmoon_mobile> technomancy: not really, I am happy to helped out a little
		 bit
<technomancy> team Concourse rules!
* technomancy high fives everyone
<Fullmoon_mobile> my last checkin was the safari fix, nothing more after that,
		 looked at code, did not understand... problem is, I barely
		 slept the day *before* railsday where i should have
<Fullmoon_mobile> :)
<evilchelu> Fullmoon_mobile, thanks for the help dude, be sure to svn up
	    tomorrow to see it in all it's glory :)
<technomancy> hah; right
<technomancy> no worries
<technomancy> i think i can handle the meeting edit
<Fullmoon_mobile> maybe next year :)
<Fullmoon_mobile> have luck / caffeine / spirit
<technomancy> thanks
<evilchelu> thanks :)
<technomancy> you guys both in the same timezone, right?
<evilchelu> no, he's one hour before me
<evilchelu> 4am here, 3am there
<technomancy> right
<technomancy> my euro geographical knowledge is weak
<evilchelu> :)
<technomancy> last minute simple feature idea:
<technomancy> at the bottom of the show page, have a mailto: link so you can
	      easily send messages to everyone invited to the meeting
<technomancy> whaddaya think?
<evilchelu> i don't even understand the words :)
<evilchelu> lemme just finish this and we'll talk later
<technomancy> ok, i'll do it after the core features are ready
<technomancy> yay!
<technomancy> problem solved
* technomancy puts Array#all? on his list of methods to remember
<technomancy> you still there man?
<technomancy> evilchelu: wake up!
<evilchelu> ya
<evilchelu> still around :)
<technomancy> good. =D
<evilchelu> :)
<evilchelu> i feel pretty sharp too
<technomancy> oh yeah?
<technomancy> cool
<evilchelu> still, i'm sure i'm not :)
<technomancy> i'm going to write MeetingController#edit now...
<technomancy> heh; right
<technomancy> well, i'm sure it's a pleasant illusion
<technomancy> after edit, all that's left is set_times and decide_time
<technomancy> the end is in sight!
<technomancy> is the sun back up yet?
<evilchelu> nop
<evilchelu> so, i'm showing shades :)
<evilchelu> ok, status update
<evilchelu> i did the rendering from the js stuffs
<technomancy> cool
<evilchelu> i show whether a user has an hour selected and a shaded based on
	    number of users
<evilchelu> i can click on cells, can easily add toggling
<evilchelu> then i can create a json to send back
<evilchelu> so, in a normal situation... 10 minutes
<technomancy> that's great!
<evilchelu> at this hour, i'd say 30 :)
<technomancy> =D
<evilchelu> but the hard part is over
<evilchelu> :)
<evilchelu> you know you're fucked up when you write the ternary operator
	    backwards 3 times and can't figure out what's wrong
<evilchelu> :D
<technomancy> ouch!
<technomancy> dang, the faq never got written
<evilchelu> you do that :D
<evilchelu> or, maybe i should after i finish, that would be one awesome faq
	    :)
<technomancy> yeeeeeah!
<technomancy> ok svn up and look in the browser
<evilchelu> oh crap
<evilchelu> zillions of changesets
<technomancy> hah; haven't upped in a while?
* technomancy moves the faq out of its own controller into accounts
<evilchelu> nop
<evilchelu> dude, we got a gradiend
<evilchelu> hm
<technomancy> we are T3H SHINY!
<evilchelu> a bit ugly imo :D
<technomancy> well, that's all the design i can do... =D
<evilchelu> maybe start form the other blue and make it longer?
<technomancy> ok, np
<technomancy> the lighter blue?
<evilchelu> i mean, don't start from white, start from the light blue
<technomancy> 10px?
<technomancy> err--20
<evilchelu> dunno :)
<evilchelu> try 30
<evilchelu> or smth
<evilchelu> dude
<evilchelu> go away
<technomancy> =D
<evilchelu> i forgot i was doing something :p
<evilchelu> geez
<technomancy> heh
<technomancy> ok, good idea. it looks way better with 30px and that other blue
* technomancy just needed to do something other than code for a minute
<technomancy> back to the editor for me!
<evilchelu> :)
<evilchelu> commited?
<technomancy> better shiny now!
<evilchelu> :)
<evilchelu> you know, you could try setting some decent page titles
<evilchelu> like, concourse - adding meeting, etc
<evilchelu> or something
<technomancy> yeah
<technomancy> first i'll write set_times though; that's more important
<technomancy> you're using the same json format in set_times?
<evilchelu> ya, just the part for one user
<technomancy> so you post that data?
<evilchelu> you'll get that hash
<evilchelu> or whatever
<evilchelu> ya, i'll stick it in a hidden and submit the form
<technomancy> so is it a string of json rather than a ruby hash?
<evilchelu> ya
<technomancy> ok, should be interesting.
<technomancy> think i can grok it though
<evilchelu> eh?
<evilchelu> i think there are helpers for it
* technomancy researches
<evilchelu> like, i think YAML::load will work
<evilchelu> or something
<technomancy> oh right! it's yaml-compatible
<technomancy> excellent
<technomancy> we are going to cut it pretty close, huh?
<technomancy> hey, i'd feel better if you just checked in now
<technomancy> just in case, you like fall asleep or something
<evilchelu> dude, don't worry, you'd never understand the code anyway :)
<evilchelu> but ok :)
<technomancy> also in case anything happens like you delete a file
	      accidentally or something
<technomancy> safer to check in often
<evilchelu> indeed
<technomancy> this is amazing--we have stuck with the initial schema execpt
	      for one single change
<evilchelu> heh :)
<evilchelu> commited
<technomancy> w00t
<technomancy> so what's the json string param named?
<evilchelu> whatever you want
<technomancy> times?
<evilchelu> dude
<evilchelu> take a look at that page
<evilchelu> :p
<evilchelu> you can use it
<evilchelu> a bit
<evilchelu> :)
<technomancy> good point
<evilchelu> eh?
<evilchelu> so?
<technomancy> pretty kickass
<evilchelu> :)
<technomancy> we can adjust the colors and such; the functionality looks good
<evilchelu> the colors are in css
<evilchelu> ;)
<technomancy> ja
<technomancy> it looks like it's grabbing the same meeting no matter which you
	      click on tho
<evilchelu> doh
<evilchelu> it's using the sample data :p
<evilchelu> i can't be arsed to make it work with real date before i finish
	    the save too
<technomancy> ok, just checking
<evilchelu> :)
<technomancy> it actually looked believeable for one of the meetings
<evilchelu> hah :)
<evilchelu> so
<evilchelu> quick oen
<technomancy> =) => // omg, don't tell anyone i wrote this!
<evilchelu> :D
<technomancy> what's up?
<evilchelu> i'm a bit retarded, i can't figure out a simple way to make the
	    ranges from js
<evilchelu> so i want to just send you a day with an array of hours
<evilchelu> is that ok?
<evilchelu> like '2006-06-27': [7, 9, 10, 11, 20, 21, 22]
<technomancy> array of hours so rather than [12, 15] it's [12, 13, 14, 15]?
<evilchelu> ya
<technomancy> yeah, that is fine
<evilchelu> sweeeeeeeeet
<technomancy> that sort of processing is probably a lot easier in ruby anyway
<technomancy> ok... this is the part where i go take a shower and come back
	      with renewed vigor
<evilchelu> k
<technomancy> bbiab
* technomancy is back and squeaky clean
<evilchelu> shiny!
<technomancy> drop-shadow!
<technomancy> big-font!
<technomancy> YELLOW FADE EFFECT!
<evilchelu> we got both
<evilchelu> no yellow fade tho :/
<technomancy> it's ok, we don't NEED to stinkin yellow fade effect
<evilchelu> ok, update
<evilchelu> btw, if you want a ruby hash, i can give you a ruby hash instead
	    of that
<technomancy> yaml is fine; it's practically a ruby hash
<evilchelu> k
<technomancy> so the contents of the alert is what gets posted
<technomancy> and also the id of the meeting, right?
<evilchelu> they're only alerted now
<evilchelu> :)
<evilchelu> i'd be greatful if you did the form
<evilchelu> and let me only to put the stuff in the right hidden
<technomancy> the form to send the data to set_times?
<evilchelu> ya
<technomancy> can do
<evilchelu> thanks
<evilchelu> i'll go strech a bit
<technomancy> as long as it's properly hidden
<evilchelu> :D
<technomancy> good deal
<technomancy> when you come back maybe you'll be delirious enough to write the
	      faq. =D
<evilchelu> :D
<technomancy> i actually had an idea for that in the shower...
<technomancy> Q: so, what's this concourse thing all about? A: chunky bacon!
<technomancy> Q: you mean it's a site where you can create meetings and invite
	      your friends? A: chunky bacon!
<technomancy> Q: so all i need to do is sign up and try it out? A: chunky
	      bacon!
<technomancy> and so on
<technomancy> i think it's a great idea, and i haven't had nearly as much
	      sleep loss as you
<technomancy> =D
<evilchelu> :))
<evilchelu> ok, we should finish integrating till T-1h
<technomancy> right
<evilchelu> damn, i'm so awake :)
<technomancy> also, if we have any spare time we should find a swedish guy
<evilchelu> cool :)
<evilchelu> a what?
<evilchelu> wtf for? :)
<technomancy> a swedish guy!
<evilchelu> uh
<technomancy> to register con.cour.se for us!
<evilchelu> =))
<technomancy> =D
<evilchelu> ahahahaha
<evilchelu> it's taken
<technomancy> crap
<technomancy> co.ncour.se?
<evilchelu> oncour.se is free
<technomancy> that too
<evilchelu> that's free too
<technomancy> you have to be swedish though, right?
<evilchelu> dunno
<evilchelu> dc has one
<technomancy> that's what i heard
<evilchelu> court too
<evilchelu> anyway
<evilchelu> get back to workin
<evilchelu> :D
<evilchelu> and commit that thingy
<evilchelu> :p
<technomancy> yes sir!
* evilchelu pokes technomancy
* evilchelu blinks sheepishly
<technomancy> i'm here
<technomancy> poke-pong
<evilchelu> please commit that form :)
<technomancy> oh... hold on.
<technomancy> i'm almost done writing the set_times action
<technomancy> i was going to do the form next...
<technomancy> sorry
<evilchelu> i just want to the form :/
<evilchelu> i don't want it to work
<technomancy> ok, i'll get it up
<technomancy> did you just rip a lot of stuff out of show.rhtml?
<evilchelu> ya, moved it to a js file
<technomancy> ok, just making sure i didn't accidentally delete a bunch of
	      stuff
<evilchelu> ;)
<technomancy> all the magic goes in table_container, correct?
<evilchelu> ya
<evilchelu> i have it there so we can put stuff before and after it
<technomancy> ok, and your JS sets a hidden field to the proper json string?
<evilchelu> not yet
<evilchelu> i'm waiting for the form
<evilchelu> :D
<evilchelu> and the field name
<technomancy> ok, the field is named "times", and I set the dom id to "times"
	      as well
<technomancy> sorry i took so long; it's committed
<evilchelu> wee
<evilchelu> :)
<technomancy> i'm going to see if i can change the whole attendance times
	      storage to just an array of integers rather than an array of
	      ranges
<technomancy> it's so much simpler; i wish i had done it from the start
<evilchelu> oh well :)
<evilchelu> how do add an id to the form?
<technomancy> form_tag takes two hash arguments
<evilchelu> nevermind
<evilchelu> got it
<technomancy> so form_tag {:action => 'blah'}, {:id => 'blah2'}
<technomancy> yeah
<evilchelu> you also need ()
<technomancy> right
<technomancy> so you working on getting that field filled out right?
<evilchelu> ya, i did that
<evilchelu> now trying to hook stuff up to the real data
<evilchelu> but i get an error on meeting_data
<evilchelu> i think my db is not ok
<evilchelu> how do i fix it?
<evilchelu> load_fixtures?
<technomancy> delete your sqlite, migrate and load fixtures
<technomancy> just to be safe
<evilchelu> k
<evilchelu> i'm actually on mysql :)
<technomancy> same difference
<technomancy> ok, i'm going to get working on decide_time
<evilchelu> oh crap
<evilchelu> we still got stuff to do
<technomancy> i don't think i'm going to get around to emailing the organizer
	      when all the times are in
<technomancy> yes, just *one* action
<technomancy> i think i can handle it
<evilchelu> http://nutty:3000/meeting/meeting_data/3
<evilchelu> don't you get an error?
<technomancy> yeah, a dns error. =D
<technomancy> hold on
<evilchelu> whatever
<evilchelu> :p
<evilchelu> <%= @meeting.attendances.map(&:to_json).join(",\n") %>
<evilchelu> that's the problem line
<evilchelu> The error occured while evaluating nil.map
<technomancy> i see it now
<technomancy> yeah, i'll try to get that fixed
<evilchelu> ok, i'll commit the hooking up, it should be ok
<technomancy> AWESOME
<evilchelu> just a sec, i broke it :D
<technomancy> updated the test to catch the error; haven't fixed it yet
<evilchelu> oh
<technomancy> wtf! that's not nil!
<technomancy> oh... it's when TIMES are nil; not attendances
<technomancy> the crappy error message strikes again
<technomancy> committed!
<evilchelu> me too!
<evilchelu> http://nutty:3000/meeting/meeting_data/3
<evilchelu> broken!
<evilchelu> no closing curly
<technomancy> what you say!
<evilchelu> we get signal!
<technomancy> oh, got it
<evilchelu> make your time!
<technomancy> main screen turn on
<evilchelu> :))
<evilchelu> dude
<evilchelu> 45minutes to go!
<evilchelu> auch
<evilchelu> and, there shouldn't be a closing curly there
<evilchelu> there should be an empty array
<technomancy> somebody set up us the closing curly brace
<technomancy> oh
<evilchelu> oh
<evilchelu> you're right
<evilchelu> nevermind
<technomancy> whew
<evilchelu> it's ok with curly
<evilchelu> :p
<evilchelu> didn't see there aren't any dates
<evilchelu> dude
<evilchelu> but the dates are wrong
<evilchelu> i need all the dates
<evilchelu> not the range
<evilchelu> so datestart.upto(dateend)
<evilchelu> or something
<evilchelu> ya dig?
<technomancy> yeah
<evilchelu> does that even work?
<technomancy> decide_time is not going to get written. =(
<evilchelu> the .upto ?
<evilchelu> :((
<technomancy> upto takes a block
<technomancy> right right so i'll change all the time lists away from ranges
	      to arrays of integers
<technomancy> i was going to do that a before, and i got sidetracked
<technomancy> hopefully my coupling is low enough that this doesn't horribly
	      explode
<evilchelu> uhhh
<technomancy> man! this is so much simpler to skip ranges altogether
<evilchelu> okaaay
<evilchelu> set times breaks
<evilchelu> beacuse of me
<evilchelu> i fixed my breakage and it still fails
<technomancy> how does it break?
<evilchelu> commited
<evilchelu> You have a nil object when you didn't expect it!
<evilchelu> You might have expected an instance of Array.
<evilchelu> The error occured while evaluating nil.[]=
<evilchelu> #{RAILS_ROOT}/app/controllers/meeting_controller.rb:53:in
	    `set_times'
<evilchelu> eh, you figuring it out?
<technomancy> how can i see that error
<technomancy> i think i fixed it
<evilchelu> i http://nutty:3000/meeting/show/3
<evilchelu> logged in as myself
<technomancy> it works logged in as me
<evilchelu> i set all but the topright box and press set times
<technomancy> will try logged in as you
<technomancy> no error! fixed
<evilchelu> !
<evilchelu> yay
<evilchelu> :>
<technomancy> hah; i just made the biggest change to the data model i've made
	      all day
<technomancy> and it's 30 mins away from finish
<evilchelu> so, i say that decide time should be shown to the admin when on
	    show with a big textarea saying...
<technomancy> so does set_times work properly?
<technomancy> yeah! textarea++
<evilchelu> bitch, you see the things above, make up your mind and send the
	    people an email, we didn't have time to make something fancy here
<evilchelu> :)
<technomancy> i like it
<evilchelu> :D
<technomancy> we'll even provide a mailto link
<evilchelu> "You specified a date/time outside of the meeting's allowed
	    range."
<evilchelu> wtf?
<technomancy> hmmm...
<technomancy> oh, maybe that still uses the range checking
<evilchelu> so, two bugs
<evilchelu> 1. i selected a thing on the first column, it said saved but when
	    showing it again i don't see my times
<evilchelu> 2. when selecting from the second column i get not valid date
<evilchelu> also, the thing still sends me just begin and end, not the whole
	    range
<evilchelu> so, 3 bugs :)
<technomancy> still? svn up?
<evilchelu> do i need to nuke the db again?
<technomancy> no
<evilchelu> nuked the db, restarted mongrel
<evilchelu> let's try again
<evilchelu> 1 still reproducing
<technomancy> at this point i would say let's focus on documentation so the
	      judges can see what it's _supposed_ to do
<evilchelu> sigh
<evilchelu> :/
<technomancy> sad to admit defeat, but we must
<evilchelu> indeed
<evilchelu> :(
<evilchelu> {'2006-06-01': [12,13],
<evilchelu> '2006-06-16': [12,13]}
<evilchelu> hm
<evilchelu> ok, i'll let it go
<evilchelu> you mean set_times, right?
<technomancy> decide_time is totally unwritten
<evilchelu> ya, but that would be easy
<evilchelu> set_times doesn't work
<evilchelu> oh well :)
<evilchelu> nice working with you :D
<technomancy> no, i think decide_time would be tough..
* evilchelu hugs technomancy
<technomancy> yeah, great job
<technomancy> =D
<technomancy> oh, one more thing
<technomancy> wanted to show the meeting name, description, and participants
	      on the show page; i'll add that
<evilchelu> ya
<technomancy> you can add to the faq if you like
<evilchelu> i'll try :)
<technomancy> want to add the whole transcript of the #concourse channel to
	      the repo?
<technomancy> =D
<technomancy> we could make it an easter egg type thing
<evilchelu> :)
<evilchelu> go ahead, i'm writing a sad letter in the faq
<evilchelu> :)
<technomancy> mkay
>