To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=78940


User lh changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|'oj,rene'                 |'mh,oj,rene'
--------------------------------------------------------------------------------
             Assigned to|lh                        |fs
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Mon Oct  1 11:00:19 +0000 
2007 -------
Even though the guidelines for such "touch points" are still in draft state
(will soon be made available for public discussion), one point becomes clear
already.

We will not feature "single extension promoting" (s.e.p.) touch points.

With "s.e.p." I mean the kind of touch points that _offers_ (promotes)
functionality without the necessary extension being installed, e.g. a menu 
command.

The reason is: If we start with one such touch point, nothing would keep others
from adding touch point to each of their extensions, too. At the end, OOo would
be  full of such instances, all leading to pop-us, downloads, etc. This is
nothing, a user would want. Plus, in case of conflicting extensions, each OOo
distributor would probably include only extensions they would like...

In contrast to this, we will allow for "content triggered extension" (c.t.e.)
touch points. 

An example for "content triggered" is an ODF-file, that contains data which
requires a certain extension to view or modify it. The touch point would be e.g.
a message box that pops up when the user tries to access the file or the
respective content. 

With this basic distinction between single extension touch points, I would like
to return the issue as "WONTFIX". We may look into the "content triggered"
instances for the Report Builder in more detail, but for the promoting touch
point, the state "WONTFIX" is most applicable.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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

Reply via email to