Wouldn't it be possible to use SVG for things that are done with HTML+CSS?
Seems like doing a webpage with SVG instead of CSS would also allow more flexible web design.
TinyVG: A challenger to the throne of vector graphics
141–150 of 196 posts
Re: TinyVG: A challenger to the throne of vector graphics
#142Re: TinyVG: A challenger to the throne of vector graphics
#143Wouldn't it be possible to use SVG for things that are done with HTML+CSS? Seems like doing a webpage with SVG instead of CSS would also allow more flexible web design.
> Seems like doing a webpage with SVG instead of CSS would also allow more flexible web design.
Seems exactly the opposite to me.
But maybe I don't understand the intended sense of “flexible” intended.
Re: TinyVG: A challenger to the throne of vector graphics
#144This is awesome! A few notes on the formats. > magic must be { 0x72, 0x56 } I usually use weird non-ASCII bytes in file signatures of binary formats. Many tools will then correctly identify the file as binary data. > RGB 565 Not important, but I would remove that. In hardware, these 16-bit formats is a thing of the past. Nowdays, you only saving 2 bytes/color compared to RGBA8, for non-trivial complexity cost. > with…
Also, important stroke parameters are missing, line joins and caps. See pictures on these pages for illustrations:
https://docs.microsoft.com/en-us/windows/win32/api/d2d1/ne-d...
https://docs.microsoft.com/en-us/windows/win32/api/d2d1/ne-d...
Re: TinyVG: A challenger to the throne of vector graphics
#145Earlier quoted context omitted.
> So what's the deal? Are OP and me the only devs who have ever hit up against this issue in practice? The sad truth is that many issues go unreported because people are lazy and move on when they hit a roadblock. Also, I've seen this problem reported more than a few times so you're not alone.
I've seen impressive amounts of code written to get around one line bugs that could be trivially fixed, if only reported. One time, the LOC of the workaround basically matched the LOC of the tool, with the workaround implementing a full parser to consume the output of the tool, rather than just directly loading the json the tool was consuming. I used to get frustrated at these things, but I've become a bit demented,…
The problem I encounter while developing occasionally is that I encounter a series of errors and in the end you stop wanting to report the 5th bug of the day and just want to fix things the best way you can. Sometimes that attempt goes sour, sometimes it gets me out of the problem in 5 minutes.
> if only reported
Reporting bugs can be super time consuming, especially if your project is large and the maintainer has a high bar for bug reports (e.g. "provide a codesandbox link"). I can't spend 20 minutes reporting a bug that will be auto-closed in 6 months when I can attempt fixing it instead, especially if I'm annoyed at the tool already. This used to happen a lot with browsers and nowadays it happens with build tools and libraries.
Re: TinyVG: A challenger to the throne of vector graphics
#146Earlier quoted context omitted.
> Why not just implement a subset of SVG? XML
Just curious how does XML prevent you from implementing a subset?
XML is an integral part of SVG.
Don't even know what implementing a subset without using XML would actually mean.
An XML being a strong contender for the title of worst file format ever devised by mankind, I'm not sure how 'implementing a subset' would fix that.
Re: TinyVG: A challenger to the throne of vector graphics
#147Earlier quoted context omitted.
Just curious how does XML prevent you from implementing a subset?
XML is an integral part of SVG. Don't even know what implementing a subset without using XML would actually mean. An XML being a strong contender for the title of worst file format ever devised by mankind, I'm not sure how 'implementing a subset' would fix that.
Well yes, it’s true you’d have to implement basic XML parsing to implement a subset of SVG. At the same time, despite how unpopular XML may be it’s among the easiest textual languages for which to write a parser. This isn’t hyperbole. It’s so trivial I didn’t even consider that that’s what you actually meant.
Re: TinyVG: A challenger to the throne of vector graphics
#148There are many other popular vector graphics formats beyond those mentioned here. Lottie has already displaced SVG for animation/motion graphics, and for static content IconVG exists and is backed by Google. There's also PDF, PostScript, Flash, the glyf format in OpenType, etc.
> Lottie has already displaced SVG for animation/motion graphics ... Looking at the website, it seems like the file format is OSS but the creation side of things is proprietary?
Ongoing thread about Lottie, which also highlights some OSS options for creating Lottie files: https://news.ycombinator.com/item?id=29634114
Re: TinyVG: A challenger to the throne of vector graphics
#149Earlier quoted context omitted.
I have heard very good words about the eps format from a vector-format nerd (he reads file format specifikation books because its fun). I would love to here more opinions about eps from other developers. How does eps really compare with the other formats mentioned above?
EPS is just PostScript that's designed to be more embeddable. It's a PostScript program that contains some metadata like a preview image (so you can display a thumbnail when embedding it even if you don't have a PS interpreter) and a bounding box (since PS has an arbitrary coordinate system, in order to represent an embedded document without actually interpreting it, you need to know the bounds of what it's going to…
I was under the impression that EPS didn't support the full Postscript language - merely the declarative parts. I could be wrong there.
Re: TinyVG: A challenger to the throne of vector graphics
#150if I give this to my laser cutting guy is he going to be annoyed?