…ppledoc's home page.
In short: don't worry, appledoc is still free and will remain so, you can still use it, modify it as well as use generated documentation etc. for any kind of projects - free or commercial! In long :) I'm primarily developer and don't care about legal stuff, so I didn't take much time to consider this part before. I always wanted to contribute to the community and open the tool to anybody with minimal constraints and will continue to do so in the future. But to prevent potential misuse in today's crazy money-oriented-regardless-of-consequences world :) I took some time to go through at least basic considerations of the way I want to see appledoc go in the future. After all the time I've invested in the tool, this seemed proper to do... That being said, the main reason for switching from MIT to BSD is clearer text in BSD. But generally both licenses are practically the same and are among most liberal open source licenses :) I did add one additional requirement to the license and that is to attribute appledoc in generated documentation, your website or similar. I think this is quite sensible and shouldn't interfere with open source-ness of the tool a bit. If for whatever reason you cannot agree to the license, but want to use appledoc or documentation it generates, feel free to contact me as indicated in the readme file and I'll do my best to help you out and find workable solution!
… Closes #28.
As 2.0 is a major update, starting with fresh project makes sense; old code can simply be copied over from the master branch anyway.
…lus some minor reorganization).
…ed message. The users can simply add arbitrary static text to the last updated line at the bottom of generated documentation XHTML. Note that at the moment this is only supported for XHTML output. Perhaps a better approach would be to append the information to the XML itself so it would be easily accessible to any dependent output generator or even external utilities that use appledoc clean XML for their source.
…e level 5. The new verbose level is actually the same as 4 (debug), except it additionally outputs method name and line number for each message. Changing verbose messages to debug level makes output more consistent and more readable.
The users can even provide the template for their preffered naming style similar to inter-objects links. The prefix can also be used for inter-object links. There are both, command line argument and global parameters that can be used to change the default naming template.
This can optionally be switched on or off either through the command line or global parameters. Note that while the command parameters only support a single switch that changes the status of all three items, global parameters allow enabling or disabling each individual item type. Note that at this point, example sections are not parsed properly yet.
…lect recent changes.