Thursday, July 31, 2008

Sorry for the noise, just testing here.

package
{
import flash.events.Event;
public class StockEvent extends Event
{
public static const FETCH_COMPLETE:String  = "complete";
public static const ERROR:String   = "error";
private var _data:Object;

function StockEvent( type:String, data:Object = null )
{
 super( type );
 _data = data;
}
public function get data():Object { return _data; }
}
}

<br />package<br />{<br /> import flash.events.Event;<br /> public class StockEvent extends Event<br /> {<br /> public static const FETCH_COMPLETE:String = "complete";<br /> public static const ERROR:String = "error";<br /> private var _data:Object;<br /> <br /> function StockEvent( type:String, data:Object = null )<br /> {<br /> super( type );<br /> _data = data;<br /> }<br /> public function get data():Object { return _data; }<br /> }<br />}

Okay, excellent - the only caveat is that on the main blog page, the entire page needs to load before the formatting is applied. This won't really affect a post page, but the consolidated page may be a little slower in rendering it's code content.

So the <br/> tags should be fixed now, as I had to previously set those myself every time I wanted carriage returns in ANY post (to ensure code display was formatted properly). Now that there is a method in SyntaxHighlighter (I stumbled onto this fact by accident), I can retain my auto-inserted returns without it blowing out my code blocks for display.

A good Thursday morning already.

0 Comments:

Links to this post:

 

<$BlogBacklinkSnippet$>
posted by <$BlogBacklinkAuthor$> @ <$BlogBacklinkDateTime$>

---

Create a Link