LinuxMCE Developer's Guide

[Ender]

Hi guys,

I've started a Developer's Guide for LinuxMCE, but it's document (see attachment) and I don't have to time to create wiki pages for it. I've started one here http://wiki.linuxmce.org/index.php/Developers_Guide. Can anyone help me with this?

Regards,
Ender

[Hagen]

I am on it.
Just a quick question, you have just pasted the contents straight in and want a 'facelift' only?

[Ender]

I guess we need to add the pictures from document and to format the page to have a summary and header.

Thanks.

[Hagen]

yup, a 'facelift' 
I'm on it

[Hagen]

Done a bit now, hope it helps some.
I don't know when I will be able to continue, perhaps later this evening.
Please comment on the layout as I had to make some concessions due to the limited Wiki formating.

Also I could not get the pictures to show either, the syntax is correct (according to the Wiki 'how to'), will look further into that as well.

[danielk]

Cool! 

[Ender]

I think Wiki doesn't link png's, it doesn't recognize them as pictures. Maybe we should try jpeg's ?

[Ender]

We need few new lines between command names (search for 'Keyboard input'). 

[Ender]

Yeap, adding it as a jpeg did the job 

[Hagen]

Yeap, adding it as a jpeg did the job 

Quite funny that the 'how to' uses png...
in the words of Homer: 'Doh!'

I'll switch to jpg for them all now

[Hagen]

We need few new lines between command names (search for 'Keyboard input'). 

Yes, looks like the '-' you used in the original tells wiki to continue on the above line, sort of 'reverse line break'

[Matthew]

That is an excellent resource, thank you!

I like the idea of the entire guide being rooted in a single page that specifies all of the architectural blocks (and messaging/calls between them) in summary. With the summary in a named heading, telling the name, description, and source code filespecs & DB tablenames / config filespecs, linked to another page detailing that component programming notes, like data format and other lower level detals. Like for example its link in a chain of code paths in a given use case. Then we can link pages in the main wiki that are consumer user documentation to their developer's guide summary section on the main page, clickable to more detailed info on its own page.

It would also be very valuable for the programmer's guide subpages each to specify which version of LMCE and the component is being documented. Including those version numbers in the page editor's summary field when updating it for a new version will let later readers just find their old version's docs (if it exists) by looking at the page's history tab.

Thanks again for kicking this off! I encourage everyone who can to at least add source code filespecs and DB tablenames / config filespecs to any section they know is relevant.

[dopey]

I echo Mathew's comments, but I'd like to also add that everyone posting in the forum should read that page (unless you're already a guru)! It made for enlightening read. Although I understood how DCERouter worked at a high level, this summarizes a lot of the details very well.

Thank you!