--===============4470259462014984430==
Content-Type: multipart/alternative; boundary=0015174be384070d0f04ba193eab

--0015174be384070d0f04ba193eab
Content-Type: text/plain; charset=ISO-8859-1

Hello,

this year I want to apply for the GSOC 2012 for the plasma project.
My idea for plasma's GSOC 2012 is to make plasmate ready for release.

So here it goes,

Problem 1
Right now plasmate doesn't support all the debugging tools which we offer.
Those debugging
tools live under kde-workspace/plasma/generic/tools.

Solution 1
a.Move all the debugging tools from kde-workspace/plasma/generic/tools and
kde-runtime/plasma/tools
into plasmate's repository(maybe we should rename the repository to Plasma
SDK)

b.make plasmate use those tools.

c.our debugging tools will still live as standalone applications and also
us plasmate's plugins.
Some of our devs doesn't like plasmate and we shouldn't force them to use
it. So having
our debugging tools both as standalone application and as plasmate's
plugins solves the issue.
Regarding the build system I can add the debugging tools and plasmate as
option in order not to
force some developer to build the entire repository.

Problem 2
Plasmate and plasmoidviewer have duplicate code.  Also plasma-previewer(the
plasmate's code
for plasmoid debugging) is more modular than the plasmoidviewer's code.
Plasma-previewer is more modular but plasmoidviewer has more features than
the plasma-previewer.

Solution 2
Replace plasma-previewer's code with plasmoidviewer's and make
plasmoidviewer's code more modular
in order to be reused by plasmate.

Also a side note here,
both plasma components for desktop and for active live with the same names.
So in order to use the
plasma components for active the developer has to change an environment
variable. Plasmoidviewer
should provide an option for that (I will add this option).

Problem 3
There is no plasma tool for us to open our svg images add see the available
layers.
Since we want to offer a nice sdk our users should be able to browse our
svgs easier.

Solution 3
Sreich's svgviewer solves the half of the problem(thank you Sreich) the
other half(there is no way to
see the available layers of each svg). I will implement this option.

Problem 3
KConfigXT editor isn't finished. There is still some code which has to
be written.

Solution 3
Finish the KConfigXT editor and also make it available as a standalone
application.
All of our debugging tools shouldn't force our developers to use plasmate.

Problem 4
Plasmate's editor doesn't support actions.(Like undo/redo,etc)

Solution 4
Make plasmate support those.

We have to add more comments/documentation into the code in order to bring
lower
the contribution barrier.

Is there someone who would like to mentor me for the specific project?

Regards,
Giorgos.

-- 
Giorgos Tsiapaliwkas (terietor)
KDE Developer

terietor.gr

--0015174be384070d0f04ba193eab
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style>Hello,</span><div style><br></div><div style>t=
his year I want to apply for the GSOC 2012 for the plasma project.</div><di=
v style>My idea for plasma&#39;s GSOC 2012 is to make plasmate ready for re=
lease.</div>
<div style><br></div><div style>So here it goes,</div><div style><br></div>=
<div style>Problem 1</div><div style>Right now plasmate doesn&#39;t support=
 all the debugging tools which we offer. Those debugging=A0</div><div style=
>
tools live under kde-workspace/plasma/generic/tools.=A0<br clear=3D"all"><d=
iv><br></div><div>Solution 1</div><div>a.Move all the debugging tools from=
=A0kde-workspace/plasma/generic/tools and kde-runtime/plasma/tools</div><di=
v>into plasmate&#39;s repository(maybe we should rename the repository=A0to=
 Plasma SDK)</div>
<div><br></div><div>b.make plasmate use those tools.</div><div><br></div><d=
iv>c.our debugging tools will still live as standalone applications and als=
o us plasmate&#39;s plugins.</div><div>Some of our devs doesn&#39;t like pl=
asmate and we shouldn&#39;t force them to use it. So having</div>
<div>our debugging tools both as=A0standalone application and as plasmate&#=
39;s plugins solves the issue.</div><div>Regarding the build system I can a=
dd the debugging tools and plasmate as option in order not to</div><div>for=
ce some developer to build the=A0entire=A0repository.=A0</div>
<div><br></div><div>Problem 2</div><div>Plasmate and plasmoidviewer have du=
plicate code. =A0Also plasma-previewer(the plasmate&#39;s code</div><div>fo=
r plasmoid debugging) is more modular than the plasmoidviewer&#39;s code.</=
div>
<div>Plasma-previewer is more modular but plasmoidviewer has more features =
than the plasma-previewer.</div><div><br></div><div>Solution 2</div><div>Re=
place plasma-previewer&#39;s code with plasmoidviewer&#39;s and make plasmo=
idviewer&#39;s code more modular</div>
<div>in order to be reused by plasmate.=A0</div><div><br></div><div>Also a =
side note here,</div><div>both plasma components for desktop and for active=
 live with the same names. So in order to use the</div><div>plasma componen=
ts for active the developer has to change an=A0environment variable. Plasmo=
idviewer</div>
<div>should provide an option for that (I will add this option).</div><div>=
<br></div><div>Problem 3</div><div>There is no plasma tool for us to open o=
ur svg images add see the available layers.</div><div>Since we want to offe=
r a nice sdk our users should be able to browse our svgs easier.</div>
<div><br></div><div>Solution 3</div><div>Sreich&#39;s svgviewer solves the =
half of the problem(thank you Sreich) the other half(there is no way to</di=
v><div>see the available layers of each svg). I will implement this option.=
</div>
<div><br></div><div>Problem 3</div><div>KConfigXT editor isn&#39;t finished=
. There is still some code which has to be=A0written.</div><div><br></div><=
div>Solution 3</div><div>Finish the KConfigXT editor and also make it=A0ava=
ilable=A0as a standalone application.</div>
<div>All of our debugging tools shouldn&#39;t force our developers to use p=
lasmate.</div><div>=A0</div><div>Problem 4</div><div>Plasmate&#39;s editor =
doesn&#39;t support actions.(Like undo/redo,etc)</div><div><br></div><div>
Solution 4</div><div>Make plasmate support those.</div><div><br></div><div>=
We have to add more comments/documentation into the code in order to bring =
lower</div><div>the contribution barrier.</div><div><br></div><div>Is there=
 someone who would like to mentor me for the specific project?</div>
<div><br></div><div>Regards,</div><div>Giorgos.</div></div><div><br></div>-=
- <br>Giorgos=A0Tsiapaliwkas=A0(terietor)<br>KDE Developer<br><br><a href=
=3D"http://terietor.gr" target=3D"_blank">terietor.gr</a><br>
</div>

--0015174be384070d0f04ba193eab--

--===============4470259462014984430==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============4470259462014984430==--