Just updated BindLite to version 0.9.2 (build 24). It adds the following:
- Added BindLite.retrieveLast which lets you read the previous value of any bound property.
- Added public property autoDisposeBindings. Setting this to true will make BindLite dispose a binding if it no longer has any listeners after calling BindLite.unbind.
- Added public function BindLite.disposeBinding() to hard dispose a given binding.
This means you can now read the binding’s previous value when it gets set to a new value. This is useful for—say for instance—comparing an image gallery image index against its previous value to determine if the user clicked the next or the previous button.
This version also plays better with garbage collection because you can now have BindLite detect orphan bindings and remove them. Note that you need to specifically set autoDisposeBindings to true and actively remove a binding using unbind to make it run. You can also manually dispose a binding via disposeBinding(). Doing so will free all source and target refrences immediately.
BindLite is a lightweight, flex-less data binding alternative for AS3 applications. The reason I created it is to avoid including the flex.swc in my applications and to get a cleaner, more efficient syntax for data binding with better performance than the [Bindable] meta tag.
It is currently at version 0.9 for obvious reasons; I would like to hear from you about what you think, whether it works for you and if there are features it lacks. I have already tested it on two small projects and it has worked very well for me.
Just released Olog versjon 1.3.0. Looking forward, I will begin an effort to increase efficiency and compact the file size of Olog. The first part of this process is to extract some of the functionality to classes that can be injected by you, the user. This lead to the demise of OlogEvent. I must admint I went out on a limb here, becase since I don’t ever use OlogEvent myself anymore (to pass logging messages to Olog by event), I assumed no-one else does. Holler if this was a mistake, but my impression was that this is a safe move. This however means we also loose OlogEvent listening for getting log messages out, which I do know people are using. For you guys the solution is to write a class that implements ILogTarget and pass it to Olog like so: Olog.activateTargets([MyCustomLogTarget]);
The same change also propagates to a couple of other features, namely enableJavascripConsole and enableRegularTraceOutput. These are now log targets ConsoleTarget and TraceTarget respectively.
Changes to the Utility Panel
The mantra for Olog’s UI has always been “pretty enough”. I felt the buttons in the Utility Panel were a bit dated and claiming a little too much space, making it harder to add stuff. So I replaced them with a simple HTML TextFIeld and in the process I added a “Clear” button (suggested by @jenschr) and a button for checking if there’s a more recent version of Olog than the one you already have.
New LocalConnectionTarget
You can now activate a LocalConnection logging target for log message forwarding.
1UP if you’re on Windows
@fruitnoob made me aware that the logging font in Olog looked a little choppy on PCs. I’m not adding an embedded font (and 25k) to the package to change that and “_typewriter” is the only monospaced device font in the Flash Player, so Olog will now use one point size larger if it detects that it is running on Windows.
Full list:
Features:
- Added LocalConnectionTarget to logging targets
- Added support for custom log targets. These can be activated by Olog.activateTargets().
- Simplified utility panel
- Added check for updates to utility panel
- Added clear to utility panel to clear all text from log window
- Added data type comparison to assert()
- Added support for getters and setters in Olog.describe()
- Added warning for key binding overrides
Fixes:
- Fixed return boolean on assert
- Fixed breakPoint args. Primitive values are appended to the single line log message, one object is displayed with full description and one object followed by all string args will display a description filtered against the property names passed after the first argument.