> I'm not sure I would want to build anything like this into the Terra theme, > since the audio files could significantly increase the size of the JAR. Also, > a lot of users find gratuitous sound effects annoying. Yes, I agree with you, this is a feature for not-so-common cases, and I don't want audio files inside Pivot, as you said.
> The idea to provide a pluggable API is interesting, but might be > over-desiging it. It's true. > An application that needs audio could simply use the most appropriate sound > library. To attach this type of effects to single components/events existing features are enough. But if you want to do something with a trigger on all button clicks for example ? A solution to attach a global listener (by default null/none) to events/classes ? So in this case I could handle in a transparent way this type of effects ... but maybe you have other solutions (some type of visual or non-visual decorator, or a global filter by event/component class/component name, or other). Suggestions ? Bye
