Hi,
rv-split is now mostly merged. As far as I know, puzzles is working on
a patch to change the the medialib_add_entry_args function to take a
xmmsv_t dict instead of char** array of strings (and drop the numargs
int, as it's no longer needed with a dict). At the moment, that
function still encod
At Tue, 09 Dec 2008 14:30:09 +0100, Anders Waldenborg wrote:
> Maybe the cleanest would be if "URL" would just be a dict:
>
> {
># used to find transport xform
>'type': 'file',
># this is just an aribitary argument that the file and
># gvfs plugins use, the type of the value is xm
Thomas Frauendorfer wrote:
Hi,
rv-split is now mostly merged. As far as I know, puzzles is working on
a patch to change the the medialib_add_entry_args function to take a
xmmsv_t dict instead of char** array of strings (and drop the numargs
int, as it's no longer needed with a dict). At the mome
Sébastien Cevey wrote:
At Tue, 09 Dec 2008 14:30:09 +0100, Anders Waldenborg wrote:
Maybe the cleanest would be if "URL" would just be a dict:
{
# used to find transport xform
'type': 'file',
# this is just an aribitary argument that the file and
# gvfs plugins use, the type of the
On Tue, Dec 9, 2008 at 3:12 PM, Sébastien Cevey <[EMAIL PROTECTED]> wrote:
At Tue, 09 Dec 2008 14:30:09 +0100, Anders Waldenborg wrote:
>The main reason why we need to mess with encoding strings is that paths on
>disk doesn't have a specified encoding. File paths are >just arrays of bytes
>(whe
At Tue, 09 Dec 2008 13:02:49 -0500,
> >> {
> >># used to find transport xform
> >>'type': 'file',
> >># this is just an aribitary argument that the file and
> >># gvfs plugins use, the type of the value is xmmsv_bin
> >>'path': b'/media/mp3/x.mp3',
> >># any arg can be pass
Sébastien Cevey wrote:
At Tue, 09 Dec 2008 13:02:49 -0500,
The cost to the user? She can't type xmms2 add
"http://example.com/?type=foo&path=bar";. But why... WHY would anyone
want to do that anyway?
Nobody "types" URLs. You get and copy them from elsewhere (email,
website, etc). Whatever we d
On Wed, Dec 10, 2008 at 5:18 AM, Daniel Chokola <[EMAIL PROTECTED]> wrote:
> Sébastien Cevey wrote:
>>
>> At Tue, 09 Dec 2008 13:02:49 -0500,
>>>
>>> The cost to the user? She can't type xmms2 add
>>> "http://example.com/?type=foo&path=bar";. But why... WHY would anyone
>>> want to do that anyway?
At Wed, 10 Dec 2008 12:04:11 +0100, Anders Waldenborg wrote:
> > How do you represent http://example.com/?type=foo&path=bar ? ;-P
>
> {
> 'type': 'http',
> 'path': b'http://example.com/?type=foo&path=bar',
> }
>
> which would make sense for cases like this:
>
> {
> 'type': 'http',
>
Thomas Frauendorfer wrote:
The main reason why we need to mess with encoding strings is that
paths on disk doesn't have a specified encoding. File paths are
>just arrays of bytes (where NUL and / have a special meaning). On
the other hand strings stored in sqlite (and now xmmsv_t) needs to
be UTF
Sébastien Cevey wrote:
How do you represent http://example.com/?type=foo&path=bar ? ;-P
{
'type': 'http',
'path': b'http://example.com/?type=foo&path=bar',
}
which would make sense for cases like this:
{
'type': 'http',
'path': b'http://c64.org/get-sid?id=1234&user=kbrinkmann',
Sébastien Cevey wrote:
Right, it was just me misunderstanding the whole args business, so
please ignore me on the topic.
No I think you question was valid. It displays a subtle difference between:
{ 'type': 'file',
'path': b'/path/to/file.mp3'}
and:
{ 'type': 'http',
'path': b'http://exa
Anders Waldenborg wrote:
Sébastien Cevey wrote:
Right, it was just me misunderstanding the whole args business, so
please ignore me on the topic.
No I think you question was valid. It displays a subtle difference between:
{ 'type': 'file',
'path': b'/path/to/file.mp3'}
and:
{ 'type': 'htt
On Sun, Dec 21, 2008 at 8:34 AM, Daniel Chokola wrote:
> */
> /* Client can give a prompt to the user here:
> "Add file to playlist? path: "
> "Add url to playlist? url: SSL>"
This is a great idea, it should go into the XMMS2 Human Interface Guidelines! ;)
--
Daniel Svensson
--
___
Daniel Chokola wrote:
Samba, for example, also has no known encoding.
Got a reference on that?
anders
--
___
Xmms2-devel mailing list
Xmms2-devel@lists.xmms.se
http://lists.xmms.se/cgi-bin/mailman/listinfo/xmms2-devel
Anders Waldenborg wrote:
Daniel Chokola wrote:
Samba, for example, also has no known encoding.
Got a reference on that?
http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/unicode.html
--
Dan Chokola
--
___
Xmms2-devel mailing list
Xmms2-d
Daniel Chokola wrote:
Anders Waldenborg wrote:
Daniel Chokola wrote:
Samba, for example, also has no known encoding.
Got a reference on that?
http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/unicode.html
libsmbclient.h also has a lot in the comments about url-encoding.
--
Dan C
Thomas Frauendorfer wrote:
On Wed, Dec 10, 2008 at 5:18 AM, Daniel Chokola <[EMAIL PROTECTED]> wrote:
Sébastien Cevey wrote:
At Tue, 09 Dec 2008 13:02:49 -0500,
The cost to the user? She can't type xmms2 add
"http://example.com/?type=foo&path=bar";. But why... WHY would anyone
want to do that
Daniel Chokola wrote:
BTW, I would ask where you've ever seen a meaningful URL with arguments
from the internet. I haven't heard of streaming SIDs yet. ;)
There is a very meaningful use case of args to HTTP URLs: passing a cookie.
{
'type': 'http',
'path': b'http://example.com/getmpg.py?id
19 matches
Mail list logo
