[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [equinox-dev] P2 touchpoint instructions doc
- From: "Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>
- Date: Tue, 24 Jun 2008 09:50:15 +0200
- Delivered-to: email@example.com
- Thread-index: AcjVhMEVW0cu0WqGSj202Hs+R8F7CAASUhcg
- Thread-topic: [equinox-dev] P2 touchpoint instructions doc
Ciao @ll :)
I've already had trouble with this limitation, my Desktop Shortcut
action tried to create a shortcut
"Eclipse, 3.4" messing up the parameter parsing completely.
Ended up substituting "," with "%comma%", this solved my issues but such
substitution should be generalized into p2 code if we need to keep the
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Henrik Lindberg
Sent: 24 June 2008 00:59
To: Equinox development mailing list
Subject: Re: [equinox-dev] P2 touchpoint instructions doc
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 particular reason for using the current format and not
have actions as classes read/written to XML?
On 23 jun 2008, at 21.40, Simon Kaegi wrote:
>> 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 parameters i.e "action1
>> (paramname1:value, paramname2:value,
>> paramname3:value);action2(...); ..."
>> Can someone confirm - or have I got it wrong yet one more time :) ?
> Yep. That's it. You've got it.
equinox-dev mailing list