Addons - Single Source for Classic and current?
Is it possible for an addon to be written such that the same source files can be used for Classic and current?
If a current addon uses ACE3, will it be possible to port that addon to Classic (i.e. are the ACE3 libraries being ported)? |
yes many addons just work on both and many that do not just need a couple of if
|
Depends on what the addon does. For example, an addon tracking calendar events or the collections system won't work in classic since those systems don't exist.
|
Most addons should work just fine, especially addon frameworks like Ace3. Classic has the exact same environment as live does, with the only API differences being the absence of objects that pertain to live-only stuff like banks and the calendar. Classic's Lua environment was initially forked from Legion's environment and from what I understand will stay parallel with live. It is not the actual environment from vanilla.
|
Quote:
|
So it sounds like a tradeskill addon like Skillet will work with minimal changes that can all be determined at runtime.
|
I've found one "gotcha" with single source, the "## Interface: " in the .toc. Classic should be "11302" and Retail/Live is currently "80100". Anyone have a brilliant idea how to solve this one?
|
GetBuildInfo() returns 1.13.2.xxx for classic so :
Lua Code:
|
Quote:
|
Last I checked you couldn't run with ## Interface: 11302 under BfA because it assumed it was too old to even be "out-of-date".
|
Quote:
|
I solved the issue of a conditional variable for which version am I running under but it looks like the issue of a "conditional" .toc line hasn't been solved yet. It may be awhile before I'm ready but my temporary solution will be to build retail using the existing WoWAce SVN repository and tools and then substitute the .toc file in the .zip before uploading it here.
I do have another problem all you "wizards" can help me with :D I'm not getting any lua error output when my addon gets an error. I can't find the option to turn on Blizzard's error output so either I need help with that or I need to know which error reporting addons work on Classic. |
I think we can scratch Skillet (and most other TradeSkill addons) from the single source list as all the C_TradeSkillUI. functions are gone.
I'll see if I can find the version of Skillet before that change happened and if I can find it, how badly it breaks on the current classic build, but I'm not holding my breath. |
Quote:
|
Quote:
|
Quote:
I've come to the conclusion that Skillet is a Retail addon and Skillet - Classic will be a different addon with a different set of sources. This decision is supported by a comparison of: World of Warcraft\_retail_\BlizzardInterfaceCode\Interface\AddOns\Blizzard_TradeSkillUI\ and World of Warcraft\_classic_\BlizzardInterfaceCode\Interface\AddOns\Blizzard_TradeSkillUI\ The question now becomes, do I want to write Skillet - Classic? |
Quote:
1. Do I need it ? 2. How popular is it ? 3. How time consuming will the conversion and later patches be ? 4. Is there another addon that is easier to convert and works in a similar way ? 5. Am I bored enough that I don't care what the answers are ? My MagePorts addon passes 1(kinda) and 2 (definitely)... I am at question 3 and I really am not sure yet.. it all depends on whether I can get a similar output with different functionality. |
All times are GMT -6. The time now is 06:15 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI