[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: Plasma-devel Digest, Vol 13, Issue 92
From:       "Diego Casella \(\[Po\]lentino\)" <polentino911 () gmail ! com>
Date:       2009-07-28 6:37:16
Message-ID: e6aee9e0907272337g32372d14q3117f989ca24dd47 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


>
> ---------- Messaggio inoltrato ----------
> From: "Aaron J. Seigo" <aseigo@kde.org>
> To: plasma-devel@kde.org
> Date: Mon, 27 Jul 2009 13:43:12 -0600
> Subject: Re: Plasmate Status
> On Monday 27 July 2009, Diego Casella ([Po]lentino) wrote:
> > Note that up to now you have to manually setup the working directory by
> > modifying line 165 in mainwindow.cpp, because
> > that global variable isn't set yet
>
> what's wrong with m_model->package()?
>
> > ( actually the projects directories are
> > saved in $HOME/.kde4/share/apps/plasmate which is not
> > a good choice imo, if we want to focus on beginner developers... what
> about
> > a $HOME/PlasMate_Projects folder instead? )
>
> the point is that they should never have to worry about where the files
> are.
> it's an implementation detail. and polluting the home dir with working data
> sets is not great form.
>

Ok, thanks for explanation :)

>
> > By the way, I need a DataEngine example written in JavaScript, I searched
> > in TechBase, kde-look.org and in various svn
> > modules without result.
>
> i added the first support for those 2 weeks ago, so it's not a mystery why
> you
> didn't find anything on it ;) i (or someone) still needs to do some
> bindings
> for Service as well so such dataengines can reimplement serviceForSource
> sanely.
>

Good, I'll check weekly for updates.

>
> > As regards runners, I looked for examples in TechBase and in
> > kdebase/workspace/plasma/runners, kdeplasma-addons/runners,
> > kdereview/plasma/runners but I only found c++ sources... So probably
> > scripting support for runners is not ready now, and I hid
> > the corresponding button.
>
> please don't hide buttons because they don't work. that's what you do for
> final release only if you don't manage to get them working in the meantime,
> but hiding them during development is an awesome way to ensure they never
> get
> implemented. this is the out of sight, out of mind principle.
>

Ok, I'll reset to the previous status.

>
> and yes, it's possible to write runners with ecma script. as soon as it's
> possible to write something useful with plasmate, i'll do up some examples
> using it. ;)
>
> > who decided that plasmate should use tabs for indentation and random
> > whitespacing in various places, e.g. inside of ()s? or rather, since it's
> > the more important question: why?
>
> ok, i found the offending commits. with otherwise small changes the
> committer
> also reformatted the entire file's ws. that is unacceptable. i will be
> changing the formatting back to the kdelibs style later today.
>

Sorry for the huge mistake, it wasn't my intent to make you waste your time
=(
I'll be more careful when committing.

>
> if you have uncommitted changes, you can expect conflicts, so you should
> commit soon.
>
> going forward, if i see a commit that reformats the ws to something other
> than
> the kdelibs style, i will alert the author and revert the offending commit.
> the author can re-do the work.
>
> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
>
> KDE core developer sponsored by Qt Software
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>

[Attachment #5 (text/html)]

<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">---------- \
Messaggio inoltrato ----------<br>From: &quot;Aaron J. Seigo&quot; &lt;<a \
                href="mailto:aseigo@kde.org">aseigo@kde.org</a>&gt;<br>
To: <a href="mailto:plasma-devel@kde.org">plasma-devel@kde.org</a><br>Date: Mon, 27 \
Jul 2009 13:43:12 -0600<br>Subject: Re: Plasmate Status<br>On Monday 27 July 2009, \
Diego Casella ([Po]lentino) wrote:<br> &gt; Note that up to now you have to manually \
setup the working directory by<br> &gt; modifying line 165 in mainwindow.cpp, \
because<br> &gt; that global variable isn&#39;t set yet<br>
<br>
what&#39;s wrong with m_model-&gt;package()?<br>
<br>
&gt; ( actually the projects directories are<br>
&gt; saved in $HOME/.kde4/share/apps/plasmate which is not<br>
&gt; a good choice imo, if we want to focus on beginner developers... what about<br>
&gt; a $HOME/PlasMate_Projects folder instead? )<br>
<br>
the point is that they should never have to worry about where the files are.<br>
it&#39;s an implementation detail. and polluting the home dir with working data<br>
sets is not great form.<br>
</blockquote><div><br>Ok, thanks for explanation :) <br></div><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"><br> &gt; By the way, I need a DataEngine example \
written in JavaScript, I searched<br> &gt; in TechBase, <a href="http://kde-look.org" \
target="_blank">kde-look.org</a> and in various svn<br> &gt; modules without \
result.<br> <br>
i added the first support for those 2 weeks ago, so it&#39;s not a mystery why \
you<br> didn&#39;t find anything on it ;) i (or someone) still needs to do some \
bindings<br> for Service as well so such dataengines can reimplement \
serviceForSource<br> sanely.<br>
</blockquote><div><br>Good, I&#39;ll check weekly for updates. <br></div><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"><br> &gt; As regards runners, I looked for examples in \
TechBase and in<br> &gt; kdebase/workspace/plasma/runners, \
kdeplasma-addons/runners,<br> &gt; kdereview/plasma/runners but I only found c++ \
sources... So probably<br> &gt; scripting support for runners is not ready now, and I \
hid<br> &gt; the corresponding button.<br>
<br>
please don&#39;t hide buttons because they don&#39;t work. that&#39;s what you do \
for<br> final release only if you don&#39;t manage to get them working in the \
meantime,<br> but hiding them during development is an awesome way to ensure they \
never get<br> implemented. this is the out of sight, out of mind principle.<br>
</blockquote><div><br>Ok, I&#39;ll reset to the previous status.<br></div><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"><br> and yes, it&#39;s possible to write runners with \
ecma script. as soon as it&#39;s<br> possible to write something useful with \
plasmate, i&#39;ll do up some examples<br> using it. ;)<br>
<br>
&gt; who decided that plasmate should use tabs for indentation and random<br>
&gt; whitespacing in various places, e.g. inside of ()s? or rather, since \
it&#39;s<br> &gt; the more important question: why?<br>
<br>
ok, i found the offending commits. with otherwise small changes the committer<br>
also reformatted the entire file&#39;s ws. that is unacceptable. i will be<br>
changing the formatting back to the kdelibs style later today.<br>
</blockquote><div><br>Sorry for the huge mistake, it wasn&#39;t my intent to make you \
waste your time =(<br>I&#39;ll be more careful when committing.<br></div><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> <br>
if you have uncommitted changes, you can expect conflicts, so you should<br>
commit soon.<br>
<br>
going forward, if i see a commit that reformats the ws to something other than<br>
the kdelibs style, i will alert the author and revert the offending commit.<br>
the author can re-do the work.<br>
<br>
--<br>
Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Software<br>
<br>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
<br></blockquote></div><br>



_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic