when I moved to click-once deployments you no longer had an option to elevate. In fact, it should have become unnecessary after the first time you ran the app.
Oh, the run as administrator option must have been left over from an older WAU 1.9 or an older .NET - you are right suing .NET 3.5 and the current WAU I don't see it.
I would like to offer an alternative answer to #17
17) I am running Windows Vista, and wow is installed in the Program Files directory
You have two choices here: allow WAU to update the addons for all users or just yourself.
17a) I want to update the AddOns for all users on this Vista machine using the Administrator account.
You need to run the program from an administrator account. (right click on the shortcut and click "run as administrator")
You need to fix the permissions on wow directory to give administrators full control, and propagate that to all subdirectories, or install WOW into some directory besides program files.
17b) I want to update the AddOns just for my user account on this Vista machine using the VirtualStore.
First be sure that you are using the AddOns and WTF folders located in your VirtualStore. Find your WoW installation directory ( C:\Program Files\World of Warcraft ) and copy the "Interface" and "WTF" folders to your Vista account's VirtualStore ( C:\Users\USERNAME\AppData\Local\VirtualStore\Program Files\World of Warcraft ). It is recommended that you merge folders but do not overwrite files. If you are the only user playing WoW you may safely delete the "Interface" and "WTF" folders left in the Program Files location ( C:\Program Files\World of Warcraft ).
Next change WAU to update the files in your VirtualStore and not in program files ( C:\Users\USERNAME\AppData\Local\VirtualStore\Program Files\World of Warcraft ). This will allow you to use different AddOns than other users and also may allow you to run WAU without running it as an administrator.
ambitious? how about linking to your quest log and not just listing instances.
That is in fact similar to the first use case I have listed on the Grouper wiki page! ;)
I'll add auto-grouping for active kill quests within proximity.
maybe have a way to push your instance interest via quest-log as well.
That definitely fits with some of the automation/preference ideas in the original grouper. I'm not sure how people feel about a complex grouping preference system.
Here is something I found EXTREMELY useful for endgame raiding: miss rate / parried rate. The details pages are there really just for amusement.
Parried Rate is below. Miss rate is exactly the same but with more hitDetails present. Because staying behind the boss is so important in raiding to tank longevity I think this could be included in the default display sets.
with regard to these sets, I would like to be able to show the % of hits out of a total, for example in the Damage Dealt Hit Details the lines display "1. Melee (374) 12.1k" and I want to have a percent in the middle that shows that 40% of the hits were melee, but I'm not sure what tag to use to describe the total data count.
I am interested in a new LFG browser interface. It should be its own frame so that more information can be seen and so that we can take advantage of mouse-over events to work around the user interaction requirement of LFG queries.
Thanks for the posts. Grouper has been plagued by limitations of the scanning ability... (having to spam click) as well as not being able to download the entire database. For that reason and my natural tendency to disappear when my job gets to me I haven't touched it yet.
What I have been doing is really thinking about what people would actually need in a LFG addon and what I can possibly do with the hamstrung system Blizzard gave us. They promised us a way to LFG for alts and have mubmled things about general availability but still the best way to group up is to spam TRADE CHAT and LFG.
So I'm going back to the drawing board... I want to really focus on developing use cases that people will be drawn to and that will reinforce use of the LFG system.
Check out the grouper wiki page. http://wowace.com/wiki/Grouper Feel free to add use cases if you have new ones, or notes in discussion why some use cases are better or worse.
The vitriolic reaction you are seeing (I believe) is due to people recognizing that it appears the "easiest" route was taken to generate revenue, not necessarily the smartest or most productive route.
This is a volunteer project and requiring Kael to produce a perfect way to support the site is not reasonable or respectful of his time.
If you would like to help I'm sure you will find many minds receptive to your suggestions, but you might need to do a lot of research and put a great deal of effort into producing a workable solution.
Quote from Ellipsis »
Just a suggestion, but if the majority of the problem is updater traffic, couldn't something be done to reduce/limit the traffic rather than just pay for it? For example, only allowing updates every X amount of time, or even forcing disembedded libs (since they are quite easily manageable with an updater, and it would reduce the required download traffic by quite a bit). Has any thought been put into options like this?
1) limiting the number of updates - already implemented in WAU1.9 and the next gen prototypes
2) -noext is the default for the next gen prototype (to some user's disdain)
3) also the .xml files use gzip compression now, which has cut down the xml index download size by 80% (addons come pre-zipped, no optimization there) - however these features sometimes require user action to keep their updater up-to-date which is another problem Kael has been working to address (update nags, forced updates in the next gen prototypes)
Ads in WAU should be restricted to their host frame. Any ability for ads to "pop-up", emit sound, or take control of the application should be considered a bug.
If you disagree with supporting the wowace.com website I would suggest you download your Ace addons from wowinterface.com or another similar site. I know that wowace.com is in the red.
* Changed WoWAce code to use the RSS feeds for both version checking and the "Install from WoWAce" dialog
Yay!
p.s. also the files server was changed to work with gzip encoding, so if you can get your HTTP client to send "Accept-Encoding: gzip" it will send you back the xml gzip'd for even faster updating!
They seem to act like it's a personal offense everyone isn't using their tool.
You completely (almost offensively) misinterperet our/my intentions - the goal here is to keep the wowace server stable, not to force you to use some silly open source application over another!
You'll notice that Kaelten posted a warning thread quite a while ago, and I posted in this thread because WUU is such a fantastic site-neutral & platform-neutral updater!
0
Well it looks like Vista users still need some way to elevate or they have to muck with either permissions or the virtual store.
0
My 17a is wrong.
0
0
That is in fact similar to the first use case I have listed on the Grouper wiki page! ;)
I'll add auto-grouping for active kill quests within proximity.
That definitely fits with some of the automation/preference ideas in the original grouper. I'm not sure how people feel about a complex grouping preference system.
0
Parried Rate is below. Miss rate is exactly the same but with more hitDetails present. Because staying behind the boss is so important in raiding to tank longevity I think this could be included in the default display sets.
with regard to these sets, I would like to be able to show the % of hits out of a total, for example in the Damage Dealt Hit Details the lines display "1. Melee (374) 12.1k" and I want to have a percent in the middle that shows that 40% of the hits were melee, but I'm not sure what tag to use to describe the total data count.
EDIT: filterTags above should be BarValue > 0
0
0
What I have been doing is really thinking about what people would actually need in a LFG addon and what I can possibly do with the hamstrung system Blizzard gave us. They promised us a way to LFG for alts and have mubmled things about general availability but still the best way to group up is to spam TRADE CHAT and LFG.
So I'm going back to the drawing board... I want to really focus on developing use cases that people will be drawn to and that will reinforce use of the LFG system.
Check out the grouper wiki page. http://wowace.com/wiki/Grouper Feel free to add use cases if you have new ones, or notes in discussion why some use cases are better or worse.
0
I'm also playing with guild bank support
I'll take a look at some of the issues you guys are reporting, but I can't promise anything ;)
0
Please provide the exact name of the threat that AVG identified - that trojan name does not register any search results on AVG's threat page.
0
This is a volunteer project and requiring Kael to produce a perfect way to support the site is not reasonable or respectful of his time.
If you would like to help I'm sure you will find many minds receptive to your suggestions, but you might need to do a lot of research and put a great deal of effort into producing a workable solution.
1) limiting the number of updates - already implemented in WAU1.9 and the next gen prototypes
2) -noext is the default for the next gen prototype (to some user's disdain)
3) also the .xml files use gzip compression now, which has cut down the xml index download size by 80% (addons come pre-zipped, no optimization there) - however these features sometimes require user action to keep their updater up-to-date which is another problem Kael has been working to address (update nags, forced updates in the next gen prototypes)
0
If you disagree with supporting the wowace.com website I would suggest you download your Ace addons from wowinterface.com or another similar site. I know that wowace.com is in the red.
0
yea you're right
@Flare - sorry I see who you were referring to ;)
I'd prefer to just make a higher quality updater to encourage its use.
0
Yay!
p.s. also the files server was changed to work with gzip encoding, so if you can get your HTTP client to send "Accept-Encoding: gzip" it will send you back the xml gzip'd for even faster updating!
0
You completely (almost offensively) misinterperet our/my intentions - the goal here is to keep the wowace server stable, not to force you to use some silly open source application over another!
You'll notice that Kaelten posted a warning thread quite a while ago, and I posted in this thread because WUU is such a fantastic site-neutral & platform-neutral updater!
0
2) fixed :P