|
|
 | | Re: Code Repository
|
| Joel, (...) in (...) The easiest way of implementing this would be to use the Lego-Robotics Wiki. Because it doesn't require an administrator it's easy for anyone to add the code/samples that they want. For NQC you can choose to add your links off: (...) (25 years ago, 16-Sep-99, to lugnet.robotics.rcx.nqc)
| | | | | Re: Code Repository
|
| (...) Or perhaps a more general one sitting atop the others (integrationally or as a launching point). Because even when there's pseudocode for something, the actual implementation in, say, pbFORTH, may differ fundamentally from the implementation (...) (25 years ago, 16-Sep-99, to lugnet.robotics, lugnet.robotics.rcx.nqc, lugnet.admin.general)
| | | | | RE: Code Repository
|
| Todd: Nice work on the sample page, very easy to use and browse. I would find this format very useful. Jeff Jeffrey Hazen jeffrey.hazen@northmill.net (25 years ago, 16-Sep-99, to lugnet.robotics, lugnet.robotics.rcx.nqc)
| | | | | Re: Code Repository
|
| (...) Since many algorithms apply across languages, what about a single repository for all code? (How about lugnet.robotics.rcx.code?) True, it would increase the noise-to-signal ratio for many, but it would Keep It Simple. Also, I favor follow-ups (...) (25 years ago, 16-Sep-99, to lugnet.robotics, lugnet.robotics.rcx.nqc, lugnet.admin.general)
| | | | | Re: Code Repository
|
| (...) Since many algorithms apply across languages, what about a single repository for all code? (How about lugnet.robotics.rcx.code?) True, it would increase the noise-to-signal ratio for many, but it would Keep It Simple. Also, I favor follow-ups (...) (25 years ago, 16-Sep-99, to lugnet.robotics, lugnet.robotics.rcx.nqc, lugnet.admin.general)
|
|
