update remaining links to git repository
← Older revision
Revision as of 19:21, 23 June 2011
Line 24:
Line 24: == How does merging happen == == How does merging happen ==−The first thing that happens is that the ui.rc file of you application is merged in the KDE global [http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/xmlgui/ui_standards.rc?view=markup ui_standards.rc]-file. This is to make sure that standard elements all end up in the KDE standard places.+The first thing that happens is that the ui.rc file of you application is merged in the KDE global [https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/entry/kdeui/xmlgui/ui_standards.rc?view=markup ui_standards.rc]-file. This is to make sure that standard elements all end up in the KDE standard places. Now, when you add further KXMLGUIClients (e.g. a KPart, or a plugin), in general the KXMLGUIFactory does the following: Now, when you add further KXMLGUIClients (e.g. a KPart, or a plugin), in general the KXMLGUIFactory does the following:Line 152:
Line 152: === <MergeLocal> === === <MergeLocal> ===−This can only be used in the KDE global [http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/xmlgui/ui_standards.rc?view=markup ui_standards.rc]-file. It defines points where other entries can be merged in. It can be used both with a ''name''-attribute, or without (in the latter case it acts as a catch-all merge place).+This can only be used in the KDE global [https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/entry/kdeui/xmlgui/ui_standards.rc?view=markup ui_standards.rc]-file. It defines points where other entries can be merged in. It can be used both with a ''name''-attribute, or without (in the latter case it acts as a catch-all merge place). Then, in your RC file, you can add a certain action or menu to a given MergeLocal. Then, in your RC file, you can add a certain action or menu to a given MergeLocal. - Full Post
.
ReplyDelete