November 29th, 2007 by enefekt
Following up on the efforts that a few others had already started (including someone named Robbish who’s blog is gone), I’ve updated the macros and language spec files for ActionScript 3 to work with Xcode 3.
Xcode 3 switched from pblangspec files to xclangspec. The macros format and pbfilespec files had a few tweaks to be made as well. There are a few lines still left in the pblangspec file, Xcode didn’t seem happy without them, or with them moved into the xclangspec file. I wasn’t able to keep the method parameters in the code completion, it wouldn’t properly work with some of the different characters in there. I tried a few things, but it didn’t work. If I or someone else gets that figured out, it will be updated.
As a brand spankin’ new addition, and as a result of Xcode 3 having better support for XML, I was able to get an xclangspec going for MXML too! I even have ActionScript in the CDATA blocks working! It works hand-in-hand with the ActionScript.xclangspec file.
This is a first stab, and no doubt can be improved on, but at least I’m rockin’ and rollin’ with Xcode 3 now. To use, just drop the files here:
If you are moving a project over from an older Xcode project, the ActionScript and MXML files may not automatically register. As you work on them, simply do a “Get Info” (Command+I), and select either “sourcecode.actionscript” or “sourcecode.mxml” for the type in the inspector.
Here you go, enjoy!
Flex for Xcode 3 (0.0.1)
November 12th, 2007 by enefekt
Google’s new Android mobile platform chose Java for it’s application development language. But what’s lacking in developing a Java GUI app? Oh, but of course, something that Mozilla and Adobe have implemented already as part of their platforms, an XML based user interface language!
I made up the name of course, since I couldn’t find a name for it: AXUL.
The format looks a little like SWIXML without the Swing.
This reinforces the whole strategy of using a markup language to layout interfaces and custom widgets, taking advantage of a nice box layout mechanism. But one thing I don’t see is the ability to create new AXUL components by simply composing other AXUL components. (without a hosting Java class)
But why didn’t they choose HTML 5? Ha.
November 2nd, 2007 by enefekt
Just read the NYTimes write-up on Prism.
Interesting comments by Mark Finkle:
if the Web can’t do it, Prism can’t do it
We’re not asking Web apps to change at all.
So thats the big thing really. It’s an incremental nicety to classic web browsing. This is really not in competition to Adobe AIR at all.
It’s more in line with something like Mac OS X’s new Safari Web Clips. Yank an app out of the browser and run it by itself.
As a real-world example, imagine Google Analytics without browser chrome, and then look at the Google Analytics AIR app. Designing an experience more with the user in mind, than browser limitations. And this is using Open Internet protocols and APIs. Maybe that’s not as good as the Open Web though, not sure?