A New idea for kdevelop IDE

[Vinay Khaitan]

I feel, some ideas requires to be experienced to know whethere it is really 
useful or not, because we cant figure out its uses and conveniences in 
advance.

Its okay if you dont like it. But I would give you some scenarios.
in a class, we have 15 actions and their slots.
those slots would be normally spread around the .cpp file and gives annyonance 
when trying to find the needed functions.
you may say that you should write actions slots at one place, but then IDEs 
are meant to help in such situations. normally we write functions as they 
come out to be needed.

do you think, user would search for all those 15 functions and fold them(even 
then it obstructs the thought-flow)?
what in case the file is closed and then opened again? fold them again?
The important point of idea is not just organisation but views!

what about the case, when I want to see all main functions together, when 
concentrating on class organisation? and then see functions and its helper 
functions together only, when I want to concentrate on functionality of a 
functions. //BEGIN doesn't solve this trouble.
sometimes a major functionality is spread over a few main functions. what in 
those cases?
sometimes functionalities are spread over classes and many files. Then?
Of course, much thought should be put into how these things will be 
implemented, but bottomline is that, do you realize its importance?

These days, almost all IDEs do the same things.
Provide a programming interface, class viewers, class 
makers,debugger,console,watches etc.
I think, this is time now to change the IDE paradigm radically(just like tenor 
and plasma is doing the same on dekstop front) and realise what developers 
faces problems subconciously in programming flow.  
For example:-
How many of us really use function/member maker dialogs? at least not me, 
whereas I am not an experienced programmer! I think it is simpler to write 
class by hand(without touching mouse even once) into a .h and .cpp file.
and write functions.
what should happen is that, they declare functions and member variables even 
in .cpp file(member within a function). then press a context sensitive 
keyboard shortcut/sequence(not applicationwide shortucts), and they would 
become either private/protected/public/signals/slots/functions/members of 
class automatically. (I know about F2 make member, but that is different 
thing)

above was just an example of very small things creating trouble in programming 
flow. There are loads of them. For example, the include file trouble as I 
reported in https://bugs.kde.org/show_bug.cgi?id=110694 
Hope, some of my ideas stick to one of the devs mind :D


Vinay Khaitan







On Tuesday 01 November 2005 03:44, Adam Treat wrote:

>
> As Jens has said, you could simply organize your methods and place //BEGIN
> and //END around the parts you don't want to see.  What else does adding
> other special comments give you?
>
> On Monday 31 October 2005 4:48 pm, Vinay Khaitan wrote:
> > I hope, you differentiate between code-folding and organisation!
> > code-folding+comments are useless for what I am asking for.
> > think again over the idea.
> >
> > On Tuesday 01 November 2005 03:11, Jens Dagerbo wrote:
> > > Hi,
> > >
> > > This sounds a lot like something that could be solved with simple "code
> > > folding", which is supported by katepart (the default editor in
> > > KDevelop).
> > >
> > > Enclose a block of code with
> > >
> > > //BEGIN helper functions go here
> > > ...
> > > ...
> > > //END
> > >
> > > and the editor with offer this block as collapsible.
> >
> > _______________________________________________
> > KDevelop-devel mailing list
> > KDevelop-devel at barney.cs.uni-potsdam.de
> > http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel