Re: [OpenSIPS-Devel] [opensips] Documentation updates (#440)

2015-03-25 Thread Rob Gagnon
I've posted the results of building the documentation with this .css file to http://opensips.telepointglobal.com/html To be thorough, I also re-built the README files and put those here: http://opensips.telepointglobal.com/readme --- Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] Documentation updates (#440)

2015-03-24 Thread Liviu Chircu
First of all, thank you for the initiative! I completely agree that the module doc .css needs some fine tuning! However, drastical changes usually have these kind of results: either a big *WoW!* or a *is it really better?!*. In my opinion, some of your ideas are good, others are not. While

Re: [OpenSIPS-Devel] [opensips] Documentation updates (#440)

2015-03-24 Thread Rob Gagnon
For this I probably could setup a temporary public webserver so it would be easier for commenters to see how things would look for their favorite modules, which might be easier overall to be able to see the changes without having to figure out how to build the HTML. What do you think? ---

Re: [OpenSIPS-Devel] [opensips] Documentation updates (#440)

2015-03-24 Thread Rob Gagnon
Reasons for the changes that you've marked as bad: Modern HTML should adjust to a user's monitor. Some people are using tablets, some a phone, others still have tiny monitors, while I for example have one that is 22. Hence the restriction on the width of the page was changed from a fixed

[OpenSIPS-Devel] [opensips] Documentation updates (#440)

2015-03-23 Thread Rob Gagnon
Modernize the CSS for documentation as well as match the style of main opensips.org website Update rtpproxy documentation to replace has_sdp() examples with has_body(application/sdp) Update rtpengine documentation to elaborate on where to use rtpengine_delete() You can view, comment on, or