Hi all, Hussein Shafie a ?crit:
>>Cursor doesn't change on collapse/expand arrows. > > Just after releasing XXE 2.1, we have implemented something like this: > cursor changes to the text cursor (i.e. the vertical bar) only if it is > over editable text, otherwise it is always the default arrow cursor. We > are currently testing this feature to see if is comfortable to use. OK. Looks fine to me... > We don't have a PC running Win 9.x so I cannot send you a .bat file that > works with this OS. I can :-) But, roughly : from the xxe.bat file : remove setlocal replace set dist=%~dp0 by set dist=. remove rem C:\winnt\Profiles\<user>. (the <> seem to be reserved chars) replace start javaw by javaw remove endlocal > May be it is easier to use the installer after creating a C:\temp > directory and ``declaring'' it with "set TEMP=C:\temp"? Mmmh. I have TMP and TEMP variables set... >>No native support for Docbook 4.2 ? Website ? > > The DocBook 4.2 DTD will be included in next release. OK. >>Do you think it would be possible to natively embed xrefs' text into the >>dedicated widget (which is nice) ? Possibly xreflabels ? > Do you want to see the xreflabel of the element which is the target of > the link instead of just seeing its ID (the value of "attr(linkend)" is > the ID of the target of the link)? That's it : if there's an xreflabel, I want to see this label. if there's none, I want to see the pointed element, with a possible stop on an endterm if there is no linkend, an "unresolved xref" message would be nice... Well, that's just the "Processing Expectations" for xref : http://www.docbook.org/tdg/en/html/xref.html > If you want to do this, please confirm and I'll send you the piece of > BeanShell or JavaScript (tell me what you prefer) script that must be > added to the style sheet in order to implement this. Thanks. In fact I wonder whether XXE should *natively* support Docbook's processing expectations. I've well understood that XXE is*highly* customizable :-) >>Do you think it would be possible to make links active (possibly with >>the right mouse button) ? > > The right mouse button is already used to display the Edit popup menu Does it make sense to add a menu item for "links-like" elements ? > but you can do this (add this to xxe_distrib/config/docbook/common.incl) > > <command name="docb.followLink"> > <macro> > <sequence> > <command name="selectNodeAt" /> > <command name="selectById" parameter="id" /> > </sequence> > </macro> > </command> > > <binding> > <mouseClicked button="3" modifiers="ctrl" /> > <command name="docb.followLink" /> > </binding> > > (I hope I have understood what you want.) That's it :-) >>Do you think it would be possible to localize names in .xxe files ? e.g. : > This is an omission. You can fix that yourself if you want, add > > <message> > <text>DocBook (collapsible sections)</text> > <text>DocBook (sections r?tractables)</text> > </message> > > at the end of the <localize languages="en fr"> element contained in the > xxe_distrib/config/docbook/common.incl file. OK. >>In "Edition" tab, would it be possible to have grayed, possibly stroked, >>elements ? i.e. elements that are theorically pertinent in the current >>element but are not in the current *position* ? Of course, this should >>be cutomizable : people that have a good knowledge of Docbook (or >>whatever) shouldn't need this feature... > > > Sorry. I don't understand this. Please give me an example. Well. With default configuration, I can create an (empty) article that looks like this : <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd";> <article> <title></title> <sect1> <title></title> <para></para> </sect1> </article> Now, I select the whole sect1 element in order to use the "insert" command to create a sect1info element. Unfortunately, this element is *not* listed because I think that XXE assumes that the content model is valid as it is. If I want to insert this sect1info element, I have to select the title element and the "insert before" command. This behaviour seems a little odd to me... So, what I'd like is either : Offer the sect1info in the "insert command" Offer a grayed sect1info in the "insert command" that would mean in this case : "you have to select the first child element and use the 'insert before' command"... Now, a bug report : 1) open 2 documents 2) there's no "close all" command in the "file" menu. Never mind... 3) use "file/close" in order to close the first document 4) if you want to use the same menu item to close the second document, you can't : it is grayed. Cheers, -- Pierrick Brihaye, informaticien Service r?gional de l'Inventaire DRAC Bretagne mailto:pierrick.brihaye at culture.gouv.fr
