Reputation: 7675
This is targeted at developers who consider themselves Flex or Actionscript developers.
I'm writing a helper library to aid connecting to an API from a Flex application.
If you were looking for said library; would you be searching for:
Or would you search for both?
Thanks!
Upvotes: 2
Views: 153
Reputation: 37104
Assuming that this is a client library written in ActionScript for use in any environment that supports ActionScript, compatibility with Flex is a given but that in no way makes it a 'Flex' library.
It is an ActionScript library and I would assume that a Flex programmer looking for connectivity to your API would make the connection.
If you want to promote discoverability, you could note in the verbage the various use cases for the library, e.g. ActionScript Library Foo for use in Flash/Flex/XXXX.
Upvotes: 0
Reputation: 27045
If it's Flex specific I'd say Flex. If not; Actionscript.
Flex is stricly a "subset" of Actionscript. If it works in pure Actionscript, it'll work in Flex too. I see no reason to call it a Flex library unless it's dependent on or only useful in relation to just that.
Upvotes: 2
Reputation: 21924
Unquestionably I would be searching for a "Flex client library" or "Flex component". I would only look for an "Actionscript" library if it had nothing to with Flex.
Upvotes: 1
Reputation: 1606
I would name it "Actionscript {API name} client library for Flex" since it's written in ActionScript (I'm assuming), targeted for Flex development.
Upvotes: 0
Reputation: 335
I would search for both. I'd expect the flex api to make use of the mx namespace, and the actionscript api to be vanilla actionscript. (So if you are using the mx namespace, don't call it an actionscript library).
Upvotes: 0