Few DQuick news
My friend Bruno who works on the property binding engine make some progress. After the possibility to use property binding in D (native side) in addition of Lua (script side), he currently finishing the model list implementation. This feature will allow user to create list of items for list views for example. Bruno plans to create his own parser of Lua to simplify the script syntax just like Qt did with QML that is based on a javascript VM. To do this, he will look at the std.lexer module. For my part it doesn't progress a lot cause I have some memory issues that cause me some pain to run unittests. I really want to fix those memory corruptions before coming back on the direct 3D implementation. I hope to be able to progress faster when I'd figured out how to solve it.
Re: DQuick news
Le 29/12/2013 09:26, Jakob Ovrum a écrit : On Sunday, 29 December 2013 at 01:15:50 UTC, Xavier Bigand wrote: - Improve error reporting from Lua I looked at the commit log. I like how you are *already* fixing Lua bugs... still not considering LuaD? :P We don't fix Lua, it was about how the DMLEngine catch Lua's errors and forward it to the D part, there was also some issues when there is mismatch between D signature and Lua calls,... Bruno took a look to LuaD, but for the moment he is more comfortable with Lua and he really need to be on latest Lua version. I forgot to tell we add the dub support to build the project.
DQuick news
Latest news of DQuick for this year. The good news is, the project still alive and Bruno added some interesting stuff to the DMLengine : - Adding support of arrays - Adding support of delegates - Improve error reporting from Lua Our minesweeper sample works well but don't use arrays for the moment. About arrays, a signal is emitted for the entire array, not for each values. It completely different to the Qt choice use QAbstractListModel, this force the user to create a wrapper for properties on array or list. Our solution works without any wrapper, but we have to do some real tests to see if it's a valid solution. I hope 2014 will be the year when DQuick could be tested/used by some of you, but for that we need add some missing features, fix a lot of bugs and firstly works on the documentation (that is completely inexistent).
Re: DQuick news
On Sunday, 29 December 2013 at 01:15:50 UTC, Xavier Bigand wrote: - Improve error reporting from Lua I looked at the commit log. I like how you are *already* fixing Lua bugs... still not considering LuaD? :P
Re: DQuick news
On Sunday, 29 December 2013 at 01:15:50 UTC, Xavier Bigand wrote: Latest news of DQuick for this year. The good news is, the project still alive and Bruno added some interesting stuff to the DMLengine : - Adding support of arrays - Adding support of delegates - Improve error reporting from Lua Our minesweeper sample works well but don't use arrays for the moment. About arrays, a signal is emitted for the entire array, not for each values. It completely different to the Qt choice use QAbstractListModel, this force the user to create a wrapper for properties on array or list. Our solution works without any wrapper, but we have to do some real tests to see if it's a valid solution. I hope 2014 will be the year when DQuick could be tested/used by some of you, but for that we need add some missing features, fix a lot of bugs and firstly works on the documentation (that is completely inexistent). Does dQuick ready for writing very simple apps with several buttons and other simple controls?
Re: DQuick news
Le 29/12/2013 02:15, Xavier Bigand a écrit : Latest news of DQuick for this year. The good news is, the project still alive and Bruno added some interesting stuff to the DMLengine : - Adding support of arrays - Adding support of delegates - Improve error reporting from Lua Our minesweeper sample works well but don't use arrays for the moment. About arrays, a signal is emitted for the entire array, not for each values. It completely different to the Qt choice use QAbstractListModel, this force the user to create a wrapper for properties on array or list. Our solution works without any wrapper, but we have to do some real tests to see if it's a valid solution. I hope 2014 will be the year when DQuick could be tested/used by some of you, but for that we need add some missing features, fix a lot of bugs and firstly works on the documentation (that is completely inexistent). I think I forgot to thank publicly Piotr Podsiadły for his contributions on a animations module and SDLImage replacement by devil. He did a great job on images management by adding the notion of loader/writers. He also add an animation system, but it's not binded in Lua for the moment. So thank you Piotr Podsiadły, maybe you can share some words about your experience on DQuick?
Re: DQuick news
Le 29/12/2013 15:15, Suliman a écrit : On Sunday, 29 December 2013 at 01:15:50 UTC, Xavier Bigand wrote: Latest news of DQuick for this year. The good news is, the project still alive and Bruno added some interesting stuff to the DMLengine : - Adding support of arrays - Adding support of delegates - Improve error reporting from Lua Our minesweeper sample works well but don't use arrays for the moment. About arrays, a signal is emitted for the entire array, not for each values. It completely different to the Qt choice use QAbstractListModel, this force the user to create a wrapper for properties on array or list. Our solution works without any wrapper, but we have to do some real tests to see if it's a valid solution. I hope 2014 will be the year when DQuick could be tested/used by some of you, but for that we need add some missing features, fix a lot of bugs and firstly works on the documentation (that is completely inexistent). Does dQuick ready for writing very simple apps with several buttons and other simple controls? I prefer say no, cause there is a lot of small bugs that can be a real pain. A lot of those bugs can be bypassed by workaround based on property bindings, for example aspect ratio on images certainly not work (cause I haven't already tested), but these can easily done by property binding on width and height,... But if you try, feel comfortable to report bugs in our github tracker or to send us pull request.
