Skip to content
Commits on Mar 30, 2007
  1. @pajamian
Commits on Sep 11, 2005
  1. @docelic
Commits on Apr 12, 2005
  1. @perusionmike
Commits on Jan 14, 2003
  1. @perusionmike

    * Major changes to the Interchange output model and UI.

    perusionmike committed
    * There will be more commits for menu data.
    * Zeald's redesign of the UI layout is almost fully implemented. There
      are but a few pages that don't incorporate the new layout.
    * Each page can have an entry in mv_metadata, which allows setting
      of page titles, display types, menus, and more via database setting.
      An editor is provided.
    * Virtual UI pages are fully supported. This will allow catalog-specific
      UI settings to be transmitted to a catalog with simple database updates.
      Each page is simply an entry in mv_metadata.
    * The second-level menu can be set either with the page class, as before,
      or in the page metadata with $Scratch->{second_menu}.
    * There is a third-level menu callable via $Scratch->{third_menu}. There
      are few situations where the old "next_line" menu setting causes the
      third-level menu -- old menu files should be compatible but where possible
      the third-level menu is explicitly specified.
    * [table-editor] and [tabbed-display] can now do tabs to the third-level
      menus. This provides a very seamless tabbed display that does not
      require a page access to change.
    * Many changes made to pages to map output to the new template.
    * New GPG encryption wizard to make setting up of encryption as close
      to painless as I can make it.
    * Change to menu editor to incorporate better menu loading.
    * New merge_metadata function allows management of new metadata when
      updating the UI.
    * Many, many minor changes and visual improvements.
    * A good deal of documentation about the metadata and table editor
      has been written, and those items should be committed soon. Many
      of the features are covered.
    * Output of the parser is now sent to @Vend::Output, which allows remapping
      of the parser output before output by the Server module.
      There should be no difference in behavior by default.
      Each piece of output is pushed onto an array, and pointers
      are maintained as to the name of the output. The default if
      the output is not remapped is to go to the $Vend::OutputMap{''} space.
      When output is done in non-mapped mode, @Vend::Output is simply
      joined and sent.
      The behavior diffence comes if you use the Vend::Page::output_cat
      routine. It will output the value of a named space.
      You can map output with the ITL tag:
      	[output-to name=foo]
      To return to the default space, you use:
      	[output-to name=""]
      To return to the *previous* named space, use:
      That is not normally what is wanted, though.
      All of the above allows you to map pieces of a page to different named
      spaces and unpack them with the [unpack] tag.
      This is all perhaps easier illustrated than described -- the illustration
      is in the changes to the UI, which map output from the page code to the
Something went wrong with that request. Please try again.