Dan, The problem is that we already have lot of info about Subversion, log4j and Spring. We can provide links to most friendly papers on this but nobody wants to reinvent the bicycle. Where is it. not really required, a simple howto page with steps/ screenshots for different methods, pc, osx , command line is all thats prob needed, i can do this if you like.For Subvesion, there's a great "Version control with SVN":svnbook.red-bean.com I write How2s in my spare time but Red5 documentation always goes first. Why? Because before I started to contribute to Red5 I've spent some time digging code internals which is crazy without a single documentation line :) Thanks God Eclipse has hyperlinks navigation and references search. That's why documentation comes first. At the moment I have 12 How to tips. again where is it. Like i said it would be more beneficial if it was added to a central place like the trac wiki which has nothing at the moment. If someone can give me a login i can start. I planned to add it to documentation later because some of tips are really obvious. Some of them are just re-explainations of how to use power of Spring. No need to explain how spring works, links would be easier. Right now most of questions are related to streaming problems thats an issue with the code itself not because of lack of docs. we have or compilations problems. Man, javac documentation is only 4 or 5 fullscreen Firefox pages. Call me lazy but I think there's a lot of stuff that newcomers have to learn by themselves anyway. true, but it appears there is an obvious gap between who is a java developer and who isnt and setting things up ;) Why should Red5 list become "a school of Java for AS coders"? Not saying there is. There seems however lots of people who are crossing over and asking how to setup red5 not how does java work. If people are asking there is an obvious fault in enough information or they just dont RTFM, i would like to say they just dont RTFM but i havent even seen a central doc yet. We have Ruby, Python, _javascript_, Groovy, BeanShell (via Spring 2 integration) and possibly php (via JSR223 scripting support for Java) support. Go for dynamic and have fun (I'm serious). A php scripting engine would be nice PHP5 preferably, but i dont mind coding in java for the application adaptor anyway, im not really talking about developing the application at all, mostly the setup of red5 itself. The implementation of the dynamic scripting in python, _javascript_, or actionscript would be nice, especially actionscript at it would make migration from FMS fairly an easy process, however ive not started looking into how to use it yet, and then someone will need to work out how the API for each of these work and i guess document that aswell. Its new in trunc, but im unsure if the oflaDemo which has it configured actually uses it yet. I dont have access to the code atm as its on my firewire drive, an indication where this documentation is would be a good start, you keep saying its in the trac svn but i havent seen it personally. I think a compilation of all the current documentation into a book style pdf would go down well for all. I can also help out there as i have a tonne of experience with docbook xml and i use oxygen xml for that purpose. |
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
