mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 23:25:52 +03:00
[GH-ISSUE #303] Developer Documentation #250
Labels
No labels
copy cats
duplicated
future feature
pull-request
⬜ Accepted
⬜ Completed
⬜ Help Wanted 💪
⬜ In Progress
⬜ Missing Details
⬜ Pending
⬜ Waiting For Answer ⏳
🆕 feature preview
🔷 Bug 🐛
🔷 Out Of Scope
🔷 Out Of Scope
🔷 Question
🔷Enhancement
🔷Enhancement
🔷Invalid / External
🔷Knowledge Base
🔷Won't Fix
🕑 High
🕑 High
🕑 High
🕕 Medium
🕙 Low
🕛 Critical
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ScreenToGif#250
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nguyenlamlll on GitHub (Mar 23, 2018).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/303
Originally assigned to: @nguyenlamlll on GitHub.
Hi,
I have recently looked into the source code. It's a bit... big and to be honest, I'm pretty clueless.
Is there a developer documentation somewhere? Maybe I missed it. I looked in Wiki section but it isn't there. If not, I'd love to help. (And probably need some helps to get starting as well). The documentation may include these sections: What modules and components are there? What are their uses? What are the controls? At least we can get some starting points or an overview look of the whole project.
@laiqun commented on GitHub (Mar 24, 2018):
just read the source code
@nguyenlamlll commented on GitHub (Mar 24, 2018):
@laiqun Hey man, of course, I know how to read. And the contributors made a really great job keeping the project readable. But I'm talking about the possibility to have a unified documentation where we can levitate newcomers' experiences.
For example, It goes like:
@NickeManarin commented on GitHub (Mar 24, 2018):
@laiqun You are not being helpful.
@nguyenlamlll
No, there's no documentation. :/
Yeah, the wiki contains only a guide for translators and users (this one is incomplete).
That would be awesome! I'll explain everything that you need to know.
@laiqun commented on GitHub (Mar 24, 2018):
@nguyenlamlll
After reading the source code of Author,I write some note, but only cover some part of source code.
If you like to reading it ,I will upload it for help you .
@nguyenlamlll commented on GitHub (Mar 25, 2018):
@NickeManarin What format would you like and where should they be hosted? Wiki pages on Github are not so great in my opinion. One should be invited as a contributor to edit the pages, right? Or can we update the docs on the website repository? So later, we can access it like
screentogif.com/docs, for example.@NickeManarin commented on GitHub (Mar 26, 2018):
For a developer documentation, it would be better to stay here, on GitHub (because the code is located in here).
@nguyenlamlll commented on GitHub (Mar 27, 2018):
So a folder
/Docsat the root with markdown files inside. Sounds good?Do you use any other chat tools? I think I can start working on it now and well, gonna have quite a few of quick questions.
@NickeManarin commented on GitHub (Mar 27, 2018):
Yes :)
Yes: Email, Discord, Twitter.
http://www.screentogif.com/contact