Hi Uwe,
On Wed, 2006-10-11 at 13:50 +0200, Uwe Fischer wrote:
> Don't get me wrong - I love this feature and I will never say anything
> negative about Michael Meeks, who surely is a programming genius. ;-)
Haha ;-) the sarcasm detector just exploded.
> How am I supposed to deliver a timely Help for this feature when
> - there is no Spec Doc
Is it necessary to write a full spec. for porting a feature to a new
platform ? I hope not. How about porting all of OO.o to 64bit ? ;-)
> - there is a feature mail very short before the new build that
> contains the feature
Sorry it was rather late, though it's not clear really what to expect
here.
> - there is no one to send questions or issues to?
As far as I can see, I didn't get killed yet :-) on the other hand,
you're guaranteed a more prompt response [ that is if you actually want
one ], by mailing me (or at least CC'ing me) rather than some list I
can't read all of. [ 4817 unread for this list alone ].
> I have many questions, for example
> - will the feature be visible on Linux too (I see it in m187 Sols/Gnome)
Yes - anywhere with gtk+ available.
> - will the feature replace existing quickstarters on Linux or be in
> parallel?
That is a distribution / vendor choice - but if you read the 'code' of
the existing quick-starters, you will experience the answer :-)
> - the text string on Tools/Options/OOo/General is different from the
> existing text string on former Windows versions. I have no idea if this
> change also changes the existing text string for Windows versions to be
> the same as now on Solaris.
Nope it does not - easy to see from the patch.
> - what about the start parameter "-quickstart"? Will that work now on
> UNIX? Must I change the Help here too?
We don't use that flag, so - no clue - no change there AFAIR.
> - why is the Help/Guide check box in the feature mail not marked? We did
> mention the (Windows-only) Quickstarter at numerous places, as did the
> OOo community in their printed and online documentation. The fact that a
> real developer never scans through Help or Guide pages does not mean
> that a feature is never Help/Guide relevant.
;-) haha - I often use the help myself. On the other hand, we shipped a
version of OO.o with this feature, and the help out of sync. to many
tens of thousands (if not millions) of users in our builds - and so far
I see no bug reports, so ... how important is this truly ?
> - on Windows, installing a patch will first close the application
> including the Quickstarter. Will it be the same on UNIX?
On Linux (for me) you'd upgrade a native package / apply an O/S patch.
On Unix this is somewhat less problematic than win32 wrt. file locking
etc.
> For me, and may be for a lot of other community members, it is important
> to get information about new or changed or removed features *early*.
>
> Best practice would be if every Help relevant feature has the
> helpcontent2 module added, so I (or the developer) can change the help
> files and have them integrated the same time as the feature.
Hokay - this is great best practise to know, and I'm happy to do it,
but it's the first time I've seen it mentioned.
Where is it documented ? perhaps it is already, but I havn't seen it:
* what module to add the CWS
* list of contact people to poke about updating help &
what their area of responsibility is so we get the right
people.
* means of detecting when they are done / assuring response
Then of course we need to find the right place in the wiki to do that,
and - naturally tell people the process has changed [ NB. mailing
individuals is more helpful than posting to a list people don't read ].
Anyhow - I'm sorry if this caused you some grief; hopefully we can get
it right next time, and I hope you like the feature - it substantially
improves code cleanliness, and 2nd start performance.
All the best,
Michael.
--
[EMAIL PROTECTED] <><, Pseudo Engineer, itinerant idiot
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
