Bugzilla – Full Text Bug Listing
| Summary: | Create simple update UI for RCP applications | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Patrick Paulin <patrick> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | apupier, casey.marshall, cdtdoug, chris.l.roberts, codex69, cpuidle, d_a_carver, greg.johnson, jin.phd, martin.dilger, mn, remy.suen, sletelie, slewis, to_sud, twindham, ugo.sangiorgi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Patrick Paulin
I've only worked on two RCP apps so far, and in both cases, a lite easy to use update manager would have made the job of delivering bug fixes much easier... I think. Does any one else out there have experience delivering an RCP application to end users, and then have the developers and users wanting a little more ease of use from the update mechanisms? Everyone needs a simple update UI, not just RCP. The current UI isn't really suitable for anyone other than Eclipse experts. It's a nice idea, but sooner or later someone is going to mention P2 and it'll be doomed from there on. Can p2 provide an API to this simplified UI. We have spent so much time and money trying to get something usable out of p2, but as I said at the democamp in Ottawa "p2 solves a thousand problems that we don't have". We have finally got something workable, but it works in pretty mysterious ways, and I wouldn't wish my worst enemy to have to go thru' this pain. Cross platform sparkle would be _ideal_. +10. This is a great idea and I'd really like to use this in my product! I'd even bite the bullet and migrate my app & automated build to p2 to get it ;) +1 for this. Another nice option would be mandatory upgrades. I have an RCP app deployed at an energy company with stringent requirements on versioning: everyone has to run the same version of the app. Currently I have to set a flag in the database indicating that there's a new version available, and then add logic to the RCP code preventing from the app from starting up unless there's a version match. Being able to 1) use a light, easy-to-use update manager; and 2) flip a flag in the update manager's config to force updates; would both be very helpful to me. Marking duplicate of 281226. That bug got hijacked a bit at the end, but is still open for gathering requirements. It sounds like some folks would be happy with the headless update example being officially supported (ie, something you can tack onto the app without having to cut/paste the code). That handles the "force scenario." I agree that "Install New Software" can be overwhelming for users, but unless I'm misunderstanding requirements, this wouldn't be visible anyway in this simplified world. What's wanted is the "P2Util" example + a simplified update wizard? I think we have the pieces today and it's a matter of packaging it up right. *** This bug has been marked as a duplicate of bug 281226 *** Thanks for pointing this out. I've commented on the original entry in the hope we can get a feature like this in the 3.6 release. I hope everyone interested in this will participate on the original entry. Thanks! --- Patrick |