I'm not sure why Westy is comparing things here, but apologies if I have got this this wrong.(Though he certainly likes blowing his trumpet
).
Westy is essentially sending serial commands to a firmware chip where all the Graphics controls are done by it written in compiled code by pro writers.
Whereas , NBW is trying to design the drivers from scratch -
much harder to do.
NBW, have a think about the structure of your code.
To set a dot you will have to determine X-Y coord, read a block of 8 pixels, bitwise your new dot and then write that block back. x3 for colour.
If you want to try memory mapping via an i2C RAM then good luck.
When I was doing a mono OLED I had enough PIC RAM to memory map and refreshed the OLED memory without read/write bitwising. (The logic was done in the PIC RAM). I could get screen refresh of 250 pages per second using compiled code.
But early tests on a Densitron colour OLED showed I couldn't use that method using a low-cost PIC and speed would go down to 2 or 3 fps.
If I were using external RAM I'd use parallel or, better still, use a dsPIC or similar.
You'll find that a "raw" PIC will be many times faster than an X2. You'll see that even with good code you'll probably have a pretty slow screen refresh for graphics. If you start I2C storage then I reckon it'll drive you nuts.
Good luck, just remember that what you are doing is much more complicated than sending a serial command. (I emphasise this because less experienced people may be viewing this and think "Ooh that looks easy" - it ain't!).