Nice Ben.
I have no practical programming experience unfortunately but do have a lot of project management experience, and can see things going a bit pearshaped with people working on different things etc, (of course we cant say who does what as its all volunteered)..
Im in the process of making some vids to show where we are at on all the features etc and have been updating the wiki here and there, improving spelling, and a few other minor things getting to know how it works.
Perhaps we can have some structure in here?
Id suggest the following...
- Contact whoever has global editing writes on the wiki to see if we cant get a line added to the index page of the wiki updating the news section saying that 500D/T1i/Kiss X3 is underway. (I will do this)
- Update the repository to includes Ben`s code above
- See if we cant finalise Ben`s code to clear up the second point, I read somewhere one of the functions clears the screen, so perhaps this needs adding on crop mark change. PS I dont think your first point is a bug at all, its meant to be like that I believe.
- Define whose currently doing what so duplication doesnt occur.
- Test where we are at now, see whats working fully etc (This is what Im doing currently).
- Define what needs to be done and who can volunteer to do it etc.
If we can have Coutts, Ben, and RoaldFre with a few pointers from Alex and Arm.Indy etc then it would be awesome.
Its important to realise to start small, rather than trying to jump in the deep end and try to adjust the frame rate etc, even if this is what we all really want.
