Jump to content

Plasma/libplasma2: Difference between revisions

From KDE Community Wiki
Aseigo (talk | contribs)
Created page with '= Summary = This page is dedicated to planning of the libplasma2. libplasma2 will be binary and source incompatible with the current libplasma. This means that we can fix some ...'
 
Aseigo (talk | contribs)
Svg::setImagePath
Line 21: Line 21:


= Issues with libplasma1 =
= Issues with libplasma1 =
{|
|-
! Idea:
! Svg::setImagePath is not virtual
|-
|valign=top| Summary:
| FrameSvg (and potentially other subclasses of Svg) need to take action when the image path is changed. setImagePath is not virtual nor does it call any internal virtuals. This has resulted in a necessary but unfortunate hack in Svg::setImagePath specifically for FrameSvg.
|-
|valign=top| Proposed solution:
| Make Svg::setImagePath virtual.
|-
|}

Revision as of 15:50, 31 October 2010

Summary

This page is dedicated to planning of the libplasma2.

libplasma2 will be binary and source incompatible with the current libplasma. This means that we can fix some issues that are currently present in plasma's design.

Enter the issues you wish fixed in the following form:

Idea: Change libplasma2
Summary: We have a chance to change stuff now
Discussion: http://mail.kde.org/pipermail/plasma-devel/2010-October

Issues with libplasma1

Idea: Svg::setImagePath is not virtual
Summary: FrameSvg (and potentially other subclasses of Svg) need to take action when the image path is changed. setImagePath is not virtual nor does it call any internal virtuals. This has resulted in a necessary but unfortunate hack in Svg::setImagePath specifically for FrameSvg.
Proposed solution: Make Svg::setImagePath virtual.