Proposal for GSoC, want to get your opinions

> If to be sincere, at this moment I'm a bit far from vcs
(just used
> cvs/svn commands to work with code). And my experience
in development
> consist of just few projects (sdlgraph for FPC,
QOrganizer fixes and
> from December I work with mozilla project - write
patches). 

I know a good way to get used to git - just start hacking on
KDevelop using 
git and git-svn. You'll then immediately know what you need
to implement in 
KDevelop ;)

PS: Unlike svk, git-svn actually works. I've started using
it for my other 
projects and I'm thinking I'll adopt it for KDevelop hacking
as well.

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

On Tue, Feb 26, 2008 at 9:38 AM, Alexander Dymo <dymoukrpost.ua> wrote:
> > If to be sincere, at this moment I'm a bit far
from vcs (just used
>  > cvs/svn commands to work with code). And my
experience in development
>  > consist of just few projects (sdlgraph for FPC,
QOrganizer fixes and
>  > from December I work with mozilla project - write
patches).
>
>  I know a good way to get used to git - just start
hacking on KDevelop using
>  git and git-svn. You'll then immediately know what you
need to implement in
>  KDevelop ;)
>
>  PS: Unlike svk, git-svn actually works. I've started
using it for my other
>  projects and I'm thinking I'll adopt it for KDevelop
hacking as well.

Don't bother. git-svn still doesn't do automatically
handling of
svn:externals so it won't build unless you manually copy
some stuff
over
--
Matt

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

2008/2/26, Alexander Dymo <dymoukrpost.ua>:
> I know a good way to get used to git - just start
hacking on KDevelop using
>  git and git-svn. You'll then immediately know what you
need to implement in
>  KDevelop ;)

Yeah 


-- 
E.I.

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

I have written the proposal, which I will use to submit
application.
I've used all you have told and thank to everyone for
suggestions and
ideas it helped me much to understand what should be done.

It will be cool if somebody review it:
http://docs.google.com/View?docid=df8cq4g8_14ngt57qx5


-- 
E.I.

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

On Saturday 08 March 2008 13:33:06 Evgeniy Ivanov wrote:
> I have written the proposal, which I will use to submit
application.
> I've used all you have told and thank to everyone for
suggestions and
> ideas it helped me much to understand what should be
done.
>
> It will be cool if somebody review it:
> http://docs.google.com/View?docid=df8cq4g8_14ngt57qx5

I've read it, it sounds fine.

But for the "further directions" part, I have a
suggestion what you could 
implement if you should have time left(before doing possible
incomplete 
backends for mecurial/bzr):
In gitk, you can view the source in a special mode, where
the whole code is 
highlighted by the exact commit and author that changed that
code. Holding 
the mouse over the highlighted code, a tooltop shows the
assigned author and 
commit-message for that code-line. Additionally it would be
great if the 
tooltip showed how the code looked before the commit.

That would be a great feature, and gitk shows that it's very
possible with 
git(opposed to svn).

Greetings, David

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

On 08.03.08 14:03:33, David Nolden wrote:
> On Saturday 08 March 2008 13:33:06 Evgeniy Ivanov
wrote:
> > I have written the proposal, which I will use to
submit application.
> > I've used all you have told and thank to everyone
for suggestions and
> > ideas it helped me much to understand what should
be done.
> >
> > It will be cool if somebody review it:
> > http://docs.google.com/View?docid=df8cq4g8_14ngt57qx5
> 
> I've read it, it sounds fine.
> 
> But for the "further directions" part, I have
a suggestion what you could 
> implement if you should have time left(before doing
possible incomplete 
> backends for mecurial/bzr):
> In gitk, you can view the source in a special mode,
where the whole code is 
> highlighted by the exact commit and author that changed
that code. Holding 
> the mouse over the highlighted code, a tooltop shows
the assigned author and 
> commit-message for that code-line. Additionally it
would be great if the 
> tooltip showed how the code looked before the commit.

I'm planning to add support for that to Kate in KDE4.1 or
4.2 (at the
latest), so we'd get such a border inside the kate editor.
Via the VCS
interfaces this would basically work out of the box for any
new VCS
plugin.

> That would be a great feature, and gitk shows that it's
very possible with 
> git(opposed to svn).

Huh? Ever tried Eclipse? Has exactly that feature and svn
annotate is
the underlying base command for that. Or did I miss
something?

Andreas

-- 
You're being followed.  Cut out the hanky-panky for a few
days.

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

On Saturday 08 March 2008 19:16:52 Andreas Pakulat wrote:
> > That would be a great feature, and gitk shows that
it's very possible
> > with git(opposed to svn).
>
> Huh? Ever tried Eclipse? Has exactly that feature and
svn annotate is
> the underlying base command for that. Or did I miss
something?
>
> Andreas

Sorry then, I mistakenly thought it wasn't easily possible
with svn because it 
hasn't all the information stored locally.

Greetings, David

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

On 08.03.08 19:27:35, David Nolden wrote:
> On Saturday 08 March 2008 19:16:52 Andreas Pakulat
wrote:
> > > That would be a great feature, and gitk shows
that it's very possible
> > > with git(opposed to svn).
> >
> > Huh? Ever tried Eclipse? Has exactly that feature
and svn annotate is
> > the underlying base command for that. Or did I
miss something?
> 
> Sorry then, I mistakenly thought it wasn't easily
possible with svn because it 
> hasn't all the information stored locally.

Uhm, thats completely correct. But with svn and no
connection to the
server you can't do much anyway. I mean nothing besides a
simple svn
diff works (and of course add/remove).

Andreas

-- 
You will contract a rare disease.

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

2008/3/8, David Nolden <zwabelgooglemail.com>:
> I've read it, it sounds fine.

Thanks a lot. I hope we will have a meeting in April about
project
details (discussion or how I should title it  ).

-- 
E.I.

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

On Saturday 08 March 2008 06:33:06 Evgeniy Ivanov wrote:
> I have written the proposal, which I will use to submit
application.
> I've used all you have told and thank to everyone for
suggestions and
> ideas it helped me much to understand what should be
done.
>
> It will be cool if somebody review it:
> http://docs.google.com/View?docid=df8cq4g8_14ngt57qx5

It's a decent start. I would make it look more organized
though. In years 
past, the submission form allowed for just plain text, so I
would optimize it 
for that. 

Thanks
--
Matt


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