As for your questions, I will have to answer them with: not yet. But it should easily possible, especially with the help of others. The internal roster I'm using is based on player names, so adding party1..4 and pets is rather trivial I assume. And the click'n'heal support isn't much more than a few lines - afaik.
I don't consider what I've written being done. Not at all. It's pretty stable at the moment, but it was designed for my personal needs (and a few guildies) - so there aren't many config options. But I'm hoping that once it's been uploaded to the SVN a few people start optimizing code, adding features, fixing bugs etc. My time is rather limited (3-5hrs coding per week), but I'm interested to see which direction this project will take with an active community.
At the moment I'm strill struggling with removing features. Yes, this is not a typo. This project started lots of months ago, and I didn't add frames until I ace'd it. Now the old features are nice for some, but aren't part of the core - and as I don't want to start this project with messy code you'd need to spend lots of time with to understand what's going on, I'm trying to modularize it (while thinking about how/if to release these additional modules seperately). At the moment the addon has about 1400 lines of code, but the core is probably less than 50% (and in better shape than the rest).
Cladhaire already pointed me into the direction of moving code to additional lua files, but I'm still rather clueless how such modules can e.g. add keybindings, chat command handlers, can register the same events as the core etc. This might take a while to figure out, and I'd prefer to not publish it before this isn't done. Well - if someone who has lots of time, is familiar with modularized ace-coding and would want to spend a few hours contacts me, this might speed up this process...
 these features are:
- auto selection of heal rank for (Flash/Greater) Heal, Lesser Healing Wave, Healing Touch based on healing gear and if the target has aggro and/or is in the process of being healed by someone else.
- auto selection of the first person on the list who is in range for that spell.
- skipping people with active renew/rejuv when casting HOTs, skipping people with shield debuff.
- smart resurrecting people in range with /say announcement, based on priority (ressers first, then buffers,...).
- visible/audio warning on overhealing.
Don't just hide it... I think its best if it does what it does, and you use the built in in game addon loading screen of blizzard to decide wich class/character gets wich addons (like all the other kids).
It was a simple bug that didn't let Squishy work when playing non-healing classes (btw, it doesn't have any Paladin support atm and treats them as non-healers). Just fixed it on the SVN.
As for hiding - I agree with Industrial, if you don't want to have it enabled for your rogue, just don't enable it in the Blizzard addon selector. And if you want the audio aggro warning but not the visual frame, define a class profile for Squishy (I think that is done via "/ace profile class Squishy") and then hide the frame via "/squishy frame".
/standby - what does that do exactly, and where is the difference to disabling it? Or is /standby just a toggle shortcut for /enable and /disable? I've never used /standby and am not sure how one would benefit from using this option.
I have 174 AddOns, including the Blizzard default ones. I don't want to be fiddling in my AddOn list every time I decide to play a different character. I don't see why something specific to a particular class or archetype should be appearing when I'm not playing that class or archetype. AceSwiftShift doesn't get loaded unless I'm playing my druid or shadow priest. Likewise Necronomicon doesn't load unless I'm playing my warlock.
I'm sorry, but telling players they need to manage their own AddOns because you don't feel like adding a simple if statement is arrogance nearly as bad as Saien.
The point of /standby is it allows you to disable the AddOn without logging out to character select.
I have 174 AddOns, including the Blizzard default ones. I don't want to be fiddling in my AddOn list every time I decide to play a different character.
Did you take a look at the blizzard addon screen lately? You can choose which addons for which characters are loading (dropdown menu at the top to choose the character), and only one time -- no need to switch anything everytime you log to another char.
:) - so, how do you like the addon? Does everything work as it should? Have you come across any problems/errors? And if you're an active coder, any thoughts on the code and how to optimize/modularize it?