Uwe Fischer <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Twayne wrote:
>> I just uninstalled/reinstalled OOo with AV off, etc., to see if it
>> helped some of the problems I've come across.  Which reminded me of
>> this shortcoming:
>>
>> Installation does not create any desktop or quicklaunch icons nor
>> does it place a shortcut in the Programs folder.
>>    It's only an annoyance to me, but I suspect others less versed in
>> the operating systems, will be confused by it and possibly not know
>> how to get their icons or even find their icon targets since, e.g.,
>> "writer" is "swriter.exe", etc., which was the first thing I
>>    searched for. IMO it should at least create a Programs entry and
>> a Desktop icon. Better, allow the opportunity to create them or not,
>> or at least a shortcut for soffice, minimum, during installation.
>>
>> So, documentation wise, this would make a great entry.  If it's
>> already there I can't find it, but apologies if I just missed it
>> somehow; perhaps it needs to stand out more clearly on the readme
>>    files. IMO the "s" prefix of the filenames should also be
>> mentioned.
>
> thank you for sharing your ideas.
> I've heard that even some users never use the Windows Start menu. What
> is not present as an icon on the desktop will not be used.

IME that's a pretty small community of Windows users that 'never' use 
the Start Menu.  All newbies and neophytes will use it and most users at 
least use it occasionally.  Since one of the goals is to spread OOo 
around for people to learn exists, I'd say the desktop icon is at least 
as important too.  My opinion at least.

> StarOffice/OpenOffice.org deliberately decided not to insert another
> set of icons to the users' desktops.
> May be we should rethink this at least for Windows?

Again, IMO yes, you should.  Or perhaps only create the Office Suite 
icon on the desktop.  I can see where there might be a worry about 
desktop "litter" if each application in the suite had its own icon, but 
the main suite icon lets you access any of the components, so as a 
minimum, I'd think the suite icon should appear on the desktop.
   Also as  minimum, I would think a note in a readme or install 
instructions should note how/what icons are created and let the user 
know he has to create his own if he wants individual application icons.
   Best case for Windows IMO would be to give the User the opportunity 
to say yay/nae to the iconds/Programs entry during install.  In my VB6 
applications, I let the user choose whether to create all 3 (desktop, 
quicklanuch and Programs) plus an opportunity to include the Uninstaller 
in the Programs menu.
   Quicklaunch could probably be skipped as least important of the 
three, IMO.
>
> Most other Windows setup programs offer a choice like "[x] Show
> Readme" on the last screen of the setup.

That would work too, in some cases but it's human nature to skip that 
readme for a lot of people.  However, if the information was there, at 
least it would have been stated and would be available for later 
perusal.
>
> Most other Windows setup programs offer a choice like "[x] Launch
> Program" on the last screen of the setup. (Well, this would not help
> much for the next time you want to start OOo)

They do, but personally I don't care for that.  I've had users start my 
programs, like it, and then not be able to figure out how to start it 
again.  That's when I started adding the choices about creating the 
icons/Programs entry or not.
>
> Many programs offer a Welcome screen at first launch, giving the
> first-time user some directions and links. OOo on Linux only shows a
> gray desert.

Hmm, probably handy, but not for the subject here; you can't get to that 
screen if you don't know what to click on to get the program started<g>.
>
> That filename confusion should also be addressed.

Definitely.  The prefix does do one great thing; it groups the 
components in a file list so they're easier to find, but ... upon first 
encounter, it's a "what's that?"  It'd be an easy thing to cover off.

Even if somewhere it just said in print, "I don't do icons; you'll have 
to roll your own" woucl have helped me.

I have 2 converts to OOo so far, BTW; feels good being the guru I'm not; 
not that I'm telling them that, of course<g>.

Regards,

Twayne

>
> Uwe





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to