Hi Dean,
I understand what you said. Sure - you must have good reason to hang on Director despite obvious problems with it's development.
When talking about reasons you have presented why Director is lagging behind other Adobe's product I may agree with them though I believe Director extensibility is one of them too. Extensible Director for Adobe means "uncertain, unsafe" - whatever fancy feature they implement the competitor may come offering better plugin. Look - how much they locked Flash Multimedia Server - this is what they want to do, I am sure. Director is simply too much "old style open software" and Adobe doesn't want to be a damn pipe - creating infrasturcture but not participating in lucrative incomes from VOD and similar services. How can you explain locking Director's Flash Xtra so it's can't do HTTP streaming, he?
Dean - it's so sorrow Director is dead but it's a fact. You are a kind of necromancer - really ;-)
I only look forward what will they do with the next release - simply what features they will charge these 400 bucks for upgrade? You know what? It must be something really cheap. Some really outdated, abandoned piece of code they could easily buy on stock for a few pounds and wrap into an Xtra. Then they will come with bells and whistles shouting: "wow - look what a nice new feature we put into Director - 400 bucks please!". And this will be the end. Nothing more will happen. They will earn these few bucks and will mute for next 24 months or so. Funny guys, really.
Bye!
Thank you to both of you for all your time and effort. To put it bluntly I could use Director as is without any problem as it serves all my needs BUT the service and the do not care and non support from the Director team really hurts. We pay for support and we have not received anything from them. For this reason I feel like Adobe Director (as I do not find this with any other product of Adobe) have robbed us and wasted our time. This is why I support Ziggizag. He just says it as it is. To the point.
Dean I think Director should employ you as they can learn a lot from you with regards to support and hearing what the "people" have to say. If you need a reference tell Director they can phone me any day ... heeee
>> Dean I think Director should employ you as they can learn a lot from you with regards
>> to support and hearing what the "people" have to say.
Hehe,
I can only fully support this point. But Macromedia / Adobe did their best to actually incapacitate all influential Director-friendly people worldwide.
I can't call it other way round: it was methodical execution - first they relocated all valuable Director evangelists, and only left this arrogant ****** named Allen Partridge in charge of Director community. Ths guy has completed his task in a brilliant manner - I recall the way he treated Martin Schaefer - it was a brutal kick in the *** - really.
Adobe could maintain positive Director image at no cost at all - simply through minimal affiliation to enthusiastic and strong developers community. People like Dean, like Martin, like many Director Forum wonderful contributors I do not recall names anymore (Alchemist, Christoph Leske and many others) used to keep the momentum and excitment around Director for years with no single act of support from Adobe. In a contrary - finally they only got arrogant repel or at least complete "désintéressement".
So again - we can't see this all as "incidental" - it must have been a planned, long-lasting strategy decided at the corporate level. In the result, today - even if you were in a need to develop something in Director - you are left with no learning resources (but Director Online, what is only because of Dean's irrational persistence), no community help, no customer support, fading extensions list (former "Mile High" list of xtras has shrunk remarkably). etc. And this is all for $1000 worth product! - Isn't it rediculous?
So, we are chatting here but nobody cares - the Indian guys do not visit this place obviously, nothing has changed. All communication halted in a very same manner as updating Director's official website (you can read it was last updated on 07-14-2009, so practically two years ago already). Director is dead. Whatever voodoo Adobe is doing around it, it is puppeting a zombie not real application revival. It's like a yet another "down of living death" sequel movie only made in a purpose to draw some more cash out of the cow's corpse.
Really - if there were on a position to save Director, we would already knew it. They would start from doing something about an application they allocated resources around. They would update the website, made some interesting communication, Adobe Lab samples, whatever. This is normal way they proceed in case they do something about a hot product. But Director is not hot at Adobe's. It's dead cold actually. Amen.
Now that you mention it, I was wondering about the website and why it had not been updated?
Question: Could our company sue Adobe? My point is this. We have been paying our subscription fee. We have been holding on and waiting. The one telephonic call to them was so negative (not to mention the fact that we never got the support). So what are we paying for. Adobe is happy to take our money every 2 years and if it is dead surely we can claim back our money for the product and the amount of time that we have been lingering on like this.
Or is this too far fetched?
Sorry, but I don't think I may be of any help in terms of legal advisory.
I have no idea what is applcable procedure, what is American lawsuit cost, how was the practice in case of similar issues in the past, etc.
I believe you should rather ask a professional lawyer for advice than look for our opinions as they might be completely irrelevant.
On the other hand - it would be very interesting to observe such a case. Definitely, I can fully agree Adobe has violated its own terms of service, but I really can't guess what could be the scope of legal responsibility for such a failure and how much it is actually limited due to the terms of service.
Normally, the standard base of a civil lawsuit is a claim of loss suffered due to the action (or lack of action) of defendant. So, first of all you would have to evaluate direct and indirect loss you suffered due to missing Adobe's support you paid for on the basis of subscription.
Direct losses are for instance extra costs of development you actually had because of increased time neccessary for solving an inssue in case of missing support from development tool (Director) producer (Adobe).
Indirect lossess are for instance contracts you did not gain because you had to include such possible extra costs (as described above) in your projects budgets, what rendered your company less competitive on the market.
Unless Adobe is out of legal responsibility for such lossess due to explicit terms of subscription service, your lawyer should be able to construct a lawsuit. I believe American law is quite sensitive on abuse of monopolistic positions (please notice, in many terms Director is indispensable tool for certain projects, so one may say Adobe's market position in this case is monopolistic-like), so such a lawsuit could be sucessfull IMHO. But it is only my opinion with no actual relevance.
Good luck anyway!
Allen Partridge????
THE Allen Partridge????
http://www.bbc.co.uk/programmes/b00hxqcx
My god - its all become very very clear to me ![]()
After accidentally killing one of his guests...
My godness - that really makes a lot of sense actually!
Wow !!! ![]()
(and from Wikipedia:
Partridge is characterised as an insecure, superficial and narcissistic 'wally', concerned largely with status, the level of his public profile and, to a lesser extent, the ostentatious possessions this allows him to acquire (such as his beloved Rover and Lexus cars and Bang & Olufsen stereo systems). Despite being a broadcaster, Partridge is a socially incompetent and awkward character prone to one-upmanship, embarrassing social faux pas and displays of deep insensitivity to social norms. His thoughtlessness and selfish lack of interest in anything beyond his own objectives exposes an unsympathetic character that is disliked and privately lampooned by many of those with whom he comes into contact. Among Partridge's few friends are Lynn Benfield, his put-upon and long-suffering personal assistant, and Michael, an emotionally tortured ex-soldier from Newcastle upon Tyne. It is notable, however, that he treats even these people with little more than disdain despite expecting complete loyalty from them in return; in the first series of I'm Alan Partridge he does not even seem to be on first-name terms with Michael (who exclusively addressed him as Mr Partridge throughout the two series). Bizarrely, he appears to have a close friendship with Bill Oddie, who even sends Alan Christmas presents. Partridge is otherwise depicted as being unable to forge genuine friendships or connections with other people (who are, seemingly without exception, repelled by his unpleasant and self-absorbed personality).
This is simply a perfect match !
![]()
DHMeritt,
First – remember when you read a post whether it is mine or that of Ziggizag, it is just one perspective and we all have our own biases and judgments.
If you are on a subscription for Director, or any Adobe product not part of the Creative Suite, so not in a clear product cycle timeline, then it is definitely a waste to stay on it. I’d say this for non-Adobe products too.
Ziggizag
>Adobe could maintain positive Director image at no cost at all - simply through minimal affiliation to enthusiastic and strong developers community.
Well, that does happen. I have contact with people in the Adobe team. Martin’s situation was different. Won’t go into that. I do agree that Adobe don’t do enough to engage with the community and leaders within the community.
I‘ll restate that the idea that Adobe is fazing out Director is not accurate. That’s not saying they are fully invested in it. All it means is that if they wanted to halt development, it would be a quick halt to development rather than release versions that dissatisfy the users in order to drive them away.
>updating Director's official website - you can read it was last updated on 07-14-2009
You’ve taken that out of context. The date is in the footer and follows the Terms of Use and Online Policy, so is related to that not Director. The same date appears on the Flash page and it has been updated recently to reflect CS5.5.:
http://www.adobe.com/products/flash.html
Dean
I continue to follow this thread with great interest.
Now, the lack of Adobe support seems to be generating a feeling that a lawsuit may make sense. I share in everyone's frustration, but continue to believe that Adobe needs to divest Director from its portfolio. That would be best for Adobe, and best for the Director developer community.
Perhaps a "leveraged buyout" by one or more members of the developer community would be an avenue that Adobe would explore.
Dean, since you have current contact with Adobe/Director people, could you pose that possibility? If they are really interested, I would be more than happy to fly up from Phoenix to discuss it with them.
Just imagine Director being in the hands of people who 1) understand its usefullness as an application development tool, and 2) know the needs of the developer community in terms of a clear path for the product and proper support and tools.
As I said before, it is not a bad product, it does not need to be abandoned - it needs a new home!
John
I don't believe Adobe will ever sell Director to a third-party company. Neither I believe they will open-source it.
Director is direct competitor for Flash and having proper maintnance, within a year of code refactoring, implementation of modern text and 3D engines could easily threaten Flash/Flex dominant market position.
Adobe is not stupid. They would rather sink Director source code into deep see than let it float at large on someone's boat.
Thank you Dean, I understand that this is input from everybody out there but I feel "robbed" like many others out there and think that Director should take accountability on their non support, non everything.
So I spoke to our legal team and it went very much on the lines of ZiggiZag. We would have to look at the licensing agreement. Is the licensing agreement for the individual Director product or is it for all the Adobe products as a whole? If it is for Director alone the case could be stronger. We would have to prove tangible loss and how much it amounts to. We would sue Adobe South Africa as we purchased the product through them.
The big question is, is it viable to do it? The short answer no! Why you may ask? Well even if there is a great loss and even we have a 100% full proof case and win, according to the South African law, a time period would have to be given to Adobe to "fix" the issue at hand.
So this is not the right root.
Dimitri
I'm not saying whether I think that Adobe should or should not be sued, but in the US (well, at least here in Georgia) there is always small claims court. While I believe the cap is around $15000 if you sue a company they have to send a represetative. They have to prove their case and from what I understand, it is very difficult for them to do.
Of course, winning is just half the problem (maybe less - lol) . The rest is actually collecting...
Cheers
Carl
And that is only the tip of the iceberg, Carl. To my view, the real issue here is that we, as a developer community, do not simply wish to punish Adobe. Rather, we want Director to flourish and grow because it is a major tool of our trade. A one-time collection, even if it is won in court, does nothing to solve the problem unless it moves Adobe to action in that direction. That is not a given result of taking them to small claims court unless enough people do it. And If you have ever had experience with trying to move a large group of people to action in a unified effort, you know that can take years to accomplish, if accomplished at all. I’m not saying that should not be done. That is not my personal decision to make on someone else’s behalf. I’m simply saying that perhaps we as a community can better spend our time searching for solutions that might encourage the longevity of Director without relying on “individual efforts” multiplied many times over by a group. A class action lawsuit might be such an effort. But, from a legal standpoint, do we even have a case here?
Here is my take on this issue as it now stands. I cannot believe that Adobe is going to that much trouble to be “sneaky” and “underhanded” about removing Director from their product line. I also own a company. I if we wish to take away from our product line, we will, as a courtesy, publish our intentions on our Web site. But we will not devise some diabolical plan to try to deceive and drive away the customers affected by that decision. What company has the time, or the “extra” money, to waste on such a plan? What’s the point? We will simply drop the product – end of story. As far as I know, such an action is neither illegal, nor unethical.
Adobe’s stance on Director indicates to me an uncertainty on just what to do with that product. It seems clear at this point that they are either on a steep learning curve, or simply have no idea how to deal with Director, given the poor job their people have done on the first new version they released. I have the latest one, also, but have not had the time to really get into it, yet. So, I will reserve comment on that one. Their programmers are obviously struggling with that product, and likely trying to convince Adobe to get rid of it so they won’t have to deal with it. Given its popularity, and the fact that nothing else currently competes with it, it is my opinion that Adobe should have picked up some personnel from Macromedia and kept it alive and well without handing it to those who may not be able to deal with it properly. If you have ever tried to get into someone else’s computer code, you will know what I mean. I apologize to Adobe personnel if this is not the case.
Having said that, I will admit that I do not know if any of what I have said is what is actually happening. However, I do believe that the “let’s deceive them and scare them away so we can drop Director” is not happening. That doesn’t make sense to me from a business perspective. If Adobe would come to the table and openly discuss the Director issue with the community, all misconceptions, if they exist, might go away and cooler heads could prevail. I think what we are seeing here is what we normally see when a group is left to come up with its own answers to provocative, possibly threatening questions without the data to do so. I believe it is always far better for the source of the correct answers to freely provide them.
My vote? Prevail upon Adobe to come forward with open dialog with the Director community on their future plans for Director. I believe an open forum is better than dialog between representatives of both camps so that all voices can be heard, and all ideas considered, and all skills and talents brought to the table for the benefit of both camps. If both Adobe and the Director community will be open-minded enough to refrain from anger, sarcasm, name-calling, threats, accusations, and personal agendas that might not serve the community, perhaps a workable plan for the future of Director might evolve.
If Adobe is struggling with Director development, and if they are astute, and open-minded enough, they have at their disposal a very large community of Director talent who can, and probably would, help them develop and improve Director into a powerful and profitable product for them. They are not alone. It need not be “them against us”. Shorter the road when sharing the load. We all have a stake in this, so let’s reach out in whatever ways we can to Adobe and stop throwing stones at them.
In the meantime, legal advice is required on whether or not small claims court or a class action lawsuit are even feasible. Will losing Director affect me personally? Yes. Over some period of time, it will put me out of business. Is Adobe liable for that? Probably not, but that question begs an answer. Otherwise, any ensuing discussion on such courses of action might be a waste of time.
Can anyone reading this offer a qualified legal perspective on these issues?
Dewey
From: CAnuszczyk forums@adobe.com
Sent: Friday, June 03, 2011 5:49 AM
To: Dewey Parker
Subject: Re: Director's Future Meeting - Summary and Evaluation Re: Director's Future Meeting - Summary and Evaluation
I'm not saying whether I think that Adobe should or should not be sued, but in the US (well, at least here in Georgia) there is always small claims court. While I believe the cap is around $15000 if you sue a company they have to send a represetative. They have to prove their case and from what I understand, it is very difficult for them to do.
Of course, winning is just half the problem (maybe less - lol) . The rest is actually collecting...
Cheers
Carl
Hi MECS
I agree with most of what you have said.
Yes, makes no sense to create a drawn out end to a product and annoy customers in the process.
>Adobe’s stance on Director indicates to me an uncertainty on just what to do with that product.
I sort of agree with the above. I think they have an idea of what they want to do with it. That's to capture the games developer market. However, the team is not resourced enough to make it highly competitive in the short term.
Macromedia was to blame for getting rid of all the Director engineers so when Adobe took over, they set up a new team who were all beginners in Director and new to the code. So, they were bound to take longer and make a few mistakes in the first version. I'd say the problems were more severe because of pronlems with engagement with the community and forming a strong partnership with them. D11.5 is a better version than 11.
>My vote? Prevail upon Adobe to come forward with open dialog with the Director community on their future plans for Director...
That's what I've been trying to get Adobe to do and one of the aims of the online meeting between the product management and users. The problem I see is that people in the more senior Adobe positions teat Director as a low priority so is hard to get them into to the road you're envisioning. What is needed is a Director champion within Adobe and someone with vision and creativity so that even with limited resources, a plan can be rolled out to rejuvinate the product.
Dean
Good points, Dean. We, of course, have to take care not to do exactly what the community is accusing Adobe of; that is, trying to deceive them into believing Director is something it is not. If it has the potential of being a substantially profitable item in their product line, then we have a leg to stand on in supporting its continuance. If it truly does not have that potential, then we aren’t doing anyone, ourselves included, a favor by attempting to convince Adobe that it does.
I, for one, do not have the data to substantiate such a claim. I hope it is true. I want it to be true. I even NEED for it to be true. But I don’t know the approximate size of the Director community, nor do I have any data on price points vs annual sales/profits on that product. Perhaps others in the community do have such figures. They do not need to share them per se, because they are the property of Adobe Systems. But perhaps, if they do know, they might at least state that the product is, or is not, potentially a significantly profitable item for Adobe. I am not interested in personal opinions on that issue; and probably no one else should be, either. But I think we would all have some interest in data-driven opinions.
As for capturing the gaming market, I see it as a worthwhile goal for Adobe to add that market to the Director customer community. I just hope they will not make Director so game-development oriented in content and substance that it will become lame for the rest of us who use it for other purposes.
From a business point of view, it would seem a poor choice to abandon an existing market in an effort to capture a different one that may or may not eventually embrace their product. It would seem a better bottom line choice to retain the existing market and attempt to ADD the other market as well. In fact, barring insurmountable problems in doing that, it would be a no-brainer. However, I realize that those “insurmountable problems” may really exist.
But again I say, Adobe has a huge knowledge and skill pool from which to draw to help solve Director problems, and more than likely most marketing problems as well. From where I stand, it seems doable to me. I wonder if it still would seem so if I had the data…. ?
Dewey
From: Dean Utian forums@adobe.com
Sent: Friday, June 03, 2011 9:54 AM
To: Dewey Parker
Subject: Re: Director's Future Meeting - Summary and Evaluation Re: Director's Future Meeting - Summary and Evaluation
Hi MECS
I agree with most of what you have said.
Yes, makes no sense to create a drawn out end to a product and annoy customers in the process.
>Adobe’s stance on Director indicates to me an uncertainty on just what to do with that product.
I sort of agree with the above. I think they have an idea of what they want to do with it. That's to capture the games developer market. However, the team is not resourced enough to make it highly competitive in the short term.
Macromedia was to blame for getting rid of all the Director engineers so when Adobe took over, they set up a new team who were all beginners in Director and new to the code. So, they were bound to take longer and make a few mistakes in the first version. I'd say the problems were more severe because of pronlems with engagement with the community and forming a strong partnership with them. D11.5 is a better version than 11.
>My vote? Prevail upon Adobe to come forward with open dialog with the Director community on their future plans for Director...
That's what I've been trying to get Adobe to do and one of the aims of the online meeting between the product management and users. The problem I see is that people in the more senior Adobe positions teat Director as a low priority so is hard to get them into to the road you're envisioning. What is needed is a Director champion within Adobe and someone with vision and creativity so that even with limited resources, a plan can be rolled out to rejuvinate the product.
Dean
@mbtmobile
I always keep respect to British legal tradition, so successful in providing access to courts for regular people with their small issues and problems...
@All
Adobe's "uncertainity on Director" keeps lasting far too long to be considered just incidental. I am pretty sure, when they have their monthly business meetings there is kind of ritual last accent: "and now Director please... hehe". Definitely "the people in the more senior Adobe positions" are aware of Director case and it is a conscious decision to attatch lowest business priority to it. I am not aware of particular reasoning behind that decision but it's like this - point.
This itself would not be the worst actually but the real problem is this complete communication cut between Adobe and Director community. The consequence is that even if they try to make some rational decisions - they only make wrong decisions (like complete stupid idea of making Director primary a "game development tool" - I strongly believe Director is predominantly a B2B applications development tool flexible enough to fit into various type of projects and delivery media) and year by year the application gets older, less relevant and abandoned. I do not know what to do about this stalemate but I know one day the final decison must arrive. And more time Director remains "stalemated" - more certainity it will be eventually phased-out.
Consequently, I do not see a practical way to introduce a "Director Champion" - a person of influential leadership capable of product rejuvination - at Adobe's. Simply speaking - there is no "transmission" and whatever voice eventually pass through - it can be easily suppressed with "Flash can do it too" way of argumentation - at least on their internal meetings.
So - I stay on the side of pessimism, but feel free to go on - please, try to convince Adobe's management Director is a little "Cinderella" and if they only clean the old dust it would shine like a princess in glory ;-) Sorry guys, I double bet you'll fail.
Well, when Macromedia ceased to exist and Director became an Adobe product I didnt have a good feeling about it at all, call it intuition, comercial knowledge or whatever (that was some years back). Time has only confirmed all of this. Adobe has put director "in jail" or on cold (which equates to death sentence in an ever evolving market). How can these people think Flash (or any other tool for that matter) can be better than Director...
Thanks everybody for your insights and efforts.
ps: since I had to reset my password for very low participation in recent years all my previous participation on macromedia forums is vanished. My membership dates back to at least 2003 not 2011 as is stated on the left.
>Well, when Macromedia ceased to exist and Director became an Adobe product I didnt have a good feeling about it at all...
Director has continued development since Adobe has taken over Macromedia and they have done a lot more than Macromedia did in its final years. Now, Adobe has made some mistakes with Director and I would have like faster and more extensive development of the product. However, the state of affairs for Director at the end of Macromedia was a product that was neglected, undefined in terms of its market and basically the black sheep of the suite of products. Director's profile has remained low at Adobe and therefore its development has been limited.
Dean
As a Director game developer, I feel one of us should at least speak up on this. There are TONS of us using Director to make games, our company has produced over 60 games in the last 3 years, A and AA titles, all produced in Director. We currently own 10-12 Director licenses, and we reference all sorts of Director forums that we may or may not be bothered to create an account and post on. There are plenty of other companies in the casual gaming space that have and continue to use Director to make their games. Companies who are much bigger and smaller than ours. As much as we all may have various levels of hatred for Adobe, I would think they are at least capable of data mining who is using their application and what for. You guys seem to have less faith in that than me, and I could certainly be wrong about this.
That said, NO ONE in the game development world cares at all about the 3D capabilities of Director. If we want to make 3D games, we'll use Unity or one of the cheaper cross-platform 3D development suites. Director has and always will be a strictly 2D game dev environment. The fact that Adobe doesn't seem to understand this is what leads to my doubts about their understanding of who the clientele is in my first paragraph. Unless Adobe does a major overhaul, Director can't compete with Unity3D in the world of games.
Finally, to really go out on a limb, perhaps the 3D capabilities aren't even intended for game developers? Maybe there are some bigwig medical clients who need 3D support for their large scale medical imaging software coded in Director? Now i'm just being silly, that's it for me!
...I'm just a random guy around.
I always think those at Adobe don't really have a complete understanding on what they have acquired. That's why programs are often marketed at a wrong direction (see Fireworks and even Flash), killed while having quite some recent userbase (see GoLive and FreeHand), or get mauled when a new version is almost finished (see Authorware). (Off-topic: Authorware uses Xtras like Director does, and I'd say maintaining the Xtra technology for two programs seems more cost-effective than one.)
And, with Adobe's perceived difference that Director does 3D and is more low-level, Flash Player 11 and AIR 3 could give them a reason to axe Director at anytime. And then, there's this weird Adobe logic:
No updates to FreeHand have been made for over four* years, and Adobe has no plans to initiate development to add new features or to support Intel-based Macs and Windows Vista.
* 9 years by now
Ovation has been available for more than five years without a version update. Adobe has decided to discontinue the production of Ovation in order to streamline the product line.
It sounds like that if a program is not updated for a long period of time, that would constitute as a valid reason to discontinue that product. And then...
The eLearning market has transitioned to Adobe Flash® and Adobe Captivate® software over the years. Authorware is a mature product and demand has continually declined to where it is no longer economically viable for Adobe to continue development.
Yep. Macromedia products that coexisted before the acquisition can get killed as well.
Given how work for a next version Director is currently undergoing if I read this thread right, and that Shockwave Player 11.6 was just out not long ago, it probably won't simply die off right now. But I'm not so sure about if there will be a Director 12.5 or 13.
Hi all,
Still keeping an eye on this thread. So, what's this petition being discussed?:)
I think the Adobe Director team realise there is a strong community behind the product. The challenge has been to grow the community as that's the only way more senior Adobe management would take more notice.
Dean
After more than decade with director i do not believe that this will change anything. Our company is already looking for other solutions. And i personally started to learn serious programming. But still, too many of our products are built in director, so it will take some time to change them to other core. So i will not abandon director immediately. I had alwayz reasons why to stay with director. But we are going to face new problem in near future. Using plugins in new explorer 10 will be complicated (restricted for common user) (even flash) and we do not know how director issue will be solved. Also there is another old problem that shockwave is an extra plugin that has to be installed and for common user it can be considered as "threat" to hurt the computer. Now html5 looks like can doo everything that director. (Only problem is that you need better programming skills than in director). And lately when i search internet for some troubleshoting in director, i often find shockwave = flash. :-(
I too am following in your footsteps. The learning curb is massive and slow. Then we too have a few products in Director. Luck for us we started 2 years ago to slowly move them over to another program. We still have one or two major programs to convert and then we are free of Director…Yeeehaaaaa.
Dean
At the risk of sounding political, the only thing keeping the Director
community from growing is uncertainty! I would love to tell people
how great Director is (I've been making a good living from it for 15+
years!) I won't talk about it because there is so much uncertainty
concerning how long it will be around.
The reason people are jumping on the idea of a petition is to make sure
Adobe knows that there IS a community. It does not feel like they
realize that. You say they do, but when I called Adobe to ask a
pre-sales question about Director 11 it took several attempts
before I got anyone who even knew what is was, much less an
answer to my question. Finding it on the web site, or forum lists
is nearly impossible.
The feeling of abandonment makes XTRA developers lose interest,
and that further weakens the product. Adobe could say "Director
is going to be around" through actions, like including it in a couple
of panels on their web page... wouldn't cost a dime, but would mean
everything! They could also reveal a little bit of forward planning -
"a version that works with OS/X Lion will be out
Bestwave - I agree with what you have said. I have pleaded with Adobe to be more transparent with Director. This thread was part of that attempt - having a meeting with the Adobe team so they could speak to the community and be more open.
We got into the situation of Director because Macromedia made it a low priority and Adobe could not rejuventate the product quickly.
There are other reasons why Director is not growing:
- Product is becoming dated. Does not accomondate curernt technology - e.g. export to mobile devices.
- Very little marketing by Adobe.
- Looks like the black sheep of the Adobe collection - hense uncertainty.
When you call Adobe, Director won't be known because it is a small tool in a huge company.
I have spoken to people in the Adobe Director management and they know there is a community. I'm not sure if a petition will do anything.
Dean
Wow. I found this thread by accident while googling something completely unrelated to Director. It's so sad. Director was such a great tool; and the community we built was such a great thing to be a part of. I miss it more than anything in my professional life.
This thread brought it back and reminded me at once how glad I am that I finally let go in time to salvage my career, and how sorry I was to be put in that position.
http://www.youtube.com/watch?v=-9JOmU2jFUo&feature=fvwrel
Love,
Dorothy
Not dead for sure.
Nice (and sad) words, Dorothy. I think the community is psychologically dead- rather than the software itself. Director continues giving to many of us, and our customers the best results in interactive platforms, 3D prototypes and large-scale virtual simulators. Sorry Adobe, but im not interested to put all my products inside the small screen of a mobile phone (bye bye immersion). For those who continue using this wonderful tool, hard to kill, just be always alert to new developments, platforms and interactive software market. Dont sleep in past, and dont spend more tears with Adobe. BUT, While you do that search for new tools, continue enjoying this app and deliver your best for your customers.
Tks for support my bad english.
Pablo.
LatinAmerica Community
I recall visiting this forum a few years and reading the exact same sentiments. Nothing is going to change here, people.
Despite the rumors of D12 serving as Director's resurrection, I suspect that Adobe is going to go right on keeping Director on life support. (and little more)
Which isn't entirely a bad thing, when you understand it from the proper perspective.
I have several legacy Director (kiosk) projects that I update every year. I enjoy the work and it's a little coin without any fuss. I'm grateful that Adobe is keeping Director alive as a legacy product, so that the app will continue to work on successive operating systems.
I'll be shocked if D12 comes out and proceeds to trounce other alternatives as an iOS app platform. But if it permits a guy like me who already knows the app...to export projects out to that platform...I'd sure belly up to the bar and pay $300.
Director is now an old horse. She still can get me to town...and sometimes with better efficiency than Flash or any other app. But I just don't see a future here.
HTML 5 or something like Unity is where the game will go next.
North America
Europe, Middle East and Africa
Asia Pacific