<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi!<br>
<br>
As I'm working on a script (actually i use it personally quite heavily
but i haven't released my
plugin yet because there are still some issues i want to address before
letting it loose...) for Amarok at the moment (and i plan to port the
thing to Amarok2 as soon as the dbus-interface is fixed and won't
change any more), I'm following this discussion with alot of interest.<br>
<br>
I started with a Ruby-Script but as i use threads quite heavily and i
had quite alot of trouble with Ruby and multi-threading i moved away
from Ruby and tried a different approach. As i'm not such a big fan of
Python i started to work on something completely new. I created a
really nice object-oriented library for Amarok using Mono. I called it
Monorok ;) At the moment i more or less just included the methods
necessary for my script but well i can always add other methods and
functions (if they sound useful of course ;) ). Using this library i
rebuilt my Ruby script using Monorok (and thus C# and Mono). To start
my script i use a wrapper shell-script that more or less just calls the
mono-binary with the name of my plugin and some other
commandline-arguments my script needs to run. <br>
<br>
So from what i've read in this discussion you are planning to
concentrate on one language with Amarok2? And drop support for
everything else that was possible with Amarok1.x? It would be quite
interesting to know what the plans are, so i can decide how i'm going
to continue with the development of my plugin. At the moment i'm not
using Amarok2 but it would be cool to have at least a partially working
version of my plugin when Amarok2 is released and as this plugin is
quite a monster (plus i have some plans to add some additional
functionality) i guess i should start to work on it, if you really
decide to turn away from the multi-language scripting and concentrate
on one language...<br>
<br>
Greets,<br>
<br>
Christoph<br>
<br>
<br>
Miguel Angel Alvarez schrieb:
<blockquote cite="mid:200803012020.34875.maacruz@gmail.com" type="cite">
<pre wrap="">El Miércoles 27 Febrero 2008, Mark Kretschmann escribió:
</pre>
<blockquote type="cite">
<pre wrap="">On 2/27/08, Ian Monroe <a class="moz-txt-link-rfc2396E" href="mailto:ian@monroe.nu"><ian@monroe.nu></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tue, Feb 26, 2008 at 2:57 PM, Sergio Pistone
<a class="moz-txt-link-rfc2396E" href="mailto:sergio_pistone@yahoo.com.ar"><sergio_pistone@yahoo.com.ar></a> wrote:
> Hi, my name is Sergio Pistone, and I'm the author of transKode, one of
> the scripts that can be used to transcode file to audio devices (at
> least in the 1.4.x branch, I don't know if things will work the same
> way for the 2.x release).
Really it shouldn't be your job to package it. I agree with you that
you shouldn't make binaries of it. Thats the distros job. We could
help you get in contact with them.
</pre>
</blockquote>
<pre wrap="">It being a binary is really the main problem. Back in the day when I
</pre>
</blockquote>
<pre wrap=""><!---->No, it isn't. It simply should be a static binary, and that's all.
</pre>
<blockquote type="cite">
<pre wrap="">was designing the scripting system, I thought it was a good idea to
keep it open to any kind of exectutable. I now regret this decision
</pre>
</blockquote>
<pre wrap=""><!---->It is a good idea.
</pre>
<blockquote type="cite">
<pre wrap="">and I wish we would have forced the use of scripting languages.
</pre>
</blockquote>
<pre wrap=""><!---->No, you shouldn't
</pre>
<blockquote type="cite">
<pre wrap="">Amarok 2 will very likely no longer support binary "scripts", so
</pre>
</blockquote>
<pre wrap=""><!---->Please don't do that. You shouldn't put any restriction just because.
</pre>
<blockquote type="cite">
<pre wrap="">please please use a scripting language (a portable one, not Bash) for
the next version of transKode. We could probably assist you with
porting to QtRuby.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>