RE: Architecting the Doc Solution

2006-01-15 Thread Scott Kane
> Being a newbie but having a development background with lower > level languages, I agree -completely-. It would be a great > bonus having at least some sort of crossover docs like c++ -> > Rev, from a coding point of view, its just that the syntax > and the way you think about everything is

RE: Architecting the Doc Solution

2006-01-15 Thread Gorton, Stephen (Oxygen)
Being a newbie but having a development background with lower level languages, I agree -completely-. It would be a great bonus having at least some sort of crossover docs like c++ -> Rev, from a coding point of view, its just that the syntax and the way you think about everything is greatly differ

RE: Architecting the Doc Solution

2006-01-15 Thread Scott Kane
Mark, > I think you are right, Judy. These things ought to come out-of-the- > box, as well. Rev resources are plentiful, but newbies aren't going > to be able to make sense of much of what is available. I agree. I love Rev. But it took me quite a while to come to grips with it. Compared t

Re: Architecting the Doc Solution

2006-01-15 Thread Mark Swindell
I think you are right, Judy. These things ought to come out-of-the- box, as well. Rev resources are plentiful, but newbies aren't going to be able to make sense of much of what is available. It strikes me that one large searchable/navigable stack comprised of all of the scripting conferenc

Re: Architecting the Doc Solution

2006-01-15 Thread Marielle Lange
(For some reason, I cannot post on revdocs I just posted a test message moments ago. Seems to work well. Feel free to contact me offlist to determine the source of the problem. Thanks for that...The problem was due to an email of mine that has become inactive (my ed.ac.uk one) and yahoo ver

Re: Architecting the Doc Solution

2006-01-15 Thread Judy Perry
Which, of course, really goes back to the Hypercard model of pre-built widgets ala the Buttons and Fields stacks (don't recall their exact names at the moment) that many of us have requested since Day 1. And, while it's wonderful that individuals such as Marielle and others wish to 'fill the gap'

Re: Architecting the Doc Solution

2006-01-15 Thread Richard Gaskin
Marielle Lange wrote: (For some reason, I cannot post on revdocs I just posted a test message moments ago. Seems to work well. Feel free to contact me offlist to determine the source of the problem. which has anyway become inactive, so I put my reply here) Yes, a community is only as act

Re: Architecting the Doc Solution

2006-01-15 Thread Charles Hartman
I really like the "cookbook" model of mutual help at, for example, http://aspn.activestate.com/ASPN/Cookbook/Python In various languages, I've found that after the initial bootstrapping phase (Dan Shafer's book can help people through that), the cookbook approach is very efficient: I

Re: Architecting the Doc Solution

2006-01-15 Thread Sivakatirswami
Marielle: I've been lurking on your initiative for some time as I am indeed in your boat "non-profit-education user" of rev. I fully agree: 1) we should not host the Docs 2) the docs are fine as they are: what are needed are examples! And thus your shared code library site concept is perfe

Re: Architecting the Doc Solution

2006-01-15 Thread Marielle Lange
(For some reason, I cannot post on revdocs, which has anyway become inactive, so I put my reply here) > Am sitting here with Marielle and have been discussing the wiki > strategy we wish to see at least. The aim is to work on this with or > without RunRev support in January. I have registered t