Hi Romain,
thanks for this fast implementation!
two things I figured out:
1)
after installing libxml-dom-perl (see 2) I get the following error:
Converting content/video-static.txt to html/video-static.html...
CAML_LD_LIBRARY_PATH=../src:../src/plugins ../src/liquidsoap
--dynamic-plugins-dir ../src/plugins \
--no-pervasives ../scripts/pervasives.liq --list-plugins-xml | \
./reference_to_liqi.pl > content/reference.txt
Can't use string ("__") as an ARRAY ref while "strict refs" in use at
./reference_to_liqi.pl line 98.
make[2]: *** [content/reference.txt] Fehler 9
make[2]: Verlasse Verzeichnis
'/home/milan/radio/savonet.hg/savonet/liquidsoap/doc'
make[1]: *** [doc-install] Fehler 2
make[1]: Verlasse Verzeichnis '/home/milan/radio/savonet.hg/savonet/liquidsoap'
make: *** [install] Fehler 2
2)
documentation cannot be generated if libxml-dom-perl is not installed.
Currently there is no info about this at the summary after configure.
Instead there are following lines. I wish at least a WARN hint to allow grep
for WARNings or ERRORs:
Converting content/video-static.txt to html/video-static.html...
-> You don't seem to have perl XML::DOM module installed.
-> Language reference cannot be generated.
For more convinience there could be a additional status line for doc generation
at end of configure...
BR, Peter
Am 02.10.2011 16:46, schrieb Romain Beauxis:
> 2011/10/1 Peter Retep<[email protected]>:
>> Hi,
> Hi Peter!
>
>> Switching the savonet homepage to "web 2.0" by using jquery's show/hide
>> feature makes the site comfortable to use.
>> Unfortunately deep links using #anchors do not work anymore everywhere .
>>
>> in case you are bored by fixing sound related errors I have some ideas on
>> this:
>>
>> For instance lets take the reference page:
>> http://savonet.sourceforge.net/doc-1.0.0-beta3/reference.html
>>
>> There are sections like "source/output" and elements like "output.file".
>>
>> If one wants to reference one of both items, (as I tried to do in my last
>> mail to Josh)
>> one could do this by using section/element anchors:
>> http://savonet.sourceforge.net/doc-1.0.0-beta3/reference.html#SourceOutput
>> http://savonet.sourceforge.net/doc-1.0.0-beta3/reference.html#output_file
>>
>> For users without javascript it would be helpful
>> - to put a<a name="output_file"> before the links of sections and
>> elements.
>> - to put the link href to this anchor. In this case the link href could be
>> set to #output_file.
>> This enables browsers to jump to the right section/element when loading a
>> page, referenced like above.
>>
>> For users with javascript enabled, following code could be used to
>> show all sections or elements that are addressed in the URLwhen the page
>> gets loaded :
>>
>> $(document).ready(function() {
>> var parts=document.URL.split("#");
>> if (parts.length>1){
>> var id="#"+parts[1];
>> $(id).parent().parent().show();
>> $(id).siblings().show();
>> }
>> });
>>
>> This was working already today for elements, since they provide a id already
>> (like #output_file),
>> It could work even for sections, but sections have no id today (like
>> #SourceOutput).
>>
>> These changes would make the sections and elements linkable with both web
>> 1.0 and 2.0.
>>
>> A more generic and efficient way would be, to provide for both items
>> (sections and elements)
>> - an anchor with the name of the link target
>> - a link targeting this anchor
>> - the content div which contains the id used to show/hide this element.
>>
>> example
>> <li>
>> <!-- provide a section anchor -->
>> <a name="SourceOutput" />
>>
>> <!-- set link target to section anchor -->
>> <a href="#SourceOutput">Source / Output</a>
>>
>> <!-- have an id at the content to show/hide the content -->
>> <ul id="#SourceOutput" class="liq-api-sec" style="display: none;">
>>
>> <li class="liq-api-elem">
>> <!-- provide a anchor -->
>> <a base="output_file" />
>>
>> <!-- move id to content div, set link target to output_file -->
>> <a href="#output_file">output.file</a>
>>
>> <!-- have an id at the content to show/hide the content -->
>> <div id="output_file" class="liq-api-content" style="display: none;">
>> <pre>(?id:string,?append:bool,?dir_perm:int,?fallible:bool,...</pre>
>> ...
>> </div>
>> </li>
>> ...
>> </ul>
>> </li>
>>
>> With help of this changes you could do directly
>> $(id).show();
>> instead of
>> $(id).siblings().show();
>>
>> if id, anchor, and link target contain the same value,
>> you could use the link target (href) to address the content div id, which is
>> to be shown/hidden.
>>
>> anyway, the page works good as it is.
> Thanks for all those suggestions! I have juste commited an
> implementation of it!!
>
> Romain
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
