[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:       Milian Wolff <mail () milianw ! de>
Date:       2012-02-29 20:39:08
Message-ID: 12208225.0JYXMTSnmv () minime
[Download RAW message or body]

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

> 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 <<
-- 
Milian Wolff
mail@milianw.de
http://milianw.de

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]