RE: [platform-update-dev] Update action

["Mihnea Galeteanu" <mgaleteanu@xxxxxxxxxxxxxxx>]

I agree with u...but I'm not doing because I'm lazy...i'm doing it
because I need a place to store this cache so that the user cannot
modify it (it is not obvious to the user where this data is coming from
- the cached info). Since I cannot put it in the workspace, I need to
put it in the plugins directory so that's why I thought of the update
manager. If the New Updates action would've done it for me it would've
been sufficient. But unfortunatelly it doesn't work and I needed to do
the whole add site bookmark process and update from there...that's not
an option for what I'm trying to do...

-----Original Message-----
From: Dejan Glozic [mailto:dejan@xxxxxxxxxx] 
Sent: Thursday, April 03, 2003 1:01 PM
To: platform-update-dev@xxxxxxxxxxx
Subject: RE: [platform-update-dev] Update action


It seems to me that you are piggy-backing on the update technology so
that you don't have to write your own networking code. We didn't
anticipate this scenario when we designed Update.

Regards,

Dejan Glozic, Ph.D.
Manager, Eclipse Platform Components
D2/MY7/8200/MKM
IBM Canada Ltd.
Tel. 905 413-2745  T/L 969-2745
Fax. 905 413-4854



 

                      "Mihnea Galeteanu"

                      <mgaleteanu@xxxxxxxxxxxxxx        To:
<platform-update-dev@xxxxxxxxxxx>

                      m>                                cc:

                      Sent by:                          Subject:  RE:
[platform-update-dev] Update action

                      platform-update-dev-admin@

                      eclipse.org

 

 

                      04/03/2003 12:49 PM

                      Please respond to

                      platform-update-dev

 

 




That goes through all the features..i want to do it for only one
feature...basically my feature is wrapping a plugin which is a cache.
Whenever the user clicks on the "synchronize" I basically update this
feature (the update url points to a servlet which will jar up the
information I need and put it where it needs to for the update to work
properly). So, the update is really a synchronization with the
information on the server.

-----Original Message-----
From: Christophe Elek [mailto:celek@xxxxxxxxxx]
Sent: Thursday, April 03, 2003 12:41 PM
To: platform-update-dev@xxxxxxxxxxx
Subject: Re: [platform-update-dev] Update action


Doesn't the 'one-click' update from the Help menu do that ? Beside the
automatic install

Christophe Elek
Eclipse.org (Platform Update Core)
IBM Software Group - Cross Product Support
IBM Canada Ltd.

celek@xxxxxxxxxx
(905) 413-3467




             "Mihnea

             Galeteanu"

             <mgaleteanu@fre
To
             ebalance.com>
<platform-update-dev@xxxxxxxxxxx
             Sent by:                     >

             platform-update
cc
             -dev-admin@ecli

             pse.org
bcc



Subject
             04/03/2003                   [platform-update-dev] Update

             12:25 PM                     action





             Please respond

                   to

             platform-update

                  -dev









Hi,
I want to implement an update action and basically alow the user to skip
a few steps when they want to update a certain feature i;ve implemented.
My action would be similar to what happens after you've selected a new
bookmark, you';ve opened a feature to update from that site and clicked
on update now. All these steps would have to occur when the user clicks
on an action called "Synchronize" for example. Is there an easy way to
do this or do i have to look through the update code.



Mihnea Galeteanu


Software developer co-op, Research and Development


FreeBalance Inc.


www.FreeBalance.com


T (613) 236-5150 ext.375


F (613) 236-8405


mgaleteanu@xxxxxxxxxxxxxxx


This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure, or distribution is prohibited. If you are not
the intended
recipient(s) please contact the sender by reply email and destroy all
copies of the original message and any attachments.






_______________________________________________
platform-update-dev mailing list platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev
_______________________________________________
platform-update-dev mailing list platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev



_______________________________________________
platform-update-dev mailing list platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev