Porting CTags plugin

I'd like to port CTags plugin, one of the plugins I like
most.

Does the CTags maintainer have plan to port it someday?
IIRC,
I saw him on list this february but I didn't see him
afterward.

Where should Ctags go? I think kdevplatform is suitable
place for it.
but I'm double check because other people can have different
opinion
from me.

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

On 10.06.07 14:28:07, dukju ahn wrote:
> I'd like to port CTags plugin, one of the plugins I
like most.
> 
> Does the CTags maintainer have plan to port it someday?
IIRC,
> I saw him on list this february but I didn't see him
afterward.

Megan is not the Maintainer, but she worked on it. It seems
that she
currently doesn't have much time. Also she wanted to look
into other
tools than CTags, on my list there's also CScope.

> Where should Ctags go? I think kdevplatform is suitable
place for it.
> but I'm double check because other people can have
different opinion
> >from me.

No, KDevPlatform is for stuff that can be used in any
application thats
built on it and we should strive to keep the plugin list
there small.

Also I actually hope that Ctags is not needed in KDevelop4,
because the
language support will provide whats needed to get the same
things.

Andreas

-- 
Excellent day for putting Slinkies on an escalator.

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

2007/6/10, Andreas Pakulat <apakugmx.de>:
> On 10.06.07 14:28:07, dukju ahn wrote:
> > I'd like to port CTags plugin, one of the plugins
I like most.
> >
> > Does the CTags maintainer have plan to port it
someday? IIRC,
> > I saw him on list this february but I didn't see
him afterward.
>
> Also I actually hope that Ctags is not needed in
KDevelop4, because the
> language support will provide whats needed to get the
same things.

Idealy, but language support can't be perfect, while CTags
is perfect.
Think about the KDev3 language supports. The CTags can
lookup
even macros or variable definitions, while language support
can't.
I useually use jump to XXX or QuickOpen part, but there is
some case
where only Ctags is really helpful.

Currently, we don't have any promise that each language
support
would be that perfect.

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

On Monday 11 June 2007 04:22:30 dukju ahn wrote:
> Idealy, but language support can't be perfect, while
CTags is perfect.
> Think about the KDev3 language supports. The CTags can
lookup
> even macros or variable definitions, while language
support can't.

c++-support in kdevelop-3.4.1 can lookup macros as well as 
variable-definitions, even such that ctags cannot lookup
because it only 
processes a specific directory. Also ctags cannot respect
the context, so I 
don't see why ctags should be superior in any way to
language support.

Of course kdevelop-3.4's c++ support is limited, but I don't
see where ctags 
should be superior, and kdevelop-4's c++ support will
probably be a lot 
better.

> I useually use jump to XXX or QuickOpen part, but there
is some case
> where only Ctags is really helpful.

Then we should analyze that case and see how we can solve it
with our own 
system. 

> Currently, we don't have any promise that each language
support
> would be that perfect.

Ok, for other languages than C++ I can see that it could
become useful..

greetings, David


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

2007/6/11, David Nolden <david.nolden.kdevelopart-master.de>:
> On Monday 11 June 2007 04:22:30 dukju ahn wrote:
> > Idealy, but language support can't be perfect,
while CTags is perfect.
> > Think about the KDev3 language supports. The CTags
can lookup
> > even macros or variable definitions, while
language support can't.
>
> c++-support in kdevelop-3.4.1 can lookup macros as well
as
> variable-definitions, even such that ctags cannot
lookup because it only
> processes a specific directory. Also ctags cannot
respect the context, so I
> don't see why ctags should be superior in any way to
language support.
>
> Of course kdevelop-3.4's c++ support is limited, but I
don't see where ctags
> should be superior, and kdevelop-4's c++ support will
probably be a lot
> better.

Ahh, yes I overlooked the downsides of CTags, and I didn't
know the
macro support in C++. Anyway, my intention was that I
usually use language
support but I sometimes need CTags's aid.
Both are not competing ones for superiority, rather they can
compensate
each other. But, see the bottom of this mail.

> > I useually use jump to XXX or QuickOpen part, but
there is some case
> > where only Ctags is really helpful.
>
> Then we should analyze that case and see how we can
solve it with our own
> system. 

Beacause It's just not implemented. QuickOpen opens only
file/class/methods
and is perfect only for them. Searching macro is not
implemented.

> > Currently, we don't have any promise that each
language support
> > would be that perfect.
>
> Ok, for other languages than C++ I can see that it
could become useful..

Yes. there are many language supports other than C++.

Well, then I changed my mind. It is right thing to improve
language supports
, rather than reling on other tools. I'll not port it.

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

> No, KDevPlatform is for stuff that can be used in any
application thats
> built on it and we should strive to keep the plugin
list there small.

Please have a look here: http://ct
ags.sourceforge.net/languages.html

It seems that HTML and PHP are supported, so I would suggest
to move it into 
the platform so that Quanta users could use it too.

Jens

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

Andreas Pakulat wrote:
> Also I actually hope that Ctags is not needed in
KDevelop4, because the
> language support will provide whats needed to get the
same things.

...as long as 'the same things' includes a symbol view ala
the current 
ctags view, i.e. something I can type symbols into to see a
list of all 
things that start with that symbol (and can click to go to
symbols). 

-- 
Matthew
Ngx iqct zgg dxei zodt gf ngxk iqfrl.


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

On 11.06.07 15:42:41, Matthew Woehlke wrote:
> Andreas Pakulat wrote:
> > Also I actually hope that Ctags is not needed in
KDevelop4, because the
> > language support will provide whats needed to get
the same things.
> 
> ...as long as 'the same things' includes a symbol view
ala the current 
> ctags view, i.e. something I can type symbols into to
see a list of all 
> things that start with that symbol (and can click to go
to symbols). 

Hmm, I think I need to add a Alt+<num> shortcut for
that toolview. That
is indeed quite handy...

Ok, I confess I was wrong: Porting the CTags Plugin is a
good idea.

Andreas

-- 
You'll feel much better once you've given up hope.

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

On Jun 10, 2007, at 1:28 PM, dukju ahn wrote:

> I'd like to port CTags plugin, one of the plugins I
like most.
>
> Does the CTags maintainer have plan to port it someday?
IIRC,
> I saw him on list this february but I didn't see him
afterward.
>
> Where should Ctags go? I think kdevplatform is suitable
place for it.
> but I'm double check because other people can have
different opinion
> from me.
>

This needs to wait. It's not apparent that we'll need the
CTags  
plugin yet. We have other things that need doing, IMHO.
--
Matt



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

On 11.06.07 19:40:38, Matt Rogers wrote:
> 
> On Jun 10, 2007, at 1:28 PM, dukju ahn wrote:
> 
> > I'd like to port CTags plugin, one of the plugins
I like most.
> >
> > Does the CTags maintainer have plan to port it
someday? IIRC,
> > I saw him on list this february but I didn't see
him afterward.
> >
> > Where should Ctags go? I think kdevplatform is
suitable place for it.
> > but I'm double check because other people can have
different opinion
> > from me.
> >
> 
> This needs to wait. It's not apparent that we'll need
the CTags  
> plugin yet. We have other things that need doing,
IMHO.

Also porting ctags if the need arises is rather simple, its
just a few
hundred locs and no rocket science in there. The hardest
part is
probably coming up with a mvc-design for the gui.

Andreas

-- 
Beware of a tall blond man with one black shoe.

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