Hello,
I found flash builder 4.5 for php and flash builder 4.6, where is flash builder 4.6 for php ?
Devomatic-
I got the same info from Adobe help on chat.
My 4.5 w/Zend has never worked at all... Nothing, wont even install
correctly and so I was hoping to see it working the 4.6 that rolled out
last week. The Adobe rep said May for the 4.6 w/PHP.
Adobe's misinformation is plowing full steam ahead! ![]()
I was told in the beta it would be January not Q1...this is Very Frustrating.
Not as much as the long-term vision though.
Adobe has 2 classes of software users, some are both, Digital Publishers and Developers.
I think they are digressing to their roots as Digital Publishers and leaving Developers holding the bag.
Danny Winokur really did some damage.
Edge is great, but that's just more money...now will FB 4.6 for PHP include the latest version of Zend Studio since that is what we purchased it for? There's already a Zend PHP plug-in for Eclipse.
I think the FB 4.6 for PHP team needs to get really into the Eclipse WTP and hand select the best Plugins that are for the Adobe kind of developer. Bundle the AWS Plugin or put it in the Readme.txt Notes.
The 4.6 for PHP version I think has the capability to really separate the Digital Publisher from the Developer commitment by Adobe.
There's too little Flash Builder or FLEX jobs out there and too many Java EE with Spring 3 MVC and HTML5...can Adobe eventually make an Edge div type Plugin and a PhoneGap Packager Plugin.
Adobe + Eclipse has the ability to put Adobe's brand name on an IDE that serves so many purposes from Agile SCRUM Plugins to familiar things such as JSP calling Swing or Spring 3 with MVC...try to get Tomcat or JBoss involved.
There's so much potential, but if Adobe doesn't really carry the Developer community, all that FutureWave and Macromedia stood for is for not, and all that Adobe has added is for not because most Jobs now require many different skills, including things like AIR 3.1
The obvious answer is Adobe failed to meet their first quarter deadline this year. Why that is, is anyone's guess if they even plan on still making good on this for that matter.
Workarounds? Of course:
I missed nothing. I clearly expressed that I understood your point in the first two sentences I posted. I then provided workarounds for you to be helpful. You then decided to be obnoxious and rude as if Adobe's failure is somehow my fault when I was only trying to be helpful. End of subject.
One more dissapointed user here! My company also bought FB for PHP 4.5 last year, and we never got an update.
According to this guy the FB for PHP version 4.6 once existed online: http://jaspreetchahal.org/flashbuilder-4-6-for-php-released/
But it doesn't anymore. I tried to use "ordinary" Flash Builder 4.6 (and forget Zend Studio), but guess what: because I had setup my project to have client (Flex) and server-side (PHP) on different machines, it doesn't allow to autogenerate proxy classes fro AMF-ing with PHP if those classes are on another server. So, I uninstalled the 4.6 and installed 4.5 for PHP again. Seems we are doomed to use the old version of FB and never get an update.
Very illogical and non-transparent moves from ADBE. I think the logic was something like: we haven't sold so much copies of FB for PHP, so we will buy some time and constantly move the release date for FBPHP 4.6 - eventually users will be out of their subscriptions, we will never ship it, and nobody will ever ask.
Perhaps their Zend business is also over, but they don't tell it publically?
Seems ADBE is getting rid of all the programming/IDE businesses. IMHO: if there could get a time machine - whey would use it to change the past and never acquire Macromedia.
Adobe ist the only company I konw which reverses its own innovations for years.
Never trust Adobe. This could break your business.
History:
- reduction of external interface made thousends of web-apps useless (file uploades etc.)
- no update for FB for PHP in spite of announcements.
- canceling of design view in FB makes FB nearly useless, unless you like to do skinning etc. on the good old way like in the early Flash 8 - times with AS3.
- AE is now more a 3party product then from Adobe because they missed a bunch of innovations over years.
- documentations for products are going more and more useless.
- Adobe forces its cloudsourcing by hiding inforamtions from non-members. Therefor the Edge-Projects will fail.
...and so on...
There must be something wrong with the complete management...
...time to choose another software vendor!
Is it really that difficult to add Flash Builder 4.6 as a plugin to Zend Studio? I did that for a long time prior to Flash Builder 4.5 for PHP, which is essentially the same thing. It really doesn't take a rocket scientist. =/
On that note, if you own Flash Builder 4.6 and don't feel like shelling out the extra money for Zend Studio or waiting for Flash Builder 4.6 for PHP, then it's really as simple as adding Flash Builder as a plugin to Ecliplse for PHP using PDT. Also, doesn't take a rocket scientist. Personally, I don't see the big deal myself. I don't even bother with using Zend Studio anymore and prefer to use Komodo Edit since it's autocomplete features are awesome and it's very quick at auto complete by simply adding a folder for your favorite PHP apps from different frameworks to different content management systems. Furthermore, there is still support in Flash Builder 4.6 to connect to a PHP data service if you really just want to create some automated code. Ultimately though, I don't understand why anyone would use amf.ini or the default options in production.
Rather than pointing to the default endpoint, if you're using a framework in the first place, it makes a lot more sense to setup a service controller and have the endpoint point to that such as index.php/services/amf (or if you're like me and prefer cleaner url's modify .htaccess to remove index.php). The bottom line is there really was nothing great about Flash Builder 4.5 for PHP. Alot of things were broken for one and it was far easier to use the datawizard which still exists for testing purposes.
After that, you should be focusing on deploying the applicaiton for production, and adjusting the settings in the Zend Framework to create a new project the correct way, dumping your HTML file to a view along with the swf file, and it may be a good idea to point the HTML file to swfobject on the Google Ajax Libraries page. Everything else is a cakewalk.
In other news, if you'd like a ligher footprint than using the entire Zend Framework, why not use something like CodeIgniter and create the necesssary hooks to use Zend AMF?
Cancelling data centric features? What the heck are you talking about? All of the data centric features are still available and it seems to me that a lot of the compaints on here are from people who want to use development settings in production. I'm wondering if half the people on here are actually AS3 and PHP programmers or just want Flash Builder to do everything for them.....
North America
Europe, Middle East and Africa
Asia Pacific