Hi Rafael,

On Wed, Aug 25, 2010 at 12:00 PM, rafael <[email protected]> wrote:
>    I recognize the developer's effort to organize the documentation in
> the site (api reference, cookbock, examples, etc). But I think it could
> be more efficient if we could organize a wiki or something similar,
> where non developers could also contribute (I wan't to help  !! :) )

This is a reasonable idea. However, it didn't work for us in the past.
We used to do the doc on a wiki, but had only a few user
contributions. Moreover, a wiki alone is not ideal: it is nice to have
local doc corresponding to the installed version of liquidsoap, which
requires some export to a static formal and probably some versioning.
We dealt with most of that with wakka wiki for a while, but eventually
got bored of adminstrating it (updates, spam) and found out that
putting the doc in SVN was a simple solution to all those problems.
It's probably not an ideal solution either, but this is what we have
for now, and I'd rather try to work with it rather than working on
another change.

Today, we certainly have a larger community -- we've started to see
some users helping each other on the mailing list. That being said I
don't think so many users are ready to contribute and maintain quality
documentation, so it should be possible to add motivated people to the
savonet project on sourceforge so they can directly edit the doc there
(it's actually in wiki format).

Long story short: I'm really happy that you want to help, and I'll
give you write permission on our SVN as soon as you tell me your
sourceforge.net login.

I actually had in mind to make such a call when releasing 1.0 beta
(really soon!)

>    Sometimes it is hard to find examples or answer to a specific
> question in the mailing lists ( I can't find how to search in them, had
> to use google). This probably leads to the same question being over and
> over made.. I like documentation in a single page, with a how to
> approach,  because this prevents having many tabs opened (maybe another
> one for api reference)...

I have just started a FAQ (although it's not been uploaded to the
website yet) to avoid this (very real) problem. However, it is
difficult to organize, and there is some redundancy with the cookbook
that I need to figure out. I don't think that everything could be on a
single page: even the FAQ and cookbook could not be reasonably merged,
unless we also develop tools for easier browsing/searching.

I don't meant to be too negative here. The first important thing is to
produce helpful doc, we'll see next if it's organized correctly.

>    And now my question. Is there a possibility for a album_sensitivity
> parameter (do we say parameter in funct languages?) for the switch, as
> we have track sensitivity. I have some albuns that I wan't to be played
> entirely and then after it is finished the switch would take place. I
> know I can probably do this with fallback, but for a complex behaviour
> the code can grow a lot...

If I understand correctly you want to play an album as a single track.
For example, you have a playlist, played in order, that contains
several albums, and you want it to be only interrupted (for ads or
whatever) between albums. One way to merge tracks is to use cross()
with a sequence() transition, but cross() doesn't see metadata. You
could use a reference to store metadata, but the easiest solution
(although less efficient) is to use smartcross:

s = playlist("file.txt")
def transition(_,_,m1,m2,s1,s2)
  same_album = (m1["album"]==m2["album"])
  sequence(merge=same_album,[s1,s2])
end
smart_cross(transition,s)

Hope that helps,
-- 
David

------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to