Re: Could this be done?
David Gay wrote:
>
> Hi Quark
>
> First of all, the person you mentioned is not a relation to me or in
> my family. I asked around, which was why I did not answer your question
> regarding TinyOS et al. Sorry for the delay.
>
> I agree with your suggestion about a collaborative effort on creating the
> tutorial. Other projects like Win32lib, wxEuphoria, where you have a lot
> of contributors working together have produced stellar results. The only
> reason why I initially did not go for a collaboration was because I was not
> sure if anyone wanted to do a tutorial with me. Tutorials are not as
> exciting as games or IDEs. Even I admit writing a game would be more fun
> than a tutorial.
>
> That does not mean I will not accept help if offered. If anyone had any
> ideas or assistance to offer, please let me know. I haven't even started on
> the text of the tutorial yet, nor do I know what it will look like. However,
> it would be great if I could get platform specific programming concepts and
> newbie primers to all the great Euphoria wrappers out there as a part of
> the tutorial.
>
> However, I promise there will be no remote in this tutorial :P
>
> Regards
>
> David Gay
Hi David,
As to the person I asked you about, I found a David Gay on the web who had been
at Berkeley from about the time you went off to do other things, and he had to do
with TinyOS and NexC, etc. He is at Intel now. But after I posted to you, I did
some more search and finally found his middle initial is E. So scratch that, I
thought.
As to the collaborative effort, I was thinking what a massive job you had in the
past on the DOS-based tutorial, of your own DOS interest (as it has been mine),
the Windows learning-curve, and how the tutorial possibilities have grown, and I
thought you could use some help.
I suppose tutorials can be coherent and "book-like" (simple to complex) or they
can be modules that have a narrow focus and be complete in themselves. If you
choose the former, you will have a big job ahead of you. If the latter, then you
could create the main interface program, set the general pattern, develop a list
of needed modules, and generally oversee things, but rely on other knowledgeable
people to do many of the modules. Ideally, the modules would plug in to the main
program easily, be listed coherently, and adding to the tutorial might be just a
matter of downloading a new module and placing it in the tutorial folder, or
another step might be needed, don't know. Anyway it can be allowed to grow over
time, rather than needing to be complete to be worthwhile.
But, however you decide to do it, if I can help, I will, because I think this is
a very worthwhile project.
--Quark
|
Not Categorized, Please Help
|
|
