Do you think tools like ChatGPT or copilot could generate SVG from a description?
SVG Tutorial
111–113 of 113 posts
Re: SVG Tutorial
#112Earlier quoted context omitted.
Sorry - that wasn't clear. Across the hall were our Design folks. They had the appropriate colors (in hex) that I needed.
Thanks for clarification. What’s messing with me is that you seemed to have a computer that drew hex colors. Also, you knew the hex value you wanted. Kinda hate second guessing your actions from the 20th century but why did you walk?
This would have been early 2014 (I think). If you want to see the interface in question, it's this one: https://cdn.mos.cms.futurecdn.net/d3b5b43984f43c68608886dc72...
There was a green version as well. I don't really remember why I didn't have a green graphic that I could pull the correct values from. I just recall going across the hall to talk about a Green version of the graphic and with the designer we changed the value in the SVG code instead of Illustrator (Or whatever program he was using.)
As for "Why walk across the hall?", there are times when going to someone's desk to discuss a situation is faster and more effective than an email or a chat.
Re: SVG Tutorial
#113Earlier quoted context omitted.
In XML terminology (where XHTML derives from), "tags" are the delimiters of "elements". So we have "start-tags", "end-tags", and "empty-element-tags".[1] "Element" refers to the composition of the delimiting tags and all of their (nested) content.[2] [1] https://www.w3.org/TR/xml/#sec-starttags [2] https://www.w3.org/TR/xml/#sec-logical-struct
That makes great sense. I never used "tag" properly, then. But for complete elements, like or , would it be proper to refer to them as "tags"?
In XML, they are referred to as "empty-element tags" and are functionally equivalent to a start tag immediately followed by an end tag, such as
or . If a tag has no content, it can in principle also be written as an empty-element tag, for example: . However, such use is not recommended: "For interoperability, the empty-element tag SHOULD be used, and SHOULD only be used, for elements which are declared EMPTY."[1] "For interoperability" is defined as: "Marks a sentence describing a non-binding recommendation included to increase the chances that XML documents can be processed by the existing installed base of SGML processors which predate the WebSGML Adaptations Annex to ISO 8879."[2a] "SHOULD" is explicitly[2b] used as defined in RFC 2119: "This word [...] mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course."[3]
or . If a tag has no content, it can in principle also be written as an empty-element tag, for example: . However, such use is not recommended: "For interoperability, the empty-element tag SHOULD be used, and SHOULD only be used, for elements which are declared EMPTY."[1] "For interoperability" is defined as: "Marks a sentence describing a non-binding recommendation included to increase the chances that XML documents can be processed by the existing installed base of SGML processors which predate the WebSGML Adaptations Annex to ISO 8879."[2a] "SHOULD" is explicitly[2b] used as defined in RFC 2119: "This word [...] mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course."[3]
[1] https://www.w3.org/TR/xml/#NT-EmptyElemTag