kdevelop2.0

[Bernd Gehrmann]

On Thu, 14 Dec 2000, Richard Dale wrote:

> On Wed, 13 Dec 2000, Bernd Gehrmann wrote:
> > On Tue, 12 Dec 2000, Richard Dale wrote:
> > > Currently in the 'cppsupport' part there are classes to add a new method and new
> > > attributes to a class (CAddClassAttributeDlg and CAddClassMethodDlg). I think
> > > this functionality should be associated with a 'New Class Wizard' or similar
> > > part.
> > 
> > Well, I hesitated to increase the number of shared libraries even more
> > because the startup time is already horrible...
> > Anyway, I think it would be better to turn these menu items into
> > node actions (like in the cvs part).
> Should xxxsupport parts be loaded at startup, but wizards loaded lazily, on
> demand (is that what 'node actions' would achieve?).

No, my statement about actions is independent from the previous point.
Currently the menu items in the classview are generated by the class
view itself. As a consequence, the possible menu items are restricted.
It would be more flexible if the language support part could insert
arbitrary stuff into the menus. This can be achieved by using something
like

  QList<KDevNodeAction> actionList;
  emit part->needKDevNodeActions(methodNode, &actionList);
  QListIterator<KDevNodeAction> it(actionList);
  for (; it.current(); ++it)
      it.current()->plug(popupMenu);

(not tested...)

Bernd.


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