<div dir="ltr"><div></div>We use HTTPS url for the title and HTTP url for the small link with (HTTP) text near the title:<br><br><div><br><img style="margin-right: 25px;" src="cid:ii_ikjnimjc0_152d562a809951fb"><br><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-02-12 17:09 GMT+07:00 Igor Kalnitsky <span dir="ltr"><<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Vitaly,<br>
<span class=""><br>
> Then we'll end up with 2 buttons (for HTTP and HTTPS links) for Horizon and every plugin link<br>
<br>
</span>Why? And how do you handle it with link now?<br>
<div class="HOEnZb"><div class="h5"><br>
On Fri, Feb 12, 2016 at 11:15 AM, Vitaly Kramskikh<br>
<<a href="mailto:vkramskikh@mirantis.com">vkramskikh@mirantis.com</a>> wrote:<br>
> Igor,<br>
><br>
> Then we'll end up with 2 buttons (for HTTP and HTTPS links) for Horizon and<br>
> every plugin link, which would look quite ugly. We had all these options in<br>
> mind when we designed this change and decided to go with the current look.<br>
><br>
> Seriously guys, I don't understand you concerns. After dismissing the<br>
> deployment result message, Horizon link is in the top block on the dashboard<br>
> - it's very hard to get lost.<br>
><br>
> 2016-02-11 20:10 GMT+07:00 Igor Kalnitsky <<a href="mailto:ikalnitsky@mirantis.com">ikalnitsky@mirantis.com</a>>:<br>
>><br>
>> Vitaly,<br>
>><br>
>> What about adding some button with "Go" or "Visit" text? Somewhere on<br>
>> the right size of line? It'd be easy to understand what to click to<br>
>> visit the dashboard.<br>
>><br>
>> - Igor<br>
>><br>
>> On Thu, Feb 11, 2016 at 1:38 PM, Vitaly Kramskikh<br>
>> <<a href="mailto:vkramskikh@mirantis.com">vkramskikh@mirantis.com</a>> wrote:<br>
>> > Roman,<br>
>> ><br>
>> > For with enabled SSL it still can be quite long as it contains FQDN. And<br>
>> > we<br>
>> > also need to change plugin link representation accordingly, which I<br>
>> > don't<br>
>> > fine acceptable. I think you just got used to the old interface where<br>
>> > the<br>
>> > link to Horizon was a part of deployment task result message. We've<br>
>> > merged<br>
>> > small style update to underline Horizon/plugin links, I think it would<br>
>> > be<br>
>> > enough to solve the issue.<br>
>> ><br>
>> > 2016-02-09 20:31 GMT+07:00 Roman Prykhodchenko <<a href="mailto:me@romcheg.me">me@romcheg.me</a>>:<br>
>> >><br>
>> >> Cannot we use display the same link we use in the title?<br>
>> >><br>
>> >> 9 лют. 2016 р. о 14:14 Vitaly Kramskikh <<a href="mailto:vkramskikh@mirantis.com">vkramskikh@mirantis.com</a>><br>
>> >> написав(ла):<br>
>> >><br>
>> >> Hi, Roman,<br>
>> >><br>
>> >> I think the only solution here is to underline the title so it would<br>
>> >> look<br>
>> >> like a link. I don't think it's a good idea to show full URL because:<br>
>> >><br>
>> >> If SSL is enabled, there will be 2 links - HTTP and HTTPS.<br>
>> >> Plugins can provide their own links for their dashboards, and they<br>
>> >> would<br>
>> >> be shown using exactly the same representation which is used for<br>
>> >> Horizon.<br>
>> >> These links could be quite long.<br>
>> >><br>
>> >><br>
>> >> 2016-02-09 20:04 GMT+07:00 Roman Prykhodchenko <<a href="mailto:me@romcheg.me">me@romcheg.me</a>>:<br>
>> >>><br>
>> >>> Whoops! I forgot to attach the link. Sorry!<br>
>> >>><br>
>> >>> 1. <a href="http://i.imgur.com/8GaUtDq.png" rel="noreferrer" target="_blank">http://i.imgur.com/8GaUtDq.png</a><br>
>> >>><br>
>> >>> > 9 лют. 2016 р. о 13:48 Roman Prykhodchenko <<a href="mailto:me@romcheg.me">me@romcheg.me</a>><br>
>> >>> > написав(ла):<br>
>> >>> ><br>
>> >>> > Hi fuelers!<br>
>> >>> ><br>
>> >>> > I’m not sure, if it’s my personal problem or the UX can be improved<br>
>> >>> > a<br>
>> >>> > little, but I’ve literary spend more than 5 minutes trying to figure<br>
>> >>> > out how<br>
>> >>> > to find a URL of Horizon. I’ve made a screenshot [1] and I suggest<br>
>> >>> > to add a<br>
>> >>> > full a link with the full URL in its test after "The OpenStack<br>
>> >>> > dashboard<br>
>> >>> > Horizon is now available". That would make things much more usable.<br>
>> >>> ><br>
>> >>> ><br>
>> >>> > - romcheg<br>
>> >>> ><br>
>> >>> ><br>
>> >>> ><br>
>> >>> > __________________________________________________________________________<br>
>> >>> > OpenStack Development Mailing List (not for usage questions)<br>
>> >>> > Unsubscribe:<br>
>> >>> > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> >>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> __________________________________________________________________________<br>
>> >>> OpenStack Development Mailing List (not for usage questions)<br>
>> >>> Unsubscribe:<br>
>> >>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> >>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> >>><br>
>> >><br>
>> >><br>
>> >><br>
>> >> --<br>
>> >> Vitaly Kramskikh,<br>
>> >> Fuel UI Tech Lead,<br>
>> >> Mirantis, Inc.<br>
>> >><br>
>> >> __________________________________________________________________________<br>
>> >> OpenStack Development Mailing List (not for usage questions)<br>
>> >> Unsubscribe:<br>
>> >> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >> __________________________________________________________________________<br>
>> >> OpenStack Development Mailing List (not for usage questions)<br>
>> >> Unsubscribe:<br>
>> >> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> >><br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > Vitaly Kramskikh,<br>
>> > Fuel UI Tech Lead,<br>
>> > Mirantis, Inc.<br>
>> ><br>
>> ><br>
>> > __________________________________________________________________________<br>
>> > OpenStack Development Mailing List (not for usage questions)<br>
>> > Unsubscribe:<br>
>> > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> ><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Vitaly Kramskikh,<br>
> Fuel UI Tech Lead,<br>
> Mirantis, Inc.<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Vitaly Kramskikh,<br>Fuel UI Tech Lead,<br>Mirantis, Inc.</div></div></div></div>
</div>