GS Custom Settings [v0.6.2]

[Tyblitz]

Something I don't like at the moment:

I can't see the full code line in the admin. Have to copy the text to text-editor or something to see fully.
This is the same for the (mage/web) urls. A tooltip hover would already be an improvement.

There some other element in the ui which have also a limited size.


Some idea: Setting an image for a setting state. So if you activate a certain setting (for example background color or css file) you see this change in example image (could be a screenshot of the site, or a screenshot of a font, or something). This way you could make a more visual oriëntated setting panel.

Thanks for your feedback.
About 1), yes I agree, I might think of stripping out the  PHP / content filter tags so you only see the lookup, and I'll implement your suggestion about the tooltip in the upcoming version already (0.4). A temporary workaround is to set GSSTYLE in gsconfig.php to GSSTYLEWIDE (which will increase the code input's size considerably, as well as the setting fields).

About 2) I think I get what you mean, though I admit this will be hard to implement if it is to be completely automatic, and where would that image be?. In the meantime, in v0.4 the setting descriptions will be allowed to contain HTML, so you could have a workaround by using JS inside an HTML attribute.

For example, if you had a setting for image size, with type text which accepts values like 100x300, you could set the setting's description like below, which will output an image in the setting's description & update the image size with the setting's value everytime it is changed:

Code:

<img src="http://placehold.it/256x256" id="my_setting-img" onload="(function() { $('#my_setting-output').on('change', function() { var src = $('#my_setting-img').attr('src'); $('#my_setting-img').attr('src', src.slice(0, src.lastIndexOf('/')+1) + $('#my_setting-output').val()); }); }())">

As for grouping settings: dear me, you can read my thoughts! In v0.4 you will be able to use return_setting_group($tab, $group, $prop=NULL) where $group = a prefix on multiple settings, separated by an underscore (eg in social_facebook & social_twitter, the 'group' would be 'social') in PHP, but for the plugin UI I'm not sure it would be a benefit + it's already easy to move settings around in the multi-select Edit mode.