Hello guys is it possible ti have the documentation of JMonkey but in a PDF format? so we can have it at all times on us? without the need of an internet connexion :S ?
maybe i’m asking for too much lol!
Hello guys is it possible ti have the documentation of JMonkey but in a PDF format? so we can have it at all times on us? without the need of an internet connexion :S ?
maybe i’m asking for too much lol!
Just download the webpage you want to read offline.
or press F1 in the jMEDK, pretty sure that is useable offline
Getting all the pages would be a lot of work. Not everybody has a website crawler, or knows how to use it (e.g. to get just the doc pages and not all forum threads with them).
So it would indeed be useful, whether as PDF or as a single HTML file.
I suspect that the current website setup isn’t built for that kind of request, so while it’s useful I doubt it’s going to happen.
As was indicated, you could print the SDK manual (F1) using a “to PDF” print tool. Idk if windows has that by default now, MacOSX has.
“Print to PDF” would be a browser function. Would be a browser plugin in most circumstances I think.
I interpret his initial post that he’s after a way to have the whole website available offline, and PDF is just the first thing that came to his mind.
So… a single large HTML would work, or a directory of HTML&stylesheets&images would do as well.
Since I have a flaky internet connection right now, I’d see that as a useful addition myself…
@toolforger said: "Print to PDF" would be a browser function. Would be a browser plugin in most circumstances I think.I interpret his initial post that he’s after a way to have the whole website available offline, and PDF is just the first thing that came to his mind.
So… a single large HTML would work, or a directory of HTML&stylesheets&images would do as well.
Since I have a flaky internet connection right now, I’d see that as a useful addition myself…
Browser? oO I am talking about the manual in the SDK, its the same as the wiki pages on the web that you apparently talk about.
The was talking about offline availability. I take it that the SDK comes with an offline copy of the docs already, so my assumption is indeed that he was talking about the wiki.
Thinking about the in-JDK docs, are these available as a directory somewhere? That might be useful to look up stuff from outside the running JDK.
@toolforger said:so my assumption is indeed that he was talking about the wiki.
But I was talking about “print to PDF” :?
@toolforger said: Thinking about the in-JDK docs, are these available as a directory somewhere? That might be useful to look up stuff from outside the running JDK.
Are you actually asking me where to find the SDK manual? Press F1 as the first page in the wiki, the manual, the SDK welcome screen and even this thread say.
I see you want a file directory /facepalm No, its a nbm (jar) file.
Yeah, and the OP was talking about offline stuff.
And yes, a file directory would be nice to have, for those situations where the SDK is unavailable or undesirable.
Single-page HTML would be even better since that would be searchable inside the browser. Downside is that it requires a companion subdirectory for stylesheets and images.
PDF would be a single file, hence easier to copy around. Not everybody has a non-sucking PDF reader though.
@toolforger said: Yeah, and the OP was talking about offline stuff.
But the OP wasn’t talking about “print to PDF” and in the SDK it isn’t “online stuff”. I am pretty sure you can print the whole manual in the SDK in one fell swoop from the directory/index of the manual. So thats what I wanted to say, you can make your own “one document PDF” in the SDK, without a browser.
i think by definition of having the jme sdk you have the wiki files as well as the documentation of the wik. All of the files used in the wiki are from jme3-testdata and all of the written documentation is either javadocs or found in the f1 screen as a tutorial. And then in addition to that there is the JME3 tests project template with loads more examples. I think that pretty much covers all cases of locally accessing the wiki.