wwWidgets

[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]

I'm back now, so I can answer all the questions

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 ?

1) Qt works exactly the same way
2) dynamic cast is not needed as the component designer knows the class name, so there is no point of using dynamic cast because you can't access pimpl from outside the class anyway.
3) dynamic_cast relies on RTTI from the compiler, so you'd want to avoid that if possible.

I know you said not to to comment about "unstable" widgets,

That was because some things may not work, so I didn't want to see comments like "X doesn't work" - I already know it doesn't work Any other comments on unstable widgets are welcome.

but I had some minor success yesterday hacking the qwwnavigationbar component into some sort of stability.

The navigation bar is stable, the problem with it is that you can't use its Designer plugin correctly, because of a major bug in Qt.

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?

Sure, let's have a look . I don't think you have to add any images to the resource file, as CSS capabilities from Qt should allow you to make use of external images. About the button in the header - you can access the button and disable its "clicking" functionality if you don't like it without modifying the actual class (or you can subclass of course).

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.

You should have run "nmake install" after the compilation. The dll needs to be present in both the lib directory (so that you can make use of the component from your applications) and in the bin directory (so that Designer can access it). Furthermore you should have the file "wwwidgets4plugin.dll" available as well and it should land in your plugins/designer folder (nmake install should take care of that).

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

Well... you should have received a .so file if you didn't stick any "static" keywords during preconfiguration. I'll have a look at the project file to see what might have gone wrong and I'll get back to you on that.

[pdolbey]

The navigation bar is stable, the problem with it is that you can't use its Designer plugin correctly, because of a major bug in Qt.

Unfortunately, when you claimed the widget was unstable it wasn't clear what this meant. When I started testing it I used a test routine like this

#include <QtGui>  
#include <qwwnavigationbar.h>
 
int main(int argc, char ** argv)
{
    QApplication app(argc, argv);
    QMainWindow* win  = new QMainWindow();
    QwwNavigationBar* nav = new QwwNavigationBar(win);
    nav->addWidget(new QFrame(), "First Widget");
    nav->addWidget(new QFrame(), "Second Widget");
    nav->addWidget(new QFrame(), "Third Widget");
    win->setCentralWidget(nav);
    win->show();
    return app.exec();
}

#include <QtGui>  
#include <qwwnavigationbar.h>
  
int main(int argc, char ** argv)
{
    QApplication app(argc, argv);
    QMainWindow* win  = new QMainWindow();
    QwwNavigationBar* nav = new QwwNavigationBar(win);
    nav->addWidget(new QFrame(), "First Widget");
    nav->addWidget(new QFrame(), "Second Widget");
    nav->addWidget(new QFrame(), "Third Widget");
    win->setCentralWidget(nav);
    win->show();
    return app.exec();
}

To copy to clipboard, switch view to plain text mode 

which creates the screen window attached. The text for the second and third widgets was missing. This is when I started hacking . I believe I have a working solution, but as I can't be sure that this matches your original design, I'd rather PM the changes to you.

Pete

[wysota]

AFAIR the titles are taken from the "windowTitle" property of widgets added to the bar (that's one of the workarounds for one of Qt Designer problems), so this should work:

QwwNavigationBar* nav = new QwwNavigationBar(win);
QFrame *frm = new QFrame;
frm->setWindowTitle("First widget");
nav->addWidget(frm);
frm = new QFrame;
frm->setWindowTitle("Second widget");
nav->addWidget(frm);
frm = new QFrame;
frm->setWindowTitle("Third widget");
nav->addWidget(frm);

QwwNavigationBar* nav = new QwwNavigationBar(win);
QFrame *frm = new QFrame;
frm->setWindowTitle("First widget");
nav->addWidget(frm);
frm = new QFrame;
frm->setWindowTitle("Second widget");
nav->addWidget(frm);
frm = new QFrame;
frm->setWindowTitle("Third widget");
nav->addWidget(frm);

To copy to clipboard, switch view to plain text mode 

The same goes for windowIcon property and the decoration of the button. I can't be certain the current code works this way (and I can't test it on this computer), but it is the way it was meant to work.

[pdolbey]

Unfortunately that pattern isn't obvious from either the interface description, or from my initial test with only one button that worked "correctly". I could see that window titles were being used in the code, but I didn't realise that these were supposed to be the primary title source, and when I have specified text in my method call I would have expected it to have been displayed. Thats whay I thought the widget was inherenently unstable.

Pete

[wysota]

Unfortunately that pattern isn't obvious from either the interface description, or from my initial test with only one button that worked "correctly". I could see that window titles were being used in the code, but I didn't realise that these were supposed to be the primary title source, and when I have specified text in my method call I would have expected it to have been displayed. Thats whay I thought the widget was inherenently unstable.

That's why the widget is called "unstable" and the whole release "beta" The interface of the navigation bar will change a bit because some things will be done outside the widget and inside Designer (just like with the task panel). When this is done, the behaviour will be coherent.

[wysota]

Ok, I finally forced myself and published the next, (almost) fully usable beta of wwWidgets.

http://www.wysota.eu.org/wwwidgets

All comments are of course welcome.

Oh... and of course a screenshot of some of the widgets.