Newgroups for Director: Macromedia or Adobe?

Now that Adobe has officially announced the next version of
Director ("Adobe
Director") are we to continue using these Macromedia
newgroups or will they
change to an Adobe New Server. Are there already Adobe
Director Newgroups
that I am unaware of (and how do I access them?).

On Thu, 27 Jul 2006 02:44:00 GMT, TJD posted in
macromedia.director.basics:
> Now that Adobe has officially announced the next version
of Director
> ("Adobe Director") are we to continue using these
Macromedia newgroups
> or will they change to an Adobe New Server. Are there
already Adobe
> Director Newgroups that I am unaware of (and how do I
access them?).
I can't speak for Adobe, but I'm still using the
forums.macromedia.com news
server.
If you prefer (yech!) Web Forums over newsreaders, you can
log into the Adobe
web forum pages which access these newsgroups at
http://www.adobe.com/support/forums/
They have NNTP servers for their other products on this
server:
adobeforums.com
I think you can only read those newsgroups with a newsreader
- I haven't been
able to post to them. Otherwise, log into their web forums.
FWIW, all of the HTTP macromedia.com links are automatically
pointing to
adobe.com servers. I have no idea if something similar is
happening with
NNTP.
Mark A. Boyd
Keep-On-Learnin' :)

Similar Messages

Director 12 - Does Adobe have a strategic plan for this product ???

Adobe staff, and Director experts reading this, please answer these questions, for the benefit of all developers who purchased Director 11.x licenses, and for those who are thinking of purchasing Director 12 licenses.
Why is the Director 11.x and Director 12 documentation, as published by Adobe, so incredibly bad?
Why are the Adobe Director resources on the web and in book form, mostly in reference to Macromedia Director MX and Director 8.5?
After Director 8.5 people stopped writing about Director, even though Adobe continues to release new versions. Case in point, Director 12 was just released in February 2013.
For example, Amazon.com lists a handful of books under "adobe director", all of them published in 2003 or before, all referring to Director MX or D8.5, and most of them out of print. Those versions of Director are ancient history in the software world.
Are Silverlight3D and Unity3D taking over the "3D in a browser" niche?
HTML5 WebGL is not ready for prime time, and may not be fully supported in all the major browsers for many years (especially not in Internet Explorer).
So which is the dominant de facto "3D in a browser" solution right now, and for the next few years?
Why doesn't the Adobe Director development staff or the Adobe marketing staff talk in public about Director, like for example on this forum?
Adobe is obviously spending capital dollars to write and release new versions, but we don't see Adobe employees on this forum (which is published by Adobe), evangelizing and promoting Director.
It's as if the Adobe marketing people don't talk to the Adobe Director development staff.
This may be because Adobe has no strategic plan for Director.
If that's wrong, then what is Adobe's strategic plan for Director 12?
What is Adobe's strategic plan for future versions of Director?
Without a strategic plan for future versions, Director is already dead in its tracks.
So is Adobe Director a dead platform?
Should all of us "3D in a browser" developers put our Director 11.x CD's for sale on ebay, and move on to another platform before it's too late for us?

I agree with you. I have been complaining on this forums and asking Adobe to provide us with good documentation about Director 12 since its release a few months ago. I haven't seen any replies from Adobe or updates to the web site.
The iOS support is really poor. No support for video? Adobe is really dropping the ball here. I am very disappointed as many other customers about Adobe's unprofessional behavior releasing a product that is incomplete. I think they want to kill this product and this is the best way they found how to do it. I don't find any other reasonable explanation.

Adobe Shockwave for Director Installer Availability

Why must we visit this forum and browse through posts and answers in order to obtain the hyperlink to download the Shockwave "Full Installer"??
It would be so much easier if Adobe would get its act together and make downloads for Shockwave Player and for Shockwave for Director easily accessible from the home page instead of trying to enable Google to install Chrome on everyone's computer system and make it the default browser. During the update of the previous version, Google installed Chrome on my computer system and made it the default browser without ever asking permission to do that. When I uninstalled it, that did not restore my system to the way it was, and I had to spend time and effort to track-down the problems remaining in the Windows Directory. But that was then and this is now.
When I attempted to update Adobe Shockwave via the Mozilla Firefox "Plug-in Update Check" page, the installation failed because the dialog in which the user is asked permission to install Google Chrome and make it the default browser was displayed on the desktop, behind the windows that were opened for Firefox. Of course, there was no way to know why the whole process stalled, since Adobe's software installation personnel still do not have a clue to this day as to how to design and implement a procedure to effectively install and update their software on a Windows computer system.
After I abandoned the update and exited Firefox, I discovered the dialog, which was irrelevant at that point. I responded "no" and it vanished. So I attempted to update Shockwave again. However, its plug-in was already uninstalled from Firefox 26. Why would that be a problem, you ask?
It's a problem because the Shockwave plugin is required to download and install the update for the Shockwave plugin! The San Francisco Bay Area is replete with competent software people. Apparently either Adobe just doesn't hire them, or they don't want to work for Adobe.
There is an option to install the requisite plug-in (which is not named in the notice that a plug-in is required). Using it displays a Firefox dialog to install Adobe Shockwave Player. The installation was reported as successful, but the update still did not proceed. Then again, if the installation was done correctly, installing the "required plug-in" would in and of itself update Adobe Shockwave Player, would it not?
When I checked the Firefox plug-ins, Shockwave was still not present, even after exiting and re-starting Firefox. Why that was so I could not discern.
So the only solution, if it is a solution, is to run the "full" Adobe Shockwave for Director installer. Looking for access to it requires far too much time and effort. Why should anyone bother??

''3DogNight wrote:''
Should I try uninstalling Shockwave for Director first?
Not necessarily, but that could eliminate some potential problems, so I do recommend it.
# Go to http://www.adobe.com/shockwave/download/alternates/#sp
# Save the Shockwave Player Uninstaller somewhere handy, like the desktop.
# Save the Full Installer for Netscape¹. If you plan on using Shockwave for Director in Internet Explorer as well, also save the Full Installer for Internet Explorer/AOL¹.
# Exit all browsers.
# Run the uninstaller.
# Once the uninstallation has completed, run the full installer for Netscape.
# Once the installation for Netscape has completed, run the full installer for Internet Explorer.
¹ Although the links on the page currently say "Shockwave Player 11", they point to the latest version, which at the moment is 12.0.7.148.

Overhauling the Documentation for Director

Hi Everyone,
Please excuse this cross-post. You can also find it on the Direct-L mailing list and on the Director Online Forum. I will post a summary of answers to each of these places.
Rajnish Bharti, Product Manager for Director and Shockwave, asked me last week for my input on how best to overhaul the documentation for Director. In particular, he asked me to give him an idea of what the Table of Contents should look like.
You can find my first draft of the Table of Contents here:
http://www.openspark.com/adobe/Director_Documentation_01.zip
While preparing this, I contacted a number of Director teachers and trainers, talked to some newcomers to Director, consulted dozens of Director books (mostly from the Macromedia days) and pored over the various reincarnations of Director's own help.
Examples
Lots of real-life examples that you can copy and paste and
know that they will work
Images
Clear and concise screen shots that capture the essence of
a concept at a glance
Fast and Powerful Searching
Beginners don't know which menu item or scripting term they
are looking for. The search engine should help users to home
in from a layman's expression to the appropriate documentation
article. Articles should be intelligently cross-referenced.
I have suggested dividing the documentation into three sections:
1. Director Step by Step
A series of short hands-on tutorials which introduce all the
commonly-used features of Director in the context of simple
movies. Beginners can start here.
This section imagines that you have never used Director or
studied its documentation before. You select a project that
is similar to the one you are planning, and the documentation
shows you how to achieve your goal using Director.
Hyperlinks lead you to more in-depth entries in the Feature
Guide on how a feature works, or to the appropriate entry in
the Scripting Dictionary.
2. Feature Guide
This section will give detailed explanations of each feature,
category by category. It will be divided into three main
chapters:
The Workspace
Working with the various windows and menus
The Raw Materials
Understanding sprites, members, the various media types
and data types
The Process
Designing your project, animating sprites, using scripts
and publishing your work.
This section will give you a categorized view of what Director
does. It imagines that you start with a "How do I..." type of
question, and guides you to the appropriate part of the
User Interface or the correct scripting terms to use.
It will contain links both to the Step by Step tutorials and
to the entries in the Lingo Dictionary.
3. Alphabetical Scripting Dictionary
I have abandoned the idea of having the Dictionary divided
into categories. I believe it is much easier to find an
entry without having to wonder whether it is a keyword, a
method or an operator. If you don't know what entry you
should be looking for, the Feature Guide will help you. If
you do know the word you are looking for, then you only
need to know the alphabet.
Each entry in the Scripting Dictionary should link back to
the articles in the Feature Guide which refer to it, and to
each of the tutorials in the Step by Step section which use
the term.
I also suggest (Section 4) implementing a much more powerful Search engine than the D11.5 browser-based help currently features, but that is not really a part of the Table of Contents.
The document that I have posted at...
http://www.openspark.com/adobe/Director_Documentation_01.zip
... is by no means definitive, but it is at a point where I am ready to share it, to check if my general approach is acceptable.
I have not gone into much greater detail in some areas than in others, so past the 4th level, you may find certain areas are still vague. You may have better ideas for the Step by Step tutorial movies than the ones I have included.
Red text indicates new content.
I welcome feedback from all members on the community, both in terms of the content and the structure.
Once we have a comprehensive list of all the topics to cover and a consensus on the structure, then we will have to work out the most cost-effective way of generating the actual content.
Let me know what you think,
James

James, this looks outstanding!
I'm too far behind in versions to offer much here, but one thing I noticed that, I think is an oops:
3.4. Java Dictionary
should be:
3.4. JavaScript Dictionary
Unless they brought back the Java beast, that is.
Mark A. Boyd
Keep-On-Learnin' :-)

Director 11 in Adobe News?

Why was Director 11 not mentioned in the News section of
Adobe's home
page?

If ever there was a time, this might be the time for Adobe to
break their
own policy and give advance detailed information on the
development plans of
future versions of Director (the already announced 12 &
13).
"Dean Utian" <[email protected]> wrote in message
news:[email protected]...
> newbie wrote:
>
>> Why was Director 11 not mentioned in the News
section of Adobe's home
>> page?
>
> Hi,
>
> Many people have asked why Adobe hasn't acknowledged
their release of
> Director in their own news area of their home page. And
many have
> speculated to why this is and suggested the commitment
from Adobe must be
> lacking if they can't even treat the Director 11 release
as a news worthy
> announcement.
>
> Here's a more accurate answer.
> Director 11 is still at a lower status level than other
Adobe products.
> That's just fact. That does not mean it will always be
that way, but it
> is just the way things are now. We know Macromedia
neglected the product.
> We know it has been years since the code base was given
attention. We
> know Director has fallen way behind Flash in the
development cycles.
> Director 11 is a step forward in that Adobe has invested
time and
> resources into an upgrade that can continue into the
future. But, D11 is
> a starting point for Adobe. Hopefully Director 12 will
be more of the CS
> type upgrade with some major wow factor that can be
celebrated by all.
>
> To the Adobe news section on the home page. If we look
at what's there
> today, we have statements about Adobe Flash Media
Encoder, Adobe TV,
> Adobe Media Player, Creative Suite 3 prize, Webby-In
Motion contest, Font
> Folio. In other words, there is a lot of news. And there
is definitely
> other things that are happening at Adobe that are not
mentioned in there.
> The Adobe News section on the home page is really just a
marketing space
> to promote new technologies or the top products in the
Adobe collection.
> It is a highly limited area of real-estate and product
teams are likely
> to compete for a mention there.
>
> Adobe have been promoting Director. A little while ago,
I was contacted
> by an agency that Adobe commissioned to promote Director
in Learning.
> Just in the last week, I received email from an author
for a computer
> magazine who's writing up something about Director 11.
So, the Adobe
> Director team is releasing information to the press and
promoting the
> release. The news section on the front page is not the
main news agency
> for Adobe. Is is really just small area for the latest
top Adobe
> promotions.
>
> I'd like to see Director mentioned on the home page, and
have the product
> icon show in with the CS3 ones. I believe Director can
build up its
> status but it can't happen overnight. Director 12 may
lead us into that
> realm.
>
> regards
> Dean
>
> Director Lecturer / Consultant / Director Enthusiast
>
http://www.deansdirectortutorials.com/
>
http://www.multimediacreative.com.au
> email: [email protected]
>

The Shockwave for Director plugin is no longer working in Firefox 7 for mac

Dear Firefox,
I run a website which uses Adobe's Shockwave for Director plugin to view an animation. This plugin worked perfectly in Firefox for mac, up until Firefox 7. Firefox now sees it only as an unknown added plugin and the animation can no longer open. I have the latest plugin version installed from Adobe, which works fine in Firefox 7 for windows, in Safari (mac, win) and Internet Explorer (win). The Flash plugin is also working fine.
In the preference panel, I have allowed Adobe to install plugins. Do I need to change other settings? Is something stopping Firefox for mac from properly loading the plugin?
Many thanks for your help.

Have you tried this one?
https://addons.mozilla.org/en-US/firefox/addon/roomy-bookmarks-toolbar/

Firefox 4b8 not working with Shockwave for Director 11.5.9.615

Have installed Firefox 4b8 and Shockwave for Director 11.5.9.615. 
Also have Firefox 3.6.13 with '''separate profile'''. 
Director plugin works fine in Firefox 3.6.13 but not in Firefox 4b8. 
Loading a Shockwave for Director page is initially blocked in both Firefox versions by NoScript;
*clicking on the space for the game/whatever loads in Firefox 3.6.13
*clicking on the space for the game/whatever in Firefox 4b8, the entire space for the game/whatever disappears and never re-appears
What I have already tried:
#Uninstalled Shockwave for Director and re-installed - no change
#Firefox 4b8 in Safe Mode - no change
#Tested Firefox 4b8 on Mozilla plugins site - shows correct current version
#Tested Firefox 4b8 on Adobe site with games - won't work (Firefox 3.6.13 works on same site)
#Copied '''''np32dsw.dll''''' to Firefox 4b8 installation folder/plugins, ran same tests -no change
Any suggestions?

Found a solution based somewhat on cor-el's reply with some interesting differences in Firefox 3.6.13 and 4b8. '''cor-el''', please see my question at the end.
I added the item (boolean) ''dom.ipc.plugins.enabled.np32dsw.dll'' in about:config and set it to false. There was no change. I changed the value of that item to true and the box/area where the SWF item was to be located on the page did not disappear as before -- that was an improvement! -- but the SWF item would not load.
I then discovered that I needed to allow a site (temporarily) in NoScript and everything worked.
Some interesting differences and findings in Firefox 3.6.13 and 4b8 regarding this situation; all based on the same web site behavior with the 2 versions of Firefox:
#preference ''dom.ipc.plugins.enabled.np32dsw.dll''
#*Firefox 3.6.13 '''does not''' require the preference to exist in order to work
#*Firefox 4b8 '''requires''' the preference, set to true, for everything to work as expected '''
#**the preference ''dom.ipc.plugins.enabled'' can be set to '''false''' or to true with no negative difference in behavior (the preference ''dom.ipc.plugins.enabled'' when set to false seems to be ignored when ''dom.ipc.plugins.enabled.np32dsw.dll'' is set to true)
#NoScript (same version and exactly the same settings in NoScript for both versions of Firefox)
#*Firefox 3.6.13 '''does not''' require user to temporarily allow any other domain for the item to work properly
#*Firefox 4b8 '''requires''' the user to temporarily allow another domain for the item to work properly
'''cor-el:'''
*Should I post this in Bugzilla for investigation?
*It would be good to know what the difference is in 4b8 that necessitates the 2 above items in 4b8 and not in 3.6.13 on the same web site.

Prerelease Program for next version of Adobe RoboHelp

I am happy to announce that we have started the prerelease
program for next release of Adobe RoboHelp. You might have already
read about some rave reviews of the Sneak Peeks of Adobe RoboHelp
that we did at STC, Minneapolis. It's now your turn to get your
hands dirty with a prerelease build.
Apply now by filling up the Prerelease Participation Form by
visiting the following link:
https://prerelease.adobe.com/callout/default.html?callid=1DE2E04FA23D46C886DD55A88F611D11
Enrolling into the program does not guarantee access to the
prerelease program. You shall get access only once your application
has been approved.
Please note: You would be required to submit a short
questionnaire, while you apply for the Prerelease Program for Adobe
RoboHelp.
During the application process, please use the "Existing
Users" section if you have an existing Adobe Prerelease Program
user account. If you are participating in prerelease programs for
the first time and do not possess a prior account, then use the
"New Users" section for creating a new account. You will have to
provide your email address and password for creating a new Adobe
Prerelease Program user account. A mail containing a link to the
Prerelease program will be sent to the specified email address for
verification. Use the link specified in the mail to continue with
the registration process to join the Prerelease program.
We look forward to your participation.
Regards,
Akshay Madan
Product Manager - Adobe RoboHelp
http://blogs.adobe.com/techcomm/robohelp/

Hi DaLy
Sure, I'll be happy to try. However, all I really know about
it is what has been relayed to me over the years. I have no idea as
to how accurate it is or isn't.
I've been told that because Adobe (and formerly Macromedia)
are publicly traded companies, they have to be extra careful in
divulging any information that could impact the sales of their
stock. However, I balance this with the fact we regularly see
Microsoft (Who, unless I'm mistaken is also publicly traded)
divulgiing assorted features and whatnot.
I've also heard from time to time that it's more of a
"competitive edge" thing. Where if Company A divulges features in
progress, competitors may be able to somehow use this against
Company A by bringing their own software to market sooner wth the
features in place.
So I have to look at this and rather assume it simply comes
down to the company choice.
Cheers... Rick

How can I update shockwave for director?

Hi
My Shockwave For Director plug-in is out of date but when I try to download it from Adobe's website stage 2 is skipped & the update will not even download let alone install. Could anyone help please?
I am currently using 12.0.4.14
Thank you!

If you are running Windows, this link always points to the latest version of the full installer

Plugin Check keeps flagging Shockwave for Director despite latest version

When I point Firefox 4.0.1 to the Plugin Check page
<http://www.mozilla.com/en-US/plugincheck/>
It flags the following plugin as outdated:
Shockwave for Director
Adobe Shockwave for Director Netscape plug-in, version 11.5.9
However, I have the latest version of Shockwave installed (11.5.9.620) installed. Reinstalling the plugin does not change how the Mozilla Firefox Plugin Check page sees that plugin.

Thanks Helper7677.
So, paraphrasing your answer, the Adobe Plugin isn't identifying itself fully (.620), hence the Firefox Plugin Check page thinks my copy of the plugin is out-of-date.
I had checked the Adobe sites you noted, so I was sure I had the latest version. I was thinking this might be a bug in the Plugin Check page, but you've now cleared that up.
Using Property List Editor, I examined the Info.plist within the bundle for this plugin. It identifies the plugin fully in several key-value pairs as '''11.5.9r620''', but the WebPluginDescription key it has the value:
'''Adobe Shockwave for Director Netscape plug-in, version 11.5.9'''
If Firefox is collecting that value, then passing it along to the Plugin Check page, that explains why the Plugin Check page thinks my version is obsolete.
I don't know how Firefox checks for the version information for the plugins it loads, but if it checked the "Bundle versions string, short" key for this plugin it would find the correct version (assuming Adobe always populates that field correctly).

No option to uninstall Shockwave for director plugin

I want to get by without Adobe and have uninstalled all but am left with this shockwave for director plugin that only give options whether to activate or not. But I want it gone. How do I do that?

Thanks. The about:plugins way worked. I couldn't use the control panel as it didn't list the plugin.
Good to know this method as there are some other plugins that got installed that I don't think I need, or use, so I can declutter.

Future for Director ??

I've been using Director on and off since 1995 and when D7
users couldn't upgrade to MX we didn't upgrade. Now I see Adobe is
offering an upgrade path for D7 users for $399. But this begs the
question, what's the future for Director, moreso now that Adobe
owns the product?
I think Director is a great and powerful app, does anyone
have any insight as to a product refresh?
thanks.

The official Adobe word on the next version of director:
http://www.adobe.com/products/director/special/crossproduct/faq.html
Interview with Tom Higgins, discussing the next version of
director:
http://www.digitalmediadesigner.com/articles/viewarticle.jsp?id=53027
(Tom is no longer with Adobe, however)
- Ben

System Requirements for Shockwave for Director 12.0.2.122

I’m on a Mac running OS X 10.6.8.
Main browser Firefox 19.0.2 tells me my Shockwave for Director 12.0.0.112 Full 64 bit needs upgrading to 12.0.2.122, but the Adobe download site says the System Requirements are OS X 10.7.
Secondary browsers are an older Safari (5.1.8) and the current Chrome (26.0.1410.63). Do these meet Sys Reqs?

SouthernTrouble1975 wrote:
Hi Necromanthus!
Thanks for your help! I don't know why the path would be wrong as it is how it comes out during the install. I attempted the download as you suggested and still received the same error. I did notice however that going through this way did offer the full version and not just the "slim" version that is given off the standard download. However, the same error is given for both.
Any other suggestions? I am starting to think my computer is possessed! Oh, and as for the Admin rights, yes, I have full rights, I'm actually the only user on this computer.
Admin account without write permissions indicates infected OS and hijacked administrator account.
Anyway, Pat is right: you need to provide more details about your OS.
In case of Windows 7 64bit, the installation folder is C:\Windows\SysWOW64\Adobe\Shockwave 12\
Try the following:
- check out if you have any installed SW plugin. If yes, just remove it.
- download the full installer
- disconnect the network connection
- turn off the antivirus, firewall and any other "application locker"
- run the installer as administrator.
- see if everything is ok.
Good luck.

How can I make (automatic) accounts for users of my adobe muse site?

Adobe, google, facebook and more site haves accounts for his users, but how can I make a system with accounts for users of my adobe muse site?

Hi,
Try some suggestion given in this thread
http://forums.adobe.com/message/5362643#5362643

How to Network Interface for Remote Debugging in Adobe Flash Professional CS6?

How to Network Interface for Remote Debugging in Adobe Flash Professional CS6?

Check out : http://helpx.adobe.com/flash/using/whats-new-cs6.html
In that click on "Choose network interface for remote debugging for AIR" section.
Hope it helps.

Newgroups for Director: Macromedia or Adobe?

Similar Messages

Maybe you are looking for