You make the notion of working with vector-based artwork sound completely trivial. This is primarily a
sign making forum, not a forum about embroidery. The vast majority of us do not spend our time creating stitching patterns from pixel-based images. Some of the production tools we work with, such as vinyl cutters and routing tables, work only with vector-based artwork. Pixels mean nothing to those machines. When cutting or routing the best results are obtained by using clean, authentic, vector-based artwork. Not some crummy, inaccurate re-creation of it.[/quote]
The main format of stitching files (not the ones that are sent out to the machine) are vector based as well. This comes in handy for when I have to go to the
cutter to cut out Applique shapes. So yes, I'm fully aware of programs that need wire frames to run. My Statler Stitcher needs DXF files to then create the file that it needs to stitch out.
Yes, those need to have some level of precision to them.
The, lets call them raw files, but think of them as Ai compared to say DST which is like a png or jpg (in more ways then a lot of people realize) are vector objects. The information that they contain is different compared to what a traditional Ai object would contain. Because of XML capabilities tied to objects, I'm able to include a whole lot of info on these vector objects compared to Ai/Draw file (unless they have changed since CS6 and Draw x5).
But, I still deal in vectors, I'm still recreating in vectors. The only time that I'm not doing that, is when I'm doing realistic animal designs which is then like using Ps for designing. One "pixel" at a time.
The "warts" of re-created artwork might be able to hide in a stitching pattern. The same warts will show up far more easily in cut vinyl, routed lettering or large format printed graphics. You might have a good quick routine for creating stitching of every letter or object in a piece of artwork. But there's nothing quick or easy about having to vectorize a bunch of letters from scratch if the finished result is supposed to look good. It's a whole lot faster and easier to have the same typefaces the client used in the logo. The best thing is just being able to use a vector file of the client's logo and not have to waste any time re-creating any artwork at all.
The process that I use to create the stitch files is actually very similar (if not exact, I don't know his whole process only what videos he has shown) process that Vector Dr uses to create his work.
In some ways, they tools are actually easier to use then doing things via bezier pen tool (which is my preferred tool in any vector software).
And they produce vector objects. They just get exported into stitch files (just like exporting an Ai file to a jpg/png file) or when I'm doing production into text files versus the typical DST file.
You wanna see something interesting, look at the ones that do digitizing services like myself. I would say a good portion of them also do vector creation services. The ones that I know and am in contact with, use digitizing software to create those files. Your higher end digitizing software actually have traditional vector tools to skip even generating stitches in the objects. Output is exclusively a traditional vector object with no stitch information in it at all.
Name a specific application that is a fully functional replacement for Adobe Illustrator, or even CorelDRAW for that matter.
I didn't say 1:1 parity in that post you quoted. I was talking about ones that just
view as that's all I needed. I said nothing about 1:1 parity. No program that I'm aware of would have that level of parity. Something will always be different. Doesn't matter if it's workflow or something else. Even the 2 programs that you mention don't have 1:1 parity. Unless one has full 1:1 parity, in my mind, can't qualify for "
fully functional replacement".
People who are making
signs, not embroidery stitching patterns, are stuck more along the lines of the process I have to follow. There's no point to us taking a screen shot of a PDF in Adobe Reader and working only from that.
That doesn't make people like me incompetent either. The key thing is using the right tools for the job.
If I can avoid wasting a bunch of time trying to fix a customer provided PDF or AI file simply by using the right software that actually makes me and my company more competent.
I didn't say that it did. I was illustrating the fact that having an Ai file does not mean that what
I do is somehow substandard compared to if I was given an Ai file. Or my using just a viewer versus being able to view on Ai software means that I'm not able to get what I need to get.
Like you I don't hold out much hope for Adobe to port CC to Linux. Part of the problem is the philosophy of some Linux users who think everything should be open source. Ultimately it's an issue of the sales potential and I think Adobe probably doesn't see much there regardless of how many up votes the idea gets.
That and you also have some users on other platforms that have have perceptions of the platform that are rooted in the past more then how things are now. Combine those two, it's a big ass hurdle to get over.