Hello Hussein,
Ok, here's what I've got; there's something going on with the drop-site command
that I don't understand.
When I form my CSS like this:
chapter:before[navtitle]{
content: paragraph(content(item-collapser(), " ",
attr(navtitle), " ",
drop-site(icon, icon(drop),
command, "setObject",
parameter, "href anyURI -
'%{value}'"), " ",
xpath("if(substring-after(substring-after(substring-after(substring-after(@href,'/Content/'),
'/'), '/'), '/'),
substring-after(substring-after(substring-after(substring-after(@href,'/Content/'),'/'),'/'),'/'),
substring-after(substring-after(substring-after(@href,'/Content/'), '/'),
'/'),
substring-after(substring-after(substring-after(@href,'/Content/'),'/'),'/'),
substring-after(substring-after(@href,'/Content/'),'/'),
substring-after(substring-after(@href,'/Content/'),'/'),
substring-after(@href,'//') )"
), " "
),
topicref-format());
}
When I open the document the abbreviated path created by the xpath command is
displayed correctly. When I drop a new target on the drop-site, however, the
path fails to redraw. When I insert an extra " attr(href)," between the
parameter and the xpath command, however, it behaves differently. When the
document is first opened both the full path (the result of the attr(href),
command) and xpath output are displayed. When I drop a new target on the
drop-site, the output of the attr(href), command disappears and the xpath
output is redrawn correctly.
I can't see any reason for this behavior in the documentation of the drop-site
command. Does this make any sense to you?
chapter:before[navtitle]{
content: paragraph(content(item-collapser(), " ",
attr(navtitle), " ",
drop-site(icon, icon(drop),
command, "setObject",
parameter, "href anyURI -
'%{value}'"), " ",
attr(href),
xpath("if(substring-after(substring-after(substring-after(substring-after(@href,'/Content/'),
'/'), '/'), '/'),
substring-after(substring-after(substring-after(substring-after(@href,'/Content/'),'/'),'/'),'/'),
substring-after(substring-after(substring-after(@href,'/Content/'), '/'),
'/'),
substring-after(substring-after(substring-after(@href,'/Content/'),'/'),'/'),
substring-after(substring-after(@href,'/Content/'),'/'),
substring-after(substring-after(@href,'/Content/'),'/'),
substring-after(@href,'//') )"
), " "
),
topicref-format());
}
Thanks,
Jeff.
-----Original Message-----
From: xmleditor-support-boun...@xmlmind.com
[mailto:xmleditor-support-boun...@xmlmind.com] On Behalf Of Jeff Hooker
Sent: October-03-13 4:33 PM
To: xmleditor-support@xmlmind.com
Subject: Re: [XXE] Refreshing the CSS generated content
Finally getting to return to this:
Is there a simple test case I can run to see if "refresh" is working or if I've
somehow overridden it?
Thanks,
Jeff.
-----Original Message-----
From: xmleditor-support-boun...@xmlmind.com
[mailto:xmleditor-support-boun...@xmlmind.com] On Behalf Of Hussein Shafie
Sent: July-17-13 12:52 AM
To: Jeff Hooker
Cc: xmleditor-support@xmlmind.com
Subject: Re: [XXE] Refreshing the CSS generated content
On 07/16/2013 09:37 PM, Jeff Hooker wrote:
>
> Small misunderstanding; it's not the whole screen that goes blank,
> just the spot where the href value should be displayed in the topicref
> element. XXE is not crashing or locking.
OK.
>
> The root of my question is that either the "refresh" command is not
> working (or is not for this context), or I am misunderstanding its
> function. When run against an element with peusdo-elements such as
this:
>
> topicref:before {
> content: paragraph(content(item-collapser(), " ",
> attr(navtitle), " ",
> drop-site(icon, icon(drop),
> command, "setObject",
> parameter, "href anyURI -
> '%{value}'"), " "
> ), " "
>
> ),
> topicref-format());
> }
>
> Should the command "refresh refresh[implicitElement]" force XXE to
> re-layout and repaint selected topicref, including any associated
> peusdo-elements?
It's very difficult to answer your question. Invoking command refresh is rarely
needed and I fail to see cases where there is a need to invoke refresh from
say, a macro-command.
The refresh command is correctly documented here:
http://www.xmlmind.com/xmleditor/_distrib/doc/commands/refresh.html
Parameter "rebuild" (not "refresh") recreates the full view, including
generated content, of the selected node. This is what happens when the document
is first opened in XXE.
For example, what follows is the deepest, fullest, kind of refresh of a view of
a document:
---
refresh rebuild[implicitDocument]
---
Therefore if you need to use refresh in a macro, please use
---
refresh rebuild[implicitElement]
---
and not
---
refresh refresh[implicitElement]
---
> If so, am I understanding correctly that this process should be the
> same process as the one used to layout and paint the screen when the
> file is first opened, but run on a specific part of the file rather
> than the whole file?
>
> If so, it's puzzling, because the elements are laid out and painted
> correctly when the file is opened or reopened, but using the "run
> command" dialog to run the refresh command on the misbehaving
> topicrefs does nothing and produces no error output in the command
> window. Perhaps it is tied into the "topicref-format()" function, for
> which I have yet to find documentation.
Yes, that's right. The map view is styled using a CSS extension.
Excerpts from map.css or bookmap.css:
---
/*
* Implementation of methods topicrefContent and chunkIcon.
*/
@extension "com.xmlmind.xmleditext.dita.MapStyleSheetExtension";
...
topicref:before {
display: inline;
content: invoke("topicrefContent", normal); }
---
There is no documentation for this CSS extension. However you may want to read
its Java source code (short and straightforward) which is found in
src/com/xmlmind/xmleditext/dita/MapStyleSheetExtension.java
More information about CSS extensions:
http://www.xmlmind.com/xmleditor/_distrib/doc/dev/styleext.html#solution
1
>
> In answer to your question, yes, I am introducing some fairly minor
> changes to your default map view; just moving the functions needed
> closer to the user and trying prevent them from using the Attribute
> pane, which just leads to trouble.
>
OK.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
