On Thu, 5 Jun 2003, Rankin, SE (Stephen) wrote:
> 9. Treeview just runs from bin dir. Tried to view an image
> from the fits demo data and got some java errors in the window
> instead of the image?
That shouldn't happen. If it still does, please tell me which file
you were trying to view and give me the stacktrace (you can cut'n'paste
it from the window).
> 1. Set starjava/bin on path (all java stuff in ${INSTALL}/starjava).
>
> 7. Nothing in bin/task dir.
>
> 8. Topcat just runs from bin dir.
>
> 10. Starmirage just runs from the bin/ dir.
>
> 11. Tablecopy just runs from the bin/ dir.
As regards where the executables go - since there are not many, I've
put these in the bin/ dir rather than following the starlink classic/PWD
approach of sticking them in their own package bin directories,
This applies to my application scripts treeview, topcat, tablecopy,
starmirage. Ndtools is anomalous since as I said in an earlier
message it doesn't really count as a user-level application for now.
I believe it makes life easier for users if they just need
to add one entry to their PATH rather than a load of path entries
or aliases (especially when there's no guarantee that their OS has
aliases). It's not like the starlink classic situation where there
were hundreds of executables per package and there were real
possibillities of name clashes.
In any case it might make sense to have a consistent policy about this
and do it one way or the other. This would require a Command Decision
from someone. I don't mind moving my executables in accordance with
such a policy if one arises.
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] 0117 928 8776 http://www.star.bris.ac.uk/~mbt/
|