Version: unspecified (using KDE 1.2) OS: MS Windows Reproducible: Always Steps to Reproduce: Click on Open File from the File menu and then try to rename any file, the Kexi database application just shuts down completely. Actual Results: After trying to rename any file, the Kexi database shuts down completely. Expected Results: It should allow the user to rename any file as the rename option is present.Also the user will at least not expect the kexi database application to shutdown.
Thanks for reporting. Could you please disclose version of Kexi? It is available by clicking "About Kexi" button in Kexi tab.
The version for kexi which we are using is Kexi Demo 2007.1.1. (In reply to comment #1) > Thanks for reporting. Could you please disclose version of Kexi? It is > available by clicking "About Kexi" button in Kexi tab.
This version is not supported within the Kexi project. Upgrading to new version is recommended. Unfortulately upgrade option is available only for Linux/Unix systems for now.
Thanks for the information. Could you please let me know where could I find the source code for the older Windows version ?
It's equivalent of 1.1.x, stored here: http://websvn.kde.org/branches/koffice/1.1/ You need old commercial Qt 3.x for Windows, msvc, and old kde libraries from http://websvn.kde.org/branches/KDE/3.5/.
Thanks. Where can find source code for the latest kexi version in UNIX / LINUX. I would like to build on my own.
Good Idea. Updated recipes are at http://wiki.koffice.org/index.php?title=Building/Building_KOffice
Hi Jarostaw, I could build my own on windowsXp and Kubuntu also. I wanted to know whether you can provide me some unit test for different kexi modules such os kexidb, ksecire, sql3 abd so on. Also which tool do you use for writing unit test. Thanks, Jinal
We have tests is in koffice/kexi/tests/newapi/ directory of the source code tree. These are more like examples of usage of the public API (in typical cases) than tests of all possible functions. No particular testing tool is used here, the test program 'kexidbtest' executed with given arguments by hand and can fail or succeed what this indicates the result of the test. We would like to have detailed unit tests for each function, and looking for contributors in this field. Natural tool for this task would be QTestLib (http://doc.qt.nokia.com/4.7/qtestlib-manual.html). Another task would be to write benchmarks and work on profiling.
Noted down at http://wiki.koffice.org/index.php?title=Kexi/TODOs#Database_Support
We are working on a group prject for Kexi and we have done profiling of kexi , using the Intel VTune Ampplifier tool... Also I would go through the information you have provided for Unit testing... in koffice/kexi/tests/newapi/ folder and get back to you if I have any doubts.. Thanks, Jinal
Good to hear the feedback from you. Jinal, for your information there are works on Qt-only database layer, succesor of KexiDB, called Predicate. Currently it is in pre-beta version, published at branches/work/predicate in KDE SVN.
I am very new to KDevelop, so could you please let me know how do I execute .cpp files from the Kdevelop GUI, my OS is Ubuntu...
I tries to compile the main.cpp from the console with g++ -o main -wall main.cpp and its giving me many errors...do I need to specify any other library when I am compiling ?? Can you please let me know...as its kind of urgent...
Can you please guide me on how to execute test files which you have in the newapi folder. Please metion how to use cmakefiles..I am having hard time to understand the KDevelop GUI and I was Kconsole to compile the C++ files. After I can executue the files you have, I would be in a better position to develop new Unit tests..I would really appreciate if you could get back to me at your earliest..
Also where can I find kexidbtest...file...
On 30 November 2010 01:32, Jinal <hijinalhere@yahoo.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=254188 > > > --- Comment #16 from Jinal <hijinalhere yahoo com> 2010-11-30 01:32:28 --- > Also where can I find kexidbtest...file... (In reply to comment #15) > Can you please guide me on how to execute test files which you have in the > newapi folder. Please metion how to use cmakefiles..I am having hard time to > understand the KDevelop GUI and I was Kconsole to compile the C++ files. > After I can executue the files you have, I would be in a better position to > develop new Unit tests..I would really appreciate if you could get back to me > at your earliest.. Hi, I am answering also to the Kexi mailing list in order to reach wider audience. Have you compiled Kexi already using command line? If not, you have to do so as explained at http://wiki.koffice.org/index.php?title=Building/Building_KOffice. If you want to do that in KDevelop, I cannot help with this very specific task for now. You can consult the KDevelop documentation or ask on a kdevelop users forum or mailing list. Tests are not built by default, since not everyone needs them. Regarding tests, please read http://wiki.koffice.org/index.php?title=Building/Building_KOffice#Executing_unit_tests which explains that you have to add -DKDE4_BUILD_TESTS=ON to the cmake command you execute at the beginning of the build process. If you already built Kexi, re-run the cmake with options as before but with this extra option; then run "make install" again. This will build all available tests for KOffice components (only for apps you selected for building). Below I am assuming you use command line and you are in the build directory (may work with KDevelop or Qt Creator, since these have support for CMake). In the document above it's referred as $HOME/kde4/build/koffice (the build directory). KOffice tests, in particular Kexi tests, will no be installed, you run them from the build directory. Once you run "make install" in the build directory, type "cd kexi/tests/newapi". kexidbtests can be found here. For usage instructions read koffice/kexi/tests/newapi/README file from the source code directory. Is says that you run 'kexidbtest --help' for usage details. Only kexidbtest is maintained test for now, the sqltest is not actual. As said in a conversation before, Predicate, aka KexiDB v 2 will provide easier access to tests and will not be a part of KOffice, so the building process will be rather faster.
OK, If you want to continue this conversation please answer to the mail you received, by posting to kexi@kde.org mailing list. You have to subscribed at https://mail.kde.org/mailman/listinfo/kexi I am setting this bug as Resolved.
Hi Jarosław, I have just build koffice and not kde so I don't have the structure as kde/build/koffice... instead I directly have only koffice... I just wanted to know that to build unit test do we have to have kde4 or we can do with koffice directly I would really aprreciate if you get back to me asap.. I tries to enroll in you email list so I can email you, but I have not got confirmation from them.. Thanks, Jinal