On Tue, 2007-01-16 at 12:49 +0000, Dieter wrote: > > 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.
Sorry, I hadn't caught that. Yes, that would be wonderful :) > > > Has anyone written any code for this yet? > > First design, then code. I hold that design is overrated -- there's a limit to how much interacting stuff people can hold in their heads. "Do the simplest thing that might possibly work", "You ain't gonna need it" combined with short iterations and code factoring seems to work better for many people. But maybe we don't disagree much, really. It may just be a question of terminology. > 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. Maybe it's better to use the user's colour theme, because if the user is colour blind, he or she might already have fixed the theme for that. > 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. Which is perfectly understandable. It was just an example of a feature I would have had good use for before. > 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. Sure, but my Tektronix 502 is a bit old for those high speeds ;) > 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. I think they tell us the danger of allowing too easy access to the individual colour settings ;) > 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. I think your design is getting ahead of you here. But we'll see. -Peter _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
