Karl Wick wrote:
This doesn't fit in very well with the idea of
reusing the same modules in different ways for different textbooks.
Now, I don't know how big of a deal that is;
will such reuse be limited to a few cases,
so that copying modules will work:
One final idea is to use an idea similar to that
employed
by the Yahoo briefcase where you can copy modules from one
folder to another, for example to create a derivative
textbook or just take a couple of modules from one to
another without having to open each page and copy out the
code.
:or if we'll be reusing modules all over the place in many ways.
In the later case, a URL that first states the module name,
then lists whatever other data we need in ?%%=%% format,
would be best IMO.
The idea of using nested URLs will also help us get
around
funky URLs and/or page names for pages with common names
like "Problem set". Plus this structure of URL hierarchy
should be familiar to most internet users already so there
is little learning curve.
Even if the latter case wins above and y'all agree with me,
still [[Vital force/Problem set]] would be a reasonable module title.
That said, problem set modules could well present
their own special difficulties
if the modules that they build on are reused in many ways.
Here an idea off the cuff:
Each /problem/ is a separate file,
with some of its data specifying which modules it uses,
and the problem will appear in a given textbook
as soon as all of its prerequisites have been read.
(The textbook itself might specify, however,
that problems can appear, say, only at the end of a chapter.)
This is just off the cuff, remember! ^_^
-- Toby