I agree something like this might be nice. However, it seems like an opportunity for a third-party commercial or community project, rather than a Nokia Qt project. I'd hate to see Qt development resources go toward it. It should be possible to build something like LightSwitch on top of Qt without core changes, and there are many other advancements for the Trolls to work on, which would help the larger Qt community.
I had a closer look at the Cola wiki. It uses the Eclipse Communication Framework (ECF), which seems quit big. Didn't find anything similar in Qt Creator. Seems to be a bigger job than I first thought.
pushpendrak: Check the "shop":http://shop.qt.nokia.com/en/product-licenses.html for pricing information. The trolls here tend to be developers and most are not really aware of the current pricing schemes (at least I am not:-). Depending on what you want to do you may even be able to use the open source license, so you might want to check that first.
Since I am not aware of any Qt 5 related planning can not tell you whether it makes sense to wait for it or not.
[quote author="Tobias Hunger" date="1284381360"]You might want to file a wishlist item in our "bugtracker":http://bugreports.qt.nokia.com/. That is the best place for stuff you want to see in future releases.[/quote]
Yes, i know but i think this is the place for tell about idea...
Question : if you just don't have the required memory, can you do something to prevent the crash? Something like:
send a warning to the user "you should save your data... memory shortage coming soon... crash following"
release unused objects... is impossible in most of the cases
manage by yourself an of the core strategy (hand made HD swap)
In most cases, you don't need to wait until the last kb is used. Allocation tests can be performed on big allocations and the turnaround strategy (if any) can be started when more than 80% is used.
I have a follow on question about data sharing and a QImage.
If I create the QImage from a pointer to a unsigned char in memory (and a width and height argument), is it possible to change the pointer withing deleting and re-creating the QImage? Data sharing seems to say that it doesn't copy the data until you try to write to it (which I won't do).
I have a circular frame buffer of images that are being filled by the camera. In my paintevent method, i'm currently creating and destroying qimages.. Would it be faster to re-assign the memory location to the image data? Is that possible once the qimage has been created?
I'm new to the use of this data structure and want to make sure I'm using it as intended.
bq. Yes you can. E.g. for all non editable blocks use QTextBlock::setUserState() and give them 666. Then reimp keypress event or install an event filter and check if the cursor is in a block where the user value is 666. If so, don't propagate the event. That's all.
We have started a project of that kind for French: translation of the Qt 4.4 tutorial, some Qt Quarterlies, some Qt Labs, then a bunch of doc. We are using SVN for the first projects; for the doc, we used a totally different system: a DokuWiki, with a tool for importing pages from the doc (written by ourselves). We used a wiki rendering plugin to create the pages we serve to our visitors (basically, a PHP script calling the rendering engine and writing the result in a file).
Why DokuWiki? It does not use any database, so is easily hackable in every chunk of code. Also, it has a plugin system that makes writing new rendering engines really easy (for the other kinds of plugins, we're doing it ... well, not so beautiful a way).
Where you will have problems is pages you don't have translated. What we are doing is downloading it from Nokia's servers, then do some hack to have it render well in our template, and eventually cache it - it costs several seconds for pages like QWidget!
Also, there were things we did not like in the Qt doc: for example, you cannot ask for the page
Thank you for the pointer for Qt 4. If we move forward I can look at that.
I found an old entry in a www.qtcentre.org forum that says Qt 3 QTable does not support spanning columns which is what I ultimately need to do.
There is a third party widget QicsTable that should do the trick and I think it is still available for Qt 3.
Chris, I'm also very interested about this topic. I haven't done much DDD myself but I have read about it and done some toying.
One thing I toyed with was to create a Repository to fetch entities (json-objects from the internet). I found it hard to use QNetwork because the asynchronous nature of the module. Repositories are often modeled to return an entity and the entity can then be used to traverse the children etc.
If you're interested in shaping the future of Qt, I suggest you get involved there.
Essentially, Qt is moving towards being an open driven project, and as a result, the open infrastructure I talked about is going to have to happen.
The work I did on testing infrastructure for merge requests is also being worked on by some people at Nokia, so I've largely decided to not reinvent the wheel, and instead, to fit in with their efforts.