Processing MIDI in non-realtime (Transform Window)

Question

The only thing I miss from my PC days & Cakewalk (years ago) is the CAL scripting language, which allows the user to process MIDI (in non-realtime) in practically any way imaginable.
The Transform Window seems pretty close, but I'm running into a lot of brick walls now (after three years of Logic use) that I'm finally trying to recreate some of the functionality I remember having in CAL.
Particularly, one can't seem to make parameters affect each other? In other words, I can't select a range of MIDI notes (say a snare rush of 16th notes) and apply a velocity crescendo on them based in time (ie, the first note in the measure gets a velocity of 0, the sixteenth gets a velocity of 127, everything in between is scaled appropriately)
Or, I would love to be able to select a measure of (again, let's say a snare rush of 16ths) notes, and change the start position exponentially based on it's current start position (creating an AphexTwinnian log/exp snare rush)
I can do this stuff in Max, but it's such a headache to export MIDI, process, reimport, etc etc ...
I would love to be able to do non-realtime MIDI programming like this without leaving Logic. Is it possible? looking at the manual makes me think it isn't, but I thought I'd ask.

Answer 1

Ok, a bit of an update.
Essentially, I'm just trying to make log/exp drum rushes, which means I'm trying to get the "Exponent" operator to work as expected with the position value, which it does not.
I've figured out how to apply changes in time (by using the position inside operator) like say taking a constant velocity rush and making it fade in or out, and I can use the same principle to move things in time (by adding, subtracting, multiplying, dividing the position value) but there's no way to apply exponential events to time in the Transform Window, unless I'm very much mistaken.
It almost seems as though the way which the exponent operator affects the position value is a bug (gasp)... almost any values but very very low ones (ie .00001) move everything hundreds of bars either forward or backwards (depending on negative or positive values) and do not scale the start times exponentially regardless ...
or am i just not figuring out how using the exponent operator in conjunction with position is supposed to work? this is not covered in the manual.
the 'crescendo' operator is baffling as well. One would expect that using a starting value of "0 0 0 0" would be the base position in your selected region, but actually "-9 0 0 0" is ... and it won't work exponentially, regardless.
I just wish there was a way to open a little text window, and type in an equation to apply to the selected midi notes. that would be amazing.
ie "note(position)=note(position)^1.4" or some such