Today I was looking at my roadmap, and it pretty much looks like I reached my beta1 status goal. In my first post I did mentioned I needed to have the following solved for beta release:
- Make it work as if you are on QCad CE, but then with the qt4 interfaces – DONE
- Fix all segfaults – DONE
However, not only that was solved, I also managed to make basic OSX and Windows packages. They are pretty much ‘bare bone’ and for OSX I really want to make a DMG installed, but now it’s just a zip. Most people on OSX would know what to do with that, right?
Anyways, for windows I created a NSIS file that will be soon committed to SVN so anybody that knows NSIS better then me, and that should be pretty much everybody that knows NSIS can create a better version.
Hope you enjoy this version of CADUntu and please leave a comment if it worked, or if not worked for you here or in the tracker in sourceforce.
R. van Twisk
I just committed a new version of CADuntu, with it’s main ‘new’ feature that I moved away from using forms3 and uic3 and the forms now are natively qt4. That said, the project didn’t move away your from q3support so that’s still in there. I feel that this isn’t really a real biggy, as long as the software works as it suppose to work, right?
I still have some standing issues reported by sliptronic and I feel that they are annoying enough to keep this software still in Alpha. Sometimes the icons seems to clutter, and text queues in multi-step operations are not shown correctly. These are somewhat the more harder items to tackle because I haven’t played around much with that area of the software. However, in reality I haven’t seen any crashes anymore since a update a couple of weeks ago.
I would like to invite you to try and compile it, if you want I could make a screencast how to compile and run on Windows. It’s really not at all that hard, you only need a SVN client like TortoiseSVN and the QT4 SDK (use the lgpl version), even I could do that on windows!
anyways, I truly hope I can make a binary release for windows pretty soon as soon as I have figured out how to make a install script. Somebody suggested to use NSIS
Ries van Twisk
Sliptronic has been giving me a lot of feedback lately, and I am trying to squash the bugs as fast as he puts them on my desk, It’s kinda fun working this way and I am very grateful he does test CADuntu and provides feedback. So today I have been working on getting the screen properly updated after a entity is de-selected. There are/many of these sort of issues because the way QCad used to renders on the screen isn’t supported by Qt4 anymore. Mostly notiably XOR operations during drawing and in Qt3 3 it was possible to draw outside of the paint event. With Qt4 all this work has been brought inside the paint event. For this, 3 QPixmaps where created:
- Layer 1 -> Draws grid and paper, basically the bottom layer
- Layer 2 -> Draws the actual drawing
- Layer 3 -> Draws the overlay, items that are currently in action like moving and drawing of lines, but also the Snapper and selection boxes.
This will speed up overlay performance of CADuntu by not drawing everything over an over again unless we have to. Second, by moving this all in the paintEvent we can take advantage of graphics acceleration.
So, today I worked on getting the [Edit] menu fixed with proper check marks for [Grid], [Draft] and [Status bar] and with accelerators so they can be accessed through they keyboard commands.
On last item I made today, was a colored box with alpha layer selection of entities. This looks a lot better, and I feel it’s much more clear then the original cyan colored rectangle. Here is a small video that snow’s that in action : http://screencast.com/t/MzMyYzg5O
First, a little history about CADuntu and why I started to do the QT4 port.
Initially, when I was working on my CNC machine I was slightly irritated by the fact that I couldn’t ‘send’ my design directly from QCAD to EMC2. I had to save the file, load it into dxf2gcode, save it back again and load it back into EMC2. This looked a rather time consuming. And as such, I decided to make a little CAM additional to QCAd CE.
When I started to do the work, and looked around I noticed there where a lot of complains about that QCad CE was only available for Qt3, and if I would give my CAM program any change to be used by others, I came to the conclusion that I needed a version of QCad in qt4. When looking around, there where some projects available, ideas and what not… But nobody really did it start to finish with a well working version of QCad that could be compiled and run on Linux, OSX and Windows with the default QT SDK. So I decided to make my own port, this would lead me to the advantage of knowing QT’s internals better, in case I needed to know that during my CAM project. And hopefully this version of QCad will be taken into the many Linux distributions.
So, here is the roadmap aka TODO list:
- Get CADuntu be compiled on Windows, Linux and OSX – Done
- Reorganize the sourcecode so it only needs one QT .pro file – Done
For Beta release:
- Make it work as if you are on QCad CE, but then with the qt4 interfaces – work in progress
- Fix all segfaults
For final release:
- Build accelerators for menu’s – in progress
After Final Release
- Move away from qt4support library – in progress, but many things todo still
- Build Windows and OSX packages – TODO
- Add CAM utils like pocketing, profiling etc…
last thing, why the name CADuntu?? It sounded fun but it has nothing TODO with the Ubuntu project.
R. van Twisk