Quote:
Originally Posted by brianosmi
Gerry, my sentiment is the same. Most of the developers on my team are not able to implement and make work some of the more complicated work arounds, and frankly the more of these types of workarounds are needed the less it becomes "rapid" eLearning.
|
. . . and the more one is sometimes tempted to look at other solutions (or pressured by others to do so).
I have high hopes (and faith) for the next versions of AP, QM, and AE--hope they (i.e., Articulate) remove at least a few of these workarounds from developer fixes to user software features.
I really like that people like daveperso and spectre and others can push and extend the Articulate apps so much. Great for them and us.
But I want some of the same things for the "technically challenged" eventually in the apps themselves. Wish we didn't have to wait for new releases to see that. And I wouldn't mind seeing a new thing or two in a service release (like adding web object support to AE).
Best!
- Gerry