[spe.pycs.net] welcome

[Tina Hirsch]

Hi all :)

Stani, I eventually downloaded the latest version of spe :)
About the wrong lineendings: you have to remove the directories
build/scripts-* before you zip everything. Then the problem will be gone
for all platforms. Other than that the install seems to run fine - no
problems anymore.
Btw. I'm running spe with python2.3 on gentoo without probs (hm, should
probably make a new ebuild (package for gentoo) :)).


To the others, the script was originally made just for *nix -
mainly because of lineendings :P and that there's something on PATH.

Though if someone has the wrong spe in /usr/*/bin, a new install of spe
won't overwrite it. One has either to use the uninstall script or remove
/usr/*/bin/spe by hand.

Stani, in README.txt (removal part of linux/bsd/..) there's missing that
one needs also to remove /usr/local/bin/spe.


Regarding the terminal thing. xterm is probably the best default term,
though it's still possible on a few distros (debian?) that it is not
installed by default (sometimes FREEDOM *can* be annoying ;)).
About the lists in the path options in general: I just made a wild guess
when I sent them to Stani. They aren't complete nor may they be correct
for everyone. That's why the paths are in the options. Everybody can
adjust them to their likings/needs.
I hoped that over time other users will send more correct entries and
more variations to update those lists.

I personally prefer wterm (windowmaker related rxvt clone, btw. Eterm
is enlightenment related terminal) at the moment and this one won't
work without "-e" (nor has it -hold) and a given command at all :(
(Well, actually xterm doesn't work without -e and a command neither?)


Rasjid Wilcox wrote:
> def menuToolsConsole(self,event):
> ...
>     if terminal==DEFAULT:
>         if sys.platfrom='win32':
>             os.system(... win32 stuff)
>         else:
>             os.system("cd \"%s\"; /usr/X11R6/bin/xterm &"%(path,))
>     else:
>         os.system("cd \"%s\"; %s &"%(path,terminal)   ## Problem here!

Oh, I didn't think about that! First cd to a directory and then open the
terminal. This works very nice for "Open terminal emulator". "-e"
option even doesn't hurd when there's no command after it - at least
with wterm ... *sigh* but xterm complains about it. 

I found out that menuToolsRunExternal is fine with replacing
Eterm by xterm as suggested (Question: should this function be blocking
or non-blocking? If the latter then there must also be a "&", like in
menuToolsConsole above.). But on the other hand wterm doesn't work like
that - maybe it's sort of a bug of wterm/rxvt or they wanted it like
this. For wterm to work with opening a interactive console or running
a command, it'd need two different path options in the dialog (maybe
this is also true for some other terminals - I don't know, anybody
else here maybe?). 
I.e. for the first I need to type just "/usr/bin/wterm" and for the
second one I need (aargh!!!!!): "/usr/bin/wterm -e /bin/bash -c" 
Now the question is: Do we need seperate paths for opening a console and
run a script in the console?


Now something different:
A gentoo user asked recently the following:
> 1) The SPE package includes wxGlade (bug#29002), so perhaps either (a)
> the SPE ebuild should inject wxGlade into the list of installed
> packages, or (b) make wxGlade a dependency, so that the wxGlade ebuild
> has exclusive right to install it, and the SPE ebuild might delete
> SPE's wxGlade files before installing, and create a symlink to the
> actual wxGlade installation.

What do you plan to do with wxGlade, Stani? If you just distribute
always the original, unmodified code of wxGlade, I may do what this user
suggests, i.e. delete wxGlade from spe directories and use the official
one. By creating links to that version this would mean no changes for
spe itself.


Greetings,
Tina


Ps: Submitted the new ebuild right now :)