Remaining issues

[Bernd Gehrmann]

Let me first say that I enjoyed Linuxtag very much. It
was nice to see and speak with several people in real
life, in particular Christian whom I hadn't seen before.
Oh, and Thomas and Cornelius... the number of people
contributing to KDevelop is really significant nowadays :-)
Discussing things when you're sitting face-to-face is
certainly some orders of magnitude more efficient than
doing it online. It was also fun to demonstrate KDevelop 
and show that writing plugins is not rocket science :-)
Now, back to work... btw if you ever see a nice girl
with a cool Trolltech t-shirt in Berlin or Basel, then
that might be my flatmate ;-)

Unfortunately, it was not really possible to get all
people together at the same time in order to discuss
what has to be done in the HEAD branch. So I've made
a little list of what I remembered afterwards from
various occasions, and who will work on it... any 
comment or addition is welcome:

* The mechanism for deciding which plugins are loaded for a 
  project (1. the Context flag in the desktop file and 
  2. the <ignoreparts> tag created by the appwizard) does not
  scale for the ever-increasing number of plugins, in particular
  not for 3rd-party plugins. It also requires much maintainance
  for the template project files. One further possibility we
  came up with is deciding on the programming language (where
  several languages can be specified) and key words (e.g. for
  simulators etc.) => Sandy

* The Add class needs to be readded and adjusted to our framework
  which allows an arbitrary number of targets and subdirectories.
  Need some kind of 'active target' => Bernd

* Code completion: This should be fairly easy to implement for
  PHP and Python. Need an editor interface for this and implement
  the popup. Qt designer should give some inspiration for this :-)
  => Sandy. I will do the Python stuff then.

* Need access to the status bar for parts (e.g. the debugger displays
  its current state as a single letter in the status bar)
  => Matthias? You should ignore my StatusBar class for this.
  Maybe later I'll come back to what I originally intended for it,
  but this has very low priority.

* Matthias E's talk about Qt's component model and the qt_invoke
  stuff was very interesting for the scripting implementation.
  So I guess we'll wait and see whether we can use that and put
  my pydcop implementation on ice meanwhile, and maybe dump it
  later. Apart from the technical implementation, scripting has to
  become more user-friendly, allow the user to store different
  files and edit them... since kmud has copied our component 
  design for its architecture, maybe we can let them do this and 
  then copy it back for a change ;-)

* Granularity of parts: Have we come to any conclusion on this?

* Editor stuff: I think Matthias knows what to do here :-) BTW,
  the TextEditorDocument::isEditing() from lib/texteditor.h is
  still not in the framework...

* Scripting project has to detect added files => Bernd
  Maybe also removing files... hmm.

Bernd.


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