Williams, Chris (Marlboro) wrote:
That's not developer documentation. Do you not know what developer
documentation is?
I'm talking about everything from high level flow charts down to
detailed annotated source code listings.
Descriptions of functions, what they do and why. Files, modules, data
types, etc. Style guides, APIs and library docs. Development history,
authors and contacts.
All presented to a new developer in a persistent, organized manner.
Well, from my experience as a professional software developer (some
years ago) I can tell you that the only documentation that is always
accurate, up-to-date, complete, structured and 'readable', is the source
code. All other documentation is either not-existing, outdated,
incomplete or otherwise not that useful.
For what its worth and as far as I know (vnc 3.7 knowledge), the Xvnc
server is a combination of an X11 server (Xfree or Xorg or such, I
donnot know the current status) and a vnc display driver. For the X11
part, expect only the required parts to be used. For the documentation
on that part, see there.
For the vnc part of the implementation, I've sent some example code that
puts up a counter or a clock in a vnc-session. That was part of the old
vnc documentation, if someone is interested and it cannot be found on a
webpage, I'm happy to send it.
Something like this:
http://developer.mozilla.org/en/docs/Code_snippets:Tabbed_browser
Or this:
http://www.x.org/wiki/PciReworkProposal
Or this:
http://library.gnome.org/devel/libgnome/stable/libgnome-gnome-program.ht
ml
This is all basic documentation for new developers getting involved in
existing projects. Telling someone to read raw source files at the mere
mention of development assistance is tantamount to summary dismissal.
-Chris
_______________________________________________
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
