New TODO list for 2.0 (23/04/2001)

[F@lk Brettschneider]

Hi,

So what is still to do for version 2.0? What are known bugs?
------------------------------------------------------------
- Tab page mode of QextMDI is in alpha stage. That's why the
  version of QextMDI is called 2.0pre. Many cases for that mode simply
  aren't implemented yet. For instance switching through the MDI modes.
  I only actived Tab Page mode to let developers the oportunity to
  finish the implementation of that MDI mode if there was a volunteer.
  In case of timeout, I simply will disable Tab page mode, and we will
  only have Childframe MDI mode and Toplevel MDI mode for KDevelop-2.0
  (like in QextMDI-1.0).

- tree and output tool-views:
    - the toolbar buttons for showing/hiding the trees/outputviews
      are reimplemented for a compound group of dockwidgets
      but the mechanism still doesn't work in all cases
    - tool view states (geometry, position,...) aren't saved to
      kdeveloprc yet (usuability safety)

- Choosing the default MDI mode by an additional dialog widget in the
  KDevelop _setup_ program isn't implemented yet.

- the MDI view taskbar isn't restored properly although it is saved to
  kdeveloprc in the right way.
  And there's a flicker effect in the taskbar from time to time, seems
  to be an event cycle in QextMdiTaskBar::layoutTaskBar()

- editor:
  - Closing an editor view doesn't ask for saving if it was changed
  - An anoying question because of 'changed outside the editor' always
    appears although not changed outside
  - Setting the editor cursor by activating the editor view doesn't
    work in all cases. The reason seems to be that setFocus() for the
    embedded editor widget isn't always called if you activate the
    covering widgets (Scrollbar, view frame window, caption...)

- Proper enabling/disabling of toolbarbuttons/menuitems depending on the
  program state doesn't work correctly. Often some "actions" are allowed
  which do not make sense in that certain situation. 

- Printing is currently under rebuild by JBB. It will be based on
  KPrinter. Actually finished?

- Code completion buildin of KDEStudio is still missing. I've no idea to
  get the official KDEStudio version work here with a SuSE-7.0 system.
  I gave up code completion and focus on the MDI again.
  Roland put in the ctags support which can be the base of a code
  completion...

- code cleanup is needed.

--------
Well, this is the current TODO list, maybe I forgot something you could
add. Probably we can put this on a public TODO list.

I would highly appreciate your help. Don't hesitate to focus on one or
two of the issues. Then we will become quite stable until 8. May.

Ciao,
F at lk

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


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