wwWidgets

[wysota]

Delete the line the compiler is complaining about or compile the library in release mode, the missing object reveals itself only in debug mode which you probably don't need anyway.

Oh...you're using Windows... so maybe you do need it, that's one of the downsides of using Qt and Windows together

[AD]

Thank you for this library!

I have finded out a small errors. There are what does mean the word stylable , acompaniating ? Is the second word mean accompany?


I told about this library at the russian crossplatform forum and allocated description on there. Don't you mind?

crossplatform
wwWidgets russian description

Thanks!

[wysota]

Thank you for this library!

You're welcome.

There are what does mean the word stylable ,

Something that can be styled (its style (as in style-sheets or QStyle) can be manipulated)

acompaniating ? Is the second word mean accompany?

bundled with, coming together with.

I told about this library at the russian crossplatform forum and allocated description on there. Don't you mind?

No, of course not, be my guest.

[AD]

You're welcome.

Something that can be styled (its style (as in style-sheets or QStyle) can be manipulated)

bundled with, coming together with.

Thanks!
Accompany is the synonym bundle with

[wysota]

wwWidgets version 0.9.6 has been released. It's mostly bugfix release that hopefully improves the process of installation of the widget set. Expect 0.9.7 to be released soon once I get some feedback about the changes. So in other words - if you have time and will, please test the library and post your comments.

[pospiech]

Just out of interest, did you get one of my private messages or email?
...
EDIT: Thank you for including the debug build on windows, I will test it the next days.

[wysota]

I did get some messages from you but I don't know if I got all of them. I sent you a reply or two but I don't know if they reached you.

Cheers!

[pospiech]

It does not compile (nothing changed to the make files, just qmake + nmake):

link /LIBPATH:"c:\Programme\Qt\msvc\4.5.1\lib" /NOLOGO /INCREMENTAL:NO /
LTCG /DLL /MANIFEST /MANIFESTFILE:"release\wwwidgetsplugin.intermediate .manifest
" /OUT:release\wwwidgetsplugin.dll @C:\DOKUME~1\Matthias\LOKALE~1\Temp\nm4ED.tmp

LINK : fatal error LNK1181: Eingabedatei "wwwidgets4d.lib" kann nicht geöffnet w
erden.
NMAKE : fatal error U1077: ""C:\Programme\Microsoft Visual Studio 8\VC\BIN\link.
EXE"": Rückgabe-Code "0x49d"
Stop.
NMAKE : fatal error U1077: ""C:\Programme\Microsoft Visual Studio 8\VC\BIN\nmake
.exe"": Rückgabe-Code "0x2"
Stop.
NMAKE : fatal error U1077: "cd": Rückgabe-Code "0x2"
Stop.

so, he does not find 'wwwidgets4d.lib'


which indeed is inpossible, since in debug folder the lib is called 'wwwidgets4.lib'

[janus]

Hi, I get a similar error with XP/MinGW

C:\MinGW\bin\..\lib\gcc\mingw32\3.4.2\..\..\..\..\mingw32\bin\ld.exe: cannot find -lwwwidgets4d
collect2: ld returned 1 exit status
mingw32-make[2]: *** [release\wwwidgetsplugin.dll] Error 1
mingw32-make[2]: Leaving directory `C:/wwWidgets-0.9.6/wwWidgets/plugin'
mingw32-make[1]: *** [release] Error 2
mingw32-make[1]: Leaving directory `C:/wwWidgets-0.9.6/wwWidgets/plugin'
mingw32-make: *** [sub-plugin-sub_Release_ordered] Error 2

C:\MinGW\bin\..\lib\gcc\mingw32\3.4.2\..\..\..\..\mingw32\bin\ld.exe: cannot find -lwwwidgets4d
collect2: ld returned 1 exit status
mingw32-make[2]: *** [release\wwwidgetsplugin.dll] Error 1
mingw32-make[2]: Leaving directory `C:/wwWidgets-0.9.6/wwWidgets/plugin'
mingw32-make[1]: *** [release] Error 2
mingw32-make[1]: Leaving directory `C:/wwWidgets-0.9.6/wwWidgets/plugin'
mingw32-make: *** [sub-plugin-sub_Release_ordered] Error 2

To copy to clipboard, switch view to plain text mode 

[wysota]

Compile the plugin in release mode only. What's the dll called, by the way?

[janus]

Thats what I did: "make release"

After removing

-L../widgets/debug -lwwwidgets4d

-L../widgets/debug -lwwwidgets4d

To copy to clipboard, switch view to plain text mode 

from the makefile it compiled. I didn't put it there

[pospiech]

The widgets.pro skript is missing the target for the debug mode. Adding the following fixed it for me:

win32 {
    CONFIG(release, debug|release): TARGET = wwwidgets4
    CONFIG(debug, debug|release):   TARGET = wwwidgets4d
}

win32 {
    CONFIG(release, debug|release): TARGET = wwwidgets4
    CONFIG(debug, debug|release):   TARGET = wwwidgets4d
}

To copy to clipboard, switch view to plain text mode 

[wysota]

I changed "win32" to "unix" in line 36 of the file to test it on unix and forgot to switch it back :-) If you change "unix" to "win32" everything should work.

[bunjee]

Great tool,

Anyone knows about this:
http://www.qtcentre.org/forum/f-qt-p...ets-21269.html

Thanks.

[janus]

wwwidgets 0.9.6

I am using uiloader and suddenly (did not happen before 0.9.6) the wwwidgets menu appears in my app. But in this one I do not even use wwwidgets. I guess uiloader scanns the designer plugin path and initializes wwwidgets menu if wwwidgets plugin is found regardless of weather it is used or not. I have seen that you have put the menu initialization in wwwidgets.cpp instead of qwwtaskpanelinterface. Is this behaviour intended?

[wysota]

No, it's intended to popup in Designer and Creator You can disable it in wwwidgets.cpp.

[pospiech]

.pro files are broken again.

I compiled from scratch, latest version and get the error that 'wwwidgets4d' is not found. This happens at compilation of the plugin

This is true, since the debug version is _not_ compiled as 'wwwidgets4d', but without the 'd'.

Matthias

[wysota]

Then don't compile the plugin in debug mode. What do you need it for anyway? Do you have Designer compiled in debug mode? It is only useful for the widget library to be in debug (and release) mode.

[pospiech]

Then don't compile the plugin in debug mode. What do you need it for anyway? Do you have Designer compiled in debug mode? It is only useful for the widget library to be in debug (and release) mode.

I did not compile debug mode. I did not even touch the .pro files. I only called qmake and nmake. If it compiles in debug mode, then because of the .pro file settings.

[wysota]

Is there a "CONFIG-=debug" statement in your plugin.pro?