Knowledgebase does not mention Show Log

[drbits]

Should JD make it easier to create a log (and Java logs) and send them to the staff?

The knowledgebase article that tells how to upload a log is out of date:
http://jdownloader.org/knowledge/wik...reate-a-jd-log

By default, the JD log tab is not visible. This is a change since the wiki entry was written.

The user must use the "?" menu entry "Show Log" to make the log visible.
________________________

Perhaps the createlog script should use a command line entry to automatically change the logging level to ALL and save the log to disk on exit (or everytime the database is saved). Then, the script could zip and e-mail the three log files after JD exits.

This would require a new JD command-line option to change the Log Level and save the log to disk.

This item, if out of date, is not the only one. Several knowledge base items are more out of date and even more are simply missing. The question is how do we tackle this moving target problem? The slightest change to the GUI might have a ripple effect of changes on the knowledge base.

This is not the only problem. Some important knowledge base items are missing in some languages. This means that some customers will never read them because they don't sufficiently master English and their GUI does not correspond to what they search for in the forums. These customers will continue asking questions in an automatically translated English that many of us don't understand.

IMO, the jD knowledge base should be structured as a semantic web, with small knowledge chunks, referring to each other. They should make use of the translation knowledge in the .loc files.
In order to make it flexible and easy to maintain, we should extend the concept of reusability to technical authoring.

[drbits]

Depending on the Wiki software being used, we might be able to easily use the .loc files already. Wiki is designed to be the kind of semantic web you are talking about.

The only more advanced software like that I know of is Mind Maps, such as "thebrain.com". The Personal Brain might work.

Of course, if the team were using Javadoc for the UI components, a style sheet could be defined that would take care of most of the problem.

I do not recommend building a documentation program. There are too many reinvented wheels in this area already. Trying to write their own documentation program has crushed some profitable companies.

[pspzockerscene]

Well it would be nice to get some help...the devs more like to develop so the best thing would be to have users that make the knowledge base :D
....okay i am a supporter but i also hate typing endless texts..

GreeZ pspzockerscene