Just curious, it was convenient - but I've already worked around it. I'll take a look at Reflector.
Was there some problem with having the lib reference online? I found it to be accurate... perhaps versioning or some business strategy to maybe obfuscate the API a little more for support rev gen purposes? [pessimistic I know, but that seems to be the fad among open source projects that become somewhat popular]
The wiki is open to all community members, so please do feel free to create (or update) any of the pages.
As for why was it removed - I think the APIdocs were quite out-of-date ... especially with such heavy/continuous development in the core. I highly doubt that there would be any malice behind removing it. Recently the effort has been to shift more documentation on to the community wiki.
APIDocs Library page gone?
http://umbraco.org/apiDocs/html/AllMembers_T_umbraco_library.htm
used to have a great API reference there... it's loading a blank page for me today.
Any Ideas of where that went? It was pretty handy.
Hi montana,
I'm not sure where that APIDocs page has gone, but the majority of the umbraco.library methods are documented on the wiki:
http://our.umbraco.org/wiki/reference/umbracolibrary
Personally, I use Reflector on the umbraco.dll as a reference for those methods.
Cheers, Lee.
Right, it's easy enough to have python spit out all the PEMS from umbraco - but that reference was certainly handy... =(
it was nicely formatted as well...
ag shame. hope it comes back
You could always generate your own API docs? Using something like Sandcastle (or nDoc, or whatever is "cool" these days) on the source from CodePlex?
As for Reflector... there is a free version too!
Cheers, Lee.
or grab Google's cache, whilst its still hot?
I'd recommend Visual Studio with the IronPython plugin if you're not using that already + Reflector. +1 that the (auto) docs should be online.
Just curious, it was convenient - but I've already worked around it. I'll take a look at Reflector.
Was there some problem with having the lib reference online? I found it to be accurate... perhaps versioning or some business strategy to maybe obfuscate the API a little more for support rev gen purposes? [pessimistic I know, but that seems to be the fad among open source projects that become somewhat popular]
Hi montana,
The wiki is open to all community members, so please do feel free to create (or update) any of the pages.
As for why was it removed - I think the APIdocs were quite out-of-date ... especially with such heavy/continuous development in the core. I highly doubt that there would be any malice behind removing it. Recently the effort has been to shift more documentation on to the community wiki.
Cheers, Lee.
Very good, I'll contribute what I have then. Thanks!
is working on a reply...