---------- Messaggio inoltrato ----------
From:=A0"Aaron = J. Seigo" <aseigo@kde.org>=
To:=A0plasma-devel@kde.org
D= ate:=A0Mon, 27 Jul 2009 13:43:12 -0600
Subject:=A0Re: Plasmate StatusOn Monday 27 July 2009, Diego Casella ([Po]lentino) wrote:
> Note that up to now you have to manually setup the working directory b= y
> 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 searc= hed
> in TechBase, kde-loo= k.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 bin= dings
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 meant= ime,
but hiding them during development is an awesome way to ensure they never g= et
implemented. this is the out of sight, out of mind principle.

Ok, I'll reset to the previous status.

<= blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 2= 04, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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 examp= les
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 i= t's
> the more important question: why?

ok, i found the offending commits. with otherwise small changes the committ= er
also reformatted the entire file's ws. that is unacceptable. i will be<= br> changing the formatting back to the kdelibs style later today.

Sorry for the huge mistake, it wasn't my intent t= o make you waste your time =3D(
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 t= han
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 =A0EE75 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