BxMS 0.0.18

data/bin/bxms

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby -w
+
+begin
+  require 'bxms'
+rescue LoadError
+  require 'rubygems'
+  require 'bxms'
+end

data/bin/bxms.bat

@@ -0,0 +1,3 @@
+@ECHO OFF
+
+ruby -S bxms.rb %*

data/bin/bxms.rb

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby -w
+
+begin
+  require 'bxms'
+rescue LoadError
+  require 'rubygems'
+  require 'bxms'
+end

data/bin/bxms.sh

@@ -0,0 +1,3 @@
+#!/bin/sh
+
+ruby -S bxms.rb $*

data/examples/www.berlinfactor.com/Bx.css

@@ -0,0 +1,317 @@
+
+a:visited
+  {
+  color: #602000;
+  text-decoration: none;
+  background-color: transparent;
+  }
+
+a:link
+  {
+  color: #602000;
+  text-decoration: none;
+  background-color: transparent;
+  }
+
+a:active
+  {
+  color: #602000;
+  text-decoration: underline;
+  background-color: transparent;
+  }
+
+a:hover
+  {
+  color: #602000;
+  text-decoration: underline;
+  background-color: transparent;
+  }
+
+body
+  {
+  font-family: Trebuchet MS,Trebuchet,Arial,Helvetica,sans-serif;
+  font-weight: normal;
+  font-size: 10pt;
+  color: #705D2C;
+  background-color: #FFFFFF;
+  }
+
+p
+  {
+  }
+
+img
+  {
+  font-family: Trebuchet MS,Trebuchet,Arial,Helvetica,sans-serif;
+  font-size: 12pt;
+  border: 0px;
+  }
+
+
+
+#body
+  {
+  width: 802px;
+  height: 602px;
+  margin: 10px auto;
+  padding: 0px;
+  }
+
+#frame
+  {
+  width: 800px;
+  height: 600px;
+  margin: 0px;
+  padding: 0px;
+
+  background-image: url(images/background.png);
+
+  border-style: solid;
+  border-width: 1px;
+  border-color: #CBBCB3;
+  }
+
+#header
+  {
+  height: 183px;
+  }
+
+#logo
+  {
+  float: left;
+  width: 380px;
+  height: 183px;
+  }
+
+#sections
+  {
+  float: right;
+  width: 418px;
+  height: 183px;
+  overflow: hidden;
+  }
+
+#section_name
+  {
+  width: 418px;
+  height: 150px;
+  overflow: hidden;
+  }
+
+#section_menu
+  {
+  float: right;
+  padding: 3px 3px 0px 0px;
+  }
+
+#logo_above
+  {
+  width: 380px;
+  height: 8px;
+  }
+
+#logo_clickable
+  {
+  width: 380px;
+  height: 38px;
+  }
+
+#logo_below
+  {
+  width: 380px;
+  height: 137px;
+  }
+
+#page_body
+  {
+  padding: 6px 3px 3px 3px;
+  height: 383px;
+  }
+
+#column_left
+  {
+  float: left;
+  width: 373px;
+  height: 383px;
+  overflow: auto;
+  }
+
+#column_right
+  {
+  float: right;
+  width: 415px;
+  height: 383px;
+  overflow: auto;
+  }
+
+#section_paragraph
+  {
+  padding: 10px;
+  }
+
+#footer
+  {
+  padding: 5px 5px 2px 5px;
+  height: 18px;
+  overflow: hidden;
+  }
+
+#footer_left
+  {
+  float: left;
+  }
+
+#footer_right
+  {
+  float: right;
+  }
+
+#w3c_logos
+  {
+  float: right;
+  padding: 10px 5px;
+  }
+
+
+.section_menu_entry
+  {
+  width: 39px;
+  height: 27px;
+
+  text-align: right;
+  }
+
+.news_entry
+  {
+  color: #602000;
+  }
+
+.news_entry_date
+  {
+  float: left;
+  font-weight: bold;
+  }
+
+.news_entry_title
+  {
+  float: left;
+  font-weight: bold;
+  padding-left: 10px;
+  }
+
+.news_entry_body
+  {
+  clear: both;
+  padding: 5px;
+  padding-bottom: 15px;
+  }
+
+.news_ref
+  {
+  clear: both;
+  }
+
+.news_ref_date
+  {
+  font-weight: bold;
+  }
+
+.news_ref_title
+  {
+  font-weight: bold;
+  }
+
+.book_entry
+  {
+  padding-top: 12px;
+  color: #602000;
+  }
+
+.book_entry_title
+  {
+  font-weight: bold;
+  }
+
+.book_entry_body
+  {
+  padding: 5px;
+  padding-bottom: 15px;
+  }
+
+.book_ref
+  {
+  padding-top: 12px;
+  color: #602000;
+  }
+
+.book_ref_title
+  {
+  font-weight: bold;
+  }
+
+.book_ref_body
+  {
+  padding: 5px;
+  padding-bottom: 15px;
+  }
+
+.link
+  {
+  }
+
+.link_back
+  {
+  padding: 5px;
+  }
+
+.external_link
+  {
+  }
+
+.simple_link
+  {
+  }
+
+.project_details
+  {
+  }
+
+.project_screenshots
+  {
+  padding: 5px;
+  }
+
+.project_downloads
+  {
+  padding: 5px;
+  }
+
+.project_notes
+  {
+  padding: 5px;
+  }
+
+.project_screenshot
+  {
+  padding: 5px;
+  }
+
+.project_credits
+  {
+  padding: 5px;
+  }
+
+.project_downloads
+  {
+  padding: 5px;
+  }
+
+.symbian_project_link
+  {
+  float: left;
+  width: 150px;
+  }
+
+.text
+  {
+  }

data/examples/www.berlinfactor.com/Bx.js

@@ -0,0 +1,39 @@
+<%
+  sections = list_file_names "Section*"
+  sections.each do |section_folder|
+    section = section_folder.downcase.gsub '.', '_'
+
+    suffixes = [ '', '_name', '_hover' ]
+    suffixes.each do |suffix|
+      image_handle = section + suffix
+%>
+      var <%=image_handle%> = new Image();
+      <%=image_handle%>.src = "images/<%=image_handle%>.gif";
+<%
+    end
+  end
+%>
+
+
+
+function select_section( aImagesFolder, aSectionID, aSectionTitle )
+	{
+	image_prefix = aImagesFolder + '/section_' + aSectionID;
+	set_image( 'section_name', image_prefix + '_name.gif' );
+	set_image( aSectionID, image_prefix + '_hover.gif' );
+	window.status = '// ' + aSectionTitle;
+	return true;
+	}
+
+function unselect_section( aImagesFolder, aSectionID, aBackgroundImageURL )
+	{
+	set_image( 'section_name', aBackgroundImageURL );
+	set_image( aSectionID, aImagesFolder + '/section_' + aSectionID );
+	window.status = '';
+	return true;
+	}
+
+function set_image( aImageID, aImageURL )
+	{
+	window.document.images[ aImageID ].src = aImageURL;
+	}

data/examples/www.berlinfactor.com/Section.Books/books.txt

@@ -0,0 +1,198 @@
+FORMAT: AUTHOR, TITLE, BODY
+ANCHOR: BOOKS
+
+[ENTRY]
+Andrew Hunt & Dave Thomas
+The Pragmatic Programmer
+
+A must read for every serious developer. That's it!
+
+I love this book. It somehow managed to <i>streamline</i> my thinking..
+Powerful metaphores. Important techniques.
+
+This really is a must have!
+
+Recommended read!
+
+[ENTRY]
+Michael C. Feathers
+Working Effectively with Legacy Code
+
+Absolutely a must read!
+
+Like Kent Beck's Test Driven Development with code you're about to
+write, the focus on testing is really important with legacy code, too.
+
+But what is legacy code? Don't make the mistake of thinking this is
+about Cobol code or something.. :) Even though it could be Cobol code, it
+also covers the code you wrote last week - before you knew how to do it
+the right way..
+
+Have you read Kent Beck's Test Driven Development? Do you do test
+driven development? If not, there's something out there which definitly is
+worth exploring..
+
+Michael Feather's book is really good at giving names to common
+situations/problems. And showing you how to make legacy code 'testable'.
+All this is important to have a safe foundation for cleaning up legacy
+code, or adding features, or fixing bugs.. Good and interesting book!
+
+Recommended read!
+
+[ENTRY]
+Kent Beck
+Test Driven Development
+
+Very(!) interesting read. Honestly, I am not really as disciplined as
+one should be to be able to follow this approach. But I surely see the
+benefits.
+
+I understand - in comparison - the limited benefits of "stupid unit
+testing" as most people I know (including me) are doing. That is, writing
+the tests after you coded bullshit :)
+
+I wish I could just throw away my current behaviour and go 100% TDD
+(Test Driven Development). But somehow it is not that easy. I am not sure
+why..
+
+Anyway, this is important stuff! The Art of Unit Testing :-) So grab a
+copy and read through it.
+
+Recommended read!
+
+[ENTRY]
+Pete McBreen
+Software.Craftsmanship
+
+What a nice book! I wish I could be one of those craftsmen getting paid
+five times as much as the rest of the world.
+
+Seriously, this is a good book. Also sometimes stretching a topic a bit
+too long or restating a point a bit too often, this book clearly states
+what people should realize about software development: It's really like
+that 1 to 10 factor. You simply cannot expect a guy having a
+Fucked-Up-Bullshit Licensed Engineer certificate to be a good developer.
+You need to check the background of the people. Ask about their projects.
+Ask the customers! Get this feedback. This is much more important than
+some kind of bullshit certificate or perfect grades in school ;-)
+
+This book is for managers, I think. Because as a developer, when reading
+this book, you just get more angry about the way things are.. :-(
+
+[ENTRY]
+Alistair Cockburn
+Agile Software Development
+
+A difficult book. Not easy to read. Well.. for me.. at least. I think I
+am reading this book for three months now :-) Still not finished. Hmm..
+somehow it is not as "easy" as most other books.
+
+Is this bad? I am not sure. I guess it is the topic that makes it so
+"uneasy" to read. Parts of it, like for example about "Theory Building"
+are very interesting. Other parts like for example the discussion about
+how people should be seated are.. well.. I guess they are required. But I
+found them quite.. boring.. :-)
+
+Anyway. Very interesting read here. Agile is the way to go. Check out
+${ExternalLink( "http://www.agilealliance.org", "The Agile Alliance" )}.
+
+The Unified Process and stuff like that? Not my kind of thing..
+
+[ENTRY]
+Steve McConnell
+Code Complete (2nd Edition)
+
+Forget about the first edition of the book. Total crap! But this 2nd
+edition. Well.. a lot like a developer matures on his way, Steve managed
+to drop all the bullshit subjective advice and wrote a nice 'summarizing'
+book on a lot of topics.
+
+Good read this one!
+
+Recommended read!
+
+[ENTRY]
+Steve McConnell
+Rapid Development
+
+Didn't like this book. Maybe because I have a different view on things.
+A bit a least. And maybe, just maybe, because I don't like Micro$oft too
+much.
+
+It's a bit like this guy's first edition of Code Complete. Too
+subjective. Not really sound.. well..
+
+[ENTRY]
+Diomidis Spinellis
+Code Reading
+
+More or less for beginners only. If you're a passionate developer, you
+don't need this book. You already do what you do.. bascially.. :)
+
+[ENTRY]
+Mike Gunderloy
+Coder To Developer
+
+I bought this book after I saw it being mentioned on some web-site. Some
+blog maybe? Joel maybe? Don't remember..
+
+It's not bad. But it's not really good, either. Far from the importance of
+The Pragmatic Progammer, or Working Effecively with Legacy Code, or Test
+Driven Development. And somewhere between the quality of Code Complete
+Edition 1 and 2.
+
+But somehow I liked it. It gave me a different view on some topics. Which
+I always consider a good thing..
+
+[ENTRY]
+Andrew Hunt & Dave Thomas
+Pragmatic Version Control, Pragmatic Unit Testing
+
+Good books - especially for beginners. Contained a few things I didn't
+know about (some special CVS features). And all in all nice write-ups of
+how to get started(!) with version control and unit testing.
+
+[ENTRY]
+Mike Clark
+Pragmatic Project Automation
+
+Personally, I think this is the best (read: most intersting) book of the
+Pragmatic Starter Series.. How to get started with project automation.
+Build servers, notification, setting up a project, .. Nice book!
+
+[ENTRY]
+Robert L. Glass
+Facts and Fallacies of Sofware Engineering
+
+I liked this book. Sure, you can always disagree on certain topics. But
+what does that mean?
+
+This book has some interesting stories and a lot of interesting 'facts'. I
+enjoyed reading this one!
+
+[ENTRY]
+Luke Hohmann
+Beyond Software Architecture
+
+The one thing I remember about this book is 'spikes'. Architectural
+'spikes'. For exploring a certain aspect of a system's architecture.
+
+Well, this topic had been covered in an Artima interview, too. Maybe
+that's why I remember it.. :)
+
+Anyway, I liked this book. Covered some interesting stuff. Far from the
+quality of The Pragmatic Programmer or something like that. But then again
+definitly with different subject/focus and therefore worth a read.
+
+[ENTRY]
+Scott Meyers
+Effective C++ Second Edition
+Must read for serious C++ developers.
+
+My personal opinion on some advanced C++ features (and probably advanced
+language features in general): Avoid them as often as possible! :)
+
+[ENTRY]
+Jon Bentley
+Programming Pearls
+Interesting read. (That was helpful, right? :)