The fundamental idea we are trying to achieve is to take a pamphlet
file from an external website URL and somehow "drag-and-drop" it onto
a browser location.
Looking for a workaround now.
The paper and its embedded code should become
part of Axiom so the user can read it and use the code, perhaps in a
\begin{axiom} block.
This is something that troubles me. What does it mean to become part of
axiom.
If you have in a pamphlet:
\begin{axiom}
integrate(sin, x)
\end{axiom}
then this command should be executed and displayed inline, similar to
what Bill has now with
\begin{sage}
maxima(....)
\end{sage}
Now to include a file, function or something else then the right way should be to
use something like:
<<newfunction>>=
.....................
@
and have something similar to what the tangle button inside Mathaction does, but
looking for all the chunks and putting them together as one file. Maybe this is what
you mean to added it then to axiom (assuming that we can determine that is axiom),
maybe: <<newfunction.axiom>>= or <<newfunction.maxima>>= or maybe let the user
add the file manually.
It would be ideal if the drag-and-drop facility were not axiom specific
(or could be customized that way) so we could drag-and-drop onto any
system. That way the researcher can use any language to implement their
work. I realize that this does not benefit Axiom but the Doyen idea is
not just about Axiom, it is a science platform.
Understood.
The drag-and-drop will work any way you choose to implement it.
The implementation determines a lot of what we can do. Since you've
looked at the wiki and the axiom connection you are in the best
situation to say how it should work. Since no-one knows how to do it
your work is clearly research and you get to decide everything.
I guess I better start writing specs and design for this, so anybody can
give more input in a page in MathAction.
Like any good research idea it will likely get adopted. The SAGE
people could clearly use such a feature, especially if they adopt
some or all of Bill's work.
Of course, once people try the feature they will have new ideas so
your first implementation will likely get additional feedback.
I really hope so. Without feedback I feel that I am not doing the right thing.
Please be sure to document how it works so we can build and maintain it.
Doyen is as much about documenting the process as it is about building
the CD.
Loud and clear.
Regards,
Jose Alfredo Perez