On 3/30/07, <b class="gmail_sendername">Barth Netterfield</b> <<a href="mailto:netterfield@astro.utoronto.ca">netterfield@astro.utoronto.ca</a>> wrote:<div><span class="gmail_quote"></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Working With Views -> View Object Types -> [all]<br>Working With Views -> View Object Types -> Plots -> auto labels:<br>Working With Views -> View Object Types -> Plots-> Range tab:</blockquote><div>
<br>Ok, thanks for comments. Will do.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Ch 8 Adding and Removing Plugins:<br>Built-in plugins -> Butterworth filters
</blockquote><div><br>I didn't touch anything to do with Plugins. I haven't looked at the new Plugin setup yet, and when I originally started doing docs I think that you said Adam would be interested in changing the documentation for them himself.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Indirect files: description seems wrongish.<br> These are files that point to data sources. Yes, they can use KIO, but
<br>anywhere we use a file name, we can use KIO - that is not the point. These<br>were actually invented to tell kst the name of the current file being written<br>to by an experiment. For example, for BLAST, the data loggers would write on
<br>the local machine to files whose cryptic name was created by from the time of<br>creation (so 112312312.d or some such...). In addition the data loggers<br>created these files:<br> defile.cur: pointed to the current line-of-site data file being written to
<br> tdrss.cur: pointed to the current tdrss sattelite data file being written to<br> slowDL.cur: pointed to the current slow data file being written to.<br>So if you wanted to plot GYRO1 data from the LOS data file currently being
<br>written to, you would type "kst -y GYRO1 -n 1000 defile.cur". The .kst files<br>can refer to defile.cur. Then, running a kst file later always refers to<br>whatever the current data file is.</blockquote><div>
<br>Hmm... Ok. My experience with the Indirect data source has only been that it is the datasource which claims things from http, etc. I will look at the code for it more closely and try to come up with a better description.
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Appendix A. Command Line Usage and Examples<br> My email address is wrong.
</blockquote><div><br>I didn't touch this stuff either-- has anything else in the command line changed? </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Appendix B. Creating Additional Plugins<br> Does this describe the new plugin system, or the old (depricated) plugin<br>system. (I think old - can someone verify).<br> If so, could we describe the new one instead?
<br><br>Installing Kst from Source -> requirements<br> I think we require KDE 3.4 and qt 3.3. George?</blockquote><div><br>I'll wait for George to respond. There's a thread on the list about this, where
3.3/3.3 is touted, but Andrew says at the end that it's actually 3.4/3.3.<br><br>Duncan.<br></div></div><br>