No protocol specified
webissues: cannot connect to X server :0

give me error when i try to run webissues

This seems to be a general problem not related to WebIssues. Try googling for the error message, you should be able to find a solution.

Great to know u have switch to qmake.

I can now start on trying implement web issues as a plugin for my Qt IDE : Monkey Studio.

http://www.monkeystudio.org

I will gladly assist you with any help. The WebIssues forums seem like a good place to start (http://webissues.mimec.org/forum).

I'm planning to have a little break from developing WebIssues after the final release, but that sounds like a perfect thing to do in the meantime.

webissues 0.9.0 (from sources) crashes on win32 just after successfuly log in to server.

builded without any errors with cmake 2.4p6, gcc 3.4.5, qt 4.3.0.


what i can to do?

I just installed Qt 4.3.0 (previously I had 4.2.3) and indeed, the original 0.9.0 version crashed after connecting to the server. However the current development version didn't crash, so perhaps you could get the latest sources from the SVN repository and check if that works?

The soft sounds quite nice but...

1) Why the hell do you use CMake? Ok that's a stupid question... It's your choice but anyway please consider bundling a regular qmake project file (.pro) for everyone to be able to try your app (FYI I have cmake installed but it failed to build due to conflicts with my Qt installation and I had to write my own .pro files which wasn't a synch ...)
2) The web based setup is nice but what about providing a way to edit the config file through a simple webpage? Would have saved me some time...
3)CMake really sucks! Or at least it introduces a bad (i.e. not backward compatible with qmake) coding style : I was forced to write a shell script to comment out all occurrences of #include "some_file.moc"
4) Splitting your app into static libraries works with cmake but made me such a tough time porting the porjct files back to qmake...

OK that should be all for the cons by now... ;) I've set up the server and the client is now building smoothly so you'll get more feedback when I try it :)

I've chosen CMake because I come from KDE and that's what they recently switched to. If it works for the project the size of KDE, it must work for me :). I'm sure it would work for you as well, perhaps you just have to set some paths etc. What errors did you get with CMake?

About the config file... setting three or four parameters in a text file is not a big inconvenience. When the config reaches 20 options, I promise to write a wizard :).

The problem is that I use a distro (Frugalware) which doesn't export Qt 4 paths/variables by default. This cause qmake itself to miserably fail unless I do a source /etc/profile.d/qt4.sh

Yet even doing this left CMake failing. I got an error on the first moc call which told me that invalid options/parameters had been passed.

Being unfamiliar with CMake I decided to write a qmake project. Your cmake architecture confused me at first but I finally managed to get it work by running "qmake -project" within src directory and then setting a few additional variables by hand in the generated .pro file (I can send it to you if you feel like adding support for qmake).

The config file is not a big issue... It's just something I mentionned because it might discourage some users, especially those who don't use a neat KDE text editor which allows on-the-fly editions of files over ftp... ;)

There are two things left to mention :
* I'd greatly appreciate some kind of notification mechanism (even a very simple one). For instance it would be great to know when connecting whether new issues have been added (which type and where...) since last connection. A great (and simple) way to highligt this would be colored icons and a status bar... Also colored icons indicating new comment/attachemnt/property change of an issues would be helpful
* I suggest you split your application in two : a lib handling the protocol and data representation + providing a set of widgets (no dialogs!), which could later be used to create plugins bringing WebIssues support in other apps such as IDEs, and a wrapper application which would link to it and organize widgets into a consistent UI. (I'm really interested in making a WebIssues plugin for Edyuk :) )

OK, I see. It may be a problem with cmake indeed. Can you email me the generated makefiles? Maybe I'll be able to find a solution / workaround.

The idea of highlighting new issues, comments etc. is very good, I will add it to my roadmap.

I also like the idea of splitting the application. It's actually quite easy as the code is already separated. Of course there are some restrictions in library code like binary compatibility and not using global variables, but this is doable, I will consider it.

Thanks for your comments. I invite you to the WebIssues forums (http://webissues.mimec.org/forum).