Fwd: Bug#27716: see function under container file in project treeview

[Bernd Gehrmann]

On Fri, 29 Jun 2001, jbb wrote:
> I agree with this one.
> a c file usually reflects a "module".

Same for Perl. Maybe we need a symbolview part in addition
to the class view. The complexity in the class view is already
very high, and it will even slightly increase when some code
to disable certain items is added (e.g. in Java and Python
the 'Goto declaration' doesn't make sense). For non-OO languages
the class view (with some options more) is also not ideal from
a ui point of view. 

> And another wish for kdevelop3.0
> can we have the global namespace as well in the class view
> ie
> + global
> + KIO
> + blah
> Otherwise most of the classes are missing.

Probably... I also wonder how the class parser handles anonymous
namespaces.

> and yet another
> in the other mode (not namespace) rather than just every class in the tree 
> how about spliting them into the subdirs they are in - presumably the 
> programmer did that to organise the files. Having the dir structure reflected 
> in the tree would be better that everyclass merged.

It's already in the TODO file...

> options upon options eh :-)

Well, yes, actually splitting classes into sub directories isn't unique
- you can also do that with differents depths. For example, if you have
directories foo and bar with nested directories fooblah? and barblah?, you
can display this as

  foo/fooblah1
      class Quarximurksel1
      class Quarximurksel2
  foo/fooblah2
      class Quarximurksel3
      class Quarximurksel4
  bar/barblah1
      class Bimmel1
      class Bimmel2
  bar/barblah2
      class Bommel1
      class Bommel2

or 

  foo
      Quarximurksel1
      Quarximurksel2
      Quarximurksel3
      Quarximurksel4
  bar 
      Bimmel1
      Bimmel2
      Bommel1
      Bommel2

Now which one do you prefer? Or should that be configurable too? ;-)

Bernd.


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«