Release 1.1, introducing Ruby 1.9.3 support!

All tests pass, and the built documentation is identical in Ruby 1.8.7 and 1.9.3. However, a lot of tweaking took place, so use caution. Be prepared to encounter and report issues. If this is a problem, please use an earlier commit.

* The exifr gem is no longer used, and internal code for measuring the size of other image types has been removed. We now depend on the dimensions gem for all image sizes.

* Numerous regex matches that were really just ways of detecting whether a string starts or ends with a certain substring have been replaced by start_with? and end_with?

* Uses of to_a on a single-line string as a silly way to ensure an array have been replaced by Array().

* Pathname now implements to_str explicitly, to make up for the fact that it was taken away in Ruby 1.9.2. Ideally I'd like to eliminate all cases of implicit Pathname-to-String coercion; then this can be removed.

* Pathname.relative_uri_from attempts to work around a curious 1.9.x change of output from URI::Generic.route_from, on which it depends. Added a test for this edge case.

* Vastly improved our message/exception reporting routines. The require is brought to top level. In our stdout diverter, implemented flush, as Ruby 1.9.3 expects it. Much better behavior when there's an exception; at last exceptions containing <...> expressions will be legible! (I wondered what that lone "#" meant, but I didn't grasp that it was my own darned fault.)

* Altered one test to take account of changed structure of YAML library in Ruby 1.9.3; this is the only place in the code where I have to test for the RUBY_VERSION. Rename one badly named test. Rewrote some requires, as "." is no longer in $: in Ruby 1.9.3.

Author: mattneub

README.md

@@ -1,45 +1,45 @@
 RUBYFRONTIER
 =======
 
-RubyFrontier is a TextMate bundle, implementing a template-based system of building Web pages and (especially) Web sites in a highly automated manner. It generates static Web pages; it isn't a Web application framework. It is excellent for heavily hyperlinked pages and for automatic generation of navigation structures such as breadcrumbs, next-prev links, etc. The system is modeled in the first instance after UserLand Frontier's `html` suite, which I documented in my [Frontier book](http://sbc.apeth.com/frontierDef/ch41.html). RubyFrontier is written in Ruby and you are expected to know Ruby and to be willing to read and to program in Ruby in order to customize and specify its behavior. It also makes some rudimentary use of [YAML][]. You can optionally employ any other cool tools you like; for example, most of my RubyFrontier sites use things like [kramdown][] and [SASS][].
+RubyFrontier is a TextMate bundle, implementing a template-based system of building Web pages and (especially) Web sites in a highly automated manner. It generates static Web pages; it isn't a Web application framework. Its purpose is to make Web sites a convenient writing tool, separating form from content (you concentrate on content, and RubyFrontier wraps up that content into Web page form when you build the site). RubyFrontier is excellent for heavily hyperlinked pages and for automatic generation of navigation structures such as breadcrumbs, next-prev links, etc. The system is modeled in the first instance after UserLand Frontier's `html` suite, which I documented in my [Frontier book](http://sbc.apeth.com/frontierDef/ch41.html). RubyFrontier is written in Ruby and you are expected to know Ruby and to be willing to read and to program in Ruby in order to customize and specify its behavior. It also makes some rudimentary use of [YAML][]. You can optionally employ any other cool tools you like; for example, most of my RubyFrontier sites use things like [kramdown][] and [SASS][].
 
-For more information and full documentation, read <http://www.apeth.com/RubyFrontierDocs/>. 
+For more information and full documentation, read <http://www.apeth.com/RubyFrontierDocs/>. The documentation is itself a RubyFrontier-built site.
+
+For another example site, see my [documentation for Script Debugger 5](http://www.apeth.com/sd5help/index.html).
 
 
 GROUND OF BEING
 -----
 
 RubyFrontier is *not* a GUI tool. It is *not* for naive users. It is a programming tool for power users, and it has a learning curve: extremely full documentation and a couple of sample demonstration sites are included (one of the sample sites *is* the documentation), but you have to learn to do things the RubyFrontier way. Knowing Frontier, though not required, will help (RubyFrontier was written specifically to allow me to migrate my Web sites out of Frontier without much alteration); there are some differences, but they will be readily grasped by any former Frontier user, and I believe RubyFrontier actually does a number of things better than Frontier did.
 
-I have moved RubyFrontier from Sourceforge to GitHub, about the beginning of October 2011, in part because Sourceforge is horrible and getting worse by the day whereas GitHub is cool, but also because I want open source to mean open source. The chief purpose of RubyFrontier is as a tool for *me*, and for me, it works. If you don't agree, you don't have to use it. If you have a positive contribution to make, feel free to report, suggest, or fork and we can go from there.
-
-In preparation for the move to GitHub I've been writing some unit tests, thus providing some basis for believing that RubyFrontier mostly does what it's supposed to do. Because of these unit tests, along with the relative maturity and proven track record of RubyFrontier (in my own life at least), I have declared the version number 1.0 at the time of the move to GitHub, marking a milestone in the life of the code.
+I moved RubyFrontier from Sourceforge to GitHub, about the beginning of October 2011, in part because Sourceforge is horrible and getting worse by the day whereas GitHub is cool, but also because I wanted open source to mean open source. The chief purpose of RubyFrontier is as a tool for *me*, and for me, it works. If you don't agree, you don't have to use it. If you have a positive contribution to make, feel free to [report][], suggest, or fork and we can go from there.
 
 
 HISTORY
 -----
 
-For past history and version number, see the file "HISTORY" (inside the bundle).
+In preparation for the move to GitHub in October 2011 I wrote some unit tests, thus providing some basis for believing that RubyFrontier mostly does what it's supposed to do. Because of these unit tests, along with the relative maturity and proven track record of RubyFrontier (in my own life at least), I declared the version number 1.0 at the time of the move to GitHub, marking a milestone in the life of the code.
 
+In September 2012 another milestone was reached: RubyFrontier started working under Ruby 1.9.3. See the next section for more about that.
 
-FUTURE DIRECTIONS
------
+For past history and version number, see the file "HISTORY" (inside the bundle).
 
-I have two chief goals for the long term:
 
-* More and better unit tests. I've made a decent start, but in particular I need to get more specific about testing finer-grained parts and stages of the rendering engine.
+DEPENDENCIES
+-----
 
-* Compatibility with Ruby 1.9.x. I'm far from certain that Ruby 1.9.x is an unqualified success, but it is reasonable that people who use it should eventually expect RubyFrontier to work with it. Obviously the unit tests are intended, among other things, to lay the groundwork for implementing such compatibility.
+You need a Mac and TextMate (presumably TextMate 1.5.x; I have not tested with TextMate 2). Windows / Linux users and TextMate detractors, this is not the droid you're looking for. I might eventually relax the dependency on TextMate, but for now, despite its flaws, TextMate does so much for me and for RubyFrontier that I have not bothered to consider any other milieu.
 
+RubyFrontier was originally written under Ruby 1.8.6. I now use it under Ruby 1.8.7. In September 2012 I installed Ruby 1.9.3 and spent a couple of days testing and tweaking, and I am happy to say that RubyFrontier now appears to be working equally under Ruby 1.8.7 and 1.9.3. By "working equally" I mean that:
 
-DEPENDENCIES
------
+1. All tests pass. You could argue that the tests are a little weak and don't hit certain edge cases or go very deep into the page/site-building mechanism, and that's true enough. But it's something. And...
 
-You need a Mac and TextMate. Windows / Linux users and TextMate detractors, this is not the droid you're looking for. I might eventually relax the dependency on TextMate, but for now, despite its flaws, TextMate does so much for me and for RubyFrontier that I have not bothered to consider any other milieu.
+2. The documentation site (included in RubyFrontier) builds _identically_ under Ruby 1.8.7 and Ruby 1.9.3. I regard that as a highly encouraging sign.
 
-RubyFrontier was originally written under Ruby 1.8.6. I now use it under Ruby 1.8.7, and that is the version of Ruby I currently support. I would not expect RubyFrontier to work under 1.9.x yet (that is an eventual goal, however; see above).
+Therefore I now permit use of RubyFrontier under Ruby 1.9.3. Please bear in mind for now that getting RubyFrontier to work under Ruby 1.9.3 required a lot of tweaking, and I took the opportunity to do some code clean-up. Therefore it is _possible_ (though not expected) that some new bugs may have been introduced. I urge you to try it and to [report][] any issues. If the current state of RubyFrontier worries you, stick with Ruby 1.8.7 and use commit 611d787958, the last commit before the plunge into Ruby 1.9.3.
 
-Various parts of RubyFrontier, and the demonstration sites, use various libraries and gems, some of which you may not have installed. Many of these are initially "weak-linked", meaning that it is not a fatal error to lack them, but you'll probably want to install them anyway, as doing so can do no harm. For example, the part of RubyFrontier that deals with images uses the `exifr` gem to get the dimensions of TIFF images, but you do not need to install the `exifr` gem immediately - RubyFrontier will complain of its absence to you, but it will work just fine nevertheless as long as your Web sites have no TIFF images.
+Various parts of RubyFrontier, and the demonstration sites, use various libraries and gems, some of which you may not have installed. Many of these are initially "weak-linked", meaning that it is not a fatal error to lack them, but you'll probably want to install them anyway, as doing so can do no harm. For example, the part of RubyFrontier that deals with images uses the `dimensions` gem to get the dimensions of images, but you do not need to install the `dimensions` gem immediately - RubyFrontier will complain of its absence to you, but it will work just fine nevertheless as long as your Web sites have no images.
 
 
 INSTALLATION
@@ -53,7 +53,7 @@ What I personally do is put a symlink in _~/Library/Application Support/TextMate
 PREPARATION
 -----
 
-You are expected (though not required) to have a _user.rb_ file outside the bundle. Whenever a RubyFrontier command runs, the _user.rb_ file is loaded after all of RubyFrontier's own code has loaded. Thus, _user.rb_ is your opportunity to add to or customize RubyFrontier's behavior globally (as opposed to the many customizations you can have in a particular Web site folder). For example, this is where you implement glossary entries and outline renderers that you wish to have available in all your sites. If you wanted, you could even open the PageMaker class and add or even rewrite methods, without touching the code in the bundle.
+You are permitted (though not required) to have a _user.rb_ file outside the bundle. Whenever a RubyFrontier command runs, the _user.rb_ file is loaded after all of RubyFrontier's own code has loaded. Thus, _user.rb_ is your opportunity to add to or customize RubyFrontier's behavior globally (as opposed to the many customizations you can have in a particular Web site folder, plus there is also a mechanism for keeping a _user.rb_ in an individual site folder). For example, this is where you implement glossary entries and outline renderers that you wish to have available in all your sites. If you wanted, you could even open the PageMaker class and add or even rewrite methods, without touching the code in the bundle.
 
 To set the location of this _user.rb_ file, use the RubyFrontier > Locate User.rb File command. Your _user.rb_ does not actually have to be called "user.rb", but it should be a Ruby file.
 
@@ -65,10 +65,14 @@ The docs are available on the Web:
 
 > <http://www.apeth.com/RubyFrontierDocs/default.html>
 
-However, the docs are also included in RubyFrontier, and they are themselves a RubyFrontier Web site, so they are a demonstration (and test) of RubyFrontier. Choose RubyFrontier > Build RubyFrontier Docs. (Alternatively, drill down in _RubyFrontier.tmbundle_ to _Support/bin/RubyFrontier/longestJourney/docs/RubyFrontierDocumentation/default.txt_. With the _default.txt_ file selected, choose RubyFrontier > Publish Site.) After a heart-stopping pause, the documentation Web site will be built in a new folder on your Desktop and the first page of the site will open in your browser. Read and enjoy.
+However, the docs are also included in RubyFrontier, and they are themselves a RubyFrontier Web site, so they are a demonstration (and test) of RubyFrontier. Choose RubyFrontier > Build RubyFrontier Docs. After a heart-stopping pause, the documentation Web site will be built in a new folder on your Desktop and the first page of the site will open in your browser. Read and enjoy.
 
-A shortcut to view the source for the docs (so that you can study how the docs site is constructed) is RubyFrontier > Show RubyFrontier Docs Source.
+Alternatively, choose RubyFrontier > Show RubyFrontier Docs Source. This command is so that you can study how the docs site is constructed. You can then also build the docs by selecting the _default.txt_ file and then choosing RubyFrontier > Publish Site. 
+
+FUTURE DIRECTIONS
+-----
 
+Now that RubyFrontier is apparently usable with Ruby 1.9.3, my chief goal is more and better unit tests, in order to keep making sure that RubyFrontier works equally in Ruby 1.8.7 and Ruby 1.9.3.
 
 LICENSE
 -----
@@ -85,4 +89,5 @@ Matt Neuburg (<matt@tidbits.com>, <http://www.apeth.net/matt/>)
 [Haml]: http://haml-lang.com/
 [SASS]: http://sass-lang.com/
 [YAML]: http://yaml.org/
+[report]: https://github.com/mattneub/RubyFrontier/issues
 

RubyFrontier.tmbundle/HISTORY

@@ -1,7 +1,7 @@
 VERSION
 =======
 
-This is version 1.0.2.
+This is version 1.1. The version increment marks the beginning of usability under Ruby 1.9.3. WARNING: This took a lot of tweaking, and despite my best efforts, new bugs may have been introduced.
 
 HISTORY
 =======
@@ -42,3 +42,5 @@ In version 1.0.1, expanded the user.rb mechanism to allow inclusion of a #user.r
 
 In version 1.0.2, introduced a mechanism to allow a `.txt` file to function as an outline (like a `.opml`) file, by using indentation and setting the `:treatasopml` directive to `true`. Documentation updated.
 
+In version 1.1, support for Ruby 1.9.3 was added, along with some general code cleanup. Dependency on exifr removed, replaced by dependency on dimensions. Improved message/exception formatting.
+

RubyFrontier.tmbundle/Support/bin/RubyFrontier/longestJourney.rb

@@ -2,7 +2,7 @@
 # utilities: myrequire, myraise, Memoizable, and various modifications to existing classes
 require 'longestJourneyUtilities.rb'
 
-myrequire "pathname", "yaml", "erb", "pp", "uri", "rubygems", "exifr", "enumerator", "kramdown", "haml", "sass", "nokogiri"
+myrequire "pathname", "yaml", "erb", "pp", "uri", "rubygems", "dimensions", "enumerator", "kramdown", "haml", "sass", "nokogiri"
 
 =begin make 'load' and 'require' include folder next to, and with same name as, this file 
 that is where supplementary files go

RubyFrontier.tmbundle/Support/bin/RubyFrontier/longestJourney/docs/RubyFrontierDocumentation/#tools/truenext.rb

@@ -16,7 +16,7 @@ def truenext()
     nomad = obj
     while true
       nomad = nomad.dirname
-      if nomad.to_s =~ /folder$/i
+      if nomad.to_s.downcase.end_with? "folder"
         daddy = nomad.basename.to_s[0..-7]
         if @adrPageTable[:autoglossary][daddy]
           daddyObj = @adrPageTable[:autoglossary][daddy][:adr]

RubyFrontier.tmbundle/Support/bin/RubyFrontier/longestJourney/docs/RubyFrontierDocumentation/defaultfolder/whyrf.txt

@@ -2,7 +2,7 @@
 
 ## Why RubyFrontier?
 
-There are plenty of Web site frameworks and generators out there, from the massive [Dreamweaver](http://www.adobe.com/products/dreamweaver/) or [FrontPage](http://office.microsoft.com/en-us/frontpage/default.aspx) down to alternative Ruby-based systems such as [Webby](http://webby.rubyforge.org/) and [nanoc](http://nanoc.stoneship.org/) and [webgen](http://webgen.rubyforge.org/documentation/) and [jekyll](http://github.com/mojombo/jekyll) and many others, so who needs another one?
+There are plenty of Web site frameworks and generators out there, from the massive [Dreamweaver](http://www.adobe.com/products/dreamweaver/) or [FrontPage](http://office.microsoft.com/en-us/frontpage/default.aspx) down to alternative Ruby-based systems such as [Webby](http://webby.rubyforge.org/) and [nanoc](http://nanoc.stoneship.org/) and [webgen](http://webgen.rubyforge.org/documentation/) and [jekyll](http://github.com/mojombo/jekyll), [ZenWeb](https://github.com/seattlerb/zenweb) and many others, so who needs another one?
 
 I do. RubyFrontier was written for *me*. It does what I want it to do. I had a particular problem and RubyFrontier solves it.
 

RubyFrontier.tmbundle/Support/bin/RubyFrontier/longestJourney/userland_class_methods.rb

@@ -38,7 +38,7 @@ def self.releaseRenderedPage(adrObject, flPreview = true, doTimings = true)
 
     pm.saveOutAutoglossary # save out autoglossary if any
 
-    if flPreview && (File.extname(pm.adrPageTable[:fname]) =~ /\.htm/i) # supposed to be a test for browser displayability
+    if flPreview && (File.extname(pm.adrPageTable[:fname]).downcase.start_with?(".htm")) # supposed to be a test for browser displayability
       if (apacheURL = pm.adrPageTable[:ftpsite][:apacheURL])
         f = pm.adrPageTable[:f].relative_path_from(Pathname(pm.adrPageTable[:ftpsite][:apacheSite]).expand_path)
         `open #{URI.escape(apacheURL + f)}`
@@ -86,7 +86,7 @@ def self.everyPageOfFolder(f)
     # distinguish from pagesInFolder which is shallow, only during rendering, only renderables, and uses #nextprevs order
     result = Array.new
     Pathname(f).find do |p|
-      Find.prune if p.basename.to_s =~ /^[#.]/
+      Find.prune if p.basename.to_s.start_with?("#", ".")
       result << p if (!p.directory? && p.simplename != "") # ignore invisibles
     end
     result

RubyFrontier.tmbundle/Support/bin/RubyFrontier/longestJourney/userland_pagemaker.rb

@@ -290,14 +290,14 @@ def buildPageTableForDirectory(adrObjectDir) # never call this directly unless y
       found_ftpsite = false
       adrObjectDir.ascend do |dir|
         dir.each_entry do |f|
-          if /^#/ =~ f
+          if f.to_s.start_with?("#")
             dirf = dir + f
             case (directive = f.simplename.to_s.downcase) # special casing of certain directives
             when "#tools"
               # gather tools into tools hash, hashing pathnames under simple filenames
               # new feature (non-Frontier), .txt files go into snippets hash
               dirf.each_entry do |ff|
-                unless /^\./ =~ (tool_simplename = ff.simplename.to_s.downcase)
+                unless (tool_simplename = ff.simplename.to_s.downcase).start_with?(".")
                   case ff.extname
                   when ".rb"
                     adrPageTable["tools"][tool_simplename] ||= dirf + ff
@@ -309,7 +309,7 @@ def buildPageTableForDirectory(adrObjectDir) # never call this directly unless y
             when "#images", "#stylesheets", "#javascripts" 
               # gather contents into single hash, hashing pathnames under simple filenames
               dirf.each_entry do |ff|
-                unless /^\./ =~ (ref_simplename = ff.simplename.to_s.downcase)
+                unless (ref_simplename = ff.simplename.to_s.downcase).start_with?(".")
                   adrPageTable[directive[1..-1]][ref_simplename] ||= dirf + ff
                 end
               end
@@ -427,15 +427,15 @@ def incorporateDirective(k, v, yieldToExisting=false, adrPageTable=@adrPageTable
     if s =~ /^stylesheet./i
       adrPageTable[:linkstylesheets] << s[10..-1]
     elsif s.downcase == "linkstylesheets"
-      adrPageTable[:linkstylesheets] += v.to_a
+      adrPageTable[:linkstylesheets] += Array(v)
     elsif s.downcase == "linkstylesheetsnot"
-      adrPageTable[:linkstylesheets] -= v.to_a
+      adrPageTable[:linkstylesheets] -= Array(v)
     elsif s =~ /^javascript./i
       adrPageTable[:linkjavascripts] << s[10..-1]
     elsif s.downcase == "linkjavascripts"
-      adrPageTable[:linkjavascripts] += v.to_a
+      adrPageTable[:linkjavascripts] += Array(v)
     elsif s.downcase == "linkjavascriptsnot"
-      adrPageTable[:linkjavascripts] -= v.to_a
+      adrPageTable[:linkjavascripts] -= Array(v)
     else
       if yieldToExisting
         adrPageTable[k] ||= v
@@ -610,7 +610,7 @@ def pagesInFolder(folder, adrPageTable=@adrPageTable)
     else
       # if not, just use alphabetical order
       folder.children.each do |p|
-        next if p.basename.to_s =~ /^[#.]/
+        next if p.basename.to_s.start_with?("#", ".")
         arr << p.simplename.to_s if renderable?(p)
       end
     end

RubyFrontier.tmbundle/Support/bin/RubyFrontier/longestJourney/userland_standard_macros.rb

@@ -173,7 +173,7 @@ def bodytag(adrPageTable=@adrPageTable) # generate body tag, drawing attributes
       if s = adrPageTable.fetch2(oneatt.to_sym)
         if %w{alink bgcolor text link vlink}.include?(oneatt)
           # colors should be hex and start with #
-          unless s =~ /^#/
+          unless s.start_with?("#")
             if s.length == 6
               unless s =~ /[^0-9a-f]/i
                 s = "#" + s