Hello, I'm a student now, and I want to look inside your project for studying and re-developping, Can You Send Me the develop document to me? Thank you!
Okay, I was unsure about the term "develop document", too - but "design documents" is a bit more concise, thanks for clarification.
Robin's assumption was probably right nevertheless - there is no such thing as a design document for Greenshot.
We are developing Greenshot in a very small team working tightly together, and we are the product owners ourselves - so maintaining a design document would rather be a lot of overhead, keeping us from doing the actual development.
But of course, you are still welcome to study the sources in our repository
Thanks a lot! I'v just begun learning C#, your project is a big deal for me. Thanks for your effort!
I'm so confused that how can you develop such a large project without some design docs(even without docs about the structure/model)? I feel such a distance to you...
It's some difficult for me to figure out how you develop the project. And I'm thinking that it will take some time for me to find how the different module work together. Maybe I'm to young, too simple.
Sorry if you can't understand what I'm talking about. My English is very very poor, you know. But It would be helpful if you can even give me your drafts to me. /.\
Sorry to hear you are having problems...
But keep in mind that you are looking into nearly seven years of development work - of course it is quite complex and elaborate, and the focus was never to create a tutorial or a project to learn C# from, but rather to create a cool screenshot tool; so maybe it just is not the best project for getting started with C#.
By the way, please be aware that not everything in this project is technically state of the art, parts of the program are several years old, for example we are working on getting rid of most WinForms for Greenshot 2.0 and all of them until Greenshot 2.1.
If you want to dig deeper, start with MainForm.cs, have a look at what the context menu invokes and follow the code step by step, use debugger/breakpoints to figure out what exactly is happening, etc.
But there are really no drafts or other documents to help you with this, sorry...
'guess i have a long way to go...