What do you not understand about the distance of 5,424 miles I'm forced to be separated from actual hardware for an indeterminate period of time while I'm trying to do development? I can't see what's happening outside of X, so, I can't see anything sent directly to the framebuffer.
Given all of the other "unfortunate events" associated with this project up to this point, I can't afford to believe any more claims that things will work just fine. I need to see what I'm doing with code executing on the hardware to make sure the display looks as expected, particularly within the constraints of the hardware. I've made it abundantly clear that the vast majority of what I will be doing will be executing on the GPU, and I've demonstrated in WebGL that I know what I'm doing, since that uses essentially the same GL techniques as those needed for ES.
As I've already stated, eventually, the entire Pi-finity! software suite will be running full-screen, but, all I want to do for now is run bits, pieces, and stubs in whatever mode I can access remotely. Based on the latest vague reports from the distributors, it appears I'm at least a third or fourth month away from receiving a board beyond the original "for-sure" date when availability was supposed to occur (which was four months beyond the original estimate of hardware availability to developers). We have to be able to do at least a modicum of time and other resource planning, especially since we're trying to do this on top of already-overloaded schedules for work that keeps us fed, dry, and slightly less cranky than we otherwise would be.
Such comments precisely reflect the lack of comprehension of what frustrated developers are having to do to get things done under very disappointing circumstances. They also reflect how priorities have not been aligned so that there will be the kinds of eye-popping software available sooner that is critically needed to differentiate the Pi from the crowd of ho-hum, yet-another-computer systems. The misalignment is also impeding the work to adequately document how students can create their own impressive software, which is my primary goal. Just tossing out URLs to pages with upwards of hundreds of links to code that won't actually run on the Pi is not going to win any young fans who are already being distracted by game consoles, mobile devices, and everything else with billions of dollars of flashy marketing behind them.
I still have high hopes that I'll be able to get some really great software running on the Pi that will make it even more popular than it already is, sight unseen. The situation reminds me of the comic from "The Far Side", where a pair of vultures are watching some poor soul crawling across a parched desert, and one vulture says to the other, "Patience my ass, I'm gonna kill somethin'." I am in no way advocating violence against any poor souls crawling across deserts, I just love the warped humor of Gary Larson.
Well, I guess now that I can't make any progress on GPU-oriented software, I have no excuse for not concentrating on the peer-to-peer experiments. However, that means I need to sweet-talk at least one more lucky stiff with a Pi to allow me to invade their board to install and test a Pi-finity! P2P transponder (not the same as a file-sharing P2P client such as bit-torrent software, but, it's based on some of the same principles and code fragments).
I suppose things could be worse, and it was Monday instead of Saturday
The best things in life aren't things ... but, a Pi comes pretty darned close!
"Education is not the filling of a pail, but the lighting of a fire." -- W.B. Yeats
In theory, theory & practice are the same - in practice, they aren't!!!