Hi Reinier, This wiki page [1] will give you more information on extending the cms, and the extensions-directory.
You can specifically point to a folder or pipeline in the extensions by using extensions://. So for example of you want to use a pipeline in the extensions/myxinha-folder you can use extensions://myxinha/resources/etc In the URL you can point to it by using http://localhost:<port>/extensions/myxinha/etc Regards, Steven [1] http://wiki.hippo.nl/display/CMS/08.+Extending+Hippo+CMS -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Reinier van den Born Sent: dinsdag 28 oktober 2008 12:26 To: Hippo CMS development public mailinglist Subject: Re: [HippoCMS-dev] Xinha questions Hi Steven, Jasja, or anyone else, Sorry for the delay but other activities came in between. Finally got back to try the suggestions made. They didn't work so I made an effort to understand how things work and what your suggestions are trying to achieve. Below my findings. It is very likely that I missed something, so I'd appreciate any help or an alternative solution that does work. As I understand, to achieve what I want, I need to replace the Xinha that is part of the standard CMS editor distribution. The CMS frame loads the script using the URL "/cforms/resources/xinha/htmlarea.js". So all we need to do is convince cocoon to serve my Xinha instead of the standard one. The suggestion Jasha gives does not do this. This mechanism is used in our project, but with the purpose to customise Xinha (which buttons are present, etc) and still relies on the standard Xinha to be loaded. I guess I could use this method to load another Xinha together with the old, hoping it will overwrite the standard definitions. Or would I need to change all names in Xinha?? Didn't seem a very neat solution, so I dropped it. Steven suggests to put my Xinha in extensions/project-specific/... First problem is that I do not have an extensions/project-specific directory. The "project-specific" setup is referenced in a few forum messages, but I haven't found any real explanation. Just creating this directory and sitemap doesn't do it. Going through the site/sitemap etc. I found that one can set cms.project-specific.sitemap in (eg) build.properties. But when I set this to cocoon://extensions/project-specific/sitemap.xml, logical choice (?), it still doesn't give me my Xinha. Which makes sense since if I look at the site/sitemap I see that project-specific is only used on URLs starting with project-specific. So urls like http://localhost:<port>//project-specific should get me into the sitemap I configured. Which seems to work although I do get the odd error message: The current URI (/project-specific/cforms/resources/xinha/htmlarea.js) doesn't start with given prefix (project-specific) So clearly I am doing something wrong. But anyway the goal was to have cocoon serve something different on the old URL, which I don't think this will do. Since we are replacing standard functionality I also looked at the instructions at: http://www.hippocms.org/display/CMS/Overriding+core+CMS+code I created extensions/cforms/overrides.xmap, moved Xinha in etc., but that didn't work either. I found that site/sitemap has an explicit pipeline matching cforms/resources/** so it never looks at the override possibility (which is all the way at the bottom of the sitemap). Thanks, Reinier Jasha Joachimsthal wrote: > The location of the Xinha configuration is done in the business logic of > your template. > The default location (in the samples is): > <libs> > <!-- declare a code library > 'src' is a html uri, in this case we use the default library > --> > <lib src="/editing/cf2/js/htmlarea.js"/> > </libs> > > All lib's are converted into script tags. > > Jasha Joachimsthal > > [EMAIL PROTECTED] - [EMAIL PROTECTED] > > www.onehippo.com > Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 > San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA > 94952-3329 +1 (707) 773-4646 > > > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> Steven Grijzenhout >> Sent: vrijdag 10 oktober 2008 11:04 >> To: Hippo CMS development public mailinglist >> Subject: RE: [HippoCMS-dev] Xinha questions >> >> Hi Reinier, >> >> If I'm correct, xinha is configured in >> editor\src\site\cforms\resources\xinha\htmlarea.js. You can >> override this file with your own configuration by creating >> the file >> extensions\project-specific\cforms\resources\xinha\htmlarea.js. >> >> In the project-specific folder you have to add this pipeline to your >> sitemap: >> >> <map:match pattern="cforms/**"> >> <map:read src="cforms/{1}"/> >> </map:match> >> >> This way, you can also add plugins. For example by adding >> project-specific\cforms\resources\xinha\plugins\InsertLink\ins >> ert-links. >> js. >> >> Steven >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> Reinier van den Born >> Sent: woensdag 8 oktober 2008 17:43 >> To: Hippo CMS development public mailinglist >> Subject: [HippoCMS-dev] Xinha questions >> >> >> Hi, >> >> I have a couple of questions about Xinha: >> >> Q1: >> I would like to add some plugins to Xinha that don't come >> standard with the Hippo editor (eg. definition lists). >> And fiddle with/replace some that are standard (because they >> don't place themselves correctly on the toolbar). >> >> I was hoping to be able to add the plugins somewhere down my >> extensions folder and tell Xinha to look there, but haven't >> found a way to do this. >> Any suggestions? >> >> Q2. >> Looking through the Xinha docs I don't see any reference to >> the type of HTML it generates: >> XHTML, HTML 4.01, or some older version. >> It looks like it is XHTML. If so, is there a way to tell it >> to generate HTML 4.01? >> >> Q3. >> I noticed some keyboard shortcuts are defined for Xinha >> (<ctrl-1> for H1, etc). >> They have apparently nothing to do with the plugin that >> allows changes like that from the toolbar. >> So is there a way to disable these boys? >> (I don't want to allow content editor anything but entering >> plain text, lists, emphasis etc.) >> >> Any help is greatly appreciated. >> >> Thanks, >> >> Reinier van den Born >> >> -- >> >> Reinier van den Born >> >> HintTech B.V. >> Rotterdamseweg 183c, 2629 HD Delft >> T: +31(0)15 268 2573 >> F: +31(0)15 268 2567 >> M: +31(0)6 494 171 36 >> -- >> HintTech levert specialisten op het gebied van >> softwareontwikkeling (.NET en Java), projectmanagement, >> informatiebeveiliging en business consulting. >> KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01 >> ******************************************** >> Hippocms-dev: Hippo CMS development public mailinglist >> >> Searchable archives can be found at: >> MarkMail: http://hippocms-dev.markmail.org >> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >> >> > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > -- Reinier van den Born HintTech B.V. Rotterdamseweg 183c, 2629 HD Delft T: +31(0)15 268 2573 F: +31(0)15 268 2567 M: +31(0)6 494 171 36 -- HintTech levert specialisten op het gebied van softwareontwikkeling (.NET en Java), projectmanagement, informatiebeveiliging en business consulting. KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01 ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
