<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">I apologize in advance if this got posted at the top level again (the Yahoo<br>
web mail client doesn't play well with the list...)<br><br>Now to the point.... It's true that binary scripts can't be reasonable<br>
distributed as I done until now with transKode, which is why, as<br>
I've said, I won't be doing it anymore. But that's also why I suggested<br>
distributing
it directly with Amarok. All the problems attributed here<br>
to
binary scripts automatically go away in that scenario.<br>
Also, transKode depends solely on
TagLib and Qt/KDELibs, so no<br>
additional dependencies would be required (and
there wouldn't be a<br>
need to compile it as a static binary either as someone suggested). I<br>
don't think there's a problem with binary scripts per se, just with their<br>
distribution. Regardless,
there are at least 3 possible choices in dealing<br>
with this issue:<br>1) Include transKode script more or less as it is with Amarok (once<br>
ported to Qt/KDE 4)<br>2) Port transKode to Ruby or Python (and maybe include it with<br>
Amarok)<br>3) Make transcoding part of Amarok itself.<br>If
I'm not alone in thinking Amarok should ship a default transcoding<br>
script, then the first option has the obvious advantage of being the one<br>
that requires less work. I think the non trivial effort of porting it to Ruby<br>
or Python only begins to make sense if the intention continues to be not<br>
to provide a default script; in which case I'd like to hear the reason for
it.<br>
I seriously doubt I'll be porting transKode to Ruby or Python myself<br>
(though if anyone else want to do it, then fine by me). The language<br>
port itself is annoying enough, but it's not the only problem: 1) It will add<br>
more
dependencies: QtRuby and Korundum for Ruby or PyQt and<br>
PyKDE for Python. It may be perfectly acceptable for a transcoding<br>
script to be "just" a Qt app, but transKode is not just a script and<br>
looking at the "bigger picture" it is and will remain a KDE app.<br>
Some of the GUI aspects can be modified to be Qt only (at least for<br>
the script), but some parts in the core will still depend on KDELibs<br>
(for example, the current worker threads and jobs will be ported to<br>
Threadweaver) 2) While I prefer Ruby over Python, threads support is<br>
lame in the first, so Python might actually be the only reasonable language<br>
choice. That's not an terrible problem as some people surely prefer<br>
Python over Ruby... just not me. 3) Porting will most likely carry other<br>
problems as
well. For instance, most encoders dialogs are currently Qt<br>
Designer dialogs (XML files), code generated at compile time and <br>
subclassed, I don't think QtRuby nor PyQt can handle this. Also, I'm<br>
not sure how internationalization will work in this scheme (though this is<br>
probably a non-issue).<br>Now, there's still the third option... both Mark and Ian have expressed<br>
their doubts about
whether the transcoding aspect should be handled by<br>
a script at all.
Given that, don't you guys think it's reasonable to have<br>
some sort of discussion on that topic? Unlike with the 2nd choice I listed,<br>
I might actually be willing to cooperate with that.<br><br>Sergio.<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Mensaje original ----<br>De: Miguel Angel Alvarez <maacruz@gmail.com><br>Para: Amarok Mailing List <amarok@kde.org><br>Enviado: sábado 1 de marzo de 2008, 20:44:30<br>Asunto: Re: transKode<br><br>El
Sábado
01
Marzo
2008,
Colin
Guthrie
escribió:<br>>
Miguel
Angel
Alvarez
wrote:<br>>
>
El
Miércoles
27
Febrero
2008,
Mark
Kretschmann
escribió:<br>>
>>
On
2/27/08,
Ian
Monroe
<<a ymailto="mailto:ian@monroe.nu" href="mailto:ian@monroe.nu">ian@monroe.nu</a>>
wrote:<br>>
>>>
On
Tue,
Feb
26,
2008
at
2:57
PM,
Sergio
Pistone<br>>
>>><br>>
>>>
<<a ymailto="mailto:sergio_pistone@yahoo.com.ar" href="mailto:sergio_pistone@yahoo.com.ar">sergio_pistone@yahoo.com.ar</a>>
wrote:<br>>
>>>
>
Hi,
my
name
is
Sergio
Pistone,
and
I'm
the
author
of
transKode,
one<br>>
>>>
>
of
the
scripts
that
can
be
used
to
transcode
file
to
audio
devices<br>>
>>>
>
(at
least
in
the
1.4.x
branch,
I
don't
know
if
things
will
work
the<br>>
>>>
>
same
way
for
the
2.x
release).<br>>
>>><br>>
>>>
Really
it
shouldn't
be
your
job
to
package
it.
I
agree
with
you
that<br>>
>>>
you
shouldn't
make
binaries
of
it.
Thats
the
distros
job.
We
could<br>>
>>>
help
you
get
in
contact
with
them.<br>>
>><br>>
>>
It
being
a
binary
is
really
the
main
problem.
Back
in
the
day
when
I<br>>
><br>>
>
No,
it
isn't.
It
simply
should
be
a
static
binary,
and
that's
all.<br>><br>>
For
what
arch?
i586,
i686,
x86_64,
MMX
extensions,
CMOV
support, <br>For
those
just
one
binary
fits
all<br>>
PPC, <br>>
Sparc,
ARM,
Windows
EXE,
OSX
binary
etc?<br>For
those
one
binary
for
arch,
evidently<br>><br>>
Binaries
are
evil
when
thinking
about
this
kind
of
stuff.
It's
all
well<br>>
and
good
when
you
live
in
a
windows
32
bit
bubble
but
in
the
real
world<br>>
where
people
often
run
linux
(and
thus
Amarok)
on
their
toasters
and<br>>
dead
badgers
then
binaries
can
and,
as
is
clearly
evident,
do
cause<br>>
headaches.<br>I'm
not
saying
that
binaries
do
not
cause
headaches,
but
they
are
not
so
evil. <br>Even
script
languages
can
cause
quite
a
headache
(just
think
about
language <br>versions,
modules,
etc).
Even
using
just
bare
python,
same
release,
I
can't <br>run
the
same
script
on
linux
and
win.<br>But....
why
I'm
defending
binaries?
Just
because
on
some
ocassions
they
are <br>the
only
option
to
do
something
in
a
reasonable
time
frame.<br><br>><br>>
_______________________________________________<br>>
Amarok
mailing
list<br>>
<a ymailto="mailto:Amarok@kde.org" href="mailto:Amarok@kde.org">Amarok@kde.org</a><br>>
<a href="https://mail.kde.org/mailman/listinfo/amarok" target="_blank">https://mail.kde.org/mailman/listinfo/amarok</a><br><br><br><br>-- <br>Don't
see
the
world
through
a
window,
be
open{source}minded,
and
be
free
:-)<br>_______________________________________________<br>Amarok
mailing
list<br><a ymailto="mailto:Amarok@kde.org" href="mailto:Amarok@kde.org">Amarok@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/amarok" target="_blank">https://mail.kde.org/mailman/listinfo/amarok</a><br></div><br></div></div><br>
<hr size=1><br><font face="Verdana" size="-2">Tarjeta de crédito Yahoo! de Banco Supervielle.
Solicitá tu nueva Tarjeta de crédito. De tu PC directo a tu casa. <br> Visitá www.tuprimeratarjeta.com.ar</font></body></html>