[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Regarding development of an application for KDE
From: Atri Sharma <atri.jiit () gmail ! com>
Date: 2012-02-29 18:55:55
Message-ID: CAOeZVid7B5+1SMstb5mWth8R++QBpjJoPxErUyseUADfZ+aZ7A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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
On Thu, Mar 1, 2012 at 12:19 AM, Jacky Alcine <jacky.alcine@thesii.org>wrote:
> On Wed, Feb 29, 2012 at 1:39 PM, Milian Wolff <mail@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.
>
> >
> > 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
> > mail@milianw.de
> > http://milianw.de
> >
> >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>
[Attachment #5 (text/html)]
<div>Hi all,</div><div> </div><div>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.</div> <div> \
</div><div>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.</div><div> </div><div>Milan/Jacky:Could anyone please mentor me in \
this?</div> <div> </div><div>Thanks,</div><div>Atri<br><br></div><div \
class="gmail_quote">On Thu, Mar 1, 2012 at 12:19 AM, Jacky Alcine <span \
dir="ltr"><<a href="mailto:jacky.alcine@thesii.org">jacky.alcine@thesii.org</a>></span> \
wrote:<br> <blockquote style="margin:0px 0px 0px \
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" \
class="gmail_quote"><div class="im">On Wed, Feb 29, 2012 at 1:39 PM, Milian Wolff \
<<a href="mailto:mail@milianw.de">mail@milianw.de</a>> wrote:<br>
> On Wednesday 29 February 2012 16:20:07 Atri Sharma wrote:<br>
>> Hi,<br>
>><br>
>> I am Atri Sharma.I am a C++ developer.<br>
>><br>
>> I had an application in mind which I believe can be implemented on KDE.<br>
>><br>
>> All the FOSS developers have a set of applications and tools which are<br>
>> needed regularly.Accessing them seperately can be time consuming.My \
system<br> >> would give the developer a single GUI from where he/she can \
code,manage<br> >> their task and bug lists,stay connected on IRC,manage their \
projects,access<br> >> the repository,run diff/patch with a single click,set \
their status,manage<br> >> their projects,access the terminal and many other \
features.<br> ><br>
> integration is nice and all, but please keep the usefulness in mind. an<br>
> integrated irc client is really nothing I want to have in kdevelop, quite<br>
> frankly... next someone wants an email client and we end up being emacs...<br>
><br>
> Rather I think - assuming you want to contribute to kdevelop - you should<br>
> think about integrating smaller utilities that are acutally useful in an<br>
> integrated development IDE. Having a list of bugs would be useful. Some way \
to<br> > share meta data with developers, i.e. where their mailing lists are, \
what<br> > their irc channel is etc. pp.<br>
<br>
</div>I've been working on a plug-in that scans source code to populate the<br>
Problems pane whenever it detects specific task-tags, similar to that<br>
of Eclipse. I found it useful when developing Android applications,<br>
and I would love it desperately in KDevelop.<br>
<br>
Another nifty idea would be being able to link bugs directly in the<br>
code. Using a simple template for URL, like<br>
<a href="http://bug_url.org?index=%index" \
target="_blank">http://bug_url.org?index=%index</a>, developers could just click and \
view<br> the bug in a browser (or in a KHTML window).<br>
<br>
As for your meta-data idea, would it have to be like information about<br>
the project specifically? If so, we could incorporate that into the<br>
project file and build a plasmoid that shows that information.<br>
<div class="im HOEnZb"><br>
><br>
> All the above is exactly the idea of our integrated plasma dashboard. If you<br>
> want, you can try to bring it up2speed and making it useable.<br>
><br>
> bye<br>
> --<br>
> Milian Wolff<br>
> <a href="mailto:mail@milianw.de">mail@milianw.de</a><br>
> <a href="http://milianw.de" target="_blank">http://milianw.de</a><br>
><br>
</div><div class="HOEnZb"><div class="h5">>>> Visit <a \
href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe <<<br>
<br>
>> Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe <<<br> </div></div></blockquote></div><br>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic