New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: extension.icon
#3
Comments
Logged as SU-38303 |
<echoing my comments from topic #683 (now closed as a duplicate of this issue)> Currently the icon is being downloaded as a web resource from the EW. It requires that the developer manually upload the icon to their product page. A method isn't really needed. If a common name were to be finalized and published, developers could just include an image in their RBZ. (Similar to how the RBZ archive contains a "extension_info.txt" file that is read by the API's
In the spirit of the existing "extension_info.txt" file, I believe that I had proposed filenames using "extension_icon", ie (chosen in this order): "extension_icon.svg" (or "extension_icon.pdf" on Mac), "extension_icon.png", "extension_icon.jpg", "extension_icon.bmp" ... _etc. (Meaning that the When uploading to the Warehouse (for those extension that publish there) the inclusion of images with the "extension_icon" name present in the extension subfolder should take precedence over a manually uploaded icon. But I am not opposed to the An ext_path = File.dirname(ext.instance_variable_get(:@path))
ext.icon= File.join(ext_path, "icons/manager_icon") The manager should know what file extension (image type) that is best to use. |
It is probably a matter of priority. This issue (I think) has been considered cosmetic. But as we saw in the public forum recently, users see a grayed out icon (in the Extensions Manager) and think that this signifies something as not working or having not been loaded correctly. So this is also (I will argue) an UX usability / interface issue. |
Correct, it's all a matter of priority. Enabling new functionality gets high priority, along with crash fixes and high-impact bugs. The icon would be nice, but it is a cosmetic feature that's only seen when users occasionally open the Extension Manager. That's not to say it won't ever be done. There's a number of things we'd like to improve with the Extension Manager and this would be a piece that could very well fit into that larger bulk of work. |
Yes, enabling us developers to to set an extension icon independently of Extension Warehouse would be great. Preferred formats would include .svg and .png. The current extension manager placeholder icon implies to end users that these extensions are: In the Sketchup Studio package, Trimble now includes V-Ray, at a premium price. Yet the extension manager still brands V-Ray with another generic placeholder icon. It's a tiny feature. But it would add value to a growing swathe of premium extensions distributed off the Extension warehouse. And make the extension experience more approachable. Especially for people trying out extensions. Icons help identify, individualise, and befriend extensions. Trimble, would you please harvest this ripe and low-hanging fruit? |
Add a method to SketchupExtension class which will allow us to define icon of the extension.
The icon is visible when user opens Extension Manager Window and it is currently visible only when extension is loaded from Extension Warehouse (or if we include extension_info.txt from it :-).
The text was updated successfully, but these errors were encountered: