Introduction ...

2007/4/24, Sandro Andrade <sandro.andradegmail.com>:
>
> Hi all,
>
> I would like to present myself and expose my desire to
contribute to
> KDevelop project.
> I hope to become an effective KDevelop contributor and
I would be grateful
> for some initial guidelines. I have successfully
compiled the last snapshot
> for KDE 4.
>

Welcome!

I am also quit a new person so my guideline wouldn't be
that useful but..

http://www.kdevelop.org/mediawiki/index.php/KDevelop_4


Here is kdevelop4 architecture design. Among them the title
named
as "KDevelop 4 Platform Information" is useful.

http://techbase.kde.org/
and http://api.kde.org/

These are common for all kde apps. Also there is KATE CTags
plugin in http://www.kde-apps.org/


To send us a patch, use svn diff.

Currently there are many things that aren't implemented
yet.
Review the wiki, source codes and find the not implemented
part.
You can grab one component and implement it.

Thanks.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 24.04.07 23:06:09, Sandro Andrade wrote:
> I hope to become an effective KDevelop contributor and
I would be grateful
> for some initial guidelines. I have successfully
compiled the last snapshot
> for KDE 4.

Welcome 

First things to do apart from what dukju said is to compile
the latest
svn version of qt-copy,kdelibs,strigi,kdepimlibs,kdebase and
kdevelop
(thats what you need to get fully "functional"
kdevelop4). Then browse
around the code, try to understand it and see what interests
you have.
If you found something and work on it, send the patches to
this list and
we'll review them.

Once you've sent a couple of patches and we found them to be
good you
may apply to get your own svn account so you can check in
directly.

Andreas

-- 
You will remember something that you should not have
forgotten.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Wednesday, 25. April 2007, Sandro Andrade wrote:
> My first doubt is: I successfully compiled the qt-copy,
strigi, kdelibs,
> kdepimlibs, and kdebase as suggested in
> h
ttp://techbase.kde.org/Getting_Started/Build/KDE4.
> After checkout the last KDevelop snapshot I tried to
follow the
> instructions in
> http://www.kdevelop.org/index.html?filen
ame=HEAD/branches_compiling.html,
> but there is no admin/Makefile.common file in the svn
tree !!!
>
> I was able to successfully compile KDevelop4 simply by
executing cmakekde !
> Is this the right procedure for compilation ? Is the
website information
> out of date ?

Yes, the website is out of date. admin/Makefile.common and
all the other 
autotools stuff stems from KDE 3 times, while everything in
KDE 4 is done 
with cmake, or cmakekde for that matter.

Wishing the best of luck for your contribution efforts,
  Jakob

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

A welcome from me too, the important things are said
already. 

Have fun!

greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Wednesday 25 April 2007 15:21:00 Jakob Petsovits wrote:
> On Wednesday, 25. April 2007, Sandro Andrade wrote:
> > http://www.kdevelop.org/index.html?filen
ame=HEAD/branches_compiling.html,
> > but there is no admin/Makefile.common file in the
svn tree !!!
> >
> > I was able to successfully compile KDevelop4
simply by executing cmakekde
> > ! Is this the right procedure for compilation ? Is
the website
> > information out of date ?
>
> Yes, the website is out of date. admin/Makefile.common
and all the other
> autotools stuff stems from KDE 3 times, while
everything in KDE 4 is done
> with cmake, or cmakekde for that matter.

Could someone post up-to-date instructions for KDevelop4 on
the wiki ?
I could them port it to the "normal" website.

-- 
Amilcar Lucas
Webmaster
The KDevelop project

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 24.04.07 23:06:09, Sandro Andrade wrote:
> Hi all,
> 
> I would like to present myself and expose my desire to
contribute to
> KDevelop project.
> 
> My name is Sandro Andrade and I've been using FreeBSD
and GNU/Linux since
> 1997 both as user and developer, with special interest
in development using
> the standard C++ language.
> I've been working for the past eight years with object
oriented-design and
> implementation using C++ and I am a quite appraiser and
full-time user of
> KDevelop and Qt technologies. Qt3 and KDevelop have
been my major
> development technologies in the last four years and
recently I join a
> research project that relies entirely on Qt4.
> 
> As part of my master dissertation, I've been designing
and developing a
> reusable component-based platform for industrial data
acquisition based on
> CORBA Component Model (CCM), the CIAO
(Component-Integrated ACE ORB)
> middleware ( 
> http://www.cs.wustl.
edu/~schmidt/TAO.html<http://www.cs.wustl.edu/%7Eschmidt/
TAO.html>),
> and Qt3. Our project, called ARCOS ( http://arcos.sf.net),
encompass a OMG
> DAIS (Data Acquisition from Industrial Systems)
Standard implementation and
> qt3-based client applications for industrial
supervision.
> 
> I hope to become an effective KDevelop contributor and
I would be grateful
> for some initial guidelines. I have successfully
compiled the last snapshot
> for KDE 4.

Hey, the plugins/teamwork code is pretty new and surely not
occupied by
anybody. Its also rather large and uses every C++ feature
you can think
of (thats what I've been told). So if you have a good
knowledge of C++
including advanced templates and maybe you know boost, then
that plugin
is a great starting point.

For starters the include's need to be worked over,
duplicates removed
(like a .cpp including foobar.h and bar.h and foobar.h
includes bar.h
too), includes should be moved from .h to .cpp as far as
possible. Also
I saw a few #include's in the middle of .cpp files, that
needs to be
changed too.

Then it would be cool to look into the libdiff2,network and
dynamictext
libraries and see which of the classes and functions are
used by the
teamwork plugin and which are internal to those libraries.
Those that
form the public API need to use a proper _EXPORT macro so we
can make
the libs shared libs.

I also think it could be beneficial to split up some of the
larger
header files and eventually rename all files to not have any
underscore.

Thats all that came to my mind about the plugin, I know some
of these
things are tedious (like the include cleanup), but they also
allow you
to get to know the code in the plugin.

Andreas

PS: Of course I don't want to push you into working on that
plugin, but
at least there's a "plan" of what needs to be done
to it...

-- 
Your present plans will be successful.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel