Modify ↓
Opened 3 years ago Closed 3 years ago #207 closed bug (fixed)Some installer Issues with YAM 2.6p1
Description
I try to install YAM and found the follow issues:
Attachments (1)Change History (5)Changed 3 years ago by opiopicomment:1 Changed 3 years ago by thboeckel
comment:2 Changed 3 years ago by thboeckelcomment:3 Changed 3 years ago by opiopi
The issue 8 is not yet fixed in the todays archive (13.09.2010).
Here the Installer create a directory 'rexx' in the install dir
It the Files should go into the first 'rexx' Directory and the second comment:4 Changed 3 years ago by thboeckel
Ok, #8 is finally fixed now. I will upload new test archives as soon as I finished building them. Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber
| ||||||||||||||||||||||||||||



#2, #4, #5, #6 and #8 have been addressed already, hence #9 should be fixed already as well.
Concerning #1, this is quite hard to fix, because we cannot know which font will be used on the individual systems and the window opened by Installer has a fixed size and there is no way to display a long text with a scrollbar attached. The text should be readable with topaz/8 as well as with any other not too big font, but we simply cannot change the window dimensions. The only solution would be to break up the text into two pages. But since the text has not changed since the 2.6 release (except the additional "p1" here and there) and the possible change would have to be done by several translators, too, it is unlikely this will be addressed. The benefit would be quite small. Another solution would be to used Guido Mersmann's MUI based Installer replacement (http://aminet.net/util/sys/Installer.lha). This one is able to resize its window and IIRC long texts are scrollable.
Concerning #3, the german guide was not included in the 2.6 release, because it is quite outdated by now being for YAM 2.4. I cannot estimate how much work has to be done to update it to 2.6, but it will definitely too much work until the scheduled release date in about 12 days.
I don't know if there can be a fix for #7, because everything concering a protocol file is done by the Installer application internally. The script doesn't even know if a file is created or not. Thus it cannot avoid deleting it for any reason.