File:  [mozdev] / betterblogger / www / index.html
Revision 1.5: download - view: text, annotated - select for diffs - revision graph
Sat Apr 16 07:43:06 2005 UTC (12 years, 8 months ago) by foobario
Branches: MAIN
CVS tags: HEAD
*** empty log message ***



<!-- ***************** INFO/NEWS *************** -->
<div id="infoTabs">
<div class="infoTab" id="whats-new">
<h5 class="infoHeader">What's New</h5>
<ul>
<li>Initial release</li>

<li><a href="http://www.mozdev.org/">mozdev.org</a></li>
</ul>
</div>

<div class="infoTab" id="other-stuff">
<h5 class="infoHeader">Release history:</h5>
<ul>
<li>Bb0.1 - 6 April 04</li>
</ul>
</div>

<!-- alternative image/table base tab works better in NS4 -->
<!--
<div class="infoTab" id="whats-new-image">
<h5 class="infoHeader"><img src="http://www.mozdev.org/sharedimages/whatsnew_top.gif" width="154" alt="What's New"></h5>
<div class="infoItems">
<div>News item goes here</div>
<div>More news item goes here</div>
<div><a href="http://mozdev.org/">mozdev.org</a></div>
</div>
</div>
-->
</div>
<!-- ***************** INFO/NEWS *************** -->

<!-- MAIN CONTENT -->
<h3>Betterblogger: Using Greasemonkey to customize Blogger.com's GUI.</h3>
<p>Download <a href="http://betterblogger.mozdev.org/betterblogger.user.js">betterblogger.user.js</a></p>
<p><a href="http://greasemonkey.mozdev.org">greasemonkey</a> made most of the code I'd written obsolete in one fell swoop.  Thanks, greasemonkey!  As a result I have decided to turn this into a greasemonkey user script rather than an extension... if you can't beat em (and greasemonkey rocks, btw), join em.</p>
<h4>The medium is the message?</h4>
<p>With the advent of CSS and DHTML, the dominant web-coding paradigm shifted from table-mania to strict separation of presentation and content.  As with any issue, there are numerous interpretations of how to do this.  Blogger chooses the strictest separation: even <b>bold</b> and <i>italic</i> are &lt;span&gt;s with <i>style</i> properties applied.  I found myself not using their handy little GUI buttons, because replacing &lt;b&gt;&lt;/b&gt; with &lt;span style="font-decoration: bold"&gt;&lt;/span&gt; seemed a bit excessive to me, and because I believe that in an information-theory sense there are times when bolding or italicizing some text is part of the message, not part of the presentation of the message... i.e. if that text shows up unstyled, information has been lost.</p>
<p>I also find that I have a number of tasks I repeat endlessly when using Blogger, pieces of code that could benefit from automation.  For example, I attribute the source of an item with &lt;span class="via">[via <a href="whereever">whatever</a>]</span>.  The 0.1 release of Betterblogger adds a CTRL-SHIFT-V macro works similar to Blogger's link button: popups ask for the link and the link text, and the code is plopped into place.</p>
<h4>To do:</h4>
<ul><li>Figure out how to actually inject buttons into the Blogger GUI.  The first version of Betterblogger, which was an extension, could do this, but greasemonkey code executes before the DOM objects have been instantiated.  I'm working on finding a way around this that doesn't involve arbitrary-length setTimeout()'s.</li>
<li>Add additional formatting buttons for various markup-heavy operations: gallery-style formatting for posts with a lot of pictures (such as tutorials), smart nested UL generation, and application of classes and styling to definition lists, ULs and OLs.</li>
<li>Add enough functionality to justify the existence of this user script :)</li></ul>

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>