How I can add a button to the right click menu?
And how to register the command of the menu item?

If you want to save it, it must have some representation in the xml file, for example as elements. Then you would have to edit your xslt to render these elements with a different background.

To apply these elements, you can make a selection, either a small portion of an element or a selection that spans more elements, and when you apply it several elements are created, one for each parent element.

To create such a highlight, you would have to make a button that loops through the selection and creates the elements where needed, look at http://xopus.com/documentation/api/dom/xopusrange.htmlhttp://xopus.com/documentation/api/dom/xopusrange.html for a starting point on how to do this.

Hello Fredrik,
I tried this example,but the effect was not that I want to achieve.
I want to change the background of selected content.
The selected content is part of a xml element;
and maybe the selected content span two xml element.
At last ,I want to save the changed background.

Hi Max,
You might want to check out this article:
http://xopus.com/devblog/2009/highlighting-the-current-context-element.htmlhttp://xopus.com/devblog/2009/highlighting-the-current-context-element.html
Is that what you are trying to achieve?

I want to change the background of selected content.
The selected content is part of a xml element;
and maybe the selected content span two xml element.
At last ,I want to save the Highlight.

how to highlight the selected content in the xml of Xopus?

You can find several guides and references at our documentation section: http://xopus.com/documentation.htmlhttp://xopus.com/documentation.html

A good starting point is the developer guide, supplemented with the API and DOM references. If you still have specific questions, you can always contact us here or on support@xopus.com

Where can i get, a information about xopus? or a guide? thank you.

Since you are saying "somehow", what you could do is to put warning messages in placeholders:
http://xopus.com/documentation/configuration/elements/placeholder.htmlhttp://xopus.com/documentation/configuration/elements/placeholder.html

You could a add a CSS rule
.xopus-placeholder { color: red !important }
to show the placeholders more prominently.

I have found that Xopus has a tendency to leave empty elements in the source document if the user is less than fastidious about checking the effects of what they are doing. I can easily delete such elements in a post-save XSL transform, but I would prefer the user to see a validation error while they are editing the document. Is there a set of methods/events which would allow me to do this?

For example, suppose my schema has a "title" element which has a simple content model (in DTD form for brevity) of

(#PCDATA|em|bold|sup|sub)*

The schema can't mandate this "mixed" element to contain something more than nothing, so Xopus allows the user to insert an empty title. I would like Xopus to object (somehow!) to anything the user does which produces an empty title element. (And I have a short list of other elements with similar semantic restrictions too.)

Is there something I can do here, or am I barking up the wrong tree?

Cheers
T

Are you sure there's such a big difference between MSXML 4 and 6? I wasn't aware of that.

Ok that is great! But is there also a message if MSXML 6 is not installed? I know about the test on http://xopus.com/files/msxmltester/,http://xopus.com/files/msxmltester/, but a lot of users do not. The problem is that Xopus 'kind of' works with MSXML 4, but it is buggy / slow. This leaves users frustrated as they feel the editor is not working properly, even though the solution to the problem (installing MSXML 6) is very simple.

A WebApplication is just a website in the end. Xopus consists of an HTML page with a lot of Javascript. In order to "add" Xopus in your WebApplication I suggest you read the developer guide available from the documentation page.

You can then download Xopus and place it in your WebApplication.

The developer guide will teach you how to give Xopus a place, and how to load and save documents. Using the API you can then use AJAX calls to communicate the XML or parts thereof to other pages.

Then,is there any help document to tell me how I can add Xopus in to my WebApplication?

Sure. Xopus allows you to do anything you can do in a normal HTML page. This includes AJAX calls which is what you need here.

Can the xml in Xopus communicate with the WebApplication created by VS2010?
I want to get the value of the xml node and pass it to another page in WebApplication .

The only way I can think of is to load the document again, which will have some side-effects like resetting the selection.

Editor.getActiveCanvas().loadDocument(uri, true)

I use external script for saving XML from Xopus. I don't use saving function of Xopus' API.

How I can with API reset hasUnsavedChanges flag?

I'd say that this is pretty clean. We wouldn't build it very differently ourselves.

Other options you have are to use the XSL and string() to confuse Xopus about where the contents came from, but this would not prevent splits, or inserts of other elements.

A stronger way of preventing anything from happening is to use " throw new Editor.RevertingException(); ", as this will also revert anything that might have happened before you canceled the event. I am not sure you need it.

I knew as soon as I posted my question I'd figure it out. Here's the roughed in code that gets it to work:

function doLoad(evt)
{
//get the XML document that has been loaded
var doc = evt.document;
//attach an event to the document, listening to when element have been inserted
//doc.addEventListener("XopusBeforeSubtreeModified", doNothing);
doc.addEventListener("XopusBeforeNodeValueModified", doNothing);
doc.addEventListener("XopusBeforeChildInserted", doNothingChildNode);
doc.addEventListener("XopusBeforeNodeSplit", doNothingSplitNode);
}

function doNothing(evt) {
if (evt.target.getNodeName() == "reviewer.note" || evt.target.getParentNode().getNodeName() == "reviewer.note") {

}
else {
evt.cancelEvent = true;
}
}

function doNothingChildNode(evt) {
if (evt.childNode.getNodeName() == "reviewer.note" || evt.target.getNodeName() == "reviewer.note") {

}
else {
evt.cancelEvent = true;
}
}

function doNothingSplitNode(evt) {
if (evt.target.getNodeName() == "reviewer.note" || evt.target.getParentNode().getNodeName() == "reviewer.note") {

}
else {
evt.cancelEvent = true;
}
}

Now I guess my question is... Is there a cleaner way than this?

How do I configure Xopus so the user can only add one element and edit the text in that element?

The following sorta works:

function doLoad(evt)
{
//get the XML document that has been loaded
var doc = evt.document;
//attach an event to the document, listening to when element have been inserted
//doc.addEventListener("XopusBeforeSubtreeModified", doNothing);
doc.addEventListener("XopusBeforeNodeValueModified", doNothing);
doc.addEventListener("XopusBeforeChildInserted", doNothingChildNode);
}

function doNothing(evt) {
if (evt.target.getNodeName() == "reviewer.note" || evt.target.getParentNode().getNodeName() == "reviewer.note") {

}
else {
evt.cancelEvent = true;
}
}

function doNothingChildNode(evt) {
if (evt.childNode.getNodeName() != "reviewer.note") {
evt.cancelEvent = true;
}
}

But when I try to insert the reviewer.note, it doesn't let me type in the newly created element. How do I get it to let text nodes inside reviewer.notes to be added?

Yes, assign the role "hidden-from-ui" to the old element.

Our XSD allows a choice of three elements. Recently one was renamed.

We'd like to avoid re-writing all our XML documents to use the new element name.

Is it possible to continue to allow both the old and new names, but simply not show the old element as a choice in the selection list in Xopus?

Ok thx for your help.

This is a known limitation of the current implementation if I am not mistaken. Xopus requires the footer rows to come after the body rows.

Great. That did the job. But now the footer makes problems. I gave the tablefooter role to the tfoot element like this:
<x:node match="tfoot">
<x:role>tablefooter</x:role>
</x:node>
When i do this, the editor creates a new tgroup below the tgroup where tbody and thead is in and writes the colspec in the later tgroup. Like this:
<table>
<tgroup cols="">
<thead>
<row>
<entry />
<entry />
<entry />
<entry />
<entry />
</row>
</thead>
<tbody>
<row>
<entry />
<entry />
<entry />
<entry />
<entry />
</row>
<row>
<entry />
<entry />
<entry />
<entry />
<entry />
</row>
<row>
<entry />
<entry />
<entry />
<entry />
<entry />
</row>
</tbody>
</tgroup>
<tgroup cols="1">
<colspec colname="colA" />
<tfoot>
<row>
<entry />
<entry />
<entry />
<entry />
<entry />
</row>
</tfoot>
<tbody>
<row>
<entry />
</row>
</tbody>
</tgroup>
</table>

Have you tried to remove the tableheadercell role? That role use used for the HTML table model and might confuse the table inserter.

Hey guys,

i'm currently trying to configure the built-in table editor properly but i can't get it to create a table header. Our table model is leaned on the cals table model and built as follows:
<table>
<tgroup>
<colspec column=“name“/>...
<thead> (the header which makes the problems)
<row>
<entry> <p/> for a normal entry, <li> for a list item and <img> for a image </entry>
</row>
</thead>
<tfoot> row, entry... like in <thead> … </tfoot>
<tbody> row, entry like in <thead> and <tfoot... </tbody>

The roles i applied for the header

<x:node match="thead">
<x:role>tableheader</x:role>
<x:role>tablerowcontainer</x:role>
</x:node>

<x:node match="thead/row/entry">
<x:role>tableheadercell</x:role>
</x:node>

The editor offers the checkbox to select whether a header should be insterted or not but if selected that a header should be created a tbody, row is created.

Are the roles properly set?

Thx, I already fixed this problem.

Can you use Ctrl+Alt+R after starting Xopus to send us a reproducer? We can take a look at the case then and give you an answers.

The error is an error in Xopus, but it is crypted, so we cannot see from this end either what the problem is. Using your case in an unencrypted Xopus allows us to find the problem.

I added new button to toolbar with command what inserting element into my document. But after inserting I see the message "\u02A0.\u0426() is null" and Xopus stops working correctly.

What does this message?

Ooh, cancel that - it's there :-)

Cheers

Hi, can you provide an (approximate) ETA for 4.1.3 please?

There is. I just went to
http://xopus.com/demo/simplehttp://xopus.com/demo/simple
with Safari and this was the page that Xopus then shows:
http://xopus.com/files/demo/xopus/media/requirements.htmlhttp://xopus.com/files/demo/xopus/media/requirements.html

Feature request: we often get questions of users that do not use a supported browser, or do not have the right MSXML installed. Would it be possible to build in an automatic message whenever someone uses Xopus with an unsopported browser or with the wrong MSXML? I believe this would save a lot of frustration for users.

Then this is a know bug, which will be fixed in 4.1.3.

IE 8.

The stylesheet which we supply to Xopus to map XML to HTML generates a meta tag of X-UA-Compatible, IE=EmulateIE8 in the html header.

Which browser and which version are you using?

Following up http://xopus.com/forum/how-to/312.htmlhttp://xopus.com/forum/how-to/312.html (automatic scroll to anchor on open).

Reverting the config.js to its original form, i.e. removing all the functions implementing the scroll-to feature, I am still experiencing problems with the editor.

If the user (1) clicks in the document, (2) uses the vertical scrollbar to scroll up or down so that the cursor is no longer visible, (3) clicks again in the document:
Xopus "jumps" the display and positions the cursor in the wrong place. The jump often leaves the "right" place outside the visible region, which leads to an extremely frustrating cycle of clicks and curses :-|

I am using Xopus 4.1.2.

Xopus opens the document for editing and scrolls to the specified anchor. If the user clicks anywhere in the visible area of the document Xopus behaves correctly. However if the user drags the scrollbar up or down to display a different region and then clicks in the document, Xopus jumps and displays the cursor (or the highlight) somewhere else. For example, if I scroll up a page and click at the beginning of a line in the middle of the view, Xopus will redisplay the document so that the line I clicked in is the very first visible line - but the cursor will be near the end of the line. If instead of clicking in the line I double click a word in a line Xopus will suddenly scroll up and highlight a completely different word several paragraphs below where I was clicking.

It is not the scrollToId listener that is doing this, because an alert in the listener is displayed when the document opens, and not displayed when the user clicks. It appears to be one of the default listeners which is generating this wrong behaviour after we have scrolled our anchor into view.

Any ideas?

For Xopus 4 see: http://xopus.com/documentation/how-to/add-a-button-to-the-toolbar-in-xopus-4.htmlhttp://xopus.com/documentation/how-to/add-a-button-to-the-toolbar-in-xopus-4.html

For Xopus 3 see: http://xopus.com/documentation/how-to/add-a-button-to-the-toolbar.htmlhttp://xopus.com/documentation/how-to/add-a-button-to-the-toolbar.html

Brilliant!

Thank you so much
T

var originalLoadXMLFunction = IO.getLoadXMLFunction();
var hashPart;
var range;

function getHashPart(uri)
{
var hashPos = uri.indexOf("#");
if (hashPos > -1)
{
hashPart = uri.substr(hashPos);
uri = uri.substr(0, hashPos);
Editor.addEventListener("xmlContextChange", scrollToId);
}
return originalLoadXMLFunction(uri);
}
IO.setLoadXMLFunction(getHashPart);

function scrollToId(evt)
{
if (!range)
{
range = Editor.Selection.getRange();
if (!range) return;
}
Editor.removeEventListener("xmlContextChange", scrollToId);
var node = Editor.getActiveCanvas().getDocument().selectSingleNode("//*[@id='" + hashPart.substr(1) + "']");
if (node)
{
range.selectNode(node);
range.collapse(true);
setTimeout(function() {
Editor.Selection.setRange(range);
var htmlNode = Editor.getHTMLElementsForXMLNode(node)[0];
if (htmlNode) htmlNode.scrollIntoView(true);
}, 0);
}
}

> Documented, you mean like this?

Sorry, I must have missed it. Intuitively "context change" isn't the right event to use for this feature, but "load" (which makes more sense to me) didn't seem to work when I tried it. The redraw event has empty documentation so I've no idea whether it is a sensible option or not - but I'll try it next :-)

Hello all,
I want to remove some buttons which don't use in my Project,and add some new button. Can you tell how to do it?

Documented, you mean like this?
http://xopus.com/documentation/api/editor/editor.gethtmlelementsforxmlnode.htmlhttp://xopus.com/documentation/api/editor/editor.gethtmlelementsforxmlnode.html

The only reason I used xmlContextChange is that the API really is missing a createRange method, and the only way to get one is getRange, which in this case apparently often returns null.

It works the first time, so the script could be adapted to reuse that range. I'll give it a shot when I'm back at work on Tuesday, unless you get it working before then.

working brilliantly - with one caveat.

On the load of the initial url everything is perfect. The document opens and immediately scrolls to the correct location.

However when a second url is loaded the xml context change (the event we listen for to trigger the scroll-into-view) doesn't happen until the user clicks in this new document. At that point they suddenly find the document redrawn (and if they were trying to select a word they find they have selected a huge chunk of the document!)

Thus: on the initial load the xml context change is fired without user input, but on subsequent loads it is not. What do you suggest as a solution here?

Aha! This method needs to be documented :-)

Thanks very much
T

1. This is an Xopus bug. You can work around it by doing the setRange in a setTimeout.
2/3. Then the getRange probably returns null.
4. This can be fixed by getting the corresponding html node, and calling scrollIntoView on it.

This code has these fixes applied:

var originalLoadXMLFunction = IO.getLoadXMLFunction();
var hashPart;

function getHashPart(uri)
{
var hashPos = uri.indexOf("#");
if (hashPos > -1)
{
hashPart = uri.substr(hashPos);
uri = uri.substr(0, hashPos);
Editor.addEventListener("xmlContextChange", scrollToId);
}
return originalLoadXMLFunction(uri);
}
IO.setLoadXMLFunction(getHashPart);

function scrollToId(evt)
{
Editor.removeEventListener("xmlContextChange", scrollToId);
var node = Editor.getActiveCanvas().getDocument().selectSingleNode("//*[@id='" + hashPart.substr(1) + "']");
if (node)
{
var rng = Editor.Selection.getRange();
if (!rng)
{
// try again
Editor.addEventListener("xmlContextChange", scrollToId);
return;
}
rng.selectNode(node);
rng.collapse(true);
setTimeout(function() {
Editor.Selection.setRange(rng);
var htmlNode = Editor.getHTMLElementsForXMLNode(node)[0];
if (htmlNode) htmlNode.scrollIntoView(true);
}, 0);
}
}

Xopus 4.x/4.1.12 does not support an external spell check server. It is a feature we are considering for a future release.

Can you send an email tomailto: support@xopus.com support@xopus.com to explain how this affects your project? We may be able to come up with a workaround.

OK, here's the relevant part of my config.js as of today:

var originalLoadXMLFunction = IO.getLoadXMLFunction();
var hashPart;

function getHashPart( uri ) {
var hashPos = uri.indexOf( "#" );
if ( hashPos > -1 ) {
hashPart = uri.substr( hashPos );
uri = uri.substr( 0, hashPos );
}
else {
// without next line get null object error on opening xopus.html
hashPart = "#";
}
return originalLoadXMLFunction( uri );
}
IO.setLoadXMLFunction( getHashPart );

function scrollToId( evt ) {
// only scroll once on load
Editor.removeEventListener( "xmlContextChange", scrollToId );
// this is the element AFTER the id
var node = Editor.getActiveCanvas().getDocument().selectSingleNode("//*[preceding-sibling::*[1]/@id='" + hashPart.substr(1) + "']//text()" );
if ( node ) {
var rng = Editor.Selection.getRange();
rng.selectNode( node );
rng.collapse( true );
Editor.Selection.setRange( rng );
}
}

Editor.addEventListener( "load", myLoadHandler );
function myLoadHandler( evt ) {
// re-establish scroll on each new load
Editor.addEventListener( "xmlContextChange", scrollToId );
}

This code has the following problems:

1. On the first document load the scroll happens, but the save button is enabled in the Xopus toolbar before the user types anything. A ctrl-Z clears the breadcrumb trail in the status line and disables the button, but I'm not sure why Xopus thinks the document has changed.

2. Load a different document (or reload the same document) and scrolling does not happen, instead the user sees a scripting error which says:
Line: 1
Char: 1
Error: 'null' is null or not an object
Code: 0
URL: ../xopus/xopus.html

3. Strangely, if the url passed to xopus's load includes a non-existent #anchor, this error doesn't happen!

4. Not an error, but a quibble; the method used here to show more than a few pixels of the given id is a bit unsatisfactory, but I can't see a better way to achieve what I would like (which is to position the fragment corresponding to the given id at the top of the window).

Thank you for your help so far!

Cheers
T

One more thing; the display is scrolling so that the given element (an anchor placed immediately before a title, normally) is at the very bottom of the window. Is there a method that would position it at the top instead?

Sorry to be tiresome; this would be a neat feature if we could get it right.

Cheers
T

Cool, thanks!

I am having two problems with this, though.
Firstly, the code causes Xopus to think that the document has been modified, because the save button is already enabled when the document is displayed, and if the user navigates away the "unsaved edits" dialog appears.
Secondly, if the user navigates away and then requests to edit again - either the same document and location, or a different location, or even a different document entirely, the scroll/redraw doesn't happen.
I've checked the code very carefully and it matches yours precisely - and it is working the first time in, of course.

Is there something we have overlooked?

Is is possible to configure an external spell check server as per Xopus 3.2.11 in the latest version (4.1.12) please? I see that the config element for this is marked as "unavailable"?


We need to be able to add / remove words from the dictionary on the fly.

Kind Regards,
Chris

Interesting idea!

The following code does this:

var originalLoadXMLFunction = IO.getLoadXMLFunction();
var hashPart;

function getHashPart(uri)
{
var hashPos = uri.indexOf("#");
if (hashPos > -1)
{
hashPart = uri.substr(hashPos);
uri = uri.substr(0, hashPos);
}
return originalLoadXMLFunction(uri);
}
IO.setLoadXMLFunction(getHashPart);

function scrollToId()
{
if (hashPart)
setTimeout(function () { document.location = hashPart; }, 100);
Editor.removeEventListener("afterRedraw", scrollToId);
}
Editor.addEventListener("afterRedraw", scrollToId);

However, when testing this I noticed that it would be easier if the cursor would jump to the node with the id. (And scrolling then happens automatically.)

Replace the last part of the above code with this:

function scrollToId(evt)
{
Editor.removeEventListener("xmlContextChange", scrollToId);
var node = Editor.getActiveCanvas().getDocument().selectSingleNode("//*[@id='" + hashPart.substr(1) + "']//text()");
if (node)
{
var rng = Editor.Selection.getRange();
rng.selectNode(node);
rng.collapse(true);
Editor.Selection.setRange(rng);
}
}
Editor.addEventListener("xmlContextChange", scrollToId);

I have a Xopus Editor html page which contains an edit frame into which the xml document to edit is loaded. This is done by calling

editFrame.contentWindow.Editor.getActiveCanvas().loadDocument(myurl);

If myurl is something like "myfile.xml#Links" I would like to open myfile.xml in the edit frame, and scroll immediately to the anchor named "Links". The anchor does exist; the XSL transform from xml to html generates named anchors for all id'ed elements.

How can I implement this?

Thanks

It is used for all XSL resources.

Thanx.

Is the LoadXSLFunction also called when the include is loaded, or only when the root xsl is loaded?

Yes, do attr.showLookup().

See also IO.setLoadXSLFunction
http://xopus.com/documentation/api/io/io.setloadxslfunction.htmlhttp://xopus.com/documentation/api/io/io.setloadxslfunction.html

If this is indeed the problem mentioned on StackOverflow, then this is something we need to fix in the next version of Xopus.

If you can, please send us your files to us so we can make sure it is fixed in the next release.

To work around it, you can use IO.setLoadXMLFunction to remove the schemaLocation attribute from the XML file.
http://xopus.com/documentation/api/io/io.setloadxmlfunction.htmlhttp://xopus.com/documentation/api/io/io.setloadxmlfunction.html

Is it possible to use an onclick-event to open a lookup? Instead of using the attriubte editor..
I'm using Xopus 4.1.2

Yes, that will work fine. xsl:include and xsl:imports are resolved by Xopus.

Hi,

Is it possible to use xsl:includes (or xsl:imports) for the WYSIWYG stylesheet in Xopus?

Our XSL code is retrieved from database, so we need to resolve the inlcude url. What would be the best way of working?

Thanx.

browser name:
Microsoft Internet Explorer
browser version:
4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; CIBA)
DOMDocument FreeThreadedDOMDocument XSLTemplate XmlHttp XMLSchemaCache
MSXML version 4: installed installed installed installed installed
MSXML version 5: installed installed installed installed installed
MSXML version 6: installed installed installed installed installed

What version of MSXML are you using?
You can test that here:
http://xopus.com/files/msxmltester/http://xopus.com/files/msxmltester/

IFY:I used the Altova XMLSpy to validate the xml, it is OK. But I don't know when I use the Xopus I got the error like that.

It seems both xsi:schemaLocation and the SchemaCache are used during validation resulting in a conflict. Ik know i can use ResolveExternal=False so xsi:schemaLocation won't be used, but in that case xsd:import/xsd:include are not resolved either, so that's not an option.
pleas go to this website:
http://stackoverflow.com/questions/1565608/schema-validation-error-duplicate-named-element-name-xhttp://stackoverflow.com/questions/1565608/schema-validation-error-duplicate-named-element-name-x

I think this is an error in the schema, not in the XML file.

Probably there are 2 schema files that both declare the same element. Maybe you need to import the schemas instead of including them?

If you need more help, click the "Get help from Xopus" button in the error dialog. Then you will have the option of sending your files to us, which makes it a lot easier for us to help you find out what the problem is.

Hi all,
My schema have include 4 other schema,when i validation Xopus throw this error to me?

Node configuration is attached to schema items, so this is not going to work for processing instructions. You'll have to create your own lookup dialog, with you own iframe, and your own callback handler. Be sure to use Editor.runInTransaction in the callback, so the change to the PI will be undoable.

Don't hesitate to ask more questions, it's quite non-standard what you are trying to do here, so the documentation will not be of much help.

[1] http://xopus.com/documentation/api/editor/editor.runintransaction.htmlhttp://xopus.com/documentation/api/editor/editor.runintransaction.html

There is no perfect way to solve this. The issue depends greatly on configuration and schema.

Configuration can be used to map th and thead to their proper roles for the Xopus TableInserter. However this will not result in the expected result because the two elements more or less mean the same, also to Xopus. It will not give the following:

<thead>
<tr><th>...
</thead>
<tbody>
<tr><td>...
</tbody>

Removing minOccurs="0" from the thead in the schema is probably the best solution, and then relying on the role for th to insert:

<tbody>
<tr><th>...
<tr><td>...
</tbody>

Hello all,

Thank for your help. Now I have a better understanding of the way lookup is working.
I am able to trigger a lookup dialog when inserting an element.

But what I was trying to achieve first was a bit different.
Instead of triggering a lookup dialog upon element insertion, I would like to be able to trigger it when inserting a processing instruction (by clicking on a custom buton in the menu bar), so that I could select the "content" of the processing instruction in a lookup table.

Suppose that the custom button performs createProcessingInstruction('somepi',''). How to trigger a lookup ?

Unfortunately <x:node match="processing-instruction('somepi')"> is not allowed in config file.

I could not find any workaround.

Regards,

Fred

It works now!

Thank you very much!

Ah, it is a whitespace issue (whitespace handling has improved a lot in Xopus 4).

The solution is to add select="*" to the apply-templates in the table, so the whitespace text nodes will not be copied.

There's something in there that breaks the calculation of differences between the old xsl output and the new xsl output. The odd thing is that there's hardly anything changed in that code between Xopus 3 and 4.

There must be something specific in my document (XSL, XSD, config) that is causing this. I've created a simple table document without any special logic, and there it works fine.

But what could cause such strange behavior?

Hmm, that's odd. It works fine in Xopus 4.

A similar problem now also occurs when trying to remove a single column, it removes/hides the entire table!

And again, in the Tree view it looks fine. If I remove column (table gone), switch from WYSIWYG to Tree view and back, the table is there again.

Please help.

I have probem with table header. When table is created all rows are created in thead element
<thead>
<tr><th/></tr>
<tr><td/></tr>
<tr><td/></tr>
</thead>
<tbody/>
How I can force xmetal to create rows with td in tbody element ?

Ow, and I'm using Xopus 3.2.22

Hi,

I'm creating a document type (XML, XSD, XSL) for Xopus containing a table. The table structure is table/tbody|thead/row/cell/p. The cell elements have @colspan and @rowspan attributes. I've defined the element and attribute roles similar to the default-config.xml.

However, I'm experiencing issues with applying rowspan and colspan to the table. When merge left, right, down or up, the entire row or column simply disappears instead of merging the cells, even when merging 1 cell to the left on a row with 4 cells.

The strange part is, that this strange behavior only shows in the WYSIWYG view, if I apply rowspan or colspan via the Tree view it works fine. In the Tree view I can see a properly structure XML file; cell gets colspan attribute, p elements are combined in one cell, and the other cell is removed.

Please help.
Thanks.

Thijs

A reproducer uploads all files that are loaded by Xopus, basically the XML, XSD, XSL, but also configuration files, javascript files, and css.

If you are not allowed to send us the XSD, you should not use it.

Hi again,

if i upload my current configuration what will there be included? I'm not allowed to upload the XSD file.

Thanks for your help.

For the reset css, see f.e. http://developer.yahoo.com/yui/3/cssreset/http://developer.yahoo.com/yui/3/cssreset/

Maybe we can help you better if you send us your setup. The easiest way to do this is to load your document in Xopus and press Ctrl+Alt+R to run the Reproducer.

Hey Guys,

@Sjoerd: How would you realize such a "reset" css. Im not quite sure what you mean? And yes i have xml tags with the same name as html tags.

@Laurens: I want to use a CSS which is used for formatting documents under eclipse to format the Xopus presentation. The Problem is that the CSS reacts directly to the XML tags of my source file and not to HTML tags which are automatically created unless i do the above mentioned. I have tried the suggested actions. It worked fine with Firefox but not with IE. The IE shows only lists and pictures in basic html style.

Hi Trevor,

Have you tried Xopus 4.1.2 yet? It should solve this issue.

greetings,
Sjoerd

Which elements are causing problems? I assume you want your CSS to work as-is. In what way doesn't it do what you expect?

If your XML contains elements with the same name as HTML elements, I think you're out of luck, although including a "reset" css file that removes all default styling could get you a long way.

But I would expect that to be a problem in Firefox too.

Hey Sjoerd,

thanks for your answer. I tried it for Firefox and it works. But for IE it doesn't work. I called a document.createElement("tagName") for every used XML Element and i am doing a identity transform via:
<xsl:templatemailto: match="@*|node()"> match="@*|node()">
<xsl:copy>
<xsl:apply-templatesmailto: select="@*|node()" select="@*|node()" />
</xsl:copy>
</xsl:template>
but IE 8 still shows me the basic html interpretation of my xml file, which means Xopus is still transforming the XML file. Any suggestions? Ideas?

Thanks,
Robert

You can connect lookups to element, by using the new nodeConfig.

Next you can communicate with the Xopus DOM in the lookup dialog through top.dialogArguments.node. This represents the node that the lookup was opened for, and is an XopusElement. From there you can use

node.getOwnerDocument().createProcessingInstruction("text");

to create the processing instructions.

Hello all,

I would like to build a kind of lookup dialog in order to be able to insert some processing instructions.

From what I understand lookup dialogs are aimed at inserting attribute nodes.

Would it be possible to insert processing instructions instead? What route should I follow to perform this task?

Thanks for your help.

Best regards,

Fred

That's right. Xopus expects you to provide an XSL to transform your XML into HTML. However, this can simply be an "identity" transformation, which just copies the XML as is.

To do this, insert an identityTransform element in the view element[1], instead of a transform element. And if you include your CSS in the HTML page that contains the XML island, then it will be applied to the XML.

To get this to work properly in Internet Explorer you have to do document.createElement(xmlName) once for each type of element that the XML contains.[2]

[1] http://xopus.com/documentation/configuration/elements/view.htmlhttp://xopus.com/documentation/configuration/elements/view.html
[2] http://xopus.com/devblog/2008/style-unknown-elements.htmlhttp://xopus.com/devblog/2008/style-unknown-elements.html

Hey guys,

based on this answer: "When copying from html pages or Word
document the pasted information is first formatted to HTML, and then
Xopus checks if he can translate the HTML tags to corresponding tags in
the XML." (http://xopus.com/forum/how-to/56.htmlhttp://xopus.com/forum/how-to/56.html) i assume, that Xopus
formats a during startup given XML file also in HTML?

If i am right, is it possible to disable that feature. I'm asking because
i have a CSS Stylesheet that reacts on the XML Tags and not HTML.
If i am not right, do know any other work around?

Thanks,
Robert

Dude... Nice solution!

Hi Trevor,

Coincidentally another customer noticed this too 2 weeks ago. These issues will be fixed in Xopus 4.1.2, which we plan to release in early April.

greetings,
Sjoerd Visscher

Advanced to 4.1.1, no difference (none expected as there was nothing in the list of changes to suggest otherwise). I have confirmed that the value of <x:ignoreUnsavedChanges> is apparently ignored by Xopus; I get identical dialogs in every scenario I test.

Given that I can't stop the Xopus dialog appearing, I have taken the test for hasUnsavedChanges out and left it to Xopus to tell the user his document has changed. But this is no better; sure, the user only sees one dialog when backing out of his edits, but if he cancels it, then the loadDocument(null) is not completed and the (changed) document remains in the edit frame, so that when the user goes back into the editor, either with the same document or a different one, they get presented with the same standard "document has unsaved changes" dialog again.

So:
a) If I want my own application to manage changes, how do I stop Xopus managing them?
b) If I can't stop Xopus managing changes but have to use its built in dialog, how do I get the user's response to the dialog back to my application? I can see nothing relevant to this in the documentation, I'm sorry.

Cheers
T

Hi

My xopus-config has ignoreUnsavedChanges set to "true" and my wrapper html screen is calling document.hasUnsavedChanges() to determine what to do if the user tries to close the browser or navigate elsewhere. The problem is that my generated dialog (displayed when hasUnsavedChanges is "true") which allows the user to continue or cancel, is immediately followed by Xopus's own "document has unsaved changes" dialog.

(If the user wants to continue, discarding their changes, I invoke Editor.loadDocument(null) to unload the unsaved document).

I am assuming that I should not be seeing the Xopus dialog if the config has ignoreUnsavedChanges set.

I am using Xopus 4.1. Is there something I have misunderstood here?

Cheers
Trevor

The best solution to integrate Xopus with GWT would be to create an Xopus GWT component. We have not done a GWT integration before, but we may be able to work with you to create such component. Send us an email if you're interested (info at xopus dot com).

Prices can all be found in the shop (http://xopus.com/shophttp://xopus.com/shop)

We aren't completely familiar with Apache Forrest, but perhaps the first thing to do is to use Firebug or Fiddler to check and see what goes over the line. If the encoding of files is not correct, the browser, and also Xopus itself, will not be able to parse, use and display them correctly.

Let us know what you find.

It seems that 4.1.1 has an issue with certain setups and an older MSXML version.

You can check your MSXML on http://xopus.com/files/msxmltester/http://xopus.com/files/msxmltester/ with IE. Updating to MSXML 6 can solve the problem.

In order to solve this issue, I would like to ask you, and others who are experiencing this issue to report the following here:

- OS version
- Browser name and version
- MSXML version (according to above tester).

Hello,

we will run Xopus on a large scale integrated in an CMS-like system.
There will be a lot of customizing (e.g. adding event handlers in the DOM etc.).

Our framework, where Xopus will be integrated is based on Java (GWT in this case). The question would be:
do you have any ideas how to acess the DOM etc. without scripting JavaScript but using Java. There is of course the option of inline javascript in GWT but this doesn´t solve the problem that we will have to script in javascript again.
What we basically need is a acess from Java to all Javascript objects and properties.

Had some of you maybe already faced the same problem? Ideas are welcome!

Thanks a lot!

Best Regards,

Jonas

I would like to test Xopus with Apache Forrest.
I have found the location where the xopus folder can be stored and accessed by localhost:8888/xopus/xopus/xopus.html
But only the content is shown within the Forrest project site:
Version
Xopus 4.1.1
Released
March 3, 2010
Release Notes
Copyright
©2010 Xopus BV
Legal Notices
Visit xopus.com

But nothing happens. No editor is starting.

Where can I find help and/or documentation?
Thanks! Ulrich

I get the following error after the splash screen in the simple demo. I'm using the trial version to run on local host only. It works when installed on a non-server machine. All demos have the same error.

#/schema[1]/element[position() = 1 and @name = 'article']/complexType[1]/attribute[1]
Reference to undeclared namespace prefix: '__xopus_schema'.

We solved this by tricking Xopus into believing someone pressed a key on the keyboard(only tested in FF):

var evt = document.createEvent('KeyEvents');
evt.initEvent('keyup', true, true);
inputFieldElement.dispatchEvent(evt);

Adding a Xopus canvas from script is one of the features we're working on right now. This will probably be released in Xopus 4.1.3. All feedback on wishes, ideas and example usage is highly appreciated!

I don't see a way to get this to work. But it might not be too hard for us to add this as a feature to Xopus.

Can you run JSP on your IIS?

If so, perhaps you just need to enable the POST method for JSP files.

This looks like it might explain how to do that:
http://blogs.msdn.com/joseph_fultz/archive/2009/07/23/enabling-the-put-verb-with-handlers-and-iis-7-0.aspxhttp://blogs.msdn.com/joseph_fultz/archive/2009/07/23/enabling-the-put-verb-with-handlers-and-iis-7-0.aspx

when I run the asp.net demo and hit save it works:
var result = HTTPTools.postXML("save.aspx", xmlDocument);

However, the following:
var result = HTTPTools.postXML("save.jsp", xmlDocument, "UTF-8");
from the jsp example however gives this error: <title>IIS 7.5 Detailed Error - 405.0 - Method Not Allowed</title>

Any ideas?

We are using the jQuery mousewheel plugin(http://plugins.jquery.com/project/mousewheelhttp://plugins.jquery.com/project/mousewheel) to alter the values in the properties sidebar input fields when the user hovers over an input and scrolls the mousewheel. This works well and nice, but Xopus does not seem to notice that the input's value has changed. It seems to trigger only on keyup or keypressed. Is there a way to force Xopus to re-evalute these input fields?

BR // Fredrik

We now have a working solution where we place the xopus island in an iframe and display an absolutely positioned div on top of the iframe when the user clicks an element. This is also the only DOM element that we need to make draggable. With jQuery we can find out the element's absolute position(by adding the height of the toolbar) which we use to position our own div. When the user is finished we update the xmlnode's attributes(top/left) directly.

Thanks for the quick reply. I will post back the successful solution if we have it.

Yes, within the xml island Xopus has to interfere with the events to make the cursor work. gewfy was working with Xopus 3, where we did not have our own cursor implementation, and needed to interfere less with the events.

The only solution I can think of is to find a way to have the draggable items outside of the xml island. This means that you have to clone the parts of the xsl output that have to be draggable, and insert them in the html document outside of the xml island. Note that you should *clone* the content and not *move* it, otherwise Xopus can't find the content when it has to render updates. You can hide the originals of the clones with css.

Xopus does not support DTDs. But you can use a tool like Trang to convert the DTD into XSD and use that.

Has anyone managed to make this work? I have followed the example above and can via Firebug confirm that the inserted HTML element gets the jQuery class "ui-draggable" and should thus be draggable. But when I try to drag it, nothing happens.

After trying to make this work for some time I opted to implement my own dragging implementation, but that does not work either. It seems that the mousemove event is not fired when a mousebutton is held down. Does Xopus interfere with these events in any way?

BR // Fredrik

Hi,

is it possible to use a dtd in the same way a xml schema file is used to automatically fill the + and - buttons of xopus?

Thx.

prices hidden or at least very hard to find. What a turnoff

Hello!

In our project, we cannot configure Xopus via the <xml>-tag. The reason for this is out of our hands. Is there any way to configure Xopus programmatically?
It is possible that we can create all the html(anx the xml-tag)with Javascript, but we need some way trigger Xopus to look for this.

BR // Fredrik

Ok. I would remove the tableheadercell role from the td. This removes the header options from the tableinserter.

Once we have the idea above implemented, the header row and footer row options should reappear (and not the column options).

Sounds good :-)

I have the following nodes defined in my xopus-config.xml (this is just the bit relevant to tables):

<x:node match="table"><x:role>table</x:role></x:node>
-- remainder abbreviated --
match=tt role=tablecaption
match=th role=tableheader, tablerowcontainer
match=tb role=tablebody, tablerowcontainer
match=tf role=tablefooter, tablerowcontainer
match=tr role=tablerow. tablecellcontainer
match=td role=tablecell, tableheadercellmailto:match=@rowspan
match=@rowspan role=cellrowspanmailto:match=@colspan
match=@colspan role=cellcolspan

Cheers
T

It certainly is.

By the way, did you assign the tableheadercell role, and if so, to which element? (As it doesn't seem to have an effect in your case, which sounds like a bug.)

So, is this pure a styling thing? The Xopus lookup modal dialog is already quite sheet like.

If so, you might be able to get quite far by adding a link to your own css file in xopus/xopus.html.