> What do you mean a walk through of a simple demo app, you mean document
> how the current examples work, i think most are str8 forward but there
> is def no docs for them.
>

What "getting started" docs often do is take a relatively simple
example and walk through what each step is and why you are doing it.
For example, if you look at the flash media server documentation, that
is exactly what they do. They take simple examples and explain what is
being done and why. It gives the writer an ability to explain a little
bit of the system design in a practical easy to understand context.

> I think walk throughs and steps would make a very bulky pdf, as it would
> be nice to include screenshots and code screen blocks, that kinda stuff
> could be generated for html though.
>

I think text and pictures work pretty well in pdf, flash paper as well
as html. Most of the documentation I have ever read has been on paper
which makes pdf & flash paper useful. Personally, I cant sit at a
computer screen and read 10 pages. I always need to print it. I think
a good printable document also reflects a level of professionalism
since most serious products have easily printable documents along with
their html documents.

But again, the formating *really* doesnt matter. The goal is to get
the words and the pictures together, then we can worry about
formatting. I would prefer to initially do this stuff in a word
processor like word or open office where documents are easily shared
for editing. html is really not good for document management and the
editorial process.


>
> Let me know what you mean, im prob talking more about configs, customise
> the configs (reduces the need to know everything about spring especially
> when you only need it or use it in red5, takes out the complexities of
> having to learn spring first to admin red5 properly),

This sounds like a particularly important subject. I dont know spring,
and surely wouldnt want to learn it in order to do red5
administration. If you have some ideas on this and would like to write
something I think it would be great.

 logging,
> customised logging per application / app instance (if i ever manage to
> work out how), custom log appenders :D, impelemnting stream aware
> handlers, implementing stream filename generator (i had to work this one
> out by digging deep into the API)
>

I think anything like this that you want to write would be helpful.
But I do think from a prioritiztion perspective, I would like to get
basic getting started stuff done first so that we can bring more
people easily into the fold.

Regards
Hank

_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org

Reply via email to