i have poked around and found i have read access to the WoWAce SVN (though i am leaving it at read access... i was never "officially" able to obtain commit access, in fact never had a word from the WoWAce folks of any kind, and i don't want to mess with things without permission, so i moved my fork of Aloft to WoWInterface).
Everyone has read access to svn.wowace.com, but nobody has write access to svn.wowace.com. The only write access is on dev.wowace.com, which requires a username and password for any access (read or write). Getting a username and password set up involves weeks (possibly months) of waiting for Kaelten to get around to reading your email and setting it up for you. At this point in time, I'd guess he's simply ignoring all SVN responses, since the current SVN will be read-only for everyone in the very near future.
Once the transition happens, it will probably be easier to get SVN access, since each project will have its own repository, rather than there being one big repository that everyone has (more or less) equal access to.
I've always thought of the paladin class color as pink, not purple...
Quote from acapela »
- separating Aloft modules out into separate addons sounds like it could be a good idea to me, but understand that there are a large number of these modules; it could end up looking like Grid or Pitbull3 with no trouble whatsoever. there will be people who want mana/threat text tags but not bars, and maybe even vis a versa, so i am at a loss to see a way to chunk functionality at a coarser granularity than individual modules. i suppose only those folks who want "everything" would end up being nickled/dimed to any great extent, but still, it could get ugly. nevertheless, i will give it some thought.
There wouldn't be any overhead beyond what already exists if, say, you had Aloft and Aloft_Aliases instead of just Aloft with the alias module built in. You'd be adding a folder and a TOC, and nothing more. As for separation, it doesn't need to be that fine-grained. Aloft_Threat would contain both threat bars and threat text. Aloft_CCTimers would contain both polymorph and shackle timers.
Yeah, it's fairly common to see people posting "OMG ALOFT USING 2MB MEMORY WTF". I think splitting off some of the special-interest modules -- such as the CC timers, aliases, and comments -- into external modules would be great.
As long as you don't have a hunter who named his pet after himself or a teammate, it isn't really a problem, as PvP opponents have unique names, and names are one of the few things you can get from a nameplate. I'd rather PvP-specific stuff didn't find its way into Aloft though. A third-party/external module is fine, but as I don't do arenas or battlegrounds, it'd just be one more chunk of code getting loaded into memory that I don't need.
It's quite big and I guess complex. Dunno what other people use for modules, but an Aloft light would be fine for me.
Yeah, I don't use a lot of the modules. All I really use Aloft for are changing the frame size, setting alpha levels for target/nontarget, setting the size/texture/color of the health bar, size/font of the health/level texts, raid/boss icon sizes, and positioning of all of the above. I used to use the Visibility module to hide nameplates for critters and neutral creatures, but it doesn't seem to work anymore.
You'd have to edit the code. I don't know anything about the MobInfo2 API, but there's probably only one place where Aloft does anything with MobHealth. Just figure out what the equivalent functions are for MI2 and change accordingly.
Not a whole lot Aloft can do... essentially any addon that uses unit names as primary identifiers will have this issue. While unit frame addons can get around this by using unit IDs or GUIDs as identifiers, you can't get those data from nameplates, so it would be rather complicated for Aloft to avoid, and would require storing a bunch of additional information about every unit it encountered.
- updating the tag system to use LibDogtag-3.0 (whatever the latest/greatest state-of-the-art is), assuming this is technically feasible; i gather UnitIDs are not available from nameplates, so i will have to figure this out
I would actually strongly prefer that Aloft did not use DogTag. TagCompiler is much simpler, and more importantly, does not consume more CPU cycles and increasing memory than most of my other ~150 addons combined, wheras DogTag does, even though the only addon I run which uses it is an action bar addon that uses DogTag to display key bindings (which almost never change) and item counts (which change rather infrequently in the grand scheme of things). If I could find another bar addon that covered most of what InfiniBar does, but didn't require DogTag, I would immediately dump InfiniBar.
- updating the threat subsystem to LibThreat-2.0; i assume the same issue exists here with UnitIDs
Correct, although with WotLK looming, I'm not sure it's worth the effort, as actual threat values will now be exposed through the WoW API and will not require Threat-x.0 to estimate them.
- fixing mouse interaction (which i notice is not working for me now), assuming this is not something blizzard has broken in the underlying nameplate subsystem
What do you mean? Mouse interaction works fine for me.
WoWInterface would probably be my pick
^ I'm already using WoWInterface as my primary addon host, and now that they've got SVN repos, I'm using them for my development as well. I'm still committing "release" versions here on WowAce for updater users, but I'll probably pull them shortly so I can see what the new site has to offer before uploading again.
can i get a quick update on the status/future of this mod?
There haven't been any updates because the author has disappeared, and nobody else has volunteered to maintain the addon. The TOC hasn't been updated to indicate 2.4 compatibility because the addon isn't fully compatible with 2.4; it still references the now-defunct Threat-1.0, for example. I have no idea if Aloft will continue to mostly function in WotLK or not, although I suppose I'll find out soon once my beta client finishes downloading and installing.
Yeah, from your posts, it seemed you were requesting the functionality be added to Aloft itself. What you're requesting would be a "plugin", not a "module". If you want to write a plugin to add this feature, or you can find someone else who wants to write it, feel free.