> Just a single (selectable) high-speed analog signal would also be very, > very nice. The resolution doesn't have to be great (4-bits?).
Yes, that would be nice. But the last I read, the hardware can't support that. Which is why I suggested adding a trigger output signal that can trigger an oscilloscope. And Timothy's reply indicated that it would be easy to do that. > > Has anyone written any code for this yet? First design, then code. > > Why is everyone caught up in what color someone wants it to be? Calm down. I haven't seen anyone suggest that v0.1 must support user color choices. But it is very little additional work to read in color choices from a file. And the feature could be very useful if the programmer picks colors that don't work well on the user's display. Or maybe the user is color blind. My goal is a design that is clean and simple. Easy to implement. Sort out the features that are absolutely required, the features that are highly desirable, the features that are desirable, and the features that are fluff. Weigh the cost (economic, time, complexity, etc.) against the usefulness of the feature. Example 1: analog data is likely to be very useful, perhaps required. But given what I've read from Timothy, it isn't going to happen, at least not on OGD1. But plan B, generating a trigger signal for a 'scope, would be fairly easy to do. Small amount of work, big payoff. Yes it requires a 'scope, but people designing and debugging PCI devices are likely to have access to one. Example 2: Color. If the programmer picks good colors, then the user probably doesn't need to change them. But people don't always pick good colors. The websites with medium blue text on slightly darker blue background teach us that allowing the user to pick the colors is sometimes essential. Very small amount of work, big payoff. Example 3: remote access. By splitting the program at the right place, we can not only get smaller, easier to write, easier to debug programs, we get remote access for free. And reduce or eliminate the need for threads. Example 4: demand paging the data. If we make each page a separate file, and include the starting sample number in the filename, then we greatly simplify demand paging. It no longer matters if the file format is set up to make paging easy. Which means we can just take the raw bits from the OGD and put them into a file. Which means we only have to parse/convert the data once. Simpler. Faster. Less opportunity for bugs. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
