ode as coding style I will wait that
> someone
> wants to review...
I agree. Mandatory reviews might work if there is a team of active people
working on a project, but if there is only one person with real knowledge of
the code, or there is nobody else with much time to spare, who is going to do
the review? It is likely to just sit waiting indefinitely. If getting code
reviewed is too difficult, the developer may have to give up and abandon the
project.
Mandatory reviewing could only work if individual projects can decide whether
to adopt it or not.
--
David Jarvie
KAlarm author, KDE developer
http://www.astrojar.org.uk/kalarm
ould be for individual projects to decide whether automatic code
formatting would be desirable or useful to them. This will allow projects to
continue to use their own coding styles where they wish, and allow for hand-
crafted formatting to be left intact where this is desired.
--
David Jar
roid app called "Simple Metronome" which doesn't have ads,
which I find ok for my purposes. I obviously don't know whether its sounds are
configurable enough for what you need.
--
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
s out.
Would you mind sharing the hook which you wrote? I've had the same dilemma as
you, and your hook seems a good solution.
--
David Jarvie.
KDE developer, KAlarm author.
ully
> > retargeting a branch doesn't seem possible from the UI and not sure if
> > you can merge up there either.
> >
> > What's keeping us from changing the strategy for the rest of KDE, too?
> >
> > Cheers
> > Kai Uwe
>
--
David Jarvie
KAlarm author, KDE developer
> >
> > > > Properly cleaning up old bugreports is important. However, it requires
> > > > some level of care and expertise to judge whether a bugreport is still
> > > > useful. Judging by the volume of bugreports that is pinged with the
> > same
> > > > c
to play catch-up before they are committed, the patches having
to be modified frequently as changes are made to the libraries and
applications affected. To insist that no regressions occur would mean that
such patches might never be committed, by part-time developers at least.
As long as there is time
There doesn't seem to be a kdesupport package in git or svn for use with KDE
4.6, equivalent to the svn tag kdesupport-for-4.5 for KDE 4.5. Are there plans
to create this?
--
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
signature.asc
Description: This
On Fri, April 15, 2011 1:24 am, Michael Pyne wrote:
> On Thursday, April 14, 2011 23:13:29 David Jarvie wrote:
>> There doesn't seem to be a kdesupport package in git or svn for use with
>> KDE
>> 4.6, equivalent to the svn tag kdesupport-for-4.5 for KDE 4.5. Are the
ate
>> it as it was.
>>
>> https://bugs.kde.org/show_bug.cgi?id=265051
>>
>> That worked perfectly in KDE-4.5, but regressed in 4.6.
--
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
to be set up). I
could hard code the /usr/sbin/ path, but that doesn't seem desirable in case
the executable is elsewhere on some systems.
--
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
signature.asc
Description: This is a digitally signed message p
On Sunday 08 May 2011 18:46:46 Enda Cronnolly wrote:
> On Sunday 08 May 2011 18:35:42 David Jarvie wrote:
> > Is there any KDE or Qt way to locate an executable using the root PATH.
> > Specifically, I want to run something which on my system is in /usr/sbin/,
> > calling i
On Monday 09 May 2011 00:07:27 johnmS2 wrote:
> On 05/08/2011 11:35 AM, David Jarvie wrote:
> > On Sunday 08 May 2011 18:46:46 Enda Cronnolly wrote:
> >> On Sunday 08 May 2011 18:35:42 David Jarvie wrote:
> >>> Is there any KDE or Qt way to locate an
o, unless it's clearly defined
somewhere. If a style does unexpected things which are not clearly documented
(in a sufficiently prominent place in the documentation that people won't
overlook it), then the style *will* introduce bugs in applications which are
not the applications
t; bar), let the user select if he wants to drag from the "non safe places"
> > with a warning that tells him that that setting might cause conflicts with
> > some applications.
> +1
+1
--
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk
r as I can tell (I don't speak Belorusian),
the translation which has been produced
(http://webhostingrating.com/libs/kalarm-be) seems genuine. If there's a
catch, it's not obvious what it is.
--
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm
&g
On Tue, July 12, 2011 9:39 am, Christoph Cullmann wrote:
> On Tuesday, July 12, 2011 10:36:05 AM David Jarvie wrote:
>> On Mon, July 11, 2011 8:40 pm, Christoph Cullmann wrote:
>> > Read my other mail here, he is a known farmer and tries that with
>> > multiple names
t has the disadvantage that if the group box shrinks, the row
containing the invisible widget will still occupy some space. You may be
able to add an extra layout to the QGridLayout instead of a widget, which
would avoid that issue.
--
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
cy().setHorizontalStretch(hexp-
>>horizontalStretch());
>
> It is still not as wide as I wish.
You could try using a QHBoxLayout covering the entire row in the
QGridLayout, and add the KUrlRequester to that, setting the 'stretch'
parameter to 1. Not sure if that will be any better than what you've
already tried.
--
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
ert a fix which a lot of other users
would also benefit from, were also to a greater or lesser degree
unreasonable.
While we can stick together on the basic principles in the argument, KDE
is surely about being free to (respectfully) question other people's ideas
and statements. It's not abou
Hi Rohan,
The best mailing list to ask this question on is the kde-pim list. All the
Akonadi developers read that list, but they don't necessarily read this
list.
Cheers,
David.
On Fri, October 12, 2012 11:59 am, Rohan Beckles wrote:
> Hi Gael --
>
> Thank you for your response. Yes, I'm aware
ew ideas. So I see user
> suggested features at max as something for new developers.
It probably depends on the type of project as to whether users' ideas are
useful, but for KAlarm I've implemented quite a number of feature
suggestions from users. So I don't think you can generali
;ve generated
the patch manually and uploaded via the reviewboard webpage. Perhaps
post-review has changed since then - I might give it another try sometime.
--
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
to do to set
up the new dependencies?
--
David Jarvie.
KDE developer, KAlarm author.
On Tuesday, 9 July 2024 23:47:30 BST Albert Astals Cid wrote:
> El dimarts, 9 de juliol del 2024, a les 22:12:40 (CEST), David Jarvie va
>
> escriure:
> > I have just changed the dependencies for KAlarm (removed Canberra, added
> > libvlc and libvlccore), but after commit
but I need an
answer to know how to fix this.
--
David Jarvie.
KDE developer, KAlarm author.
On 10 July 2024 06:29:18 BST, Heiko Becker wrote:
> On Wednesday, 10 July 2024 01:51:16 CEST, David Jarvie wrote:
> > On Tuesday, 9 July 2024 23:47:30 BST Albert Astals Cid wrote:
> >> El dimarts, 9 de juliol del 2024, a les 22:12:40 (CEST), David Jarvie va
> >>
>
y triggering the bug, but regardless, it's no
excuse
for QDateTime's misbehaviour.
--
David Jarvie.
KDE developer, KAlarm author.
On Saturday, 25 January 2025 07:45:30 GMT you wrote:
> On Sat, Jan 25, 2025 at 11:37 AM David Jarvie wrote:
> > On Tuesday, 21 January 2025 22:11:56 GMT Albert Astals Cid wrote:
> > > Please work on fixing them, otherwise i will remove the failing CI jobs
> > on
> >
29 matches
Mail list logo
