-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Document icon.png #843
Document icon.png #843
Conversation
The EXPath Package spec does not mention icon.png, but if the eXist-db Dashboard finds an image resource with a filename beginning with the string "icon" in the root directory of an app, it will display that instead of the default eXist-db blue dotted "X". See https://markmail.org/message/5m6fjqso4m4veuos
@djbpitt I was under the impression it had to be named |
@adamretter I did not test it with values other than |
In 2014 @christophe-g added support for icon.svg. The code that displays icons now lives in https://github.com/eXist-db/existdb-packageservice/blob/master/modules/get-icon.xql - but support remains limited to png and svg. @djbpitt We had a similar conversation in eXist-db/dashboard#178. |
<para>The following is not mentioned in the EXPath spec, but if an image resource with a | ||
name that begins with the string <literal>icon</literal> is found in the root directory | ||
of an app, the eXist-db dashboard will display that user-supplied image instead of the | ||
default eXist-db blue dotted <literal>X</literal>.</para> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@djbpitt These are the lines containing the new contribution, correct? I just want to be sure I didn't miss anything in the other changes, which upon first glance appear to be whitespace-only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joewiz Yes. The whitespace changes are a side-effect of pretty-printing in <oXygen/>
. Should I have known of an easy way to exclude them from the commit? They certainly do make it harder to understand.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@djbpitt No worries. To avoid this on repositories that don't have a coordinated whitespace policy, I apply format & indent to the element(s) I've edited instead of to the whole document. Right click on an element and from the contextual menu select Source > Format and Indent Element. Or from the menu bad select Document > Source > Format and Indent Element.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joewiz Got it. Thank you. Another day, another feature I hadn’t known about …
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see #637 running mvn clean package
or mvn test
will enforce a unified linting of all xml files.
@djbpitt i think this is a great contribution. Thank for your time. Maybe just add that it is for. Svg or. Png |
@adamretter Done! Thank you! |
The EXPath Package spec does not mention icon.png, but if the eXist-db Dashboard finds an image resource with a filename beginning with the string "icon" in the root directory of an app, it will display that instead of the default eXist-db blue dotted "X". See https://markmail.org/message/5m6fjqso4m4veuos