<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Jul 12, 2020, at 2:55 PM, Arjun Salyan <<a href="mailto:arjun@macports.org" class="">arjun@macports.org</a>> wrote:</div>...<br class="Apple-interchange-newline"><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><b class=""><br class="Apple-interchange-newline">"Splash screen" (upcoming)</b></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">It was pointed out that our current port page (<a href="http://macports.silentfox.tech/port/cctools/" class="">http://macports.silentfox.tech/port/cctools/</a>) contains a lot of technical information which might not be useful for the general user. This reduces the odds of user acquisition. So, we plan to add a page with a focus on the software version and installation instructions. It will have a link to the existing page under "Details". Maintainers and advanced users will be able to by-pass this page (setting a cookie with the preferred page) and reach the details page directly. Existing links will be maintained in this process.</div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Feedback and suggestions would be very constructive.</div><br class="Apple-interchange-newline"></div></blockquote></div><br class=""><div class="">Thanks again for your attention to detail on this project. I think that this webapp is going to be really useful.</div><div class=""><br class=""></div><div class="">Re the install instructions on the ‘Splash screen’, the suggestion to ‘sudo port install foo’ is correct in the vast majority of cases, but…</div><div class=""><br class=""></div><div class="">Where a port requires non-default variants for any of its dependencies, the above suggestion is not appropriate. If the port uses the active_variants portgroup, this is most likely the reason. If a naive user follows the suggested install instructions, they are going to experience a ‘failure’ and then need to take steps to fix it that are not immediately obvious. If the port has a lot of dependencies, the failure happens LONG after the user started the install. Very bad user experience.</div><div class=""><br class=""></div><div class="">In a similar vein, if the port uses the conflicts_build portgroup, it may ‘fail’ to install after a long period of installing deps. It is unfortunate that we don’t alert users much earlier in the process.</div><div class=""><br class=""></div><div class="">Ideally, the summary page might help the user avoid such pitfalls.</div><div class=""><br class=""></div><div class="">After that, a couple of personal preferences. On both the ‘Splash’ and detail views, the Description is initially truncated with a “More…” control. I think this is vital information and the entire description should always be displayed.</div><div class=""><br class=""></div><div class="">Also, on the Detail screen, I think all the dependencies should always be listed. It is a details screen so I would suggest that we shouldn’t have to click various controls to see the full details.</div><div class=""><br class=""></div><div class="">Someone else suggested that Variant Descriptions should be displayed and I agree with that. Also the default variants.</div><div class=""><br class=""></div><div class="">Since we are displaying everything else, has consideration been given to displaying the port’s Notes, if any?</div><div class=""><br class=""></div><div class="">Many thanks,</div><div class=""><br class=""></div><div class="">Craig</div><div class=""><br class=""></div></body></html>