Hard to plan until you understand the low level stuff well. Current plan:
1. Implement all required records to get a basic chart done (there's a lot of these). 2. Analyse record structure. 3. Have a first pass at writing a high-level API 4. Refine (refactor) until bored or happy. 5. Implement remaining records for other chart types. 6. Analyse remaining structures. 7. Add new functionality. 8. Refine (refactor) until bored or happy. Andy's plan may be different and since he seems to have more free time than me at the moment any of his plans will most likely trump mine. Regards, Glen Stampoultzis (TriNexus Pty Ltd) +61 3 9753-6850 0402 835 458 ICQ: 62722370 EMail: [EMAIL PROTECTED] > Avik Sengupta wrote: > > >What is the / Is there a .. plan for a high level api to the charting > >subsystem, once the low level records are implemented? > > > > > >-- > >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > > *Not yet* -- We don't yet adequately understand the grammar of the low > level records. > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
