Community
Participate
Working Groups
It would be nice if the Details text widget that appears on the various IU dialog pages would support hyperlinks. We would like our users to be able to click through to a "Whats New in Update x.x.x" type of page on our website before they install a particular IU. Sure, we can put a link in there, but they have to copy/paste it.
The thought was to actually embed a browser as the details area if the IU description has a URL. In the case of updates, it would be nice to have a separate URL for an update description (because what you show when installing is different than what you want to show when updating). I was looking for this bug while writing bug 290972, but couldn't find it. I'll mark this M4 and keep the bug alive since this is a separate issue from the main one in that bug (showing the details area without a list when there is only one item to update).
Here's some links to mockups provided in other bugs. Bug 291631 mockup: https://bugs.eclipse.org/bugs/attachment.cgi?id=149009 Bug 290972 mockup: https://bugs.eclipse.org/bugs/attachment.cgi?id=149011 Those bugs are discussing other/related issues. Comments about the general presentation of the details area this way can be made here.
(In reply to comment #2) > Bug 291631 mockup: > https://bugs.eclipse.org/bugs/attachment.cgi?id=149009 This dialog is too big IMO. As a user, I've always hoped that the "More..." link would have this sort of detailed information. It seems like the General Information section would be a good home. Thoughts? > Bug 290972 mockup: > https://bugs.eclipse.org/bugs/attachment.cgi?id=149011 LGTM. Any plans in either case for an "Open in External Browser" button/link somewhere?
(In reply to comment #3) > This dialog is too big IMO. As a user, I've always hoped that the "More..." > link would have this sort of detailed information. It seems like the General > Information section would be a good home. Thoughts? That would be the right place. Are you suggesting: - show the link on the general info page? (I could have sworn we already did, but I just double checked the code and only the doc link is shown.) - embed the URL in the general info page - the "More..." link opens the description URL and some other mechanism is provided to open the properties page. > > > Bug 290972 mockup: > > https://bugs.eclipse.org/bugs/attachment.cgi?id=149011 > > LGTM. > > Any plans in either case for an "Open in External Browser" button/link > somewhere? This is a complete oversight that it's not already in the general info page. We use an open in browser link for the doc URL but not for the description URL. I can add this immediately (though I don't think anyone provides a URL in the metadata unless hand-crafted)
(In reply to comment #4) > That would be the right place. Are you suggesting: > - show the link on the general info page? (I could have sworn we already did, > but I just double checked the code and only the doc link is shown.) > - embed the URL in the general info page > - the "More..." link opens the description URL and some other mechanism is > provided to open the properties page. I was suggesting putting the embedded content into the general info page. > > This is a complete oversight that it's not already in the general info page. > We use an open in browser link for the doc URL but not for the description URL. > I can add this immediately (though I don't think anyone provides a URL in the > metadata unless hand-crafted) I was just suggesting that if you do decide to go the embedded route here, make it possible to pop open the embedded content into an external browser, if the user so desires. Are you aware of a separate bug for URL tooling support in PDE?
> Are you aware of a separate bug for URL tooling support in PDE? Not PDE per se. I opened bug 290976 about the lack of tooling support (in publisher) for setting the update descriptor and proposing an optional update URL.
Changing milestone (to 3.6 to track for this release). Two reasons: 1) the p2 API changes happening in the branch won't be released until after M4. 2) we need to figure out our story for bug 295273 before proceeding with the branding issues. Questions discussed there include: - does the Mylyn connector support updates (if so this blurs the line between the work going on here and the connector work) - does the Mylyn branding data move into p2 or is there an extra branding/discovery publishing step on the part of a product
removing milestone. In 3.6 we fixed bug 290972 and use branding metadata in a browser for update notification if available. We aren't going to work on a more general solution.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Sorry, this is no resource to address issues such as this.
