<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jun 25, 2014 at 5:07 PM, Giorgos Tsiapaliokas <span dir="ltr"><<a href="mailto:giorgos.tsiapaliokas@kde.org" target="_blank">giorgos.tsiapaliokas@kde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Wednesday, June 25, 2014 03:41:17 PM Aleix Pol wrote:<br>
> as much as possible from KDevelop and see what is that you don't like.<br>
<br>
</div>yes this is what I am doing right now.<br>
<div class=""><br>
On Wednesday, June 25, 2014 03:45:59 PM Sven Brauch wrote:<br>
> So what I would intuitively expect for plasmate is that you'd rebuild it on<br>
> top of KDevPlatform, and then ship with the plugins which make sense for you<br>
> only (e.g. QML/JS, Qt documentation, QuickOpen). KDevelop wouldn't be<br>
> involved at all here, since you don't need most of the things from there.<br>
><br>
> Is that what you had in mind?<br>
<br>
</div>yes<br>
<br>
<br>
Because I wasn't very clear, also plasmate is called the repository which will<br>
contain the plasmate IDE and the kdevplatform plugins, which used to be<br>
inside the plasmate IDE and they will become plugins, so kdevelop could use<br>
them. My suggestion(which wasn't very clear indeed) is to move some of them to<br>
kdevplatform repository once they are ready and they have been reviewed. For<br>
instance one of them could be a notes plugin<br>
which as the name says :) the user keeps notes for his project.<br>
The question is, would you like to see stuff like that moving to the<br>
kdevplatform repository? I could prepare a list with those and discuss further<br>
on a more suitable thread.<br>
<br>
thanks,<br>
Giorgos<br>
<br>
P.S.: Also FYI my gsoc takes place in this[1] personal clone in the branch<br>
"terietor/gsoc/2014"<br>
<br>
[1] <a href="http://quickgit.kde.org/?p=clones%2Fplasmate%2Ftsiapaliwkas%2Fplasmate-kdevplatform.git" target="_blank">http://quickgit.kde.org/?p=clones%2Fplasmate%2Ftsiapaliwkas%2Fplasmate-kdevplatform.git</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Giorgos Tsiapaliokas<br>
<br>
<a href="http://terietor.org" target="_blank">terietor.org</a><br>
</font></span></blockquote></div><br></div><div class="gmail_extra">In general we only put implicitly generic stuff in kdevplatform and so far we've put more specific plugins, mostly related to C++ development in KDevelop.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">A question we could discuss is whether Plasmate will depend on KDevelop. For example, QtHelp plugin is in KDevelop.</div><div class="gmail_extra">I wouldn't mind having KDE/Plasma specific plugins in KDevelop. In fact we already have some. I would like to make sure they make sense without Plasmate though, there's where I'd draw the line.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Aleix</div></div>