symbide0.3.1 released

[basti]

this is mainly a bugfix release.
Symbide should now work properly at least on windows XP.

basti

[Ivan Iakoupov]

Hello again

While exploring Help --> Examples I tried 'functions and plotting'.
Because I didn't have PIL installed it just shows 'in progress'
animations in a never ending loop. The console output also reported:

Uncaught exception in event loop: No module named PIL
Not able to handle this format

Maybe you can handle it more graciously? Like print a message in the gui
for example...

[Sebastian]

> Hello again
> While exploring Help --> Examples I tried 'functions and plotting'.
> Because I didn't have PIL installed it just shows 'in progress'
> animations in a never ending loop. The console output also reported:
>
> Uncaught exception in event loop: No module named PIL
> Not able to handle this format
>
> Maybe you can handle it more graciously? Like print a message in the gui
> for example...
>
>

Thanks for your report!
I corrected that behaviour. But I'm not completely satisfied with
Symbides information feedback in general. There should probably be a
standardized way for such cases, how to give nice information like
"what is missing", "where do I get it" and "why do I need it". Maybe
I'll create an own widget for such cases like I did with the error widget.

By the way, do you want svn-access so that you can solve such little
things on your own? (Of course you can do bigger things too, if you have
time)

basti

[Ivan Iakoupov]

Sebastian wrote:
> By the way, do you want svn-access so that you can solve such little
> things on your own? (Of course you can do bigger things too, if you have
> time)
>
> basti
>

Thank you for your offer. But I think I don't need one just yet. I mean
you can fix the problems much faster since you know your codebase. For
example in the last case I wouldn't even know where to look (without
spending some time examining the code) and if I found the place I
wouldn't be able fix without reading various docs and howtos since
* I have no clue about how to use threading in python (I suppose you use
that)
* I have never used pygtk
* I have never used svn (although I've spent some time tinkering with
git and git-svn)
By the way do you have any coding guidelines or something like that?

Now if I was already spamming you with high quality patches the svn
access would be more practical :).

[Sebastian]

> Thank you for your offer. But I think I don't need one just yet. I mean
> you can fix the problems much faster since you know your codebase. For
> example in the last case I wouldn't even know where to look (without
> spending some time examining the code) and if I found the place I
> wouldn't be able fix without reading various docs and howtos since
>

You could start with things that are not too dependend on other things,
but you're right, code fixing will take you much more time at the beginning.

> * I have no clue about how to use threading in python (I suppose you use
> that)
>

Yeah, but not too much. But it's not that difficult to learn that in
Python. The only things I needed were threading.Thread and
threading.Lock and both are not very complicated. Some problems occured
in the beginning because one has to avoid calling gtk methods from
threads but thats all.

> * I have never used pygtk
>

I admit in the beginning it's a little awkward, but after a little
playing around it turns out to be easy enough.

> * I have never used svn (although I've spent some time tinkering with
> git and git-svn)
>

If you use any good client, there's not much to know. Just do a checkout
once and then just update/commit.

> By the way do you have any coding guidelines or something like that?
>

Not really. Only try to write easy understandable functions and methods
- don't pack too much into one function. (This is something I find
myself doing for quick-hacks)

> Now if I was already spamming you with high quality patches the svn
> access would be more practical :).
>

Hey, your day may come ...;)