Comments (13)
This includes GLSL functions like agi_rayEllipsoidIntersectionInterval.
from cesium.
It also appears that member variables don't show up properly either, if you force the doc with a memberof attribute, they will show up, but be marked as static and include the "this" qualifier.
from cesium.
@kristiancalhoun and @shunter how hard do you guys think this? A good chunk of our generated doc is missing. Maybe we should bug some of this with jsdoc-toolkit? Fix it ourselves? Workaround it in comments?
from cesium.
All of the undocumented GLSL types are from .glsl files (as compared to those found in ShaderProgram.js that are documented). I think the way the original GLSL comments are broken up into strings across multiple lines when the .glsl files are converted to .js files during the build process is preventing them from being documented. Thoughts, @shunter?
from cesium.
Not that we need to address this as the same time as everything else, but a minor doc issue (in my opinion) is the fact that their is a single "flat" table of contents, it would be nice if code where split up my directory or some other sort of tree.
from cesium.
I think I've finally worked out most of our issues and will be committing the rest of my changes shortly. However, my current fix for documenting stand-alone functions uses the @function tag, which has some unintended side-effects. What new tag name would you all prefer for documenting these types of functions? @standaloneFunc?
from cesium.
This is a temporary Cesium workaround, right? If so, how about @cesiumFunction
?
Or are you going to pull request this back into jsdoc-toolkit?
from cesium.
What does @function currently do? It seems like that's the best name,
why isn't it? I guess I would prefer something like @GlobalFunction
(even though it's not really global).
On Mon, Jun 25, 2012 at 3:27 PM, Kristian Calhoun
[email protected]
wrote:
I think I've finally worked out most of our issues and will be committing the rest of my changes shortly. However, my current fix for documenting stand-alone functions uses the @function tag, which has some unintended side-effects. What new tag name would you all prefer for documenting these types of functions? @standaloneFunc?
Reply to this email directly or view it on GitHub:
#11 (comment)
from cesium.
I was trying to keep the name generic in case we do eventually pull request our changes back in, but at this point our JsDoc fork is very Cesium specific in terms of how we separate JavaScript from GLSL, generate a list of types for SandCastle, etc. Maybe at some point I'll put all our changes into a new template so that our pull request can only contain general core changes.
Functions tagged with @function are currently pooled into one conglomerate global.html file that we choose not to publish (and if we did, not all the necessary tagged info is displayed). It's also used somewhere behind the scenes to classify methods and resolve @see links (which is the error I was running into).
I also thought of @libraryFunction, but I'll go with @GlobalFunction for now and change it if there are any objections.
from cesium.
I think I actually like @libraryFunction better, good idea.
On Mon, Jun 25, 2012 at 4:32 PM, Kristian Calhoun
[email protected]
wrote:
I was trying to keep the name generic in case we do eventually pull request our changes back in, but at this point our JsDoc fork is very Cesium specific in terms of how we separate JavaScript from GLSL, generate a list of types for SandCastle, etc. Maybe at some point I'll put all our changes into a new template so that our pull request can only contain general core changes.
Functions tagged with @function are currently pooled into one conglomerate global.html file that we choose not to publish (and if we did, not all the necessary tagged info is displayed). It's also used somewhere behind the scenes to classify methods and resolve @see links (which is the error I was running into).
I also thought of @libraryFunction, but I'll go with @GlobalFunction for now and change it if there are any objections.
Reply to this email directly or view it on GitHub:
#11 (comment)
from cesium.
Maybe at some point I'll put all our changes into a new template so that our pull request can only contain general core changes.
Yes, very good idea.
Also, I'm OK with @libraryFunction
too.
from cesium.
I just opened up pull request #80.
from cesium.
The new stuff looks great, there are two more doc issues however and @kristiancalhoun is already looking into them.
- We specify the return type in most places, but the return type does not generate a link as we expect.
- Static objects are not linked to properly, for example enumerations such as LabelStyle used in Label.setStyle documentation.
from cesium.
Related Issues (20)
- viewer.ready is undefined HOT 1
- async version of Resource Proxy getURL HOT 3
- 3D models rendering is wrong with vertical exaggeration above 1 HOT 6
- Add support for glTF KHR_materials_specular extension
- Turn off vertical exaggeration for some Models in the Scene HOT 2
- Cesium Install Fails on Gentoo @Playwright HOT 3
- Create points and billboards set different colors, execute clear all entities, and then create again, the color of the point will apply the color of the billboard HOT 1
- How can set Material class->fabric->uniforms->texture in repeat Mode ?default is clamp HOT 1
- Billboards rendering partially in 2D at particular zoom level HOT 1
- strokeWidth setting does not take effect HOT 2
- Add serial numbers to each demo in Sandcastle HOT 1
- Two node_modules directories need to be added to.gitignore HOT 3
- Cesium3DTileset flickers in large data. HOT 3
- Add `cspell` checking
- Orthographic camera projection HOT 4
- Can the options in WebMapServiceImageryProvider support customTags field? HOT 6
- `Unhandled promise rejection: undefined thrown` in CI
- External tilesets are disallowed inside multiple contents
- valid glTF fails to load in CesiumJS HOT 3
- Can't find ion-sdk-widgets/Source/TransformEditor HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cesium.