Split off API?

Hi,
I just love ActiveEdit (5.x) - it is a super time saver. Thank you for all your work on it.

I was just working on a problem for which ActiveEdit (5.x) supplied a neat solution: http://drupal.org/node/266416
ActiveEdit supplied a perfect framework and slot for me to plug-in a bit of code to solve my proble, but unfortunately to use that solution, a potential user needs to "buy the whole package" - meaning, enable activeEdit for everything and install the dependency modules, even though none of the functionality I needed from ActiveEdit relied on those dependencies (I was adding a complete form to a link).

This got me thinking - wouldn't it be cool if ActiveEdit (6.x) supplied a separate API to the underlying framework, with the goal of making is simpler to add AJAX form editing - the API should have no UI and no dependencies. All the behaviors for ActiveEdit could then be enabled via a separate module.

Here's my use-case for an example:

- I have a module that adds a links link
- that link simply opens a small form
- the form could be loaded and submitted asynchronously
- I want to add the asynchronous load as an option for my module
- I want to add a new permission 'ajax edit MY LINK'
- of course, I want everything to gracefully degrade to my default behavior.

There's probably dozens of good reasons not to do this - but I'm blissfully unaware ;-) Just thought it might be worth mentioning since you are the start of a major re-factoring.
thanks again for a great module.