Yani in building mode... he *** at drawing and as accuracy goes he needs a computer. A pencil snapper that can't draw a straight line. Lucky for the tools, like a laser level.
A router "look at those oh so cute joins"
So I did a month of homework and found a few things that are interesting and curious.
https://www.mozaiksoftware.com/
Every wonder how these kitchen companies do the software? Do they draw it up on Autocad from home grown templates?
NUP the whole thing is a package from shop front to shop back.
"Exports to Paperless Shop" It is a parts list but I suspect it includes billing components.
https://kcdsoftware.com/doors-plus/
If doors and drawers are your company’s specialty, KCD Software’s Doors Plus is a stand-alone, template design software to communicate with your nested based CNC router.
Hundreds of templates are included in the software like doors, drawer fronts and dovetail drawer boxes. It’s also easy to create your own one-of-a-kind custom templates. Parametric tool paths can be assigned for your multiple tool operations. Create your own custom libraries for doors, drawers, wine racks, fluted pilasters, valances and more for traditional and CNC manufacturing.
Doors Plus includes over 300 ready-to-use custom component templates. The order-entry system makes it easy to enter your custom items and modify details on the fly. Doors Plus gives you more custom product capacity, flexibility and efficiency than ever before.
What's interesting is the narrow vertical market and the end to end nature of the software.
In the end, the big opportunities are in workflow. You can't just throw CAD at Draw and call that workflow. There are way more opportunities in this for Corel than people think. Corel need to re-imagine workflow. They have good code, albeit a bit ordinary, but they are using a workflow model from Windows 3.1.
That's where following the Adobe model is going to royally # Corel. That's the Win 3.1 model of applications, apps work but they are poorly linked.
Corel need to go back to basics are review the model of what an app is then work out historic errors. One of those errors is putting bitmap stuff in Draw while have a poor relationship to PP. It just adds to the confusion of the interface for very little gain. The energy should have, easy in retrospect, gone into complete integration of PP into Draw and not pulling in some features.
In place of that, a simple tab that opened whatever bitmap you point to in Draw in a full featured image editor within Draw.
It "feels like" they should have given parts of the Draw engine 3D capabilities, a new code base, then spat out CAD files rather than using AutoCAD logic of dots and points.
Why do you think I complain about the implications of the lousy implementation of the keep desktop objects on layer feature? That in itself is a paramount example of not understanding multiple industry usage of a workstation and secondary industry support.
To make it worse, when I got Designer, that came with Draw, I was unable to update Draw with patches. I had to dump Designer. I could not run both versions of Draw on the same system.
No real interface between PaintShop Pro and Draw or Photo-PAINT, same with Designer and Draw, CAD and Draw. The web sharing feature isn't color managed.
Making various Corel applications work together is a task. PaintShop is application color managed, what a PITA. the only file format of any real use between the applications is TIF. I have to convert all files to a single bit depth and color profile. Set PSP to match and think. It's worth it as PSP brings to the table many things that Photo-PAINT lacks.
Also since the Sony incident I must by contract strip all EXIF data from all supplied images before editing. It's automated so it's not bad.
It got messy when Corel started to buy existing products. Yes they got a work over but because they weren't a part of the original design they were never something that could be fully integrate.
Corel need to invest in development not buying stuff.
They could integrate better but the owners have no idea, the olde timers are getting along for a pension and the middle-aged staff have no core understanding. The feedback Core gets is from the I want to do crap graphics on my tablet and phone crowd.
In graphics they have Draw which needs two cycles of just bug fixes, especially CFM to reestablish the reputation. Then work on PDF importation.
They have two image editors, Photo-PAINT is great for what it can do, needs two cycles of bug fixes. Then it needs either two cycles of improvements in noise filters, a chromatic aberration filter, or a direct integration with PaintShop Pro. After that it needs DOCUMENTATION!!!!!
I would advise corporate to order bug fixes and a direct integration with PSP so as not to rock the PSP installed user base boat. That user base does not have what it takes for industry work and they buy that program big time. The extra bucks are peanuts for users and with both applications high end image post processing works really well.
I suggest increased support for cameras in Aftershot Pro 3.
I'd suggest a bundle package the CorelDRAW Graphics Suite, AfterShot Pro 3 and PaintShop Pro.
Any image inside Draw should open with any image editor. They need an interface for that.
But PP belongs to being integrated with Draw properly. That means loading up PP in the background and having a single instance for photo edits.
Better would be a "tab" within Draw that opened the bitmap with full tools.
The problem is that they separate, then integrate. Which creates monster apps full of menus and feature that are active eve when they are "turn off". All you get doing that is interface clutter and user headache.
That's part of what workflow is about and why it is a growing problem. Too much *** in your face when you don't need it.
They need to go the "Resolve" route. (I'll do the Resolve stuff in brackets)
You only need the corrections type bitmap corrections in Draw. If you are doing something more than use the full app.
The issues to fix first are
20 years ago editing a bitmap was special. Not so special anymore. Not trying to do it with 4MB of memory, what PP was designed to do. Not in a world that lacks libraries of code. Not in a world where exceptional bitmap editors are common. The world has changed and PP didn't keep up.