Jump to content

Documentation!


GameMonetize
 Share

Recommended Posts

  • 3 weeks later...

Hi all, 

 

The documentation has been updated to version 1.8.0 of babylon (with the awesome physics engine). You can find it here : http://www.sokrate.fr/documentation/babylonjs/index.html

 

Doncha think that aquamarine green on white background... sort of sucks? ;/

 

Sadly for Wingnut, the template has not been updated ;) If it's a big ask from the community, we can obvisouly change it.

 

Cheers !

Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...

Hi all, 


 


The documentation has been updated to version 1.9.0 of babylon. Still the same link : http://www.sokrate.fr/documentation/babylonjs/index.html


The babylon.js version has been added in the documentation title.


 


The old version (1.8.0) can be found here : http://www.sokrate.fr/documentation/babylonjs/1.8.0/index.html


 


I tried to take into account all your remarks/PM. If I forgot something, please send me a message.


 


Cheers !


Link to comment
Share on other sites

Dad72...  there are currently 86 classes and surely more to come.  That means the left-margin list-of-classes would need to scroll.  A scrolling left-margin list of classes... would conflict with the scrolling of the rest of the page.  Its still possible, using focus changing... but... what would you gain?  You would still (sometimes) have to scroll down through a list of classes like you do now.

 

You can only get about 35 items in a left margin list (without scrolling) and still have the font be readable-sized. If you could get the left margin list of classes to scroll independently, it would still be over 3 screens of scrolling (at the current Sokrate font size).  You gain very little class selectability, and you will lose about 25% of screen width area.

 

http://webpages.charter.net/wingthing/html/propIndex.htm  *shrug*

Link to comment
Share on other sites

But only 35 items in my left margin, and with small fonts.  We have 86 classes in BJS, so the Sokrate left margin would need to scroll vertically... lots.  We might be at 150 classes in two years.

 

My guess... 25 CLASS items per screen using Sokrate current font size.  So you would have to scroll that left margin area...  6 screens... to get from top to bottom.  Do you understand what I am saying? 

 

The current pull-down CLASS menu makes you scroll up and down a little, but a left-margin method of CLASS selection, would also make you scroll up and down a little.  Would you gain CLASS-selecting speed with the left margin method?  Not much, I think.  Just my opinion.

 

Some expert html template writer could sure try your method.  It's certainly possible.  It would be interesting to see it and test drive it.  A person would have to study JsDoc quite a bit, probably.  *shrug*

Link to comment
Share on other sites

No, if the body of page is in an iframe, then the scroll of the margin will remain a position when we click on a class.

 

for my part, I find it more convenient to have a margin to find a class... The navigation  menus selection <select> is less obvious.

Link to comment
Share on other sites

Nod.  I found a few... but not sure if Temechon would want to try them out.  And, they might be non-standard.

 

https://groups.google.com/forum/#!topic/jsdoc-users/lVz20dcVHo4  A couple links there to a 'classes sidebar' version.

 

Here is another...

 

http://www.thebrightlines.com/2010/05/06/new-template-for-jsdoctoolkit-codeview/

 

There is a picture of one here...

 

http://css.dzone.com/articles/introduction-jsdoc

 

None of these examples show a long classes list, so it's difficult to see how well that would work.

 

*shrug*  I'm easy.  Temechon might not be.  :)

Link to comment
Share on other sites

  • 4 weeks later...

The documentation is not updated? There should be a official documentation for babylon, rather than community documentation. In the case of abandonment, the documentation is not updated as it might be the case here.

There should be a documentation also explains what functions and examples of basic usage would make a really perfect documentation.

 
I have the right to dream.  :P
 
A perfect documentation attracts many users. If you look at the documentation of Unity3D (for exemple), there are many users because their documentation is great, perfect .
Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...