Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

Before we start getting tons of sample code posted to the onelist file server, I was thinking we (or netmedia) should have an organized structure for file locations. Right now, there is a BX24 and a BX1 folder. This is good, but we need more. What about files that work on both? Do we upload it twice, once to each folder? There should be some organization in the BX24 and BX1 folders. Some subfolders like, Examples, Modules, application specific (like the boebot code), etc. I'm not saying that we need to do what I say above, they are just ideas to get started. I just don't want to go there 6 months now and have to browse through some huge list of files, it would be much faster if they were broken up into subfolders or what not. What does everyone else think? I made a directory awhile ago when I first found the file server. But if we come up with some structure we like, we should submit it to netmedia and let them make the directories, that way no one but netmedia can delete or rename the folders. -C http://www.theonespot.com

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )