Currently the build.xml AddExamples auto-generates a list of linked example pde files in the index.html, based on the subfolder names under /examples.
Broken links are generated if the examples are grouped into subfolders, e.g. for
examples/foo/bar/bar.pde
examples/foo/baz/baz.pde
...it lists a single example "foo" (with a broken link to the non-existant foo.pde).
This is the style used by libraries with larger example sets, e.g. Camera3D, ControlP5, minim et cetera.
One solution might be to recurse or add a deeper pattern in AddExamples. Another might be to just link into the top level directories and allow directory browsing -- although that might create issues for e.g. needing to set browsing access, e.g. .htaccess et cetera.
Currently the build.xml AddExamples auto-generates a list of linked example pde files in the index.html, based on the subfolder names under /examples.
Broken links are generated if the examples are grouped into subfolders, e.g. for
...it lists a single example "foo" (with a broken link to the non-existant foo.pde).
This is the style used by libraries with larger example sets, e.g. Camera3D, ControlP5, minim et cetera.
One solution might be to recurse or add a deeper pattern in AddExamples. Another might be to just link into the top level directories and allow directory browsing -- although that might create issues for e.g. needing to set browsing access, e.g. .htaccess et cetera.