>I have found this thread most interesting. I am an
Authorware user as
>well. I
> have been uncertain as to what direction to go since
Adobe announced the
> end of
> Authorware development. I develop CBT and Instructor led
CBT training. I
> have
> used Authorware in the past. I have a project coming up
that will be an
> ongoing project for CBT on the web, and in certain
instances, standalone
> CD/DVD. So I decided to go back out and take a look at
what other
> products are
> available. I can honestly say I don't have the same
confidence with
> Captivate
> as I do with Authorware. Steve you seem to be very
knowlegable, what
> direction
> would you send someone in to make an informed decision?
Tom, I've been using Authorware daily for a little over ten
years - so I
probably know it as well as anyone might. There is no doubt
whatsoever that
Authorware is orders of magnitude more powerful than
Captivate. So without a
doubt, Captivate will not be a satisfactory substitute for
many Authorware
users.
But remember - many of the people who have been using
Authorware for a long
time are what has become affectionately known as 'icon
draggers'. The put
together simple, or in some cases remarkably complex courses
with little or
no scripting. Many of these users will be able to move to
Captivate and,
after a little acclimatisation, continue building courses
that are
essentially similar to what they have been doing.
Here's what I have been recommending over the last year.
--
Captivate is a good product for the niche that it works
within - software
simulation and scenario-based learning. It has serious
shortcomings for
those who are used to advanced features, but for many it is
actually
sufficient for their needs.
--
Adobe's recommendation is that if you need the power of
Authorware -
specifically the need to use x32, u32, ActiveX, serial port
integration,
lots of external content, access to system-level features and
functionality,
local file system access and manipulation etc, then you
should look at
Director. A new version of Director has just been released,
and there is
every reason to believe that, at least in the near term
(let's say 5 years)
that Director will continue to be solidly supported by Adobe.
**personally I have no intention of using Director unless I
have specific 3D
needs.**
--
Flash is a powerful tool, that has become a favourite for
many eLearning
developers. It has most (not all) of the power of Director.
It lacks assess
to dlls, ActiveX, local file system etc. It has limited
access to external
content (look at how Authorware and Director can essentially
be conduits for
any file type you can imagine). But many of those
shortcomings can be
overcome if you are willing run local files instead of
web-based files, and
use tools like Swift to extend the features of Flash (if I
got the product
name right, it gives access to DLLs and other things that let
you extend
Flash's capabilities similar to X32, u32 etc in
Authorware/Director).
Flash can be used as a container for Captivate. It can also
be used to
create extra content that can be imported to Captivate. So if
you choose to
use Captivate and run into limitations, you can combine it
with Flash to
extend it. Note that you can also drop Captivate in to
Director (and
Authorware) if you need to ;-)
Flash is much more complicated to use as a development tool
than either
Captivate or Authorware .. at least, it is a lot less
approachable to the
'icon dragger' type. But for many it will be acceptable to
have the icon
draggers create some content then pass it to Flash developers
to add more
complex interactivity etc.
--
Flex is Adobe's new baby. Put very simply, Flex is Flash
without the
timeline. So it's a pure application development tool, akin
to Visual Studio
(no I'm not saying they are just the same!!!). It has some
cool things that
Flash hasn't got, but for the purposes of this conversation,
lets just call
it Flash without the timeline.
What I like about Flex is the lack of timeline. But to get
the best out if
it, you really have to be a more of a code head, and
definitely not the
'icon dragger' type form Authorware. As with other tools
listed, Flex can be
a container to other content - you can drop in Flash content,
and it should
be able to work as a container for Captivate. Captivate and
Flex don't talk
too well today, but Adobe seems to have an aggressive
approach to developing
Captivate, so I'd expect better integration between the two
in the next year
or two.
--
AIR is Adobe's newer baby
🙂 AIR (Adobe Integrated Runtime).
Simply put,
AIR allows you to create a swf-based executable file that
runs within a
desktop runtime. You can use Flex, Flash, Dreamweaver
(probably some other
things too) to create AIR output. I'm most interested in
using Flex to
create AIR content.
---
Adobe has some exiting things going on in beta and pre-beta
right now. One
is a tool called Thermo, which enables your designers to
create interfaces
in PhotoShop or Fireworks, then drag them into Thermo, and
using a wysiwyg
editor, your developers can quickly convert that interface
into a Flex file
that recognises text boxes, scrolling panels etc. There's
some cool
demonstration on Adobe Labs and YouTube that explain this
better than I do
🙂
http://labs.adobe.com/wiki/index.php/Thermo
http://www.youtube.com/watch?v=R2pgnNSpi_M
---
So why do I care so much about AIR and Flex?
Adobe has announced the Open Screen project
http://blogs.adobe.com/open/2008/04/the_open_screen_project.html
http://www.flashdevices.net/2008/05/adobe-announces-open-screen-project-pcs.html
http://www.adobe.com/openscreenproject/faq/
http://blog.digitalbackcountry.com/
This aims at creating unified players for desktop and mobile
devices
(phones, PDAs, embedded devices etc) so that a single source
file can be
used to deliver content that looks and works across all the
different
devices. This will allow Flash, Flex and AIR content to be
developed that
runs anywhere.
OK I know there has been similar promises in the past, but
browse the links
above and you can see who is involved (not just Adobe!) and
see how
seriously it is being taken.
My gut feeling is that Adobe is going to put more into
Flex/AIR over the
next few years than into Flash. Hence I am leaning towards
Flex.
Also, if you want your content to automagically reflow when
delivered to
mobile devices, like a good web site will, then Flex is
designed to handle
this easily.
-------------
So my final answer to you.
My recommendation today is
- Use Captivate where you can.
- Extend it with Flash if necessary
- Bring it into Flash if you need to extend it further
- Consider bringing Captivate content into Flex ... but at
the moment that
has some caveats. Communication between Flex and Flash is not
easy.
- Plan for mid-term (one or two years) improvements to
Captivate/Flash/Flex
that will make all three work better together.
- Plan for all of your content becoming easier to build for
mobile devices.
So the toolkit becomes Captivate > Flash > Flex.
Depending on your needs,
current skills, longer term plans etc you may find Captivate
does all you
need. Or you may find Captivate_Flash does everything for
you. Or you may
find you need to dump both, roll up your sleeves and start
utilizing Flex
right now.
---
OK this is long enough. I'm sure you have a ton of questions
if you've
managed to read this far. I'll do my best to answer them, but
be aware that
I am out of town for the next two weeks. I'll try to respond
but that
depends on what internet connections I have. Feel free to
mail me privately
if you have burning questions.
Hopefully others can chime in too.
Oh - also you should consider attending at least one
eLearning conference to
get a better feel for what the industry is doing. My opinion
is not the only
one out there. I didn't touch on Web 2.0 technologies, for
instance :-)
Steve
--
Adobe Community Expert: eLearning, Mobile and Devices
European eLearning Summit - EeLS
Adobe-sponsored eLearning conference.
http://www.elearningsummit.eu