#summary Stuff I want to do
#labels Featured

[Bagnon]:
  * Do something with saved searches/bookmarks
  * Add in guild bank support
  * If I don't continue Combuctor, then add in a Blizzard layout style.
  * Add in more UI polish

[Bagnon_Forever]:
  * Add command line searching using LibItemSearch

Combuctor:
  * Rewrite, like I did for Bagnon.
  * Implement OO based set API, add in wrapper for LibItemSearch
  * Add in event-> tab event system (ex, show bank frame, normal tab when showing the bank, keyring when I click the keyring, trade bags...)
  * Add in a few configuration options (scale, etc)

[Dominos]:
  * Write a totem bar that more closely resembles the 
  * Clean up the auto fading and show state interfaces.
  * Revise wiki, add FAQ
  * Make a dedicated possess bar.
  * Make a dedicated vehicle bar.
  * Make Dominos have a saner layout when switching between 1-120 bars.  This includes adding a slider for numbars/numbuttons
  * Clean up the auto fading and show state interfaces.
  * Add in more UI polish

[Ludwig]:
  * Clean up GUI code

[OmniCC]:
  * Rewrite, merge in Shine and Pulse.

Sage:
  * Separate frame folders (core, party, target_target, focus_target, party_targets)
  * Write wiki on completion of the thing
  * Add "always show these buffs" and "always show these debuffs" lists

-----
Experiments/Random Ideas I Have:
  * Dominos + Perspectives: I want a system where I get to have multiple layouts based on what macro state I'm in.  Basically I only want to show a vehicle bar when in a vehicle, a possess bar when possessing something, and have key bindings setup for each form.
  * An infinite macro button addon:  I want to write an addon where I can draw as many macro bars as I want using the system I developed for Bongos3.  The scope of this addon should be heavily limited (ie, I expect you to use this addon with the stock interface, or with another actionbar addon).  Should also use the perspective system I intend on developing, for best effect.
  * A Cooldown Count type addon that works in a similar manner as Button Facade:  This way I can avoid nasty things like requiring the noCooldownCount flag, and allow finer control over how text is displayed on each element (per button group position offsets, etc).