Edyuk : fully-featured, highly flexible and free cross-platform IDE

Hi,

I'm proud to announce you the release of Edyuk 0.7.0. The sources are available on the SVN trunk and as packages. Note that this release is not fully stable yet but brings lots of nice features :

• Class browsing (much faster than existing solutions and without external dependency)
• Debugging
• Compilation
• A very good project manager, which for example, handles subdirs, file inclusion, complex scope constructs and is not confused when it encounters functions or operators others than = an += in project files
• A powerful text editing framework with syntax highlighting, auto indenting, parenthesis matching, text folding, and all this through generic XML definitions
• Designer integration
• Assistant integration
• Widget dedicated to .qrc files editing
• A plugin-based architecture which allow a nearly infinite extension of Edyuk features
• A perspective sytem and a modular GUI which allows high flexibility
• and more...

The "MOST WANTED" feature, i.e. code completion is not available yet but will be soon.

More than 570 persons have downloaded Edyuk 0.6.0-b, I admit this looks a bit small compared to downloads count of QDevelop but yet it shows some interest and makes me happy. I hope you'll like this new version.

If you feel like testing it please feed me back fast so that I can fix any bug you might encounter before I release Edyuk 0.7.0 as a "stable" package.

Thanks to all the people that already tested Edyuk, to you that took some time to read this announcement and, in advance, to those who will test the new version and feed me back! :)

Where can we get it?

Quote:

---

Originally Posted by ksqt

Where can we get it?

---

At Sourceforge

You can find the link at Edyuk's homepage

Or SVN: svn checkout https://svn.sourceforge.net/svnroot/edyuk

Quote:

---

Originally Posted by grosem

You can find the link at Edyuk's homepage

---

Unfortunately Berlios, which hosts Edyuk homepage seems to be down, use Sourceforge link directly instead...

Edyuk 0.7.0 STABLE packages are now available on Sourceforge.net
They feature lots of bug fixes and some very nice new features, especially concerning debugging.

Hello FMC,
I'm trying out Edyuk (thanks) but I've come across a problem.
I'm tring to add some includes and libraries to a project using the project options
dialog but this dialog crashes when using the Compilation tab.
http://www.ynk01.dial.pipex.com/edyuk.jpg
When attempting to add for example an include path - if you press CANCEL or OK on the
popup entry or File Dialog box then the program crashes fatally.
The little buttons are also missing their graphics/text

I built the program on Fedora Core 6 Linux using ./build and running the edyuk script.
Qt version is 4.2.1

Apart from that so far very good!

Quote:

---

Originally Posted by guestgulkan

I'm tring to add some includes and libraries to a project using the project options
dialog but this dialog crashes when using the Compilation tab.
http://www.ynk01.dial.pipex.com/edyuk.jpg
When attempting to add for example an include path - if you press CANCEL or OK on the
popup entry or File Dialog box then the program crashes fatally.
The little buttons are also missing their graphics/text

---

I'll try to fix that soon... Keep an eye on the SVN trunk.

Quote:

---

Originally Posted by guestgulkan

I built the program on Fedora Core 6 Linux using ./build and running the edyuk script.
Qt version is 4.2.1

Apart from that so far very good!

---

I'm glad to see that you like Edyuk!

Hi all,

Less than 3 weeks after its release, Edyuk 0.7.0 has already reached more than 400 downloads. As I've been fed back, I was able to fix bugs and add many usability enhancements. Thus Edyuk 0.8.0 is coming soon. If you can't wait to test the code completion and all the new features, check out the SVN trunk : http://sourceforge.net/svn/?group_id=168260

Hoping you'll like it! :)

hi, i downloaded svn version. but i didn't compile.
i received this error:
$ sh build
edyuk.pro:7: Unknown test function: warning
edyuk.pro:9: Unknown test function: warning
install.pri:78: Unknown test function: for
install.pri:135: Unknown test function: for
cd src/lib && make -f Makefile
make[1]:`/home/gilan/edyuk/trunk/src/lib' dizinine giriliyor
/usr/qt/3/bin/uic ui/aboutdialog.ui -o ../tmp/ui/aboutdialog.h
uic: File generated with too recent version of Qt Designer (4.0 vs. 3.3.7)
make[1]: *** [../tmp/ui/aboutdialog.h] Hata 1
make[1]: `/home/gilan/edyuk/trunk/src/lib' dizininden çıkılıyor
make: *** [sub-src-lib] Hata 2


i have 2 qt version. qt3 and qt 4.2.2
i tried also qmake-qt4. same error.

Quote:

---

Originally Posted by nimes

hi, i downloaded svn version. but i didn't compile.
i received this error:
$ sh build
edyuk.pro:7: Unknown test function: warning
edyuk.pro:9: Unknown test function: warning
install.pri:78: Unknown test function: for
install.pri:135: Unknown test function: for
cd src/lib && make -f Makefile
make[1]:`/home/gilan/edyuk/trunk/src/lib' dizinine giriliyor
/usr/qt/3/bin/uic ui/aboutdialog.ui -o ../tmp/ui/aboutdialog.h
uic: File generated with too recent version of Qt Designer (4.0 vs. 3.3.7)
make[1]: *** [../tmp/ui/aboutdialog.h] Hata 1
make[1]: `/home/gilan/edyuk/trunk/src/lib' dizininden çıkılıyor
make: *** [sub-src-lib] Hata 2


i have 2 qt version. qt3 and qt 4.2.2
i tried also qmake-qt4. same error.

---

The miscompilation is obviously related to your system's configuration... You have to change your environment variables so that qmake, uic, rcc and moc from Qt4 will be used instead of their Qt3 equivalents... Edyuk will compile with Qt4 only (needs Qt 4.1 or newer). Even if you use a symlink or script to Qt4's qmake it won't work properly if $QTDIR does not come first into your $PATH because moc/uic/.. used will be those of Qt 3. To achieve that you have to add the following lines to your ~/.bash_profile :

Quote:

---

# note that this path is generic... replace it with the one used in your system...
QTDIR=/usr/local/Trolltech/Qt
PATH=$QTDIR/bin:$PATH

---

Hoping I'm clear enough... ;)

sorry, i don't understand. my qt directory:
/usr/qt/3/ and /usr/qt/4/

how to configure .bash.profile ??

Quote:

---

Originally Posted by nimes

sorry, i don't understand. my qt directory:
/usr/qt/3/ and /usr/qt/4/

how to configure .bash.profile ??

---

If you want to compile Qt 4 applications there are several ways :

• If you want to be able to compile both Qt 3 (so KDE) and Qt 4 based apps the best way is probably to use scripts to setup env vars in your shell session. In this case, each time you will need to use Qt 4 instead of Qt 3 you will be forced to run a shell script by hand.
• If you're only interested in Qt 4 it is probably easier to embed these settings in ~/.bash_profile (if you're using bash as a shell, overwise you'll have to find what file is used by your shell to store such a configuration...) Note that such an embedding require your session to be restarted and even in some cases a reboot

In your case the script will look like this :

Code:

---

#! /bin/sh
# This header is useless when embedding in ~/.bash_profile
 
export QTDIR=/usr/qt/4
export PATH=$QTDIR/bin:$PATH

---

Once your environment is set up, compilation should work smoothly. :)

Edyuk 0.8.0-rc1 is out.

It finally brings code completion in Edyuk and features many usability improvements and bug fixes. The completion engine uses an hybrid solution combining a custom lexer/parser which allows completion of classes provided by the openned projects (without any dependency) and a ctags backend which allows completion of Qt 4 classes. If ctags is not found the completion will work but without support of Qt 4 classes. You can get packages from Sf.net or browse the SVN trunk.

Also note that Edyuk's homepage has moved to a new host (and changed its look at the same occasion : feedback would be very appreciated).

Hoping you'll like it. :)

Spring cleanup has been done in the trunk and, after proper reorganization, I'm back on hard work. If you happen to take a look at the, relocated, trunk, the code completion will probably look pleasant :

• It no longer needs ctags to complete Qt types
• real huge speed improvements have been done (average time taken to display entries, with recursive typing and entries filtering, on my 6years old box : 40ms :cool:)
• Many quirks have been fixed which provide a better accuracy
• Typedefs are now handled properly

Besides, other bug fixes and improvements have been done in editing, project management and configuration dialogs.

A new rc should be issued soon (as soon as i'll have fixed all the missing features in the new project management module actually ;))

PS :

• the new trunk URL for SVN checkout is : http://edyuk.svn.sourceforge.net/svnroot/edyuk/trunk
• Edyuk's homepage now provides RSS newfeeds

How can I change the editor font size?

Regards, Burgpflanze

Quote:

---

Originally Posted by Burgpflanze

How can I change the editor font size?

---

:oI'm afraid there is no UI for editor configuration yet (though I'm working on it) and this setting can't be changed in any other way than modifying the source file where the default font settings are decided : /path/to/edyuk/trunk/3rdparty/qcodeedit/lib/editor/qplaintextedit.cpp line 125 or 127, according to your platform...

Hope this helps. :)

A beta package of Edyuk's next version has just been released. It is actually a snapshot of the soon-to-be-released 0.9.0 version.

What's new :

• Code completion, it's not real new but SO fast that it cannot be compared with what it used to be (and it can neither be compared with existing code completions AFAIK :))
• A number of slight internal modifications which result in easier plugins writing and more consistent UI. The most important example is the "manager" dock which takes care of a project model and a code model (class browser) in a generic way. As a consequence the project explorer and class browser are now reachable from the Designer perspective which used to be impossible
• Many broken features have been implemented (create new file from project tree, add file to project, ..)
• A new template manager has been added which makes it much easier to add templates (INI files are used as templates definitions)
• A set of brand new dialogs, much more user-friendly, replaced old ones (configuration, project options, creation of new file, ...)
• A the "manager" dock now has a much nicer look thanks to the use of a QComboBox instead of tabs

And what remains the same (apart from bugfixes ;)):

• perspective-based GUI
• flawless qmake projects parsing/saving
• powerful and flexible editing framework
• Designer integration
• Assistant integration
• QRC editing facilities
• class browsing
• compilation (requires gcc / mingw)
• graphical debugging (requires gdb)
• dynamic shortcut management
• run-time translation
• ...

Looking forward to get some feedback so as to polish the final 0.9.0 release. :)

I tried downloading 0.9.0beta, but when I ran the build.bat program on windows it seemed to go into an infinite recursion.

Edyuk crashes when I load my project in v0.8.0, so I was hoping this problem would be resolved in the latest update.

I'm interested in using Edyuk... but first step is of course to get it installed and working properly.

Quote:

---

Originally Posted by magland

I tried downloading 0.9.0beta, but when I ran the build.bat program on windows it seemed to go into an infinite recursion.

Edyuk crashes when I load my project in v0.8.0, so I was hoping this problem would be resolved in the latest update.

I'm interested in using Edyuk... but first step is of course to get it installed and working properly.

---

The batch file was originally added to workaround a bug/missing feature in Window$ ME which prevented proper compilation of subdirs project. If you are not using this version of Windows you should try the "regular" commands :

Code:

---

$ qmake
$ mingw32-make

---

Anyway I checked the content of the build.bat file and I didn't see anything that might cause kinda infinite recursion... Maybe you could give me more details.:confused:

OK thanks. It's possible that it wasn't actually an infinite recursion, but just taking a long time, and I wan't seeing the compilation details.

Anyway now I get the following compilation error: (see end of message). Also, I had to add "#include <QDebug>" to a couple of the .cpp files... qgenericlanguagefactory.cpp, qshortcutmanager.cpp.

Any ideas? I'm using Windows XP SP2, GNU Make 3.80, Qt 4.2.1

....................
....................
qmakemodel\qmakeproject.cpp:507: warning: function 'void QMakeProject::options()
' is defined after prior declaration as dllimport: attribute ignored
qmakemodel\qmakeproject.cpp: At global scope:
qmakemodel\qmakeproject.cpp:513: warning: function 'virtual void QMakeProject::w
rite(QTextStream&, QString, QProjectNode*)' is defined after prior declaration a
s dllimport: attribute ignored
qmakemodel\qmakeproject.cpp: In member function `virtual void QMakeProject::setu
pMenu(QMenu*)':
qmakemodel\qmakeproject.cpp:553: warning: function 'virtual void QMakeProject::s
etupMenu(QMenu*)' is defined after prior declaration as dllimport: attribute ign
ored
qmakemodel\qmakeproject.cpp: In constructor `QMakeProjectPrivate::QMakeProjectPr
ivate()':
qmakemodel\qmakeproject.cpp:612: warning: function 'QMakeProjectPrivate::QMakePr
ojectPrivate()' is defined after prior declaration as dllimport: attribute ignor
ed
qmakemodel\qmakeproject.cpp: In constructor `QMakeProjectPrivate::QMakeProjectPr
ivate()':
qmakemodel\qmakeproject.cpp:615: internal compiler error: in rest_of_handle_fina
l, at toplev.c:2064
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
mingw32-make[2]: *** [..\tmp-default-4.2.1-\obj\debug\qmakeproject.o] Error 1
mingw32-make[2]: Leaving directory `C:/cstuff/edyuk-0.9.0-beta/src/default'
mingw32-make[1]: *** [debug] Error 2
mingw32-make[1]: Leaving directory `C:/cstuff/edyuk-0.9.0-beta/src/default'
mingw32-make: *** [sub-src_default-make_default] Error 2

Quote:

---

Originally Posted by magland

Anyway now I get the following compilation error: (see end of message). Also, I had to add "#include <QDebug>" to a couple of the .cpp files... qgenericlanguagefactory.cpp, qshortcutmanager.cpp.

Any ideas? I'm using Windows XP SP2, GNU Make 3.80, Qt 4.2.1

....................
....................
qmakemodel\qmakeproject.cpp:507: warning: function 'void QMakeProject::options()
' is defined after prior declaration as dllimport: attribute ignored
qmakemodel\qmakeproject.cpp: At global scope:
qmakemodel\qmakeproject.cpp:513: warning: function 'virtual void QMakeProject::w
rite(QTextStream&, QString, QProjectNode*)' is defined after prior declaration a
s dllimport: attribute ignored
qmakemodel\qmakeproject.cpp: In member function `virtual void QMakeProject::setu
pMenu(QMenu*)':
qmakemodel\qmakeproject.cpp:553: warning: function 'virtual void QMakeProject::s
etupMenu(QMenu*)' is defined after prior declaration as dllimport: attribute ign
ored
qmakemodel\qmakeproject.cpp: In constructor `QMakeProjectPrivate::QMakeProjectPr
ivate()':
qmakemodel\qmakeproject.cpp:612: warning: function 'QMakeProjectPrivate::QMakePr
ojectPrivate()' is defined after prior declaration as dllimport: attribute ignor
ed
qmakemodel\qmakeproject.cpp: In constructor `QMakeProjectPrivate::QMakeProjectPr
ivate()':
qmakemodel\qmakeproject.cpp:615: internal compiler error: in rest_of_handle_fina
l, at toplev.c:2064
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
mingw32-make[2]: *** [..\tmp-default-4.2.1-\obj\debug\qmakeproject.o] Error 1
mingw32-make[2]: Leaving directory `C:/cstuff/edyuk-0.9.0-beta/src/default'
mingw32-make[1]: *** [debug] Error 2
mingw32-make[1]: Leaving directory `C:/cstuff/edyuk-0.9.0-beta/src/default'
mingw32-make: *** [sub-src_default-make_default] Error 2

---

:o Not enough testing on Windows (none actually because I don't have any available windows PC to perform them). Sorry... This is actually very easy to fix :

src/default/qmakemodel/qmake.h :

Quote:

---

#if defined(_QMAKEMODEL_BUILD_)

---

should be :

Quote:

---

#if defined(_QMAKE_MODEL_BUILD_)

---

This should solve your troubles building the plugins.

Thanks for reporting this. I'll commit appropriate changes on SVN soon and advance the release of the rc1 to prevent too many people from facing similar troubles.:)

Quote:

---

Originally Posted by fullmetalcoder

This should solve your troubles building the plugins.

---

Yes, thanks.

Now I get the following error (see below). Probably some trivial things, so perhaps we should take this debugging off the forum for now? (Jeremy.Magland at gmail.com)

....................................
Creating library file: ..\..\plugins\libdefault_debug.a
./..\tmp-default-4.2.1-\obj\debug\core.o(.text+0x26cd): In function `ZN11Default
Core15parseCompileLogERK7QString':
C:/cstuff/edyuk-0.9.0-beta/src/default/core.cpp:373: undefined reference to `Edy
uk::makeAbsolute(QString const&, QString const&)'
./..\tmp-default-4.2.1-\obj\debug\core.o(.text$_ZN18CppCallbackHandler5ev entE7QS
tring11QStringList[CppCallbackHandler::event(QString, QStringList)]+0x13e2): In
function `ZN11DefaultCoreD0Ev':
C:/cstuff/edyuk-0.9.0-beta/src/default/core.cpp:223: undefined reference to `Edy
ukTemplateManager::create(QString const&, QString const&, QStringList*, QHash<QS
tring, QString> const*) const'
./..\tmp-default-4.2.1-\obj\debug\core.o(.text$_ZN18CppCallbackHandler5ev entE7QS
tring11QStringList[CppCallbackHandler::event(QString, QStringList)]+0x1425): In
function `ZNK11DefaultCore4iconEv':
C:/cstuff/edyuk-0.9.0-beta/src/default/core.cpp:226: undefined reference to `Edy
ukTemplateManager::create(QString const&, QString const&, QStringList*, QHash<QS
tring, QString> const*) const'
./..\tmp-default-4.2.1-\obj\debug\qrcedit.o(.text+0x616a): In function `ZN7QRCEd
it7addFileEv':
C:/cstuff/edyuk-0.9.0-beta/src/default/qrcedit.cpp:378: undefined reference to `
Edyuk::makeRelative(QString const&, QString const&)'
./..\tmp-default-4.2.1-\obj\debug\qrcedit.o(.text+0x76bb): In function `ZN7QRCEd
it11fileChangedEP15QTreeWidgetItemS1_':
C:/cstuff/edyuk-0.9.0-beta/src/default/qrcedit.cpp:459: undefined reference to `
-- More (7%) --

Quote:

---

Originally Posted by magland

Now I get the following error (see below). Probably some trivial things, so perhaps we should take this debugging off the forum for now? (Jeremy.Magland at gmail.com)

---

Sure, I've send you a solution to this by e-mail and will issue another beta really soon (as soon as you report proper compilation actually ;))

For the others, here comes the solution : the EDYUK_EXPORT macro needs to be added so that several classes/functions get exported properly under windows :

src/lib/edyuktemplatemanager.h :

Code:

---

class EDYUK_EXPORT EdyukTemplateManager

---

src/lib/edyuk.h :

Code:

---

EDYUK_EXPORT QString settingsPath();
EDYUK_EXPORT QString makeAbsolute(const QString& rel, const QString& abs); 
EDYUK_EXPORT QString makeRelative(const QString& src, const QString& ref);

---

We worked through the Windows-specific installation problems offline, and everything looks very nice indeed.

Windows users should wait for the corrected version to be released since there were a bunch of small adjustments.

... but I certainly like what I see... thanks for the help!

magland

Here we go! Edyuk 0.9.0 had indeed many compilation problems under Window$ but, thanks to the perseverant feedback of Jeremy Magland, I've been able to fix them and also some potential crash issues.

A second beta is thus available which now feature real "platform independence" and several minor improvements! Enjoy! :)

https://sourceforge.net/project/show...ease_id=499004

It's still impossible to compile on FreeBSD 6.1
Reason:
gdbthread.cpp : line with

#ifdef OS_LINUX

should be

#ifdef OS_UNIX (I suppose)
i
I deleted this line wih it's corresponding #endif and the compilation goes well until the end. Sadly, when running edyuk after the 'make install', I get a core dump just a while after the splash screen appears :/

Hi
I compiled edyuk on windows but with the visual studio compiler and had some compilation problems, too.
After finding some work arounds (which I may post soon after some more tests) the compilation finishes well.
But when I try to start the program I face what I believe is the same problem hoborg has: Right after the splash screen appears the program terminates.

This only happens if the "default.*" library files are in the "\plugins" directory. Edyuk starts when there are no plugin files.

QtmPlayer

Thanks for your suggestion, QTmplayer :)
I deleted the .so file from plugins subdirectory and now edyuk starts.
I still can't run it as a normal user - I had to do 'make install' as root and only root can start the environment (when I try as an user, nothing happens, even the splash screen doesn't appear).

------
edit:

Well, I was celebrating too early. The environment launches well but after I select 'Open' it goes down with a core dump (Illegal instruction).

I must correct my old statement:
This crash occurs only when I build the \lib, \exec and \default one after another and then run the executable.

When I do all these steps together by simply using the .pro file in the main directory it works perfectly after the workarounds have been installed.

I listed all workarounds in the "msvc_fix.txt" file attached to the post.

Hope this helps.

QtmPlayer

PS: Now Edyuk runs I admit that it's really nice work ;) :D

Quote:

---

Originally Posted by QTmplayer

I must correct my old statement:
This crash occurs only when I build the \lib, \exec and \default one after another and then run the executable.

When I do all these steps together by simply using the .pro file in the main directory it works perfectly after the workarounds have been installed.

---

Sounds weird but my poor knowledge of MSVC won't help here... You might consider reporting the bug to Trolltech...

Quote:

---

Originally Posted by QTmplayer

I listed all workarounds in the "msvc_fix.txt" file attached to the post.

Hope this helps.

---

This surely does! I'll fix the source as soon as possible. :)

Quote:

---

Originally Posted by QTmplayer

PS: Now Edyuk runs I admit that it's really nice work ;) :D

---

I'm quite happy to see that my work satisfy you. Hope you'll have fun :D

Quote:

---

The environment launches well but after I select 'Open' it goes down with a core dump (Illegal instruction).

---

This is weird but I encountered this issue already under Pardus 2007. For an unknown reason the use of QCompleter (by QFileDialog, among others) seems to cause a crash... I admit I don't know how to fix this... Maybe you can confirm this guess by sending me a gdb backtrace. If it really is what I suggested, I shall report a bug to Trolltech, otherwise I'll try to fix this by hand.

I geting this error :

C:\edyuk-0.8.0-rc1\src\exec>mingw32-make
mingw32-make -f Makefile.Release
mingw32-make[1]: Entering directory `C:/edyuk-0.8.0-rc1/src/exec'
windres -i edyuk.rc -o ..\tmp\obj\exec\release\edyuk_res.o --include-dir=.
cc1: unrecognized option `-E'
windres: no resources
mingw32-make[1]: *** [..\tmp\obj\exec\release\edyuk_res.o] Error 1
mingw32-make[1]: Leaving directory `C:/edyuk-0.8.0-rc1/src/exec'
mingw32-make: *** [release] Error 2

Please help ...

Quote:

---

Originally Posted by tebessum

I geting this error :

C:\edyuk-0.8.0-rc1\src\exec>mingw32-make
mingw32-make -f Makefile.Release
mingw32-make[1]: Entering directory `C:/edyuk-0.8.0-rc1/src/exec'
windres -i edyuk.rc -o ..\tmp\obj\exec\release\edyuk_res.o --include-dir=.
cc1: unrecognized option `-E'
windres: no resources
mingw32-make[1]: *** [..\tmp\obj\exec\release\edyuk_res.o] Error 1
mingw32-make[1]: Leaving directory `C:/edyuk-0.8.0-rc1/src/exec'
mingw32-make: *** [release] Error 2

Please help ...

---

Compilation failed for 0.8.0-rc1 under Windows but if I remember well the error reported was not the one you encounter... I suggest you get Edyuk 0.9.0-beta2 instead (which is know to compile under Windows) or possibly the SVN trunk if you want to try latest enhancements and check your version of MinGW...

I tried compiling and running eduyk 0.9.0-beta2 on my Gentoo 64 box and find it just crashes on startup.

Here is the debug output

Quote:

---

rebuilding recent files/projects menu...
cleaned previous data...
filled with new data...
Initializing shortcuts...
Initializing plugins...
system plugins path : /home/jeremy/src/edyuk-0.9.0-beta2/plugins/

file : /home/jeremy/src/edyuk-0.9.0-beta2/plugins/libdefault_debug.so
Plugin root created
PluginInterface created : 5615664
CorePlugin created
Segmentation fault

---

And the line causing the segmentation fault is line 58 of qdesignerperspective.cpp, which looks like this

Quote:

---

pDesigner = QDesignerComponents::createFormEditor(this);

---

This one whistles off into the internals of QT and I cannot track it any further.
I am running QT 4.2.3 with 3.4.5.

Any ideas anyone?

Quote:

---

Originally Posted by Usability

This one whistles off into the internals of Qt and I cannot track it any further.
I am running Qt 4.2.3 with 3.4.5.

---

This one is mandatory for Designer integration to work... If Qt Designer runs fine under your box it shouldn't cause any trouble but as it relies on private headers we never know... Try replacing all the private headers in src/default/designer (those ending in *_p.h) by their equivalents available in your Qt sources, recompile and see if it works better....

Did that, and it recompiled a few things but it still crashed on invocation.

I just tried the tool on another 64 bit Gentoo machine, and here it works. The main differences between the two are:
gcc version 4.1.1 on the working machine
gcc version 3.4.5 on the broken one.

QT Designer works fine on both. The GUI looks good, you are too hard on yourself.

My top 3 enhancement requests are:

1. Double clicking a method in the class browser should go to the code for the method, currently all the methods open the header file instead. The class name its self could do that.
2. A button to toggle between .h and .cpp file for the same class. I am always going back and forth between these two.
3. Some obvious way of adding a breakpoint. Am I missing something here?

Anyway, I think its an encouraging project. The world really needs an IDE for debugging QT4 programs.

QDevelop locks up on both my Gentoo machines, so you are already ahead there :)

Quote:

---

Originally Posted by Usability

Did that, and it recompiled a few things but it still crashed on invocation.

I just tried the tool on another 64 bit Gentoo machine, and here it works. The main differences between the two are:
gcc version 4.1.1 on the working machine
gcc version 3.4.5 on the broken one.

QT Designer works fine on both.

---

Sounds weird. I'm not very familiar with 64bit machines and tracking GCC errors is too hard for me so I guess there's no way I can fix that... If GCC 4.x works fine on some platforms where 3.x fails I'll have to mention it in the readme.

Quote:

---

The GUI looks good, you are too hard on yourself.

---

I must be missing something here... :confused:

Quote:

---

My top 3 enhancement requests are:

1. Double clicking a method in the class browser should go to the code for the method, currently all the methods open the header file instead. The class name its self could do that.
2. A button to toggle between .h and .cpp file for the same class. I am always going back and forth between these two.
3. Some obvious way of adding a breakpoint. Am I missing something here?

Anyway, I think its an encouraging project. The world really needs an IDE for debugging QT4 programs.

QDevelop locks up on both my Gentoo machines, so you are already ahead there :)

---

1. I've thought about that but didn't find time to do it in a proper way yet. It should be added in a feature release but don't ask me when, I'm rather busy ATM.
2. I was thinking about a context menu for class names to open either header or source. If that's not what you mean could you precise your button idea?
3. I admit Edyuk lacks documentation and breakpoints are not that obvious... :o

There are currently two ways to set breakpoints :

• graphically by right clicking on the leftmost part of the editor (on concerned line) and toggling the breakpoint entry
• by hand through the "custom command" entry in Debug menu and typing the corresponding command

Note : the first method currently REQUIRES breakpoints to be set BEFORE starting debugging.

I'm thinking about improving this breakpoint issue (by adding a shortcut, among other things) but, once again, I lack time... Anyway, if I'm lucky and fast enough these three might find their way in the next upcoming release which will be issued before the contest ends.:)

The long-awaited 0.9.0 version of Edyuk has finally been released.

It features many bug fixes and including miscompilation on certain platforms. The most noticeable changes/adds are:

• brand new (Unix) build script with auto-detection of qmake, Qt version check (Qt 4.2 or higher now mandatory) and compile output formatting
• Drag and drop in the workspace. Tabs are freely movable within the tab bar to let you reorder opened files on the fly. Dropping a file list (dragged from Konqui for instance) cause them to be opened
• improved completion (yet again! it's getting near to perfection :)). It is now possible to trigger it at will through an action (default shortcut : Ctrl + Space)
• changed the look of some dialogs and much improved configuration

The next version (1.0) is already being worked on and will bring many changes concerning the editing framework :

• A brand new language definition format, much more flexible and, I hope, resulting in faster highlighting
• A new way of handling breakpoints (which, because of internal deps to 1.0 series, could not be added to this release) that will allow an action to be added (and thus a shortcut) but also breakpoints to be set while debugging already started :)
• Improvements of class browsing as asked by Usability
• And many other niceties :D

cheers

fmc

Edyuk 0.9.1 has just been released. It is mainly a bugfix release which, above all, fixes compilation under Windows.

https://sourceforge.net/project/show...ease_id=512221

Hi, I'm trying to build Edyuk 0.9.1 but I'm getting the following errors:

Quote:

---

Processing form ui/createnewdialog.ui
Compiling ../../3rdparty/qpool/qpool.cpp
../../3rdparty/qpool/qpool.cpp:105: error: cast from 'QPool*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:106: error: cast from 'char*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:106: error: cast from 'char*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:106: warning: format '%x' expects type 'unsigned int', but argument 5 has type 'long unsigned int'
../../3rdparty/qpool/qpool.cpp:223: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:223: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:223: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:223: warning: format '%x' expects type 'unsigned int', but argument 4 has type 'long unsigned int'
../../3rdparty/qpool/qpool.cpp:223: warning: format '%i' expects type 'int', but argument 5 has type 'size_t'
../../3rdparty/qpool/qpool.cpp:248: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:248: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:248: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:249: warning: format '%x' expects type 'unsigned int', but argument 4 has type 'long unsigned int'
../../3rdparty/qpool/qpool.cpp:249: warning: format '%i' expects type 'int', but argument 5 has type 'size_t'
../../3rdparty/qpool/qpool.cpp:249: warning: format '%x' expects type 'unsigned int', but argument 7 has type 'size_t'
../../3rdparty/qpool/qpool.cpp:249: warning: format '%x' expects type 'unsigned int', but argument 8 has type 'long unsigned int'

---

and the list of erros continues with more errors of that same kind.

Quote:

---

Originally Posted by fedcer

Hi, I'm trying to build Edyuk 0.9.1 but I'm getting the following errors:

and the list of erros continues with more errors of that same kind.

---

It looks like your compiler is very strict with casts... Apparently I forgot comment out all the qDebug() statements I put in the QPool code and your compiler complain. All you have to do is opening src/3rdparty/qpool/qpool.cpp and comment out the concerned lines... Apologies for this...:o

I am getting the following when compiling with the follow error in the following env:

windows 2000 sp4
Qt 4.3.0
C:\qtwork>mingw32-make -v
GNU Make 3.80
Copyright (C) 2002 Free Software Foundation, Inc.


C:\qtwork\edyuk-0.9.1>build
...
...
.\..\..\Qt\4.3.0\mkspecs\win32-g++" -o ..\tmp-default-4.3.0-win32\obj\release\qm
akevariable.o qmakemodel\qmakevariable.cpp
../../3rdparty/qprojectmodel/qprojectparser.h: In member function `void QProject
Parser::qt_check_for_QOBJECT_macro(const T&) const [with T = QMakeParser]':
../../../../Qt/4.3.0/include/QtCore/../../src/corelib/kernel/qobject.h:411: in
stantiated from `T qobject_cast(QObject*) [with T = QMakeParser*]'
qmakemodel\qmakevariable.cpp:654: instantiated from here
../../3rdparty/qprojectmodel/qprojectparser.h:38: error: void value not ignored
as it ought to be
mingw32-make[1]: *** [..\tmp-default-4.3.0-win32\obj\release\qmakevariable.o] Er
ror 1
mingw32-make[1]: Leaving directory `C:/qtwork/edyuk-0.9.1/src/default'
mingw32-make: *** [release] Error 2

I tried that thing on google
Re: patched!
06/01/2007, 2:28 on content: Edyuk
some little error
must be:

3dparty/qprojectmodel/qprojectparser.h:

Code:

---

#ifndef _QPROJECT_PARSER_H_
#define _QPROJECT_PARSER_H_
 
#define QT_NO_QOBJECT_CHECK 1
 
#include "qproject.h"

---

but no luck there still same error as above.

thanks.

Quote:

---

Originally Posted by srikpen

I tried that thing on google
Re: patched!
06/01/2007, 2:28 on content: Edyuk
some little error
must be:

3dparty/qprojectmodel/qprojectparser.h:

Code:

---

#ifndef _QPROJECT_PARSER_H_
#define _QPROJECT_PARSER_H_
 
#define QT_NO_QOBJECT_CHECK 1
 
#include "qproject.h"

---

but no luck there still same error as above.

thanks.

---

There are two things left to try :

• add DEFINES += QT_NO_QOBJECT_CHECK to config.pri (dirty hack)
• add Q_OBJECT to QMakeParser declaration in src/default/qmakemodel/qmakeparser.h

If it still fails please let me know. I should anyway release a newer package soon.:)

Quote:

---

Originally Posted by fullmetalcoder

It looks like your compiler is very strict with casts... Apparently I forgot comment out all the qDebug() statements I put in the QPool code and your compiler complain. All you have to do is opening src/3rdparty/qpool/qpool.cpp and comment out the concerned lines... Apologies for this...:o

---

Thanks, now it copiled fine. By the way, congratulations ! It is a very good IDE.

Quote:

---

Originally Posted by fedcer

Thanks, now it copiled fine.

---

Good news! :)

Quote:

---

Originally Posted by fedcer

By the way, congratulations ! It is a very good IDE.

---

Thanks a lot :) Such feedback is very important when I feel lost within the sources with so many things left to do and so little time to deal with them ;)

Quote:

---

Originally Posted by fullmetalcoder

There are two things left to try :

• add DEFINES += QT_NO_QOBJECT_CHECK to config.pri (dirty hack)
• add Q_OBJECT to QMakeParser declaration in src/default/qmakemodel/qmakeparser.h

If it still fails please let me know. I should anyway release a newer package soon.:)

---

Thanks a lot.

adding the Q_OBJECT solved the problem without the dirty hack you mentioned.

With support like this I don't mind being santa's elve for any testing req's on
my triple boot windows 2K, fedora 6 AMD 32-bit, 64-bit system.

How do I build this in debug mode as well, where do the logs go ??
regards
sri.

Quote:

---

Originally Posted by srikpen

adding the Q_OBJECT solved the problem without the dirty hack you mentioned.

---

This was the clean solution. I mentioned the other one as well because some people happen to be quite lazy... ;)

Quote:

---

Originally Posted by srikpen

With support like this I don't mind being santa's elve for any testing req's on
my triple boot windows 2K, fedora 6 AMD 32-bit, 64-bit system.

---

It's very kind of you :)

Quote:

---

Originally Posted by srikpen

How do I build this in debug mode as well, where do the logs go ??

---

Edit config.pri... You can basically do any find tunning you want in it since it is included by all subdirs. You'll just need to replace CONFIG += release by CONFIG += debug. There used to be a way to redirect debug output to a log file but I think I dropped it... You can anyway bring it back by editing src/lib/edyukapplication.cpp and adding appropriate code within the message handler. :)

After running edyuk-debug I am not able to find the run.log anywhere.
I have diffed the edyukappliation with it's original as below, is it some thing else I am missing?

Code:

---

C:\qtwork\edyuk-0.9.1\src\lib>diff edyukapplication.cpp edyukapplication.cpp.ORG
75c75
< static QTextStream cout(stdout), cerr(stderr), clog;
---
> //static QTextStream cout(stdout), cerr(stderr), clog;
93c93
<       clog << type[t] << msg << endl;
---
>       //clog << type[t] << msg << endl;
98c98
<               clog << "aborting..." << endl;
---
>               //clog << "aborting..." << endl;
142c142
<       clog.setDevice(pEdyukLogFile);
---
>       //clog.setDevice(pEdyukLogFile);

---

BTW the debug edyuk justs shows up in task manager and no GUI comes up, then terminates after a few seconds. Any Idea?
Just set the debug options as you mentioned i.e.:
CONFIG += debug and
add Q_OBJECT to QMakeParser declaration in src/default/qmakemodel/qmakeparser.h

Quote:

---

Originally Posted by srikpen

After running edyuk-debug I am not able to find the run.log anywhere.
I have diffed the edyukappliation with it's original as below, is it some thing else I am missing?

Code:

---

C:\qtwork\edyuk-0.9.1\src\lib>diff edyukapplication.cpp edyukapplication.cpp.ORG
75c75
< static QTextStream cout(stdout), cerr(stderr), clog;
---
> //static QTextStream cout(stdout), cerr(stderr), clog;
93c93
<       clog << type[t] << msg << endl;
---
>       //clog << type[t] << msg << endl;
98c98
<               clog << "aborting..." << endl;
---
>               //clog << "aborting..." << endl;
142c142
<       clog.setDevice(pEdyukLogFile);
---
>       //clog.setDevice(pEdyukLogFile);

---

---

The log file should be placed in Edyuk::settingsPath() which should expand to ~/.Edyuk-$version$/ so in your case ~/.Edyuk-0.9.1 (or ~/.Edyuk-1.0.0-alpha in case you use the SVN trunk)

Quote:

---

Originally Posted by srikpen

BTW the debug edyuk justs shows up in task manager and no GUI comes up, then terminates after a few seconds. Any Idea?

---

It might come from an assert failure... You know Qt uses a lot of Q_ASSERT() macro everywhere and it can result in very different behaviours of debug and release builds... The best way to figure out what's wrong is to run on command line or under gdb. This way you'll know why the debug build fails and we'll be able to fix this :)

Sorry for bothering you much. But I am not a windows guy.
with gdb I'm comfortable on linux.

I feel impaired with the windows thing.
You have any idea how I can get started debugging this with proper tools on windows.
I don't want to start configuring tools to get running, some quicky debugger, ctags(or find, grep) kind of thing on windows?

Just wanted to know, I see you're also not a windows guy but thought you might have some idea.

thanks
sri.

Quote:

---

Originally Posted by srikpen

Sorry for bothering you much. But I am not a windows guy.

---

I'm a little lost here? Do you mean you're testing under Window$ and facing troubles there that you don't know how to handle?

Quote:

---

Originally Posted by srikpen

You have any idea how I can get started debugging this with proper tools on windows.
I don't want to start configuring tools to get running, some quicky debugger, ctags(or find, grep) kind of thing on windows?

Just wanted to know, I see you're also not a windows guy but thought you might have some idea.

---

Sure! gdb is also available under Window$. You don't need ctags to use Edyuk code completion but I think it is available for Win as well. As for grep/find and other *nix tools I don't think there is any equivalent but you can always have a look at Cygwin...

Hope this helps :)