forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sjur N. Moshagen (JIRA)" <>
Subject [jira] Commented: (FOR-581) Toolbar icons not found if tool is installed in user config dir
Date Thu, 27 Oct 2005 10:10:55 GMT
    [ ] 

Sjur N. Moshagen commented on FOR-581:

The tool is also updated to version 1.3 with the recent fixes and changes.

> Toolbar icons not found if tool is installed in user config dir
> ---------------------------------------------------------------
>          Key: FOR-581
>          URL:
>      Project: Forrest
>         Type: Improvement
>   Components: Tool: XXE config
>     Versions: 0.8-dev
>     Reporter: Sjur N. Moshagen
>     Priority: Minor
>  Attachments: tools.xxe.doc-update.txt, tools.xxe.icon-ref-patch.txt
> The XXE tool is referencing several icons in the XXE distribution in a way that requires
the tool to be installed within the application directory structure.
> As of version 2.10 (or was it 2.9p1?), the user config dir is a replica of the application
config dir, and is scanned upon application startup. This makes it natural to install the
forrest XXE tool in the user space, to avoid having to reinstall it each time XXE is updated.
> Because the icon references are relative to the installation dir of XXE (and assuming
that the tool is installed at a certain directory depth within it), it is presently not possible
to install the tool in the XXE user config area. The tool initialisation will crash, which
again will turn off the tool.
> A simple solution would be to just copy the icons into the forreset tool, but I have
been unable to find any license text or any other description on whether that would be acceptable.
> Another solution would be to enhance the URI of the icons with a reference to the installation
directory, but I don't know whether there exists a mechanism that would allow the necessary
platform independence and flexibility.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message