[OpenLayers-Dev] Jugl and examples.js
tschaub at openplans.org
Thu May 8 05:22:06 EDT 2008
The doc/examples.js script is generated by tools/exampleparser.py.
Until today, I had not looked at either of these (though I recall when
work was being done on this at FOSS4G).
I know that Chris has said that anything that can be auto-generated
should not be included in the repository. I see the sense in this, but
I also think it puts a lot into the hands of the people who have access
to the machines that do the auto part (generally, I think those are two
In this case, since the code in examples.html (which is in the
repository) depends very heavily on the examples.js that is generated by
some unknown process (unknown to me), it feels a little weird. For
example, I changed the examples.html code just now (and the
exampleparser.py). This broke the page because I couldn't change the
examples.js code that loads from http://openlayers.org/dev/doc/examples.js .
Perhaps this is no big deal. But I have no idea how frequently this
exampleparser.py is run. Perhaps it is only at release time. Perhaps
it is only at 3am on New Years. I know that Chris will be around in a
few hours and will do whatever needs to be done. But say he was on
vacation, or what if he broke a finger playing Wii?
Anyway, this is minor. But I would be interested in hearing ideas for
spreading around the tasks that fall entirely on the shoulders of one
And, in the meantime, I changed
http://openlayers.org/dev/doc/examples.html so it loads an examples2.js
that *is* in the repository. Now we've got an interactive examples page!
John R. Frank wrote:
> Should examples.js be part of the release tarball?
> The doc/examples.html file doesn't render the list of examples without
> that file being added to the directory.
> Also, what is the simplest way to modify that file so that it works
> properly when not connected to the Internet?
> Thanks for your help,
> Dev mailing list
> Dev at openlayers.org
More information about the Dev