Versions Compared

Old Version 4

changes.mady.by.user Joshua Scott

Saved on

compared with

New Version 5

changes.mady.by.user Joshua Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • ITInfo
    • XML Query
      • Not able to query XML to generate index pages (no XQuery), either at author time or runtime
      • Detail: We initially planned to have all of the current ITInfo content migrated to XML.  We would then use something like Xquery to query the XML, gather the appropriate data, and display said content to a page.  We have recently discovered that there is no way to effectively query XML content in this fashion, so we are investigating work-arounds.
    • More AVM in XSL
      • Almost all MIT author-time work-arounds require author time extensions via XSL which cannot trigger all of the events that we need; need more AVM functions in XSL
      • Detail: "Our approach to adding functionality to the authoring process has been to use the XSL to make AVM function calls. However, we cannot get the XSL to execute in all cases where it is needed in order to have a consistent behavior.  The repository has numerous events which can trigger some code to run (for example, to regenerate a new index page when a file in a folder is changed), but the WCM does not make them all available to us. Also, only a few AVM functions are ""built-in"" to the XSL and they are not enough for us; we have to create our own Java classes in order to access these functions.  The whole AVM API should be available to XSL."
    • Runtime DB cannot preview in Virtualization Server
      • Any runtime db/app solution is un-previewable thru virtual server; might need different solutions at author time & runtime
      • Detail: Solutions that use external tools cannot necessarily be run in Preview mode. If the data is stored differently at author time (in the Alfresco repository) or runtime (in file system, or XML database), then preview has to do something different in order to look the way it will look at runtime, and it may not be possible to get an exact correlation.
  • Static Content Migration
    • Embedding HTML / Unescaped Markup
      • Difficulty with embedding HTML in the "generic" webform using TinyMCE
      • Detail: We have a concern that our users are used to editing in Dreamweaver, and will not find the form-based GUI very easy to use.  The usability (or lack thereof) of the editor should not drive users away from the application.  Could be solved as of 2.0.1.
    • Content Regeneration
      • Regeneration of content when needed (see dependency mgmt)
      • The import process involves a great deal of re-formatting the incoming content, going from HTML to templatized XML. Even with scripts and Java classes, we keep discovering many small issues around this.

...

  • Dependency Management
    • Our solution requires our own build of the Alfresco WCM client, and there are some issues with respect to the association between source and generated content.
    • Detail: Because there is no dependency mgmt, when an XSL for an Xform is changed, the files that were generated by that XSL are not updated. We have written our own Java class and added a button to the WCM client to regenerate all files so as to get up-to-date HTML from our XML. Because of this, we have to compile & build the WCM client ourselves in order to add our new widget. We cannot deploy an out-of-the-box Alfresco distribution. It does not always work perfectly, because the association between a generated HTML and the XML/XSL that it came from is not as tight as it should be – - there are cases where the HTML has to be manually deleted.

...