Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers, Unverified Users
Joined: 10/28/2004(UTC)
Posts: 3,111
Location: Perth, Western Australia
Was thanked: 16 time(s) in 16 post(s)
|
Is there a formal definition to when code becomes an add-on and when it becomes a plugin ???
Is there a need for two defintions?
Does any one care? :mrgnr:
wabbit :D
P.S. Or is that add-in and plug-on ?? :lol:
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users
Joined: 1/19/2005(UTC)
Posts: 1,065
Location: Koh Pha-Ngan, Earth
Was thanked: 2 time(s) in 2 post(s)
|
wabbit wrote:Or is that add-in and plug-on ?? :lol:
Right-on, Wabbit. :)
My guess is that a plug-in utilizes a MetaStock DLL, whereas an add-on would just use plain vanilla MS code.
I use the word "kit" to cover an integrated collection of indicators, chart experts, templates, explorations and DLLs, such as in the MACDH Divergence kit and URSC kit.
jose '-)
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users, Unverified Users
Joined: 10/28/2004(UTC)
Posts: 121
|
Actually, the difference is if the product is supported by Equis or the developer.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers
Joined: 9/10/2004(UTC)
Posts: 863
Location: Salt Lake City, UT
|
Joe wins the fluffy bunny!
A plug-in is developed by and supported by Equis. An add-on is developed by and supported by a third party... though... we are making an effort to move away from that confusion in marketing. We will mostly likely just be referring to plug-ins in the future.
:) M
|
|
|
|
|
|
| Users browsing this topic |
|
Guest (Hidden)
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
