Plan

[wootnik]

We need a programming plan to standardize and focus our work and ideas before we all shoot into different directions and come up with a hodgepodge of code.

As guy-kun suggested, I made a SVN space on assembla for version control. In terms of the script files themselves, I think we should take a more organized approach, breaking the files down by route and day, like d1-jun, d1-sara, d1-common, etc.

Anything else?

[awayawyle]

Standardizing RenPy is fairly straightforward. The 'Scripting' required for RenPy is mostly formatting. Once we decide on the placement of the dialog boxes and transitions and so on, we'll be using those same scripts every time. Our jobs as coders (aside from establishing this formatting to begin with) will mostly just be to apply the right ones to the unformatted dialog that we get from the writers. The only things that would deviate from the model once it's established are CGs.

I'm fine with breaking things up by route and day if the routes are firmly separated. If they intertwine, it would make more sense to take the decision tree and divide the script into sections by branches and label them by location or whatever else they have in common. If it's been decided that the routes are separate, then I totally agree. Otherwise, I think it's practical to wait for the decision trees. In the meantime, we can work on establishing the format, since that'll be used in all the routes.

[hex]

It'll be the Drawfags who name the CG files.
All CG poses will be part of an open pool.
Each author writes the name of the respective file in brackets at the point they want it to appear.

Make sense?

[wootnik]

Sounds good.

[robbob]

can someone link to the standard code?

[wootnik]

We don't have anything yet, but I can give you svn access for when we start putting it together.

[robbob]

thanks.
I didn't know a bit of python when this started but I am picking it up