Until now, no qt4 supporting community version has been released.
Thanks much for your report. Unfortunately, there is nothing
we can do about this until upstream releases a community
version that runs under qt4.
Is their commercial version based on qt4?
(In reply to comment #1)
> Thanks much for your report. Unfortunately, there is nothing
> we can do about this until upstream releases a community
> version that runs under qt4.
I know that but I wanted to make sure that qt3 won't get punted from the tree since I really like using qcad :)
> Is their commercial version based on qt4?
Yes, qcad-2.2+ is ported to qt4. But there hasn't been a release neither community nor commercial since a while and their policy is to release a new community version when there has been major improvement in their commercial version. But there have been only book releases on how to use qcad in the last one or two years. I am checking their web page regularly for a new community version release because qcad is the only remaining program on my box depending on qt3. I can keep you informed about progress on this matter in this bug if you like.
(In reply to comment #2)
> I can keep you informed about progress on this matter in this bug if
> you like.
Sure, that would be great. Thanks in advance!
Or create a binary-only ebuild for it instead,
If the community is 'dead'. :/
(In reply to comment #4)
> Or create a binary-only ebuild for it instead,
Yes, this binary version would depends on qt4, but this is what is written about this version on their web page:
* There is no functional difference between the demo version and the professional version of QCAD.
* The demo version terminates after 10 minutes.
* It can be restarted and used for 100 hours in total
This means it is not usable if you really want to work with it.
> If the community is 'dead'. :/
The community is not dead. The problem with this package is that the 'community' version is NOT released by the community itself but by ribbonsoft. They decide whether to release a new community version that is sufficient old enough compared to their commercial product.
What seems to be correct though is the fact that development of their commercial product has stalled. The last releases of their commercial product was in Sep 2008.
Created attachment 215515 [details]
Binary version. LICENSE="" is missing.
You guys need to start moving on this if you want a Qt4-based version in the tree. The current version will be hardmasked along with qt:3 in 5 weeks, pending removal from portage on March 21st.
Please someone correct me, but if I understand the situation correctly
there is presently no version using qt4 which can replace the present
qcad. The binary demo version does not look like a viable version to
I am afraid you are right - so qcad for gentoo is dead.
(In reply to comment #9)
> I am afraid you are right - so qcad for gentoo is dead.
True, that's upstream decision to stop distributing sources.
Not a very nice way to force users to buy their propietary junk.
Unfortunately for me, there is no other good free replacement for QCad. So I've begun a preliminary start on porting it to Qt4 and if successful will be forking this bad boy. Assuming all goes well, I'll submit a new bug (with a link to this one) for a new package inclusion. :-)
qcad was removed from tree...
since the -bin version doesn't make sense, and the port for source version of Qt4 is now available (yet?), closing
please open new bug in case something happens in future, thanks!
What if 2 new packages were made? One for the demo, and one for the professional version with a fetch restriction on it. The professional would also have a "upgrade path" from the demo version I'd think. i.e installing the professional version forces an uninstall of the demo version.
This would be similar to the bibble packages in sunrise (#147816)
It doesn't solve the community edition problem, but it would at least let people install it through the package manager without having to create their own packages/overlays.
After looking at the "pro demo" version I can see why Mr. Mustun has been dragging his feet on a new release, especially if the upcoming ver. 3 is going to be pure Qt4. He leans heavily on the Qt3Support module and believe me, converting all that cruft to pure Qt4 is quite a chore.
And quite frankly, trying to use the "pro demo" version for any kind of serious work is a great big PITA, but you can install and run the the thing in its own directory if you're curious. And I have to agree with those who think it would be a waste of time to include it in the tree; it really wouldn't buy you much (it times out after 10 minutes--good luck trying to get any work done with that limitation in place).
But of course, YMMV. At any rate, all that to say that a reasonable alternative is coming, and hopefully sooner than later. ;-)
James, can Qt3Support in Qt4 help at all?
The answer is yes and no. :-) Yes, it's possible to get it to run using Qt3Support but it would still require some refactoring of code as some things from Qt3 have not been ported to Qt3Support. Not to mention the broken rendering path that is used in QCad 126.96.36.199 and whole host of other problems that exists in that codebase, such as a libraries that pretend to be independent when in actuality they depends on Qt. Oh, the horror... :-P
Again, a baseline with feature parity done in pure Qt4 is coming. When it's ready, a link to it will be posted in this bug so people who are wondering what happened to QCad in Gentoo will be able to find it. :-)
Yes, we have reached a fork in the road... ;-)
(In reply to comment #16)
> Again, a baseline with feature parity done in pure Qt4 is coming. When it's
> ready, a link to it will be posted in this bug so people who are wondering what
> happened to QCad in Gentoo will be able to find it. :-)
> Yes, we have reached a fork in the road... ;-)
I found this project:
someone in Japan has ported the community edition to qt4.
Here's the source:
I tried looking at the diff, but it was quite large. If someone is working on the port you can use this source code for guidance.
I haven't tried using it, just wanted to point it out.
Thanks for your work on it!
I haven't looked at their code, but I'm pretty sure they've achieved their port via Qt3Support, much like I did about two months ago. :-P I've already mentioned the problems with that approach, and I stand by what I said until proven wrong. ;-) Not only that, but what happens when Mr. Mustun decides to finally release QCad 3, and put out his crippled version of 2.2.2 for the rest of us peons?
Okay, so I'll come right out and say it: I've successfully ported it as a pure Qt4 application--no Qt3Support at all. But, I had to make some radical changes to the codebase to 1) bring sanity to it, 2) fix the rendering paths, and 3), most important to me and perhaps others, bring out a version that isn't a loss leader for another, more feature complete version that costs money. Call me strange, but I just don't like proprietary in any way, shape or form. And this whole fiasco is one great big reminder to me as to why I feel this way. ;-)
So, the goal for me is to make something even better than QCad CE; better than QCad Pro for that matter. Because, quite frankly, the QCad UI sucks. Big time. But even so, I want to thank Mr. Mustun for releasing his code under the GPL, such as it is, because otherwise I'd have been starting from scratch. :-P
I have a few loose ends to tie up in the code before making an announcement, but I will be announcing the web page and repository in this bug and then hopefully we can close it for good. :-) Or at least not have to look at it anymore. ;-)
I interessted in a new qcad version.
I you need someone for testing please send an email.
Is there any chance to get an updated version of qcad?
Check out librecad.org.
It's a qt4 fork of qcad with many (if not all) of the community patches that RibbonSoft did not have the resources to include in their releases.
Other distros (Debian based) are removing qcad and replacing it with LibreCAD, and Edubuntu is moving to make librecad the default CAD.
Interesting... Mr. van Twisk had access to my svn repo of the work I'd done in porting QCad CE to Qt4. I wish him well and much success. I guess now is as good as any time to announce. I don't have any forums or bugtrackers ATM, but hopefully all in good time.