Yet another question about touchpoint data.
Does it matter if an IU is authored so that there is only one
instruction per TouchpointData? This would make it easier in the user
interface. The user would then only see two levels - the instruction
(install, uninstall, etc.), and the actions
Agrred.
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=238240 to track
this.
[EMAIL PROTECTED] wrote on 06/24/2008 03:50:15 AM:
[image removed]
RE: [equinox-dev] P2 touchpoint instructions doc
Haigermoser, Helmut
to:
Equinox development mailing list
06/24/2008 03:50 AM
Does it matter if an IU is authored so that there is only one
instruction per TouchpointData? This would make it easier in the
user interface. The user would then only see two levels - the
instruction (install, uninstall, etc.), and the actions for the
instruction. The grouping of several
Well, I can do it that way too - I will then show a tree of
instruction blocks where each block as the nodes install/uninstall/
configure... already in place, but empty if there are no
instructions. Then the user can either add a new instruction block
or add/edit actions in the nodes. Empty
Simon, thanks for the review and update of the Touchpoint instruction
page. It is now starting to make sense :)
A couple of notes and questions:
- With the current encoding (a map of instructions), it is not
possible to use the same instruction type more than once. Is this
intentional?
A couple of notes and questions:
- With the current encoding (a map of instructions), it is not
possible to use the same instruction type more than once. Is this
intentional? What if the author needs to create two directories etc?
(I am asking because if this will be changed in the future I
Thanks Simon,
Hm, seems that my understanding of this is still unclear. I understand
touchpoint type - one IU can affect one touchpoint only, but I have
trouble with Touchpoint Data.
The IU has a list of Touchpoint Data. What exactly is one such
Touchpoint Data instance describing? I
Hm, I think may able to answer this myself. The format is actually
documented :)
The touchpoint data has a map, the keys in this map are the phases
like install, and the value is the format described on the wiki page
- i.e. a string that needs to be parsed
to understand the actions and
Hm, I think may able to answer this myself. The format is actually
documented :)
The touchpoint data has a map, the keys in this map are the phases
like install, and the value is the format described on the wiki
page - i.e. a string that needs to be parsed
to understand the actions and
:)
That means that it is not possible to have a parameter value that
includes a comma ',' - the parser will then think it delimits the
value. Which is fine for now for paths, filenames, artifact keys and
such, but perhaps not for some future touchpoints and actions.
Is there some
|
--|
|
| Subject: |
|
--|
|Re: [equinox-dev] P2 touchpoint instructions doc
I have now written a wiki page: http://wiki.eclipse.org/
Equinox_p2_Touchpoint_Instructions describing the touchpoint
instructions for the native and eclipse touchpoints, their
parameters, and how I think it works after reading the code. There
are places where I need help (indicated by blue
12 matches
Mail list logo
