PushButton Engine SDK revision 470

[bengarney]

PushButton Engine r470

PushButton Engine revision 470 is now available on Google Code at http://pushbuttonengine.googlecode.com/.

Everything on the Google Code site is free under the MIT license, and ready for you to use.

The changes over the past nearly 300 revisions are much too numerous to list in detail. Here are the highlights:

• Vastly simplified installation process. No more Engine Manager - just add the contents of src/ to you project!
• Improved documentation - including getting started guides for Flash CS4, Flex/Flash Builder, and FlashDevelop.
• Conformed to the Adobe Flex Code Style Guide - code is more intuitive and easier to work with.
• Easier to run unit testing - see the test/ folder.
• Tons of big fixes, new features, and code clean ups.

If you were using r189, this will feel like a whole new (and vastly improved) engine.

Of course, you can see our full changelog online if you do want to know the details.

How do I get it?

http://pushbuttonengine.googlecode.com has everything you need to get ahold of the engine.

[natebeck]

That previous coding convention was by far the biggest turn off I had with PushButton. I'm glad you guys fixed it. It is sooooo much nicer to program in PBE now!

[thecreatrix]

Yay! Great work, PBE team!

Uh oh. I noticed in the docs that the link from the manual index to Lesson 1 for Flex Builder is broken.

[HanClinto]

w00t!

[mas]

Great work!

[bengarney]

Whoops - you're right, thecreatrix. Sean, our friendly neighborhood web dev, just fixed it. It should work now.

BTW big thanks to the whole community - this release would not have been possible without everyone's help.

[leftblank]

Hey, it's a nice update!

It's awesome that you have agreed with Adobe's guidelines, so Flash guys won't have to get used to your previous coding style conventions (not that they were bad, but they looked weird to us, who studied AS with Colin Moock's books). Many of us are former UI designers or just artists, so AS became the first programming language for people like me, and we, of course, followed the Adobe's guidelines.

May I ask, what does "refactor" folder do? I see there are some Ruby files, but I'm not sure if I have to run these scripts.

If I remember it right, Adobe also advices to use Tab chars as line indents... Do you plan on conforming to this, or is it stupid or unnecessary?

[phil]

Hi, leftblank.

May I ask, what does "refactor" folder do? I see there are some Ruby files, but I'm not sure if I have to run these scripts.

You shouldn't have to worry about those Ruby scripts. They were used to help refactor the engine many revisions ago.

If I remember it right, Adobe also advices to use Tab chars as line indents... Do you plan on conforming to this, or is it stupid or unnecessary?

I personally prefer spaces but that's probably from working at a Python shop for a few years. It doesn't seem like that would be a deal-breaker for folks taking a look at it for the first time.

[natebeck]

If I remember it right, Adobe also advices to use Tab chars as line indents... Do you plan on conforming to this, or is it stupid or unnecessary?

Directly from the Flex Coding Conventions page:

Indentation
Use 4-space indentation. Configure your text editor to insert spaces rather than tabs. This allows another program that uses a different indentation setting, such as Notepad with its 8-character indents, to display the code without disfiguring it.

(source: http://opensource.adobe.com/wiki/displa ... ndentation)

[koopatroopa]

Congrats!