02-20-2018, 03:30 PM
(This post was last modified: 02-20-2018, 03:52 PM by JabbaDeHatt.)
I have been stumped by how many viewers in the source code section (and elsewhere) lack a proper README.TXT file listing features.
As a NEW developper here, this is my plan if nothing changes:
1- Try to find info on all viewers in the forums to make sure I'm not duplicating coding effort --- I want to add something NEW or fix something. However viewers are often incompletely documented --- or not at all. Not a single README.TXT file found today!
2- Then I download code semi-randomly, and compile viewers based on guesses of what the features are or aren't. Compile instructions on what libraries a viewer needs to compile is usually not coming and it may take bloody ages.
3- After a week or two, I'd find out what needs to be added, merged, fixed, etc to avoid duplicating work.
I would rather it go like this:
1- Find friendly README.TXT or wiki page comparative feature table in a wiki page.
2- Less than an hour later, find out something I want to fix, merge, or add because I know what isn't reinventing the wheel.
We'd duplicate a lot less work, and/or get a lot more new developpers to start coding BEFORE THEY LOSE THE DESIRE TO DO SO from the tedious search for documentation.
So here is a poll!
As a NEW developper here, this is my plan if nothing changes:
1- Try to find info on all viewers in the forums to make sure I'm not duplicating coding effort --- I want to add something NEW or fix something. However viewers are often incompletely documented --- or not at all. Not a single README.TXT file found today!
2- Then I download code semi-randomly, and compile viewers based on guesses of what the features are or aren't. Compile instructions on what libraries a viewer needs to compile is usually not coming and it may take bloody ages.
3- After a week or two, I'd find out what needs to be added, merged, fixed, etc to avoid duplicating work.
I would rather it go like this:
1- Find friendly README.TXT or wiki page comparative feature table in a wiki page.
2- Less than an hour later, find out something I want to fix, merge, or add because I know what isn't reinventing the wheel.
We'd duplicate a lot less work, and/or get a lot more new developpers to start coding BEFORE THEY LOSE THE DESIRE TO DO SO from the tedious search for documentation.
So here is a poll!