Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Administrator
|
Hi guys,
I've updated the wiki pages at http://jogamp.org/wiki/index.php/Building_JOGL_on_the_command_line http://jogamp.org/wiki/index.php/Building_JOGL_in_Eclipse to bring them up to date with the latest commits, and to add a few missing bits that Sven mentioned to me (about workspace switching in Eclipse). Michael, could we point to http://jogamp.org/wiki/index.php/Building_JOGL_on_the_command_line from our web site front page now (instead of pointing at http://jogamp.org/jogl/doc/HowToBuild.html)? I think I've incorporated all the information from the old page, plus filled in the gaps with extra information, so the wiki page should now be a superset of the old page. If anyone sees anything missing, please let me know. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Administrator
|
On Sunday, February 06, 2011 21:00:39 Wade Walker [via jogamp] wrote:
> > Hi guys, > > I've updated the wiki pages at > > http://jogamp.org/wiki/index.php/Building_JOGL_on_the_command_line > http://jogamp.org/wiki/index.php/Building_JOGL_in_Eclipse > > to bring them up to date with the latest commits, and to add a few missing > bits that Sven mentioned to me (about workspace switching in Eclipse). Sweet, I will try later. > > Michael, could we point to > http://jogamp.org/wiki/index.php/Building_JOGL_on_the_command_line from our > web site front page now (instead of pointing at > http://jogamp.org/jogl/doc/HowToBuild.html)? I think I've incorporated all > the information from the old page, plus filled in the gaps with extra > information, so the wiki page should now be a superset of the old page. I will review this and make the change later. Maybe I will link my original document in the wiki upfront, so the user can choose what pleases her more :) Wiki as root source might be better, agreed. > > If anyone sees anything missing, please let me know. Sure. Thank you. ~Sven |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Administrator
|
Michael pointed out to me that the original HTML document is also meant to be distributed with the code, which I hadn't thought of -- it seems like we would always need two documents in that case, since we can't distribute the wiki ![]() Do we have a policy for what information should go on the wiki and what should be in HTML? |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Administrator
|
On Monday, February 07, 2011 02:01:15 Wade Walker [via jogamp] wrote:
> > Sven Gothel wrote: > > > > Maybe I will link my original document in the wiki upfront, > > so the user can choose what pleases her more :) > > Wiki as root source might be better, agreed. > > > > Michael pointed out to me that the original HTML document is also meant to > be distributed with the code, which I hadn't thought of -- it seems like we > would always need two documents in that case, since we can't distribute the > wiki > > Do we have a policy for what information should go on the wiki and what > should be in HTML? My idea was that a minimal self contained documentation should be provided in the source ball, or git repo. Hence the little build, deploy, license, etc info. ~Sven |
Free forum by Nabble | Edit this page |