AWS XMS Changelog

What's new in AWS XMS 4.0

Nov 25, 2013
  • new processing order
  • removed exec, runhere and replace - functionality taken by php#pi
  • php#pi can return either text or DOMNode
  • fixed import and advanced import filters bug
  • import/eachnode can return dom node
  • domiterator/norecords returns DOMNode or text

New in AWS XMS 3.0 (Sep 17, 2013)

  • DESIGNER:
  • 0.22.01 - displays the messages from server when saving files
  • 0.21.01 - html entities encoded in #pi and comment preview
  • XMS:
  • engine is now XMS class; allows programmer to use multiple instances in the same application
  • XMS class: overloading methods defined
  • fixed to run on php 5.4
  • removed Browser class
  • GLOBALS['XMS_ENGINE'] to access XMS instance
  • router instance has a new parameter $accessControl
  • $GLOBALS[HTMLPARSER] deprecated (kept for compatibility); use $GLOBALS['XMS_ENGINE']->CLIENT
  • $GLOBALS[TEMPLATE] deprecated (kept for compatibility); use $GLOBALS['XMS_ENGINE']->APP
  • sends messages to Designer when the directory tree does not exists
  • XMS_APPS_LOCKED_IN_CWD set to TRUE (defaults.php) open files from XMS directory only
  • import/eachnode returns either bool/text/DOMElement; when bool and TRUE will just use the current imported node else will skip it; text or DOMElement will be used instead of the imported node

New in AWS XMS 2.0 (Aug 24, 2012)

  • Designer - new application core, faster, lighter and more reliable
  • Designer - multiple text nodes can be created
  • Designer - doesn't apply any xsl to the document while saving; this feature can be enabled, disabled or customized in Runtime options
  • Designer - added processing instructions support
  • Designer - advanced clipboard allows paste individual items and refreshes automatically if new nodes are copied to clipboard and the dialog is open
  • Designer - document tree shows all nodes, not only DOMElements; this option can be changed from Runtime Options/Show DOMElements only
  • Designer - Runtime options/Tree nodes display filter - a filter that is applied when a tree element is displayed so it will only show those that you want / need to seel Very good to filter application directives and not browse the entire documents looking for them; This filter can be enabled or disabled from Runtime options / Check this to apply above nodes tree display filter
  • Designer - cut and copy buttons for each attribute
  • Designer - Rename node tool fixed
  • Designer - interface tweaks (dialogs instances fixed to open an existing instance if any or a new dialog / drag and drop support disabled by default / focus on main input elements in dialogs)
  • Designer - keyboard shortcuts to extend (Ctrl+arrow right) and collapse (Ctrl+arrow left) tree nodes
  • xms application processor - $GLOBALS["HTMLPARSER"] now is awsXML - kept the name for backward compatibility reasons!!! The application only runs over XML documents only and outputs whatever we need based on the xsl supplied in the outputxsl attribute of app element
  • xms application processor - app[@outputxsl] - default is xsl/aws2html.xsl for html output type applications; when attribute removed => output as xml application
  • xms application processor - updated to engine 2.0-beta3 (temp.php) and changed all directives that interpret php code to use the first processing instruction instead of text content
  • xms application processor - xmlimport directive removed because import now handles both, xml and html (in this case the importashtml attribute needs to be set as by default import handles the document as xml)
  • xms application processor - advancedxmlimport directive removed because advancedimport now handles both, xml and html (in this case the importashtml attribute needs to be set as by default advancedimport handles the document as xml)
  • xms application processor - #pi aws directive = behavior similar with tunhere and replace
  • xms application processor - #pi exec directive = behavior similar with exec
  • xms application processor - #pi php directive = work in pairs and execute code over the DOMDocumentFragment containing all the nodes in between the two #pi
  • xms application processor - advancedimport/data/child[@type="function"] - when set, type attribute makes the directive execute the #pi inside as a function, in order to be able to set cutom data for the advancedimport directive header, when reads the data source
  • xms application processor - AWS_DEBUG_ALL_LAMBDA option in defaults.php: when set to TRUE, the processor will log all the lambda functions executed - use it only for debugging purposes, to see what, where and when was executed; in production set it to FALSE because could slow down the applications; default output is in log folder, for individual sessions or for all (GLOBAL.gz)

New in AWS XMS 1.6 (Mar 24, 2012)

  • Designer - new tool to toggle node list container width
  • Designer - minor interface tweaks
  • Designer - on mobile browser (webkit/android) will display an additional tool to toggle active node
  • Designer - runtime check type options not working: FIXED (Thanks to Seb)