Perl 6 - the future is here, just unevenly distributed

IRC log for #webwork, 2013-09-14

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:16 mgage joined #webwork
00:54 mgage joined #webwork
02:22 mgage joined #webwork
05:53 eee-blt joined #webwork
14:29 mgage joined #webwork
15:15 goehle joined #webwork
15:18 goehle hey mgage
15:18 mgage hi
15:19 goehle sent you an email
15:19 goehle It could be the max size of the answer field in the database
15:19 goehle which is 1024 char
15:20 mgage that's probably about right.  Do you know off hand if that could be made larger? what the cost of doing so would be?
15:20 mgage not sure we would want to do that, but I want to think about the alternatives.
15:21 mgage we could also just declare that essay answers need to be short --
15:21 goehle so there are two things
15:21 goehle first we should set the max characters on the input field
15:21 goehle so students know that thye have hit the
15:21 goehle max
15:21 mgage yes
15:22 goehle in modern versions of mysql the max varchar size is limited by only the max row size
15:22 goehle so 65,535
15:22 goehle (but shared among all columns)
15:22 goehle if we were to make the max bigger it wouldnt use more space (because its varchar)
15:22 goehle but searching on the field would be slower I think
15:23 mgage so perhaps I'll experiment -- set the max char at 4K about and set the input field at that max and see if I run into any obstacles.
15:23 goehle 5000 char
15:23 goehle would be *about* 1000 words
15:23 goehle which is as much as I can imagine wanting to type in
15:24 mgage I also have other alternatives for collecting really long essays (I'm using both moodle and webwork in this linear programming class).
15:24 mgage or grade :-)
15:24 goehle if you set it to be longer
15:24 goehle let me know how the problem grader holds up
15:24 mgage ok -- I'll try that experiment and see how it goes.
15:24 goehle it wasnt really designed for essay length stuff
15:25 goehle you should be abel to change the database stuff pretty easy
15:25 goehle it will require a course upgrade
15:25 mgage I realize that -- but one always ends up pushing the limits.
15:25 goehle but shouldn't break anything (at least I dont htink)
15:25 goehle right.  I just wanted to know if it needed tweaks
15:25 goehle like maybe bootstraps collapsable feature
15:25 mgage I can put you into to the linear programming class as a prof if you want to see what's happening.
15:27 goehle If it feels like the problem grader needs work then you can add me
15:28 mgage I'll experiment for a little bit and then let you know if I need help -- I think I'm ok for now.  Thanks for the information.
15:28 goehle np
15:28 goehle I had one quick quewtion
15:28 goehle question
15:28 mgage kk
15:28 goehle should I start seperating my bug fixes into seperate pull requests
15:29 goehle I dont want to overburden people with pull requests (150 still hasnt been merged for example) but if it makes things easier
15:30 mgage I think so.  I helps with documentation -- and it's not really an extra burden to pull two requests -- in fact sometimes its easier to inspect the file changes if you are only looking for one feature change.
15:30 mgage I saw the email exchange.
15:30 mgage I'll work on pull requests this afternoon -- I've gotten a bit behind during the first weeks of classes.  :-)
15:31 goehle yeah
15:31 goehle last week was problematic
15:31 goehle for me as well
15:31 mgage I'm also trying to nail down the first code camp -- hopefully I'll have a definite date on Sunday -- at the moment I'm pushing the Oct 4 -- 7 weekend -- I have fall break on Oct 7 and 8 also
15:32 goehle ok.  Well I have a handful of things to fix.  I'll submit them all seperately
15:33 mgage I think we should try that  -- as I said it helps with documentation when I put together the releases    I don't think I'm going to get too slavish about it
15:34 mgage I'm considering pulling the bite sized stuff in develop and then merging all of develop into release/2.8 -- that has been sitting there too long -- some of the stuff in develop is bug fixes to 2.8 -- a few are features but mostly manageable ones.
15:34 goehle ok.  Good to know.  I have house/baby duites this weekend so I wont be able to look into any of that until next week.
15:34 goehle Good to know
15:34 mgage then that clears develop to import some of the big stuff that has been hanging there for a while
15:34 goehle two tings
15:34 mgage np
15:35 goehle 1) I need add another default achievement file, one with items and one without items
15:35 goehle that should be done in 2.8
15:35 goehle (so that people have a choice if they want ot use them)
15:35 goehle 2) I haven't finished getting mathview integrated with pgEditor / the file manager
15:36 mgage kk -- you can submit a pull request directly to 2.8 -- that makes sure it will be in that.  it won't get lost if I merge the current develop into it
15:36 goehle but it shouldn't take too long if I can find some time to work in it
15:36 goehle ok
15:36 mgage that's fine -- I don't think that is the most urgent thing.
15:36 goehle most everything else is either bug fixes or stuff that can stay in develop
15:37 mgage we are getting interesting feedback on mathview -- after a few months we may want to take a joint look at it from several users points of view
15:38 mgage kk -- hopefully I'll be in touch tomorrow with news about the code camp and maybe I'll have the 2.8 and develop branches sorted out a bit so that we can clearly see where to direct pull requests.
16:15 mgage joined #webwork
20:00 mgage joined #webwork
23:54 mgage joined #webwork

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary