Re: [xine-user] playlists how-to

[Daniel Caujolle-B. <seg...@cl...>]

Hi Michael,

Michael Roitzsch wrote:
> Hi Daniel,
> 
> 
>>>To Daniel:
>>>I think "select" is not very intuitive, since you already select
>>>the MRL by clicking once on it. A more logical button label for me
>>>would be "add".
>>
>>	Okay, you know, me and english many^H^H^H^Hsometimes... ;-)
> 
> 
> I guess my French is equally .. problematic.
> Thanks for the change.
> 
> 
>>>Besides that, when I click this button (no matter how I call
>>>it), the MRL gets added to playlist but at the same time, xine
>>>starts playing it. This happens only in smart mode, but I think
>>>it's not very smart. When the user hits select/add, he clearly
>>>wants to create a playlist, so immediate playback is quite
>>>confusing. Your opinion?
>>
>>	errr, do you want it really ?? ;-)
>>	Well, i don't know. So, what should we do here (lemme know, i will
>>made changes tonight).
> 
> 
> Just to make sure you understand me:
> * I have smart mode on.
> * I want to create a playlist.
> * I open playlist editor.
> * I click "Add" in playlist editor. MRL browser opens.
> * I select a file in MRL browser.
> * I click "Add" in MRL browser.
> -> The file is added to the playlist. But at the same time, the file
>    also starts to play. I don't want that, because my playlist is not
>    finished.

	Okay, i see. I will made the needed changes. But, if the mrl browser is 
directly called (using the dedicated button in main panel, or using 
shortcur), the old behavior is kept (mean: if playback isn't running, it 
will start then).

> 
> 
>>>Another thing: Is the button order in the MRL browser controlled by
>>>xine-ui or by the skin? If this is xine-ui's job, could you swap
>>>the two buttons, so that the ">" (play) button is the first. This
>>>order would make it more clear, that doubleclicking means play,
>>>because the doubleclick-action should always be linked to a
>>>prominent button.
>>
>>	xine-ui it totally dependent of skin, xitk is an empty toolkit in
>>fact. So, you have to made some changes in the concerned skin's
>>skinconfig file.
> 
> 
> Understood. I updated some skins in cvs. What else do I have to do to 
> ensure that the skins downloaded from the homepage or by xine-ui are 
> the ones in cvs skins module?

	Yeah, you have to build new skin tarballs (using 'make dist'), then 
update the two cvs branch of our site, then update it 'a la mano'... 
Take it easy, i'm doing that right now ;-)

Cheers.
-- 
73's de Daniel, F1RMB.

              -=- Daniel Caujolle-Bert -=- seg...@cl... -=-
                        -=- f1...@f1... (AMPR NET) -=-