I stopped working on plugins for a year, and now I'm back to square one,
with all those stupid little questions I don't dare asking: how to open
a class in an editor when all I know is the FQ, how to find the type of
a file, etc.... That's frustrating.
Between "reverse-engineer the existing plugins" and "read this book"
there must be a simple, fun, and effective solution.
Here it is: look no further than the
Java Developers Almanac-online
Try a few terms: file, xml, image, preference, etc...
Brilliant, isn't it?
- The format is ideal : 10-20 lines of code at most, to answer simply
simple and specific questions.
- When the subject is more complex, a general
"The Quintessential xxxx Program"
page sets the general context. Smaller and more specific tips can then
refer to it, and offer their own solution in a few lines.
- Most pages contain a handful of links to the related solutions.
This could be built progressively by the community, and would be useful
from day 1.
Obviously, it's a wiki, but not intellij.org: we want search result to
only return openAPI answers. We also want an optimized format.
What to do:
- set up a new and clean wiki.
- fill it up with a dozen entries, to give a model, and tune the L&F
- collect questions, on a page
- edit the above page by subjects, reformat the question
- edit the whole KB formatting, fix broken links, add missing links, etc..
- tag obsolete pages (when the openAPI changes)
- answer to questions, from the list.
PS: I called it "Impossible Mission" because eventually, they always
succeed before the end of the episode :)