I am sure everybody is blogging about this already, so i am going to be short: Macromedia Central 1.5 is finally out. New features in this release (btw, this is still a developer release) are: - File I/O support - File upload and download support - Automatic network detection - Flash MX 2004 extensions to better integrate Flash authoring with Central during development - Support for Flash Player 7, ActionScript 2.0, and the new component architecture - Support for instant messaging and presence detection using the AOL AIM and ICQ networks Also, Macromedia distilled Central licensing down into two simple models: - open distribution - try buy
As2docgenerator Going Opensource
I recieved quite a few emails regarding as2docgenerator updates, aditional features, offering help, asking for source code … and i would like to thank each one of you for showing interest in this little project :)
I realized that if as2docgenerator is going to improve i would need help from other developers, so i decided to submit it to berliOS Developer website (thank you Aral for the tip :)) under the GNU GLP. If you want to help you need to register at berliOS and then mail me your username so i can add you to the project.
ps. i forgot to give my mail address: klaut[at]klaustrofobik[dot]org
Facelift
Just a little facelift … Don’t you just love css :) … well.. apart from the footer that does not show right in IE :|
AS2docGenerator Minor Update
Finally, i have some minor updates to the AS2docGenerator: - added suport for the @interface tag, - you can now add as a parameter a directory containing .as class files (or other directories with .as class files) and it will generate a _docs directory with all the html outputs
example usage: 1) single .as file: C:> [path to]AS2docGenerator.exe [path to]AS2class.as this generates a AS2class_doc.html file in the same directory AS2class.as is in.
2) a directory with .as files and/or other directories: C:> [path to]AS2docGenerator.exe [path to]AS2classDirectory this generates a docs directory in the same directory where the AS2docGenerator.exe was called from. All the asClass_doc.html files are in the docs directory.
The project is still in beta so bugs and other naughty insects are possible ;)
Simple Interactive Expression Parser
It’s been a long time since my last post and to put some “life” back to this blog, i thought i’d post one of those “ported from java” experiments. Very little work on my part, actually.. thanks to syntax similarities between AS2 and java.
This one is from the book The Art of Java, Chapter 2: A Recursive-Descent Expression Parser.
Movable Type and Python
There are some python utilities that use Movable Type’s XML-RPC interface and thus allow you to view, post, delete and edit weblog entries, and more… PyMT mtsend.py
.. and of course, i just got a really cool idea (to me at least ;)) what if i make a flash interface for such a tool? We know how to embed flash into python, don’t we? :) right, .. all i need is some free time ….
Flash MX2004 LiveDocs
This is something i didn’t know it exsisted until just recently: Flash MX2004 Livedocs at MM site. All the documentation from the Help panel is now online, but you can also add your own comments or code samples and read others. It is something that’s got potential if flash users (we) will start “using” it :)
MX 2004 Updater
I woke up today just to find out that Macromedia Flash MX 2004 updater is here! :) And if your trial has already expired, no worries. The updater will extend it for another 30 days. That’s really cool of Macromedia.
Leave the Last Test Broken…
Been reading Test driven Development at the moment (toghether with other 10 or so books, heh) and today i came accross this sentence that really got me. It’s one of those things you want to write on a piece of paper and stick it on your monitor so you never forget. Kent Beck says: “How do you leave a programming session when you’re programming alone? Leave the last test broken.”
Basically he is saying that one should never leave the code for the next session in a perfectly working state. Before leaving, one should always make one last thing and make sure that that last thing does not work. …so that when you come back to the code, you then have an obvious place to start - “an obvious, concrete bookmark to help you remember what you were thinking”. This will also keep you away from just staring at the code and marvelling at how everything works, trying to think of what to work on next but not really starting it yet cos you don’t want to break anything so soon ;) .. or just trying to remember the mental state you were in and thus wasting a lot of time before finally getting back to typing. (happens to me a lot of times!)
This does not work out well if you’re working with a team, though ;)
New Blog for Your Bookmarks
Burak KALAYCI , the guy behind Actionscript Viewer has started his own blog. Go bookmark it now! :)
via MediaSparkles.