the animations use either QEasingCurve or JS code (which will eventually
be converted to sub-class of QEasingCurve for performance reasons)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
according to the chanages log (see kde-workspace/plasma/design/CHANGELOG-4.4)
it was used by the mediawiki runner which is no longer supported
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
using the mask created by QPixmap::mask() is much more reliable way
to get one, fixes masking in case compositor is not active for example
side note: feels good to finally land the fix for masking
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
because Plasma::Theme (and Plasma::ThemePrivate indirectly) may be created
before QCoreApplication/QApplication instance by Theme::defaultTheme()
and application instance is required for QX11Info::display() to return
non-null (which KWindowSystem uses but has fallback in case it is null
in KWindowSystem::compositingActive())
note that KWindowSystem::compositingActive() returns cached value if
XFixes is available
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
with klauncher no longer responsible for KIO slave the next step is to
make them plugins and the feature to put them on hold will be of no value
because QLibrary reuses library/plugin instances and creating a new
slave object will be cheap
in other words the performance will be similar to that of KFileMetaInfo
for which I also wrote the plugins myself - they are pretty quick
compared to what strigi was doing and with more flexible configuration
interface but it took some effort to get there
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
`apt-file` search yeilds 221 files matching (8 packages provide such),
it is also unused by plasma even tho there are leftovers from support for it
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
who tought using the same shortcut for multiple actions is going to work?
the single character shortcuts are very likely to conflict with other
shortcuts aswell
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
very much written for use case, not to make sense. while porting to it I
already noticed there are leaks for X11 pixmaps and may have to write
glue code to keep track of the pixmaps and release them before
application quits, that will be a huge performance penalty tho so may
have to be ifdef'ed for debug builds only
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
there are 3 copies of the sources for that class because it is not
exported (one here, one in kde-workspace and one in kde-extraapps) with
one class that is very similar to it - PanelShadows (in kde-workspace
repo, part of plasmagenericshell library)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
at the point where the application is about to exit it is not safe to even
access the global static (by calling Plasma::Theme::defaultTheme()) since
it will be deleted
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
once it has been done and interesting elements information reaches the
disk cache (which is shared config) parsing the file again is a waste
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
it has to solve a few problems like:
1. blocking the current thread while listing, extracting or adding to
archive
2. lack of support for some archive formats such as 7-zip in the
previously available classes for dealing with archive
3. progress and error reporting
a KArchiveJob class may have to be implemented to solve the above
issues. the API is just as frustrating to use as KTar and KZip right now
tho and I am not happy with that but the class itself is a 3-rd rewrite
of what was once Python module, plugin for another project and now used
as base in library.
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
