Vitaly, What about adding some button with "Go" or "Visit" text? Somewhere on the right size of line? It'd be easy to understand what to click to visit the dashboard.
- Igor On Thu, Feb 11, 2016 at 1:38 PM, Vitaly Kramskikh <[email protected]> wrote: > Roman, > > For with enabled SSL it still can be quite long as it contains FQDN. And we > also need to change plugin link representation accordingly, which I don't > fine acceptable. I think you just got used to the old interface where the > link to Horizon was a part of deployment task result message. We've merged > small style update to underline Horizon/plugin links, I think it would be > enough to solve the issue. > > 2016-02-09 20:31 GMT+07:00 Roman Prykhodchenko <[email protected]>: >> >> Cannot we use display the same link we use in the title? >> >> 9 лют. 2016 р. о 14:14 Vitaly Kramskikh <[email protected]> >> написав(ла): >> >> Hi, Roman, >> >> I think the only solution here is to underline the title so it would look >> like a link. I don't think it's a good idea to show full URL because: >> >> If SSL is enabled, there will be 2 links - HTTP and HTTPS. >> Plugins can provide their own links for their dashboards, and they would >> be shown using exactly the same representation which is used for Horizon. >> These links could be quite long. >> >> >> 2016-02-09 20:04 GMT+07:00 Roman Prykhodchenko <[email protected]>: >>> >>> Whoops! I forgot to attach the link. Sorry! >>> >>> 1. http://i.imgur.com/8GaUtDq.png >>> >>> > 9 лют. 2016 р. о 13:48 Roman Prykhodchenko <[email protected]> написав(ла): >>> > >>> > Hi fuelers! >>> > >>> > I’m not sure, if it’s my personal problem or the UX can be improved a >>> > little, but I’ve literary spend more than 5 minutes trying to figure out >>> > how >>> > to find a URL of Horizon. I’ve made a screenshot [1] and I suggest to add >>> > a >>> > full a link with the full URL in its test after "The OpenStack dashboard >>> > Horizon is now available". That would make things much more usable. >>> > >>> > >>> > - romcheg >>> > >>> > >>> > __________________________________________________________________________ >>> > OpenStack Development Mailing List (not for usage questions) >>> > Unsubscribe: >>> > [email protected]?subject:unsubscribe >>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> [email protected]?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> >> -- >> Vitaly Kramskikh, >> Fuel UI Tech Lead, >> Mirantis, Inc. >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > Vitaly Kramskikh, > Fuel UI Tech Lead, > Mirantis, Inc. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
