Discussion:
build-improvements and latex
(too old to reply)
Waldek Hebisch
2006-09-13 17:08:11 UTC
Permalink
I have updated to version 133 of build-improvements branch and
retried build on the same Debian testing machine. Now build goes
further, but fails running Latex on clifford.spad.tex
The reason for failure is missing amssymb.sty file.
I am affraid that if we want clean build, then configure should check
for all latex packages used.
--
Waldek Hebisch
***@math.uni.wroc.pl
Page, Bill
2006-09-13 17:37:42 UTC
Permalink
Post by Waldek Hebisch
I have updated to version 133 of build-improvements branch and
retried build on the same Debian testing machine. Now build goes
further, but fails running Latex on clifford.spad.tex
The reason for failure is missing amssymb.sty file.
I am affraid that if we want clean build, then configure should check
for all latex packages used.
I still think it makes better sense to *not* run the LaTeX part
of the build by default. If somebody wants it, they should be
able to run something like:

make documentation-all

later. Or even individually like this:

make clifford.spad.dvi

Regards,
Bill Page.
Ralf Hemmecke
2006-09-13 17:50:52 UTC
Permalink
Post by Page, Bill
I still think it makes better sense to *not* run the LaTeX part
of the build by default. If somebody wants it, they should be
make documentation-all
make clifford.spad.dvi
That's a good one. Assume clifford.spad makes a reference to Integer. At
least when the whole documentation is build I want to see that reference
turned into a link to the definition of Integer. For that we still need
some good convention of how pamphlets should look like. Hmm, maybe we
are not at that stage ...

Ralf
Gabriel Dos Reis
2006-09-13 19:10:04 UTC
Permalink
Ralf Hemmecke <***@hemmecke.de> writes:

| Hmm, maybe we are not at that stage ...

*Yes*

We need to get running on as many platform as "popular"; then we gain
critical mass; then we get the fanciest things.

-- Gaby
Gabriel Dos Reis
2006-09-13 19:08:01 UTC
Permalink
"Page, Bill" <***@drdc-rddc.gc.ca> writes:

| On Wednesday, September 13, 2006 1:08 PM Waldek Hebisch wrote:
| >
| > I have updated to version 133 of build-improvements branch and
| > retried build on the same Debian testing machine. Now build goes
| > further, but fails running Latex on clifford.spad.tex
| > The reason for failure is missing amssymb.sty file.
| > I am affraid that if we want clean build, then configure should check
| > for all latex packages used.
| >
|
| I still think it makes better sense to *not* run the LaTeX part
| of the build by default. If somebody wants it, they should be
| able to run something like:
|
| make documentation-all

Yes, that is way most GNU standard projects work, mke; make dvi; make
ps; make pdf or whatever. But the idea is not unanimous here.

-- Gaby
Page, Bill
2006-09-13 18:15:19 UTC
Permalink
...
Assume clifford.spad makes a reference to Integer. At least
when the whole documentation is build I want to see that
reference turned into a link to the definition of Integer.
For that we still need some good convention of how pamphlets
should look like. Hmm, maybe we are not at that stage ...
What *I* would like is some kind of updated version of the
Hyperdoc browser - probably using standard browser/local
webserver technology - that would allow external references
from the documentation. So we have such references embedded
in various places and/or generated automatically by something
that can parse SPAD/Aldor source code. Then while reading some
documentation or even a paper, a user can click on a link and
be immediately at the right place in Axiom.

The contents of this new Axiom Browser should be automatically
generated from alll the Axiom source distribution pamphlets.

If Axiom is not available locally, then such links should
automatically link to a standard remote website with similar
information. This should be possible with a little javascript
magic.

Regards,
Bill Page.
Gabriel Dos Reis
2006-09-13 19:19:08 UTC
Permalink
"Page, Bill" <***@drdc-rddc.gc.ca> writes:

[...]

| If Axiom is not available locally, then such links should
| automatically link to a standard remote website with similar
| information. This should be possible with a little javascript
| magic.

that should be an option -- I would hate to see Axiom suddenly starts
competing with other network hungry software for access to the net.

-- Gaby
Ralf Hemmecke
2006-09-13 19:48:52 UTC
Permalink
Post by Gabriel Dos Reis
[...]
| If Axiom is not available locally, then such links should
| automatically link to a standard remote website with similar
| information. This should be possible with a little javascript
| magic.
that should be an option -- I would hate to see Axiom suddenly starts
competing with other network hungry software for access to the net.
Gaby, I don't understand. If you have a documentation of Axiom and click
on a like then you should get somewhere or the link should not show at
all. I would prefer a local documentation ie, the link goes to some
local html, but if that cannot be found the link should either directly
link to some resources on the net or at least link to some footnote
that tells you the appropriate URL.

Ralf
Gabriel Dos Reis
2006-09-13 20:07:02 UTC
Permalink
Ralf Hemmecke <***@hemmecke.de> writes:

| On 09/13/2006 09:19 PM, Gabriel Dos Reis wrote:
| > "Page, Bill" <***@drdc-rddc.gc.ca> writes:
| > [...]
| > | If Axiom is not available locally, then such links should
| > | automatically link to a standard remote website with similar
| > | information. This should be possible with a little javascript
| > | magic.
| > that should be an option -- I would hate to see Axiom suddenly starts
| > competing with other network hungry software for access to the net.
|
| Gaby, I don't understand. If you have a documentation of Axiom and
| click on a like then you should get somewhere or the link should not
| show at all. I would prefer a local documentation ie, the link goes to
| some local html, but if that cannot be found the link should either
| directly link to some resources on the net or at least link to some
| footnote that tells you the appropriate URL.

What I was saying is that I would like to have that as an option --
i.e. if the documentation is not locally available, I would prefer to
be given the opportunity to chose whether Axiom should contact the
world or just say "sorry, documentation missing".

-- Gaby
Ralf Hemmecke
2006-09-13 20:17:16 UTC
Permalink
Post by Gabriel Dos Reis
| Gaby, I don't understand. If you have a documentation of Axiom and
| click on a like then you should get somewhere or the link should not
| show at all. I would prefer a local documentation ie, the link goes to
| some local html, but if that cannot be found the link should either
| directly link to some resources on the net or at least link to some
| footnote that tells you the appropriate URL.
What I was saying is that I would like to have that as an option --
i.e. if the documentation is not locally available, I would prefer to
be given the opportunity to chose whether Axiom should contact the
world or just say "sorry, documentation missing".
What I was saying, that I want a more or less thumb html page maybe with
a few javascript items that are there to help showing what you want.
But there should be just links and the user has to CLICK to get some
more documentation. Nothing tries to get other documentation
automatically. I think you would favour that, right?

I guess, Bill meant nothing else with

| > | If Axiom is not available locally, then such links should
| > | automatically link to a standard remote website with similar
| > | information.

Ralf
Gabriel Dos Reis
2006-09-13 22:16:57 UTC
Permalink
Ralf Hemmecke <***@hemmecke.de> writes:

| > | Gaby, I don't understand. If you have a documentation of Axiom and
| > | click on a like then you should get somewhere or the link should not
| > | show at all. I would prefer a local documentation ie, the link goes to
| > | some local html, but if that cannot be found the link should either
| > | directly link to some resources on the net or at least link to some
| > | footnote that tells you the appropriate URL.
| > What I was saying is that I would like to have that as an option --
| > i.e. if the documentation is not locally available, I would prefer to
| > be given the opportunity to chose whether Axiom should contact the
| > world or just say "sorry, documentation missing".
|
| What I was saying, that I want a more or less thumb html page maybe
| with a few javascript items that are there to help showing what you
| want.
| But there should be just links and the user has to CLICK to get some
| more documentation. Nothing tries to get other documentation
| automatically. I think you would favour that, right?

Yes. Thanks!

-- Gaby

Page, Bill
2006-09-13 19:26:51 UTC
Permalink
[... concerning links from documentation and papers to Axiom]
| If Axiom is not available locally, then such links should
| automatically link to a standard remote website with similar
| information. This should be possible with a little javascript
| magic.
that should be an option -- I would hate to see Axiom suddenly
starts competing with other network hungry software for access
to the net.
??? Perhaps you did not understand what I meant by Axiom Browser?
In what since does this involve "Axiom competing with other network
software"?

Regards,
Bill Page.
Gabriel Dos Reis
2006-09-13 20:00:47 UTC
Permalink
"Page, Bill" <***@drdc-rddc.gc.ca> writes:

| On September 13, 2006 3:19 PM Gaby wrote:
|
| >
| > Bill Page writes:
| >
| > [... concerning links from documentation and papers to Axiom]
| >
| > | If Axiom is not available locally, then such links should
| > | automatically link to a standard remote website with similar
| > | information. This should be possible with a little javascript
| > | magic.
| >
| > that should be an option -- I would hate to see Axiom suddenly
| > starts competing with other network hungry software for access
| > to the net.
| >
|
| ??? Perhaps you did not understand what I meant by Axiom Browser?

in that case, you might to elaborate to communicate your suggestion.

| In what since does this involve "Axiom competing with other network
| software"?

I don't know.

What I meant is I would hate to have Axiom starts competing with other
software to gain access to the net. I did not say competing with
network software -- most of them are not.

-- Gaby
Page, Bill
2006-09-13 20:27:18 UTC
Permalink
Ralf,
...
What I was saying, that I want a more or less dumb html page
maybe with a few javascript items that are there to help showing
what you want. But there should be just links and the user has
to CLICK to get some more documentation. Nothing tries to get
other documentation automatically. I think you would favour that,
right?
I guess, Bill meant nothing else with
| > | If Axiom is not available locally, then such links should
| > | automatically link to a standard remote website with similar
| > | information.
Exactly. I did not realize that what I wrote was so ambiguous.
Thanks for the clarification.

Regards,
Bill Page.
Continue reading on narkive:
Loading...