muppet wrote:
> ...
> The situations you want to watch out for are:
>
> - Any form of circular reference. Avoid keeping references to yourself.
> - Take care with closures, and they can hide references to objects
> and create reference cycles.
> - NEVER override DESTROY on a Glib::Object, ...
A. Pagaltzis wrote:
> ... glad I can help. :-)
Thanks for the most clear lesson; very enlightening!
>> What's the "+" for?
>
> To force parsing as a value. Otherwise, Perl thinks these parens
> belong to `sort`, ... That caught me completely by surprise.
> ...
> You can use the unary plus
A. Pagaltzis wrote:
> ...
> Now it uses an idle callback to read directories so the UI never
> freezes.
Thanks for posting your version of the browser. I'm learning a lot going
through it--I think I almost see how it works ;-)
A couple of questions still. These are mostly Perl; feel free to a
Ratcliffe, Jeffrey (Peters) wrote:
>> Very good script. :)
Seconded! Nice example.
> I was trying to keep it short and simple, but you can replace:
>
> @{$slist->{data}} = <*>;
>
> with
> ...
Or just
@{$slist->{data}} = grep(-d, <*>);
But anything using "-d" will require an expensive "st
Emmanuele Bassi wrote:
...
We really, *really* need some hero to take over the tutorial and finish
it off. ...
Hey, I've been lurking around here in awe of the great work you guys
have done on gtk-perl; maybe this is something I could help with.
However, I think it really takes an expert to
Torsten Schoenfeld wrote:
Not really. If you put a block around a sub, you can declare a lexical
variable in that scope but outside the sub. It will then behave like a
state variable: ...
Awesome! I've wished for years to be able to do that--never thought of
adding that extra block. Yeesh d
Daniel Kasak wrote:
Beast wrote:
...
Seriously, is there any seriuos project written using gtk-perl? I
found very little number of projects in SF or freshmeat, most of them
are in alpha stage or left unmaintained.
...
I honestly don't know why there aren't more projects though. Perl just
seems
muppet wrote: [note: copious snippage]
Narrow the scope a bit; what's more important?
- saving plots (want to save them, but preview in a gui)
- interactive plots (user can mouse-over and/or edit data)
- high-quality plots (speed is not a concern)
Well said. Graphing involves serious tradeoffs:
