it depends on how you wish to reprasent that data.
a table is simply a visualisation of a list of numbers. index (position in the array/table) on the x axis and value on the y axis.
you can only input one value per index.
so you could use a table to visualise the pitch (y) of a monophonic instrument over time (x) but you can't represent velocity or anything else... unless you put that into another corresponding table.
then you could use something like [gem] to harvest the data from the two tables and draw lines on a graph whose x and y axis' follow time and pitch, and whose colour is determined by velocity. Afterwards, you could use [gem] to access as many tables as simultaneous notes and project them all to the same graph. (at this point you need to think about a better way of storing all of this information, or how [gem] is going to parse the midi file directly). And then you could work on using the mouse input to click on 'notes' in your [gem] window and move them around.
But after a lot of work, you will have made a crude and slow midi editor. congratulations.
Dual 1.8 IBM G5: Mac OSX 10.4.11 -- Asus eeePC 701: Pure:Dyne / eeeXubuntu GNU/Linux -- myspace.com/thearifd