Regarding development of an application for KDE

[Atri Sharma]

Hi,

 

I am Atri Sharma.I am a C++ developer.

 

I had an application in mind which I believe can be implemented on KDE.

 

All the FOSS developers have a set of applications and tools which are needed regularly.Accessing them seperately can be time consuming.My system would give the developer a single GUI from where he/she can code,manage their task and bug lists,stay connected on IRC,manage their projects,access the repository,run diff/patch with a single click,set their status,manage their projects,access the terminal and many other features.

 

I am more than willing to implement it.If the community approves of my idea,I shall immediately  commence designing the system.

 

I have attached a basic outline of the GUI.Please have a look.

 

Do let me know if any clarification is required.

 

Waiting for your feedback,

Atri

Attachments:Basic outline of the GUI of the system.

[Shantanu Tushar Jha]

Hi Atri,

Thanks for your mail and we appreciate that you wish to contribute. However, KDevelop[1] can do what you listed (and more) already. The only exception is the IRC client which I think you can write a KPart for, but I'm not sure. Try asking the kdevelop guys.

Cheers,

[1] http://kdevelop.org/

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--
Shantanu Tushar    (UTC +0530)
http://www.shantanutushar.com

[Jacky Alcine]

It's very possible to write a KPart for IRC support into KDevelop.
However, implementing such a KPart would be only useful if you like
resizing your pane to be bigger than your code editor window. However,
if you can work with implementing a KPart for Konversation or even
just using libircclient (in Ubuntu's repositories), then I'd test and
help you out :)

[Atri Sharma]

Hi Jacky,

Thanks a lot for your idea.

You mean write a KPart for KDevelop to include Konversation?Definitely,I would like to do that.

 

Please let me know how to go forward.

Atri

[Milian Wolff]

On Wednesday 29 February 2012 16:20:07 Atri Sharma wrote:
> Hi,
>
> I am Atri Sharma.I am a C++ developer.
>
> I had an application in mind which I believe can be implemented on KDE.
>
> All the FOSS developers have a set of applications and tools which are
> needed regularly.Accessing them seperately can be time consuming.My system
> would give the developer a single GUI from where he/she can code,manage
> their task and bug lists,stay connected on IRC,manage their projects,access
> the repository,run diff/patch with a single click,set their status,manage
> their projects,access the terminal and many other features.

integration is nice and all, but please keep the usefulness in mind. an
integrated irc client is really nothing I want to have in kdevelop, quite
frankly... next someone wants an email client and we end up being emacs...

Rather I think - assuming you want to contribute to kdevelop - you should
think about integrating smaller utilities that are acutally useful in an
integrated development IDE. Having a list of bugs would be useful. Some way to
share meta data with developers, i.e. where their mailing lists are, what
their irc channel is etc. pp.

All the above is exactly the idea of our integrated plasma dashboard. If you
want, you can try to bring it up2speed and making it useable.

bye
--
Milian Wolff
ma...@milianw.de
http://milianw.de

[Jacky Alcine]

I've only written a few sample kcm plugins (KControl modules for
System Settings) and plasmoids, so I don't know.
I'm on my school's computer checking e-mails but when I get my
Internet back at home, I'd love to help.
I'm in a bunch of KDE channels (when I'm online on Freenode) as
JackyAlcine, but you should ask around in #kde-devel; the's channel's
luke-warm, questions are answered when asked (and with a bit of KDE
charm :))

[Jacky Alcine]

On Wed, Feb 29, 2012 at 1:39 PM, Milian Wolff <ma...@milianw.de> wrote:
> On Wednesday 29 February 2012 16:20:07 Atri Sharma wrote:
>> Hi,
>>
>> I am Atri Sharma.I am a C++ developer.
>>
>> I had an application in mind which I believe can be implemented on KDE.
>>
>> All the FOSS developers have a set of applications and tools which are
>> needed regularly.Accessing them seperately can be time consuming.My system
>> would give the developer a single GUI from where he/she can code,manage
>> their task and bug lists,stay connected on IRC,manage their projects,access
>> the repository,run diff/patch with a single click,set their status,manage
>> their projects,access the terminal and many other features.
>
> integration is nice and all, but please keep the usefulness in mind. an
> integrated irc client is really nothing I want to have in kdevelop, quite
> frankly... next someone wants an email client and we end up being emacs...
>
> Rather I think - assuming you want to contribute to kdevelop - you should
> think about integrating smaller utilities that are acutally useful in an
> integrated development IDE. Having a list of bugs would be useful. Some way to
> share meta data with developers, i.e. where their mailing lists are, what
> their irc channel is etc. pp.

I've been working on a plug-in that scans source code to populate the
Problems pane whenever it detects specific task-tags, similar to that
of Eclipse. I found it useful when developing Android applications,
and I would love it desperately in KDevelop.

Another nifty idea would be being able to link bugs directly in the
code. Using a simple template for URL, like
http://bug_url.org?index=%index, developers could just click and view
the bug in a browser (or in a KHTML window).

As for your meta-data idea, would it have to be like information about
the project specifically? If so, we could incorporate that into the
project file and build a plasmoid that shows that information.

[Atri Sharma]

Hi all,

 

Milan:I think the points you made are pretty exciting.As I said in my earlier mail,my main plan is not to integrate only IRC,but every component that a FOSS developer needs.My idea is to basically integrate all the components suggested by the community.The list I initially sent is very basic.It will be expanded by interacting and taking suggestions from the community.

 

I aam really very excited about the project and I want to get started ASAP.It would be really helpful if the community could keep on providng valuable suggestions to me.

 

Milan/Jacky:Could anyone please mentor me in this?

 

Thanks,

Atri

[Milian Wolff]

sure, our problems pane is extensible, just adding problems should do the
trick. And with KDevelop 4.2 or 4.3 you also get entries there for TODO,
FIXME, XXX etc. pp.

> Another nifty idea would be being able to link bugs directly in the
> code. Using a simple template for URL, like
> http://bug_url.org?index=%index, developers could just click and view
> the bug in a browser (or in a KHTML window).

good idea, could you report that to bugs.kde.org for katepart? something
similar to what konsole does would be nice, i.e. underline on hover and offer
a "open link" in a context menu

> As for your meta-data idea, would it have to be like information about
> the project specifically? If so, we could incorporate that into the
> project file and build a plasmoid that shows that information.

yes that is the idea and was already implemented (basically) by Aleix. It just
needs more love to get it into shape to make it end-user friendly.

[Milian Wolff]

On Thursday 01 March 2012 00:25:02 Atri Sharma wrote:
> Hi all,
>
> Milan:I think the points you made are pretty exciting.As I said in my
> earlier mail,my main plan is not to integrate only IRC,but every component
> that a FOSS developer needs.My idea is to basically integrate all the
> components suggested by the community.The list I initially sent is very
> basic.It will be expanded by interacting and taking suggestions from the
> community.

Sorry, but have you read what I said? Personally I don't really like your
"lets integrate everything" approach. Integrate small parts that make sense,
like showing a link to the IRC channel and let a designated App open (like
Konversation). But don't embed an IRC part.

> I aam really very excited about the project and I want to get started
> ASAP.It would be really helpful if the community could keep on providng
> valuable suggestions to me.
>
> Milan/Jacky:Could anyone please mentor me in this?

first lets sort out what you actually want to do. If you want to do something
with the KDevelop Plasma dashboard, then I could try to give you a hand.
Please direct your questions to the kdevelop-devel mailing list or ask me or
aleix (apol) in #kdevelop on freenode irc.

bye

[Kevin Krammer]

On Wednesday, 2012-02-29, Milian Wolff wrote:
> On Wednesday 29 February 2012 16:20:07 Atri Sharma wrote:
> > Hi,
> >
> > I am Atri Sharma.I am a C++ developer.
> >
> > I had an application in mind which I believe can be implemented on KDE.
> >
> > All the FOSS developers have a set of applications and tools which are
> > needed regularly.Accessing them seperately can be time consuming.My
> > system would give the developer a single GUI from where he/she can
> > code,manage their task and bug lists,stay connected on IRC,manage their
> > projects,access the repository,run diff/patch with a single click,set
> > their status,manage their projects,access the terminal and many other
> > features.
>
> integration is nice and all, but please keep the usefulness in mind. an
> integrated irc client is really nothing I want to have in kdevelop, quite
> frankly... next someone wants an email client and we end up being emacs...

While I agree on not needing either IRC or mail interface built into KDevelop,
I can imagine tapping into instant messaging/email capabilities could create
interesting features.

For example assume that you access to KDE's committer list (I think there is
an Akonadi resource for that) and also access to Telepathy. The git/svn blame
view/annotation could display the respective committers IM availability.

Or sending the current diff as a patch email to the author or mailinglist the
code is associated with.

Cheers,
Kevin
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

[Milian Wolff]

yes, showing such info is fine but as soon as one wants to interact with some
person a designated app like kopete or telepathy or kmail or ... should be
opened.

that's the big difference I see in what is proposed here and what is in my
mind

[Kevin Krammer]

On Wednesday, 2012-02-29, Milian Wolff wrote:
> On Wednesday 29 February 2012 22:03:24 Kevin Krammer wrote:

> > For example assume that you access to KDE's committer list (I think there
> > is an Akonadi resource for that) and also access to Telepathy. The
> > git/svn blame view/annotation could display the respective committers IM
> > availability.
> >
> > Or sending the current diff as a patch email to the author or mailinglist
> > the code is associated with.
>
> yes, showing such info is fine but as soon as one wants to interact with
> some person a designated app like kopete or telepathy or kmail or ...
> should be opened.

In general I would agree but it depends largely on the feature.
For example for collaborative editing (e.g. like Google docs) or just letting
the other user having a passive view of what you are doing (e.g. like most
webinar viewers) might benefit from having the messaging channel to that person
inline.

[Atri Sharma]

Hi all,

 

I think we have nearly finalized some of the features that can be included:

 

1)BUGS list.

2)Synchronization between TODO and IDE.

3)A commiters list(and their commits and their availablity)

4)Probably,a feature that sends a diff as an patch email to the relevant list.

 

I think these features would be great on the plasma dashboard.

 

Milian:finally I understand what you meant.You mean that we should integerate small parts,that make sense.Sure,I'll do that.

 

Please let me know your comments.

 

Atri

 

 

 

[Milian Wolff]

On Thursday 01 March 2012 09:18:05 Atri Sharma wrote:
> Hi all,
>
> I think we have nearly finalized some of the features that can be included:
>
> 1)BUGS list.
> 2)Synchronization between TODO and IDE.
> 3)A commiters list(and their commits and their availablity)
> 4)Probably,a feature that sends a diff as an patch email to the relevant
> list.
>
> I think these features would be great on the plasma dashboard.
>
> Milian:finally I understand what you meant.You mean that we should
> integerate small parts,that make sense.Sure,I'll do that.

sounds good.

bye
--
Milian Wolff
ma...@milianw.de
http://milianw.de

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[Atri Sharma]

Thanks Milian.

 

Please do give me pointers on how to start developing for KDevelop,as it is my first contribution.

Also,where can I get the existing plasma dashboard code?

 

Please do let me know how to proceed further.

 

Atri

[Milian Wolff]

On Thursday 01 March 2012 17:55:46 Atri Sharma wrote:
> Thanks Milian.
>
> Please do give me pointers on how to start developing for KDevelop,as it is
> my first contribution.
> Also,where can I get the existing plasma dashboard code?

- kdevelop-devel mailing list
- http://techbase.kde.org/KDevelop4/HowToCompile
-
https://projects.kde.org/projects/extragear/kdevelop/kdevplatform/repository/revisions/master/show/plugins/dashboard

bye

> On Thu, Mar 1, 2012 at 5:49 PM, Milian Wolff <ma...@milianw.de> wrote:
> > On Thursday 01 March 2012 09:18:05 Atri Sharma wrote:
> > > Hi all,
> > >
> > > I think we have nearly finalized some of the features that can be
> >
> > included:
> > > 1)BUGS list.
> > > 2)Synchronization between TODO and IDE.
> > > 3)A commiters list(and their commits and their availablity)
> > > 4)Probably,a feature that sends a diff as an patch email to the relevant
> > > list.
> > >
> > > I think these features would be great on the plasma dashboard.
> > >
> > > Milian:finally I understand what you meant.You mean that we should
> > > integerate small parts,that make sense.Sure,I'll do that.
> >
> > sounds good.
> >
> > bye
> > --
> > Milian Wolff
> > ma...@milianw.de
> > http://milianw.de
--
Milian Wolff
ma...@milianw.de
http://milianw.de

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[Atri Sharma]

Thanks Milian.

Another thing,would you please mentor me in the project?And do I need to register somewhere as a contributer?

 

Atri

[Jacky Alcine]

So I'm typically around the KDE channels and #kdevelop under the nick
JackyAlcine.

I hope to poke you guys about this.

[Julian Bäume]

moin!

Am Mittwoch, 29. Februar 2012, 16:20:07 schrieb Atri Sharma:
> All the FOSS developers have a set of applications and tools which are
> needed regularly.Accessing them seperately can be time consuming.My system
> would give the developer a single GUI from where he/she can code,manage
> their task and bug lists,stay connected on IRC,manage their projects,access
> the repository,run diff/patch with a single click,set their status,manage
> their projects,access the terminal and many other features.

As already mentioned, integration is nice, but I wanted to add a few things.
In KDevelop it is already possible to manage projects in an integrated way.
When I read your suggestions, I didn’t think as much about KDevelop, but
rather using activities to achieve these things you want to do. We are already
working on plasmoids for telepathy, that will help you starting a new
"conversation" (like irc or something) and manage your contacts (related to an
activity). Also, I guess, some day it would be possible to put certain streams
from akonadi (rss, mailing-lists, …) onto your desktop. This way you would do
all the meta-things, like communication and related stuff, using your activity
desktop. Everything related to code would be handled in KDevelop.

What I want to point out is, using KDE’s technologies, it is possible to
achieve a great amount of integration. This integration is provided by the
workspace and the tools developed by KDE. So IMHO it would be far better to
implement the things, you are talking about, as reusable parts for the KDE SC,
so you can benefit from everywhere, not only in a single application (be it
KDevelop or any other).

Just my 2ct about this topic. That’s what I like best about KDE’s workspaces.
Everything is (supposed to be) nicely integrated by design :)

bye then
julian

[Atri Sharma]

Hi all,

 

Thanks Julian,for the wonderful suggestions.

I am actually planning to implement the features I mentioned in the dashboard(so that they are not limited to a single application,but to the entire community).

 

For what I inferred from your suggestions,you are advising me to build componenets that can be integreted in any KDE application.

 

Is that correct?

 

Also,Please let me know if you want to add any tool to my existing list(I'd love to hear and implement them)

 

Cheers,

 

Atri