Branding cleanup: KDE menu -> TDE menu.

pull/1/head
Darrell Anderson 13 years ago
parent da88b484aa
commit 8f661016cd

@ -6,7 +6,7 @@
It would need to load all the shared libs, have a JVM ready to roll straight
into the main() method of the main class, and then fork() on demand...
- Integrate java apps with the KDE menu system, so they can be invoked just like C++ ones.
- Integrate java apps with the TDE menu system, so they can be invoked just like C++ ones.
- Find any missing, but important callbacks (similar to KMainWindow::queryClose()).
Add the callbacks to the relevant C++ 'JBridge..' classes, so java sub-classes

@ -12,11 +12,11 @@ import org.kde.qt.TQObject;
/**
DCop client menu class for the Kicker panel that will insert a submenu into
the %KDE menu.
the %TDE menu.
See {@link KPanelAppMenuSignals} for signals emitted by KPanelAppMenu
@author Daniel M. Duley <mosfet@kde.org>
@short DCop client menu class for the Kicker panel that will insert a submenu into the %KDE menu.
@short DCop client menu class for the Kicker panel that will insert a submenu into the %TDE menu.
*/
public class KPanelAppMenu extends TQObject implements DCOPObjectInterface {

@ -514,7 +514,7 @@ public class KService extends KSycocaEntry {
/**
Returns a path that can be used to create a new KService based
on <code>suggestedName.</code>
@param showInMenu true, if the service should be shown in the KDE menu
@param showInMenu true, if the service should be shown in the TDE menu
false, if the service should be hidden from the menu
@param suggestedName name to base the file on, if a service with such
name already exists, a prefix will be added to make it unique.

@ -89,7 +89,7 @@ class MainWin < KDE::MainWindow
# code will create menu/toolbar items and place them *automatically*
# if you defined the KDE::StdActions as below. In fact, you can't override
# this behavior using KDE::StdActions - if you want menus to be "non-standard"
# KDE menus (eg 'Cut' in the 'File' menu), you'll need to create your
# TDE menus (eg 'Cut' in the 'File' menu), you'll need to create your
# actions from KDE::Action instead of KDE::StdAction. Obviously it makes more
# sense to use the mechanism provided to produce consistent menus and
# toolbars. You can "unplug" items if, for example, you don't want them

Loading…
Cancel
Save