<div dir="ltr"><br><br><div class="gmail_quote">On Tue, Sep 30, 2008 at 2:40 PM, Josiah Bryan <span dir="ltr"><<a href="mailto:jbryan@productiveconcepts.com">jbryan@productiveconcepts.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;">
<div class="Ih2E3d">Tzafrir Cohen wrote:<br>
> On Tue, Sep 30, 2008 at 01:35:00PM -0400, Josiah Bryan wrote:<br>
>> Tzafrir Cohen wrote:<br>
>>> On Tue, Sep 30, 2008 at 11:32:41AM -0400, Josiah Bryan wrote:<br>
>>>> Hey All -<br>
>>>><br>
>>>> Link to the index page:<br>
>>>><br>
>>>> <a href="http://www.voip-info.org/wiki/view/Asterisk+Documentation" target="_blank">http://www.voip-info.org/wiki/view/Asterisk+Documentation</a><br>
>>>><br>
>>> Why not link to the SVN instead?<br>
>> I considered that as well. My thoughts:<br>
>><br>
>> 1) Ungoogleabelness (if thats a word :-) - since google already ranks<br>
>> <a href="http://voip-info.org" target="_blank">voip-info.org</a> high on search for asterisk related content, I thought the<br>
>> docs should be where the users are, not vis-a-versa.<br>
>><br>
>> 2) Formatability - the docs are plain text in subversion, whereas<br>
>> putting the in the wiki offers the possibility for formatting and<br>
>> auto-linking as the algorithm presents itself.<br>
><br>
> Do you intend to add that formatting in your script? They can't be<br>
> changed manually.<br>
<br>
</div>The script design supports plugin formatting as it stands. E.g. I can<br>
insert any formatting algorithm if anyone has any suggestions. Right<br>
now, the formatter script just does:<br>
<br>
#!/usr/bin/perl<br>
use strict;<br>
<br>
my $file = $ARGV[0];<br>
<br>
print "~pp~\n";<br>
print `cat $file`;<br>
print "~/pp~\n";<br>
<br>
Any formatting can be added as desired - this was just a quick way to<br>
get the content online.<br>
<div class="Ih2E3d"><br>
<br>
>> 2) UI similarity - linking to the file on svn, for example:<br>
>><br>
>> <a href="http://svn.digium.com/view/asterisk/branches/1.6.0/doc/callfiles.txt?view=co" target="_blank">http://svn.digium.com/view/asterisk/branches/1.6.0/doc/callfiles.txt?view=co</a><br>
>><br>
>> Brings just the plain text view, whereas putting it in the wiki offers<br>
>> the same UI as the rest of the site.<br>
><br>
> <a href="http://svn.digium.com/svn/asterisk/branches/1.6.0/doc/callfiles.txt" target="_blank">http://svn.digium.com/svn/asterisk/branches/1.6.0/doc/callfiles.txt</a><br>
><br>
> Looks better.<br>
<br>
</div>I agree - if you're looking for the change log. However, I (if I were a<br>
first-time asterisk user) probably don't care for the change-log-esque<br>
view, I just want to read the text for myself.<br>
<br>
However, I'd be happy to add links to the svn at the bottom of the page<br>
if that is desired. Thoughts?<br>
<div class="Ih2E3d"><br>
Cheers!<br>
-josiah<br>
<br>
--<br>
Josiah Bryan<br>
IT Manager<br>
Productive Concepts, Inc.<br>
<a href="mailto:jbryan@productiveconcepts.com">jbryan@productiveconcepts.com</a><br>
(765) 964-6009, ext. 224<br>
<br>
</div></blockquote></div><br>I think there should be links for changelogs and links for every different language, so script that up ASAP :-P<br><br>I only bother with the changelog to see why something may be broken or if an upgrade might fix something. I don't think too many people care about it on the wiki anyways.<br clear="all">
<br>-- <br>Thanks,<br>Steve Totaro<br>1.888.777.1888<br>1.240.938.1212 (cell)<br><br>
</div>