The suggestions apply to the new UI, there's nothing super cool/new here (yet). There is one level of nesting removed in that you can paste in any URL without having to first go to a local/archive/remote site page. It will take any protocol and pass to the repo manager.
So that would make it easy to do as you suggest below...copy/paste or drag and drop a link into the repo page, or even better, into the "available features" tab without having to open a dialog to see what sites you have. Just drag the link and now you've got new software in the list. I've opened a bug for this suggestion, as it is simple and doesn't require any underlying support. https://bugs.eclipse.org/bugs/show_bug.cgi?id=207220 The "one click download/install" issue is way cooler, but I'm not looking into that just yet.... susan Brett Hackleman <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 10/23/2007 09:22 AM Please respond to Equinox development mailing list To: Equinox development mailing list <[email protected]> cc: Subject: Re: [equinox-dev] [prov] p2 / browser integration Forgot to mention some simple approaches we could also consider for the UpdateManager: 1. The UI could detect a standard http:// site or feature URL on the clipboard, or allow the user to paste it easily into the main UM dialog without forcing them to "Add Remote Site..." or even better, 2. The UI could allow links to be drag and dropped from the browser, into the main Eclipse workbench or the UM, kicking off the install. Providing sample "Eclipse package, drag to install" graphics for use on the web could make this more intuitive. (Susan, I haven't looked at the new UI yet, so please forgive me if some of this is no longer applicable) -Brett Jeff McAffer wrote: > > I agree that forcing people to browse via Elcipse is unfortunate. It > will address some of the usecases but not all. > > As for XPI, I'm not sure we need to define some new packaging. We have > the p2 stuff so all we really need to do is give p2 enough data that is > knows what it is to install. In theory this could be as simple as the > ID and version of an IU. p2 does the rest based on the current settings > etc of the agent. XPI seemed like overkill in our situation. > > Jeff > > > > *Andrew Overholt <[EMAIL PROTECTED]>* > Sent by: [EMAIL PROTECTED] > > 10/23/2007 11:10 AM > Please respond to > Andrew Overholt <[EMAIL PROTECTED]>; Please respond to > Equinox development mailing list <[email protected]> > > > > To > Equinox development mailing list <[email protected]> > cc > > Subject > Re: [equinox-dev] [prov] p2 / browser integration > > > > > > > > > Hi, > > * Chris Aniszczyk <[EMAIL PROTECTED]> [2007-10-23 10:36]: > > If you use the Eclipse browser to browse download sites or something > > like EPIC > > While I completely agree that we need some easy method of installing and > that it would be ideal to do so from a web browser, wouldn't this > solution require one to basically do all of their browsing from within > Eclipse? > > As hard as it will be, I think native handlers are the way to go here. > I'd love to be proven wrong, though, because I know how difficult it > will be -- especially with multiple running Eclipse instances. > > Andrew > _______________________________________________ > equinox-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > ------------------------------------------------------------------------ > > _______________________________________________ > equinox-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/equinox-dev -- Brett R. Hackleman Vice-President Band XI International, LLC 11362 E. Whitethorn Dr. Scottsdale, AZ 85262 USA Mobile: (602) 326-7374 GSM email: [EMAIL PROTECTED] web: http://www.bandxi.com _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
