Hi,<br><br>Its a quite embarrassing to admit that i could completed that work, not even able to submit what was done to FS trunk due to my own stupidity. Actually, we are having major power crisis in the country for last 1 years and most of power cuts are so long that even best UPS systems can't ensure 24/7 up time for our servers. About 3 months ago the development server i was working on for FS Docs was hit by this problem and its hard disk crashed, destroying all my hard work on FS Docs and mod_msn. It was my mistake that i didn't arrange for proper backup for my work due to shortage of resources and didn't inform the FS developers community about the loss.<br>
<br>I want to restart this work but don't want to take the lead on this due to issues described above. If you can arrange a common server for FS docs development then i can submit my work to you which you can test on this dev server before committing it to FS Trunk.<br>
<br>Second option is that i work on a single file, test it on my laptop and immediately submit it to FS trunk. But this could cause problem for end users (developers using FS doxygen docs) as many hyper links connected to undocumented files won't work till their docs are done and uploaded.<br>
<br>We also need to decide on,<br><br>1. What Doxygen version to use? i use Archlinux which has the latest 1.6.x version, I can downgrade it to 1.4.x.<br>2. What format of documentation to adopt? I think currently we have HTML format only, but Doxygen can also generate PDF and CHM formats.<br>
<br>Thank you.<br><br><br><div class="gmail_quote">On Mon, Feb 22, 2010 at 9:00 AM, Yossi Neiman <span dir="ltr"><<a href="mailto:freeswitch@cartissolutions.com">freeswitch@cartissolutions.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I am not sure how many folks make use of the Doxygen documentation. I<br>
know I do all the time. I find that it provides a nice conceptual view<br>
of FreeSWITCH's API, which can make it very easy to find the functions<br>
and data types needed for writing modules for FreeSWITCH.<br>
<br>
A person by the name of Mohammad Shahzad (apologies if I misspelled it)<br>
started to do a lot of work on revamping the Doxygen configuration for<br>
FreeSWITCH a few months back. The problem with the work that he did was<br>
that he used Doxygen 1.6.x specific configuration parameters that are<br>
not understood by the Doxygen 1.4.x tree (which is what we currently use<br>
in FreeSWITCH) or even the 1.5.x tree which is what is in Slackware. In<br>
my discussions with Michael Collins we have decided that it might not<br>
hurt to go ahead and move the Doxygen version forward to match the 1.6.x<br>
tree.<br>
<br>
We are looking for somebody who has interest in working with the Doxygen<br>
configuration to continue the work that Mohammad had started and to help<br>
the project out. If you are such a person, please contact me off-list<br>
and I can provide further information.<br>
<br>
Thanks!<br>
<br>
Yossi Neiman<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Muhammad Shahzad<br>-----------------------------------<br>CISCO Rich Media Communication Specialist (CRMCS)<br>CISCO Certified Network Associate (CCNA)<br>Cell: +92 334 422 40 88<br>
MSN: <a href="mailto:shari_786pk@hotmail.com">shari_786pk@hotmail.com</a><br>Email: <a href="mailto:shaheryarkh@googlemail.com">shaheryarkh@googlemail.com</a><br>