At Your Service

Prepress AutoTools


  Version History

In The News

Contact Info


Macrobyte Resources

Siteliner Version History

Release Notes 1.0b10

    Ok, let's keep this simple. Everything changed! Please read the "About ..." items in the Siteliner menu, for all the details of using Siteliner. Here are the biggest changes:

  • Data Storage: Now Using Tables
    The #siteline object created by the "New Siteline" menu item is no longer an outline! It's now tables, created and managed with the help of the free Frontier suite blox (required, but free), produced by Brian Andresen at Technology Solutions.

    This is now the data format for Siteliner. It's much faster and more flexible than outlines, and will allow for future upgrades such as dynamic navigational outlines, planned for release before 1.0 is finalized.

  • New Menu Item: Show Outline View
    To make it easier to see what the final structure of your siteline will be, hilite the #siteline in your website's table, and choose Show Outline View from the Siteliner menu. An outline window will be opened, showing the full structure of your site.

  • Explorer: Loads of Changes
    The Explorer-Style siteline has been simplified, expanded, and improved. You can now specify custom icons for each page (optional), and there are lots of new icon classes available. There's too much for this History List, so read about it in the suite, at siteliner.["about insertExplorer"], or choose "About Explorer" from the Siteliner menu.

Release Notes 1.0b9.2

  • Small Bug in Explorer
    There was a small bug that only showed up when generating an Explorer-style sitline. The error message said that "linetext" is not an array.

Release Notes 1.0b9

  • Next Prevs!
    The first pass at Next-Prev linking has been included. Some instructions for usage are included in the suite. You can access them through the Siteliner menu.

  • Formatting Change
    The #siteline object is now much more readable. The [[#glossPatch ...]] mechanism is hidden from view, which makes reading your siteline much easier.

  • Massive Code Cleanup
    A general code cleanup happened throughout the suite. This means that something probably broke in the process, but I've tested most everything without finding any bugs.

  • Separate Tagging for Every Line
    You can now add custom tags to every line in the siteline. Colors, sizes, fonts... anything! The "At Your Service" line in Macrobyte's Siteline is an example of this new feature.

    1. Add the #sl_omitLineTag directive to the page or table which you want to use custom formatting tags. Set the value of the directive to "false". Note that adding it to a table affects all pages within that table, at every level, unless it is overridden by another directive which sets it to "true". Adding the directives to a page only affect that page.

    2. Add a "#sl_openLineTag" directive to the page or table. Set its value to the opening tag for the line. For example, you might set it to <COLOR='#FFFFFF'>

    3. Add a "#sl_closeLineTag" directive to the page or table. Its value should be the closing tag for the line. For exaple you might set it to </FONT>

  • Callbacks
    The user.siteliner.callbacks table is now created during initialization, which means you won't get the error "The name Callbacks has not been defined.".

  • Sorting
    Previously, you were limited to 999 pages in a given level of your site. Very few people would ever exceed that limit, but it's now been raised to 9999 pages.

Release Notes 1.0b8.2

  • Small Menu Fix
    As I prepared to produce Siteliner 1.0b9, I was reminded of a small bug in the menu: now, when you choose "Read Me" from the SiteLiner menu, it will now open the text object.

Release Notes 1.0b8

  • Explorer: Minor Bug Fix
    When using the explorer-type outline, the scripts were looking to see if you wanted the summit-level entries separated by a blank line, but that's not possible with the explorer-type outlines. It was generating an error. FIXED

Release Notes 1.0b7

  • Second Renderer
    A second renderer for the siteline is included, to use it add a macro to your web page or template: {siteliner.insertExplorer ()}. This script produces a Microsoft File Explorer style outline, complete with icons and the "dots" with the plus/minus signs.

    Have no idea what I'm talking about? Here's a sample site, that only includes the File Explorer-styled navbar (there is no content).

  • New Spacer Script "explorerSpacer"
    In support of the new renderer is a new spacer script, which takes some extra, optional parameters. It provides the correct .gifs for all of the possible configurations of your explorer-style siteline. It can be used with the regular siteline also, but the images will all be 'cold', not enclosed in Anchor tags.

  • Eleven New Images
    Also in support of the new renderer are eleven new gifs, for representing files, 'expanded' and 'collpased' folders, various 'plus' and 'minus' symbols, vertical and branching 'dots', and an exaple for the 'home' icon.

  • Longer Lines
    The default siteline renderer, insertSiteline, no longer has a limit on line length. Previous versions were limited to 255 characters, due to the limitations of a line in an outline. The renderer was rewritten to avoid this problem.

  • Callbacks
    The callbacks mechanism, which was introduced in version 1.0b4, has been changed slightly. Only one parameter is now sent to the script, which is the entire text of the current line, including any tags that have been added (image tags, line breaks, paragraph tags, etc.).

Release Notes 1.0b6

  • Close Brackets Bug, Again
    Another fix for the "|]]" bug. I understand what's going on here, finally, and I think I've fixed the majority of the causes. Technically, this isn't a bug, but it's better for the suite to flexibly handle whatever the user throws at it, than for the suite to require the users to behave themselves!

Release Notes 1.0b5

  • Close Brackets in Sitline Object
    Previously, if you had empty tables in a subtable of your website, you would get "\]]" lines in your siteline. Now that this bug has been identified, it's also been squashed. Onward!

Release Notes 1.0b4

  • New Callbacks Feature
    This new feature allows you to modify every line of the outline, customizing it completely. Choose 'New Callback Script' from the 'Siteliner' menu, and name the script whatever you want. The result returned from this script will replace the contents of the current line in the outline.

    More information on callbacks can be found in the README object at siteliner.README, and in the example callback at suites.siteliner.examples.exampleCallback

  • Close Brackets in Sitline Object
    Under certain circumstances, random lines in the #siteline outline would contain only "|]]". At least one major cause of this problem has now been identified and eliminated: subtables which only contain the default page (index, default, home, etc). If you still run into this problem, please send me a bug report!

  • New Preference: 'sl_topDefaultName'
    This preference is a string, and contains the text that appears in the 'siteline' outline, for the summit-level default page. On this site, the preference is set to 'Home', as can be seen to the left.

  • Recommendation
    There is a clear .gif provided with this suite, named 'blank'. You should copy this image to your site's #images table. If you don't, an image named 'blank.gif' will be created at the same level as every page which uses the siteline outline.

Release Notes 1.0b3

  • Better rendering
    The resulting outline is no longer run through html.tenderRender, but instead just returns the result as a string. The result is that NOBODY will get bullet-style outlines anymore, unless they want them (even then, they'll need to write a custom spacer callback).

  • Image handling
    An image named "blank" is now included. This image will be used if the image specified by your #sl_indentImage directive, or if your preferred image at user.siteliner.sl_indentImage, can't be found by the html.data.standardMacros.imageRef () script.

  • Updated Docs
    The documentation in the readme now includes documentation for two more directives, which were previously unexplained.

Release Notes 1.0b2

  • Garbage Outlines
    The most notable bug was that the #siteline object sometimes contained a bunch of garbage lines. Trying to render this by publishing a page which called {siteliner.insertSiteline ()} would crash some computers.

    The garbage lines were caused by the case-sensitivity of the script at html.getOneDirective. I've patched this with a new script, siteliner.getOneDirective, and so the problem appears to be solved.

This site built using Frontier 5 with a Macintosh. Last updated Tuesday, July 7, 1998
Contact Macrobyte Resources with comments or questions.