--- In [email protected], <[EMAIL PROTECTED]> wrote: > > Amy - that would be a breach of confidentiality in the legal and business world. You can not share information like that when a company is paying you to develop/code that information, unless it is specifically called out in any agreements. I suspect that the company looking to hire you for this project is also looking to obtain a competitive advantage, so....your sharing of information outside of the employing company would be counter to their desired end game....
eLearning isn't usually about competitive advantages. I suspect that the whole work for hire thing is because they also _do_ have some business critical code that they contract out. But in general the only reason businesses care _how_ eLearning is coded is based on how that affects code. The eLearning community, however, is waiting with bated breath for Flex example code that will allow people to get their heads around how, for instance, they can present pages of data driven content with a coherent navigational structure. It's been almost a year since Authorware's EOD was announced, and people need something else they can do to with this type of content. And if I retain the freedom to post generic code that doesn't reveal the specific business practices of the client, I'm in a better position to help people move forward. The ideal would be for Adobe to step forward and provide some example code or assist community leaders in doing so, but so far we've gotten loads of lip service from various parties but no actual help. So the ownership of the code isn't so much an issue for me personally, but more for the eLearning community that would like to use this tool but so far has been stymied by lack of a clearly documented path on how to do so. -Amy
