| 49 |
|
dependent on the project configuration. There is currently no easy way of |
| 50 |
|
providing online help as to exactly what this is without relying on the |
| 51 |
|
project administrator to document it carefully. |
| 52 |
– |
<p> |
| 53 |
– |
Future developments aim to improve this interface, and move more |
| 54 |
– |
functionality to the scram command where it is only currently |
| 55 |
– |
available via less straightforward means (e.g. editing files). |
| 52 |
|
</td> |
| 53 |
|
</tr> |
| 54 |
|
<tr> |
| 76 |
|
<Require > tag.<br> |
| 77 |
|
<em>Current limitations</em><br> |
| 78 |
|
The url mechanism is limited to a simple toolname which corresponds to a file |
| 79 |
< |
in the current SCRAM toolbox area. A scram setup can only be performed once |
| 84 |
< |
for any specific file without strange results.<br> |
| 79 |
> |
in the current SCRAM toolbox area. <br> |
| 80 |
|
Future developments will allow any url (e.g file:, http:) to be specified. |
| 81 |
|
This will allow description files to be stored anywhere on the net for use |
| 82 |
|
between different projects that use the same external product. |
