* upon using the accessor i disocvered they didn't actually do anything except set the member variable; no changes actually took place in the dialogs.
eventually, we should probably consider moving the application name to a central location in libplasma, e.g. a Plasma::setMainComponent(KComponentData&) that initializes itself to the app's mainComponent()... there's too many of these app name things around
also, when the item model updates itself, the view in the dialog doesn't. i've added a hack in AppletBrowser::setApplication to re-set the item model on the view. maybe Ivan you could take a look at that sometime? it's not overly critical as it works for now due to the hack.
CCMAIL:lfranchi@gmail.com
CCMAIL:ivan.cukic+kde@gmail.com
svn path=/trunk/KDE/kdebase/workspace/libs/plasma/; revision=733614
by the SuperKaramba Plasma Applet alone that comes with SuperKaramba itself.
- Remove all previous functions to load SuperKaramba themes
- Add special code into applet browser to handle the theme loading
svn path=/trunk/KDE/kdebase/workspace/libs/plasma/; revision=724563
AppletBrowserWindow-now-AppletBrowser files to where they once were (oh
what we go through to make sure nobody's builds break and svn doesn't
puke on me)
svn path=/trunk/KDE/kdebase/workspace/libs/plasma/; revision=717963
- use standard buttons
- get rid of the completely superfluous ui file for the dialog
- add a dptr, move to Plasma namespace (why will become apparent shortly)
svn path=/trunk/KDE/kdebase/workspace/libs/plasma/; revision=717956
- correct ordering of headers in many files
- remove some unneeded headers such as iostream
svn path=/trunk/KDE/kdebase/workspace/libs/plasma/; revision=717932
