Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by drseuk: http://wiki.apache.org/lenya/HowToEditCustomDoctypesWithBXE The comment on the change is: Cosmetic ------------------------------------------------------------------------------ = Overview for the impatient = Change four lines in usecase-bxeng.xmap: + + == BXE Namespaces == {{{ <map:part src="../../resources/misc/bxeng/content-namespaces.xml"/> }}} @@ -13, +15 @@ <map:part src="resources/misc/bxeng/{page-envelope:document-type}-namespaces.xml"/> }}} and + + == BXE Config == + {{{ <map:generate src="../../resources/misc/bxeng/inc/config.xml"/> }}} @@ -21, +26 @@ <map:generate src="resources/misc/bxeng/inc/{page-envelope:document-type}-config.xml"/> }}} and + + == BXE Config XSL file == + {{{ <map:transform src="../../xslt/bxeng/config-xml.xsl"> }}} @@ -29, +37 @@ <map:transform src="xslt/bxeng/{page-envelope:document-type}-config-xml.xsl"> }}} and + + == BXE Context Menu == + {{{ <map:parameter name="contextmenufile" value="../../resources/misc/bxeng/contextmenu.xml"/> }}} @@ -70, +81 @@ }}} The text "Edit with BXE" is actually a key in cellar/../../resources/i18n/cmsui.xml and the other cmsui_nn.xml files where nn is the language code for the menu text etc. In cmsui.xml (and indeed, bizarrely, in all the other cmsui_nn.xml too!) this key is associated with the text you actually see on the menu, namely "WYSIWYG Editor (BXE)". - Anyway, so the BXE line in the code above says "go inside the usecase-bxeng.xmap file and start at the 'open' step with a href of '?' ". The usecase-bxeng.xmap file is in {pub}. You may wonder where the other usecase files for the other editors (the "One big form editor/ 1formeditor / Source editor" or whatever it's called this week, the "Forms Editor" and Kupu) are. There're in cellar/../../usecases. Strange? Well, not really. The one form editor works with all doctypes out of the box so why would you want to customise it on a per publication basis? Similarly, the only customisation likely to be needed for the multiple "Forms Editor" is in your custom doctypes' cellar/lenya/xslt/formeditor/wine.xsl file. Kupu only supports XHTML so again is not likely to need customising. Keeping the usecases up the tree just keeps the out of the way and makes sense. + Anyway, so the BXE line in the code above says "go inside the usecase-bxeng.xmap file and start at the 'open' step with a href of '?' ". The usecase-bxeng.xmap file is in {pub}. You may wonder where the other usecase files for the other editors (the "One big form editor/ 1formeditor / Source editor" or whatever it's called this week, the "Forms Editor" and Kupu) are. There're in cellar/../../usecases. Strange? Well, not really. The one form editor works with all doctypes out of the box so why would you want to customise it on a per publication basis? Similarly, the only customisation likely to be needed for the multiple "Forms Editor" is in your custom doctypes' cellar/lenya/xslt/formeditor/wine.xsl file. Kupu only supports XHTML so again is not likely to need customising. Keeping the usecases up the tree just keeps them out of the way and makes sense. The usecase-bxeng.xmap file by contrast is in cellar precisely because we (may) need to change it presumably. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
