improving context browser for declarations in file
mail at milianw.de
Fri Sep 10 17:21:17 UTC 2010
On Friday, 10. September 2010 18:34:56 David Nolden wrote:
> Yes, i also already though about improving this. Your idea is good. Also
> namespace- or class-scopes shouldn't be shown again and again, and we coulf
> abbreviate functions by parens, for variables we could shorten the prefix
> to just "var", etc. It could look like extremely simplified code.
I've made sure the decls are unique (decl->kind & decl-
But I'm not sure about the rest. If I merge the kind, it looks strange:
Function foo, bar, asdf, Namespace yxcv, qwer, Function öouir
If I add () behind functions it beomces better, but still:
Function foo(), bar(), asdf(), Namespace yxcv, qwer, Function öouir()
it should be Function_s_, Namespace_s_... but declarationKind() does not give
that info of course. But we should use declarationKind to stay language
independent, shouldn't we? This also prevents using "var" instead of
> Am 10.09.2010 17:42 schrieb "Milian Wolff" <mail at milianw.de>:
> Hey there,
> a user (blender dev) showed me this screenshot with the plea to improve it:
> I hope we all agree that this is completely bad. His idea where the "all,
> funcs, used funcs, ..." buttons to the left which are nice but imo hard to
> implement with the current api (or am I mistaken?).
> For starters I thought about at least grouping the declarations by kind.
> Imo it would be better, but right now the declarations are listed in the
> order they are declared which is probably also helpful. So maybe we could
> at least merge consecutive declarations of the same kind?
> Like so:
> Typedef foo, Typedef bar, Function abc, Function asdf, Class foo
> Typedefs foo, bar, Functions abc, asdf, Class foo
> What do you think?
> Milian Wolff
> mail at milianw.de
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
mail at milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part.
More information about the KDevelop-devel