On Wednesday 11 August 2010, Aaron J. Seigo wrote:
On Wednesday, August 11, 2010, todd rme wrote:
I would say the mandlebrot wallpaper also benefits from this, since
you can see how the colors you select work in practice. Although it
easy enough with an in-line preview, but in practice i
On Wednesday 11 August 2010 22:01:24 Aaron J. Seigo wrote:
On August 11, 2010, Marco Martin wrote:
I think in some cases we could want applet not going away, like lionmail,
even if i have kmail closed i could want lionmail continuing to notify me
about emails
true; in that case the user
On Wed, Aug 11, 2010 at 8:22 PM, Aaron J. Seigo ase...@kde.org wrote:
On August 11, 2010, Alexis Ménard wrote:
On Wed, Aug 11, 2010 at 12:21 AM, Aaron J. Seigo ase...@kde.org wrote:
On August 10, 2010, you wrote:
do you agree that this should get fixed in Qt?
Obviously. Will do
Hi!
So our dashboard is mostly working (other than the last issues I already
reported), now I just have a little itch.
The thing is that the KDevelop dashboard is the central place to show
information when a project is opened, the idea is that it's going to be
shared by all the project members
On Thursday, August 12, 2010, Marco Martin wrote:
recapping:
good summary.
in the end, if a little live preview is needed should be up
to the
wallpaper implelentation.
yes.
the attached patch is a first quick and dirty implementation of
tat:
the need of the monitor is decided by
On Thursday, August 12, 2010, Marco Martin wrote:
perhaps Newspaper::saveContents could override all geometries with dummy
values, not sure if soething would break or not...
nothing should break; but perhaps this is a good use case for a new flag in
Containment, something like a property: bool
On Thursday 12 August 2010, Aaron J. Seigo wrote:
On Thursday, August 12, 2010, Marco Martin wrote:
perhaps Newspaper::saveContents could override all geometries with dummy
values, not sure if soething would break or not...
nothing should break; but perhaps this is a good use case for a
On Thursday 12 August 2010, Aaron J. Seigo wrote:
On Thursday, August 12, 2010, Marco Martin wrote:
recapping:
good summary.
in the end, if a little live preview is needed should be up
to the
wallpaper implelentation.
yes.
the attached patch is a first quick and dirty
On Thursday, August 12, 2010, Marco Martin wrote:
On Thursday 12 August 2010, Aaron J. Seigo wrote:
On Thursday, August 12, 2010, Marco Martin wrote:
recapping:
good summary.
in the end, if a little live preview is needed should be up
to the
wallpaper implelentation.
On Thursday 12 August 2010, Aaron J. Seigo wrote:
On Thursday, August 12, 2010, Marco Martin wrote:
On Thursday 12 August 2010, Aaron J. Seigo wrote:
On Thursday, August 12, 2010, Marco Martin wrote:
recapping:
good summary.
in the end, if a little live preview is needed
hi plasma people! :)
we're working on so many different things and often very much heads down
in work that the changelog is getting neglected. we're also beyond the early
OMG, this feature will take 2 months and 100s of commits to be fully done,
so i can't use commit log msgs to build the
On Thursday, August 12, 2010, Aaron J. Seigo wrote:
features should have FEATURE in the message.
bugs should have either a
BUG:# comment or just BUG or BUGFIX in the msg.
erf.. and IMPROVEMENT for notable improvements that aren't bugfixes or
features.
--
Aaron J. Seigo
humru othro a
On Thu, Aug 12, 2010 at 2:48 PM, Aaron J. Seigo ase...@kde.org wrote:
i'd like to therefore request that all commits to plasma code in kdelibs,
kdebase and kdeplasma-addons that represent a new feature or a bug fix
include the appropriate keywords in the commit msg. kmail will filter them
for
On Thursday 12 August 2010 19:06:21 Artur Souza (MoRpHeUz) wrote:
On Thu, Aug 12, 2010 at 2:48 PM, Aaron J. Seigo ase...@kde.org wrote:
i'd like to therefore request that all commits to plasma code in kdelibs,
kdebase and kdeplasma-addons that represent a new feature or a bug fix
include
On Thu, Aug 12, 2010 at 4:21 PM, John Layt johnl...@googlemail.com wrote:
One of the things I really like about git is how easy it is to set up a
commit message template that could include all the keywords as a memory aid
+1. As soon as we move to git I can create such a template for us :)
Not
15 matches
Mail list logo