[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-update-dev] Basic flow
|
Sweet! Thanks. OO or there's alway line 1 somewhere, eh?
----- Original Message -----
From: "Christophe Elek" <celek@xxxxxxxxxx>
To: <platform-update-dev@xxxxxxxxxxx>
Cc: "Eclipse Update" <platform-update-dev@xxxxxxxxxxx>;
<platform-update-dev-admin@xxxxxxxxxxx>
Sent: Saturday, February 19, 2005 11:31 AM
Subject: Re: [platform-update-dev] Basic flow
> James, um, I probably have some UML buried somewhere from years ago, but
> they are not reflecting the design change
> I would start from Feature.install() as this is the main entry point the
UI
> has
> I would then look at the IFeatureContentProvider and
> IFeatureContentConsumer
>
> Let me know
>
>
>
>
> (Embedded image moved to file: pic03500.gif) Christophe Elek
> IBM Software Group - Toronto Lab
> Technical Team Lead - Cross product Tech Support
> Cross components problem resolution specialist
> Eclipse.org - Platform Core development
> Phone: 905-413-3467 T/L: 969-3467 Toll Free: 1-800-IBM-SERV
> Email: celek@xxxxxxxxxx
>
>
>
>
>
>
>
> "James D Carroll"
> <jamesdcarroll@ho
> tmail.com> To
> Sent by: "Eclipse Update"
> platform-update-d <platform-update-dev@xxxxxxxxxxx>
> ev-admin@eclipse. cc
> org
> Subject
> [platform-update-dev] Basic flow
> 02/18/2005 09:33
> PM
>
>
> Please respond to
> platform-update-d
> ev@xxxxxxxxxxx
>
>
>
>
>
>
> Is there a document that explains the basic interaction of the Update
> component. I'm not interested in the User interaction, per se (finding new
> sites or features, etc), but more along the lines of what happens after
the
> User has determined which features they would like to update.
>
> Thanks,
>
> James
> _______________________________________________
> platform-update-dev mailing list
> platform-update-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-update-dev
>
