Kathryn Huxtable wrote: > Is there a price discount for the upgrade if I already have a professional > license for 4.4? -K >
I'm really sorry but there is no upgrade path between "XMLmind XML Editor - User License" and "XMLmind XML Editor - Applet Server License". Important reminder (excerpts of http://www.xmlmind.com/xmleditor/xxe_applet.html): --- Licensing: * User License puts no restrictions on the deployment of XMLmind XML Editor as an applet, except of course, that the number of concurrent users must not exceed the total number of users for which the license fee has been paid. * Site License restricts the deployment of XMLmind XML Editor as an applet to machines located at the site of the licensee. * Developer License puts no restrictions whatsoever on the deployment of XMLmind XML Editor and, of course, this includes the deployment as an applet. * Applet Server License allows to freely deploy XMLmind XML Editor as an applet (but only as an applet, not as a desktop application) provided that the code of the applet is downloaded from the servers for which the license fee has been paid. --- In other words, in some cases, you don't need to purchase any special license in order to deploy XXE as an applet. > On Mar 16, 2010, at 3:06 AM, Hussein Shafie wrote: > >> Henry Mok wrote: >>> I have a question about the xmlmind. In the editor1 demo on your website, >>> you have a row with options like "convert to emphasis", "add para", "add >>> table", etc. I'm using the professional edition version 4.4.0. >> You should really upgrade to latest version because 4.4 is a bit old by now. >> >> >> >>> When I installed it, I didn't see this row of options. How do I get this >>> row? Is >>> this something that needs to get configured? >> --> It works like this: >> >> * When you create or open a document in XMLmind XML Editor, our product >> detects whether a *configuration* is associated with this type of document. >> >> * If this is the case, it applies this configuration to the opened >> document. >> >> * A configuration may contain all sorts of specifications: CSS >> stylesheets, custom menu, custom toolbar, custom keyboard bindings, >> custom commands, etc. >> >> All this is documented here: >> http://www.xmlmind.com/xmleditor/_distrib/doc/configure/index.html >> >> (See also http://www.xmlmind.com/xmleditor/customization_service.html, >> in case you prefer to delegate this customization task.) >> >> >> >> --> Let's use the editor1 applet demo as an example. >> >> * Some applet parameters are used to instruct the applet to create a new >> DocBook 5 article. >> >> * XMLmind XML Editor tests the newly created document against the all >> known configurations. >> >> * The DocBook 5 configuration (docbook5.xxe) contains this detection rule: >> --- >> <detect> >> <rootElementNamespace>http://docbook.org/ns/docbook</rootElementNamespace> >> </detect> >> --- >> >> Therefore the newly created document is detected as being DocBook 5. >> >> * The DocBook 5 configuration (docbook5_support.incl, included by >> docbook5.xxe) also contains a custom toolbar: >> --- >> <toolBar> >> <button toolTip="Convert to emphasis" >> icon="../common/icons/emphasisText_menu.png"> >> <menu> >> <item label="emphasis" command="convert" >> parameter="[implicitElement] >> {http://docbook.org/ns/docbook}emphasis"; /> >> ... >> >> <separator /> >> >> <button toolTip="Go to Opposite Link End" >> icon="../common/icons/navigate.png"> >> <command name="selectById" parameter="swapIdAndReference" /> >> </button> >> </toolBar> >> --- >> >> Therefore the custom toolbar is displayed by the applet. >> >> >> >> --> Note that this applies to both the XMLmind XML Editor application >> and applet. >> >> The reason is simple: the application and the applet share 99.99% of >> their code. Only the GUI, which is specified by a .xxe_gui specification >> file (more info: >> http://www.xmlmind.com/xmleditor/_distrib/doc/gui/index.html), >> generally differs. We can even say that there is no real difference >> between the application and the applet. >> >> Normally you should use the application to test that everything works >> smoothly and, only after doing that, deploy XMLmind XML Editor as an >> applet (with exactly the same configurations and add-ons as tested with >> the application). >> >> >> >>> I'm interested in this because there are things that we use a lot (like >>> indexterms and figures) and I would like to create buttons for these. Is >>> this something that can be done easily? >> Yes, but you'll have to read a lot of docs and also study the stock >> configurations. See >> http://www.xmlmind.com/xmleditor/_distrib/doc/configure/index.html >> >> >> >>> In the future, if I have questions like this, do you prefer that I send it >>> to xmleditor-support at xmlmind.com? >>> >> Yes, please do so.
