Are there plans to release the files for download instead of online-only access through the Infocenter? It was always so nice to have them on-hand to grep in the previous versions of the SDK.
Cheers, Dan
Are there plans to release the files for download instead of online-only access through the Infocenter? It was always so nice to have them on-hand to grep in the previous versions of the SDK.
Cheers, Dan
Re-animating this ancient thread it continues to be quite annoying not to have documentation available for download. Since I'm heading somewhere for two weeks which has 50c/minute satellite internet I thought I'd try httrack to pull in some docs, I don't recommend it. Despite restricting it to what looked like a reasonable sub-domain of the infocenter it ran for 3 days, pulled in 18Gb of data before I finally gave up and stopped it. What it has managed to produce is a fairly crude facsimile of bits of the website, with no expandable buttons, bad linking and .. it's not really usable.
I guess my next attempt is to try doxygen to at least come up with a skeleton docset to take with me.
I do wish Nordic would return to producing at least some downloadable documentation to go with each SDK and softdevice release; not everyone is connected to the Internet 24x7 and even when you are, the Infocenter from 1/2 the world away i..s.. s...l...o....w
@motlib: I'm sorry to hear. We are aware of this issue but still don't have a decision yet. However, most of the documentation can be found offline. For example the Softdevice specification are available in pdf format (you can download them from infocenter), the SDK description for functions, are available in the header files when the function are described.
Hope that helped.
@motlib: I'm sorry to hear. We are aware of this issue but still don't have a decision yet. However, most of the documentation can be found offline. For example the Softdevice specification are available in pdf format (you can download them from infocenter), the SDK description for functions, are available in the header files when the function are described.
Hope that helped.