Google Apps notes (incidentally, I think I need a "programming" icon of some sort)

[bouteillebleu]

Right. Google Apps. The overview page for the Google Apps service implies that it's good for hosting web apps written in Python (and now also ones written in Java). I have two projects that I would like to have hosted somewhere - one is the refbot (extracting CUTT downtimes from emails and putting onto the refwiki), the other is the Spinebot (

Comments

[ahdok]

Is SpineBot something you're making *for* PD, or just for kicks?

[bouteillebleu]

Just for kicks.

I want to see how hard it is to code the various different ways that the downtime system could be implemented. Currently I'm assuming they use a list of "activity" + "number of days" in order; I'd like to see how much harder a list of "activity" + "start date" + "end date" is to do (there are a lot more things to go wrong with input, for a start, also with checking bounds).

The other thing I want to see if I can find a way of implementing is part-crafting something and coming back to it later on in the season; currently I'm assuming that when downtime is processed, each "craft blah" + "number of days" pair gets processed, and a lammy ID is generated for that with info about how many days left to craft it (or just "this is a normal item" if it's finished).

[theinquisitor]

They use a start date and an end date. See the way missing time in the middle of the season is left empty, and it doesn't all fall up a bit.

Only way to deal with shared actions, of course.

[bouteillebleu]

You could do that with adding in a dummy action of "do nothing for N days" when a shared action with a different start date is accepted, though, and still have a basic system that's just activity + number of days. It would explain why missing time is left empty.

ETA: by which I mean, it's a way to let people leave gaps in the middle of downtime (but only for shared actions; is there a "do nothing for N days" option that one can do on one's own?) without having it implemented as (activity,start,end), since if you have (activity,start,end) then (a) why would you only offer input in (activity,number of days) as the system currently does, and (b) why would you constrain it to act as such when testing for overlap on start and end dates would work fine?