wwWidgets

[wysota]

Beta release of wwWidgets4 - a set of widgets for Qt4 has been released

Download package

The set consists of the following widgets:

• QwwColorButton Button acting as a colour chooser
• QwwColorComboBox Combobox that allows to pick colors. (unstable)
• QwwHueSatPicker A widget allowing color picking in a form of a hue-saturation rectangle
• QwwHueSatRadialPicker A widget allowing color picking in a form of hue-saturation circle
• QwwLineEdit QLineEdit with regular expression validation support
• QwwListWidget An enhanced QListWidget
• QwwLongSpinBox A spinbox taking long long values
• QwwNavigationBar Widget simmilar to MS Outlook navigation bar. (unstable)
• QwwNumPad A numeric keypad widget
• QwwTaskPanel Task panel simmilar to the one from WindowsXP.(unstable)
• QwwTipWidget Widget that displays application tips
• QwwTwoColorIndicator A widget allowing to choose a foreground and background colour

Widgets marked as unstable are hardly or even not at all usable. The color combobox has beed disabled and will not be built, so you won't see it in your widget box.

To build and install the set issue qmake, (n)make and (n)make install commands. The set should install cleanly on Unix and MSVC installations. There is a little problem with MinGW - you have to copy the .a file to the appropriate directory yourself.

To use the set simply add "CONFIG += wwWidgets" to your project file.

The set is not completed, but I decided to release it now anyway (GPL licence), because I don't know when I'll be able to finish the set so in the meantime it may be of benefit to someone. If you want to use any of the widgets in a commercial product, please contact me.

Comments about the release are welcome and appreciated - you can send me a private message, just please don't send reports about obviously not completed functionality. Please don't send reports about unstable widgets.

Due to a lack of functionality in Qt (at least up to versions 4.3beta1) Designer made custom container classes (such as the navigation bar and the task panel) will not work (hand coded classes should work fine).

[high_flyer]

Hehe, looking at the list it looks to me, you collected all reoccuring (in the forum) widgeds that users try to make, or look for.
Kind'a "see a need, feel a need"

Not bad, I will have a look at it as soon as I can.

Cheers!

[pdolbey]

Hi wysota

To get my VS2005 SP1 to compile/link this correctly, I needed to change qwwtwocolorindicator.h from

.
.
class QwwTwoColorIndicatorPrivate;
class Q_GUI_EXPORT QwwTwoColorIndicator : public QWidget, QwwPrivatable
{
Q_OBJECT
.
.

.
.
class QwwTwoColorIndicatorPrivate;
class Q_GUI_EXPORT QwwTwoColorIndicator : public QWidget, QwwPrivatable
{
Q_OBJECT
.
.

To copy to clipboard, switch view to plain text mode 

to

.
.
class QwwTwoColorIndicatorPrivate;
class Q_WW_EXPORT QwwTwoColorIndicator : public QWidget, QwwPrivatable
{
Q_OBJECT
.
.

.
.
class QwwTwoColorIndicatorPrivate;
class Q_WW_EXPORT QwwTwoColorIndicator : public QWidget, QwwPrivatable
{
Q_OBJECT
.
.

To copy to clipboard, switch view to plain text mode 

This looked right compared to other classes in the distro.

Other things causing minor problems

• The nmake install installs the dll into the QTDIR/lib folder, not the bin folder - yet another PATH entry required then?

• There's no "d" suffix to discriminate between debug and release build as suggested in the help pages. (I tend to use bin/bind folders as a model for my app builds but this is supposed to act a standard Qt extension)

• The "plugin" is being built with a staticlib setting in the pro file - I'm not sure if this is what you intended.

Still trying to get it working - I'm after one of those marvellous "Outlook 2003" navigation bars (and I saw some of the flame wars on the "other" Qt forum). However I've already sorted out the styling of QPushButtons - just trying to get the behaviours the same. Current screen shot attached.



Pete

[wysota]

Oh, yes... sorry about that... I thought I corrected that. I'll update the archive right away.

[sunil.thaha]

Thank you for a Great collection of widgets ...
These widgets help us to have a better understand of the Qt Sources. Your pimpl implementation rocks :-) . I liked the way you used a Base class to handle the destruction of d_ptr. Is that an implementation of RAII Idiom ?


One Question,
I found that you have used some undocumented features like the Q_Q and Q_D macros ... and trolltech warns us against the use of these macros. So is it fine to use it or should you create your own Q_WW_D ?

[wysota]

[QUOTE=sunil.thaha;35595]Is that an implementation of RAII Idiom ?
I don't have the slightest idea. If it is, then it's unintentional

I found that you have used some undocumented features like the Q_Q and Q_D macros ... and trolltech warns us against the use of these macros. So is it fine to use it or should you create your own Q_WW_D ?

It depends. I use it on my own pointers so it's safe. But you shouldn't use it on pointers Qt provides - I tried

[sunil.thaha]

Since we are expecting the our private data to be derived from QwwPrivate. Why do the functions like d_func() use reinterpret_cast rather than a dynamic_cast ?

[pdolbey]

wysota,

I know you said not to to comment about "unstable" widgets, but I had some minor success yesterday hacking the qwwnavigationbar component into some sort of stability. I've got the primary functionality working with the PushButtons activating the correct QWidget in the top half of the splitter and have sucessfully "styled" the PushButtons to the original "Outlook" (silver version) look similar to my screen grab above but without the minimize bar. The question is if you want the code fed back - I've changed both the header (replacing the topButton with a QLabel) and cpp and have added pngs to the resource file. Any interest?

Pete

[Teerayoot]

How to install component?

After i build ,i got wwwidgets4.dll and wwwidgets4.lib

i put 2 files into qtdesigner plugin folder but nothing new component load.

???

[elcuco]

On linux this creates a file called libwwwidgets4plugin.a, I was under the impression that the plugins should be *.so files...?

not workign here as well.

[pdolbey]

See my bullet point 3 above

The "plugin" is being built with a staticlib setting in the pro file - I'm not sure if this is what you intended.

Pete

[wysota]

Looks like I missed some comments...

The nmake install installs the dll into the QTDIR/lib folder, not the bin folder - yet another PATH entry required then?

No, it should have installed in both directories. As QMake doesn't seem to support installing into two dirs I had to hack the install script a little and didn't have time to test it properly, so it might have not worked.

There's no "d" suffix to discriminate between debug and release build as suggested in the help pages. (I tend to use bin/bind folders as a model for my app builds but this is supposed to act a standard Qt extension)

True, I didn't think of that, although the library is meant to be compiled against release version of Qt as that's how Designer is compiled. So if you want a debug release of the widget library, you have to adjust the name yourself for now. I'll correct it later.

The "plugin" is being built with a staticlib setting in the pro file - I'm not sure if this is what you intended.

No, it certainly shouldn't happen. Maybe KDevelop changed the project file behind my back again.

Still trying to get it working - I'm after one of those marvellous "Outlook 2003" navigation bars (and I saw some of the flame wars on the "other" Qt forum).

I was throwing the flames myself as I consider the bar stupid (waste of space, etc.), but if people need it, then it might be worth creating one.

However I've already sorted out the styling of QPushButtons - just trying to get the behaviours the same.

It should be very easy to change the appearance using CSS. If you have any comments about the functionality of the component, please don't hesitate to put them here. I have never used the Outlook bar myself, so I might be wrong about how it should work.

Thanks for the comments, I'm waiting for more.

[pdolbey]

I was throwing the flames myself as I consider the bar stupid (waste of space, etc.), but if people need it, then it might be worth creating one.

I noticed that - thats why I was suprised to see the widget in your package

It should be very easy to change the appearance using CSS. If you have any comments about the functionality of the component, please don't hesitate to put them here. I have never used the Outlook bar myself, so I might be wrong about how it should work.

See my second post - I have the widget both functioning stable enough for my needs, and styled to the MS look (but not necessarily feel). I thought I might change your interface to allow the style to be removed to give a vanilla OS look to the pushbuttons. However it is your library and it wouldn't be fair of me to make changes that might become a core element of my own project without telling you or giving you the opportunity to review them.

Cheers, Pete

[wysota]

I thought I might change your interface to allow the style to be removed to give a vanilla OS look to the pushbuttons. However it is your library and it wouldn't be fair of me to make changes that might become a core element of my own project without telling you or giving you the opportunity to review them.

From what I understand the only change needed is to call (or not) setStylesheet() with a proper string that will change the look (and possibly some of the "feel" as well) of the widget.