6 ms·
Why? And why 4.8? The 5.x branch is a far better version of Qt. This looks ridiculous. Qt is a massive framework - the work of hundreds, if not thousands, of
by scrollaway 11y ago
Why?
And why 4.8? The 5.x branch is a far better version of Qt.
This looks ridiculous. Qt is a massive framework - the work of hundreds, if not thousands, of people - and this seems to be the work of a random dev with zero backing and a 2004-style website with zero content (everything, even the 14-forum completely empty phpbb forum).
- fla 11y agoI fail to understand either, but they say: > CopperSpice has been modified to remove moc, the Qt meta object compiler. Moc was removed to simplify the build process, allow CopperSpice to be a standalone library, increase run time performance, and allow developers to utilize C++11 features. So they replaced the moc functionality with some c++11 magic ?
- zerr 11y ago> So they replaced the moc functionality with some c++11 magic ? You mean they replaced moc magic with C++11?
- cjslep 11y agoAdvanced template metaprogramming is far less common of a skill than opening a generated source file and reading source code.
- zerr 11y agoWell, one of the aim of C++11 (and 14) is to make template metaprogramming much easier.
- emsy 11y agoTo the user it shouldn't matter wether you use a moc DSL or a template DSL. If you're a developer, you'll have to learn the innards of the moc on top of C++, which already contains templating anyway. When I first saw the signal/slot API, I wondered how they solved it and was dissappointed that they used a standalone tool for something that could've been solved with standard C++.
- stevejones 11y agoC++ is a far more common skill than moc. I know C++, I can barely get my head around writing a Qt app.
- 0xFFC 11y agoExactly , Even if TMP is much harder than MOC, TMP is standard , by forcing people to learn it they are not doing something wrong or ridiculous , but by forcing people to learn something specific to framework we are doing something wrong in my opinion {then why should we have standard at first place ? every one can create its own C++ }
- fla 11y agoI didn't realize the c++11 standard could make it possible to get rid of moc. Defenately better this way around ;) I can't wait to see this happening upstream for Qt5.
- pjmlp 11y agomoc magic for signals/slots was already possible with C++98, as proven by Gtkmm already back in 2000. http://libsigc.sourceforge.net/ http://libsigc.sourceforge.net/ But it required beefy template support, which would leave out some of the compilers supported by Qt (not only MSVC).
- pgeorgi 11y ago> So they replaced the moc functionality with some c++11 magic ? Given that signals and slots were already implemented with templates in 2002 or before (see http://ftp.gnome.org/pub/GNOME/sources/libsigc++/1.0/ http://ftp.gnome.org/pub/GNOME/sources/libsigc++/1.0/), there's probably no need for c++11 magic.
- guruz 11y agoIndirectly related blog post: "Can Qt's moc be replaced by C++ reflection?" http://woboq.com/blog/reflection-in-cpp-and-qt-moc.html http://woboq.com/blog/reflection-in-cpp-and-qt-moc.html
- IshKebab 11y agoThere are some downsides to Qt5. * It's huge - something like 30 MB for "hello world" on Windows. * Deployment is a nightmare (loads of plugin DLLs, there's some crazy path stuff going on, if you use QML you have to include a load of system qml files). There is a windeployqt tool which helps but it still isn't as easy as with Qt4. * QML/QtQuick are very nice for some things, but in a lot of ways they kind of suck. E.g. passing data between C++ and Javascript is always a pain. Also most of the QML tools (compiler, usable GUI editor, profiler, etc.) are only in the enterprise version of Qt. Having said that, I don't know why they didn't just base it on Qt5, remove all the QML stuff and make unicode optional (unicode support costs about 20MB). Qt5 already uses C++11 syntax for signals and slots (though you still need moc). I don't know why you dislike their website.
- scrollaway 11y agoQML/QtQuick etc are modules in Qt 5, you don't have to depend on them at all and they're not linked in. QtCore is tiny.
- coldtea 11y ago>It's huge - something like 30 MB for "hello world" on Windows. First, 30MB for "hello world" doesn't mean it will get linearly bigger as code grows. Most is one time off overhead. Else something like Kate would be an 1 TB binary. Second, 30MB hasn't been an issue since 2002. Heck, I have 20+ apps, each over 30MB, on my PHONE.
- nadams 11y ago> Second, 30MB hasn't been an issue since 2002 Back in 2004 a demoscene group created a FPS in 96kb - http://www.pouet.net/prod.php?which=12036 http://www.pouet.net/prod.php?which=12036 That 96kb includes textures, engine and music. No they aren't downloading content or streaming from the internet. I know how they did it - and with some tweaking of gcc command line parameters you can write C you can get close to those file sizes. When I see that the game RAGE, while an excellent game, takes up 20GB of disk space I just shake my head. Now I'm not advocating that everyone should be making FPSes at 96kb - but I feel like 20GB is a little unnecessary for the game RAGE (especially how short it was). I personally try to be as efficient as possible when it comes to using other people's storage and memory.
- DocSavage 11y agoThe lack of a public repo of some kind and obvious licensing makes this a no-start for me.
- dudifordMann 11y agoso source is available, though not hosted in a VCS: http://download.copperspice.com/copperspice/source/ http://download.copperspice.com/copperspice/source/ Legal info is also available. http://www.copperspice.com/docs/cs_overview/legal.html http://www.copperspice.com/docs/cs_overview/legal.html So it's just not in github-esque hosted format you're expecting.
- asermersheim 11y agoWe had everything set up on sourceforge and we hit the limits of what we could accomplish on sourceforge last month. We have been moving everything including downloads and forums to a better location. We have not yet moved the git repo to a publicly accessible location, but this is in progress. Thank you for bringing this to our attention, and I apologize for the inconvenience.
- emddudley 11y agoThe About page [1] lists two people: Barbara Geller and Ansel Sermersheim. [1] http://www.copperspice.com/about.html http://www.copperspice.com/about.html
- codeshaman 11y agoI'm always bewildered by such aggressive reactions to things people put out for free. So you don't like it and won't use it, but why do you find it necessary to insult the people who worked on it ? Are they trying to steal something from you or cheat you into giving up your freedom or something ? I just don't get it. We are all developers and we all know how hard it is to make something.. anything. And knowing the struggle I go through to get things to completion, I have great respect for people who actually finish things and share them with the world. Even if I won't use the thing and find it useless, I still think they deserve at least a word of support, not a dismissive rant.
- scrollaway 11y ago> why do you find it necessary to insult the people who worked on it I insulted the work, not the people who worked on it. And I didn't gratuitously insult it, I've given further reasoning elsewhere in the thread: It's an obscure fork of a massive project, on an outdated version, with no chance of further support, no VCS, no discussions, no background and no author here to back any of it up. It wasn't aggressive. It certainly was negative. But from what I've seen, this was never a space where your project will be cuddled. Nor is open source in general a place you get a free ride just because "you don't have to use it if you don't like it". When one puts their work forward, it's either to either receive criticism on it or popularize it. In either case, negative criticism is a good thing. Like I said, I didn't criticize it just to be negative - if you go through my previous posts, you'll find that I try to be overwhelmingly positive, even to projects I find pointless. But this here is not "just pointless", it's a fork. Forks are divisive, and this is a fork which does not bring any net positives and which has no way of ever being merged back into the project, given that it's based on an outdated version and model of Qt.
- sqeaky 11y agoThe project is large, but superficially seem to have a reasonable approach and documentation. The website looks fine as a simple communication tool and changelog. Why attack them for their style and not something substantive?