[Fwd: Re: OFF-TOPIC: Perl...]
On Mon, 2008-01-28 at 23:59 -0800, Sergei Steshenko wrote: --- Juan José 'Peco' San Martín [EMAIL PROTECTED] wrote: Many thanks for your thoughts (Sergei and Chris). I'm not looking for a lang for all, but I'm afraid about Perl... IMHO, it needs a good push to jump into the 'new technologies' because other languages (in most of the cases, not as good as Perl) are addressing this gap. Thank you, Peco needs a good push - in most of the cases, not as good as Perl :-). Good point :-D Let me put it this way - many people simply didn't have enough ... guts to really understand Perl. Absolutely!. And I think that this is something that should be take in consideration as a Perl handicap. 5 years ago, Perl was at everywhere, but now surely because 'many people simply don't have enough time to understand perl' things has changed. Ubuntu, QT, Symbian and may be also Google (seeing its Summer Code programs) comes to my mind. They are pushing Python... For example, from a forum I recently discovered Python does not have built-in multidimensional arrays. Where Perl really excels is data structures, which along with scoping are a very elegant way to achieve readability, debuggability, modularization. And probably Perl is the best WRT regular expression - PCRE has become a de-facto standard of non-Perl application because the latter strive to be like Perl. If you are interested, I can cook up some examples - typically other languages fail miserably when people try to reimplement the same things in them. I fully agree! :-) But we are boring to see how many times the worst solution wins. FUD ON I'm afraid that if we don't do anything, this list, this project (thanks a lot guys!!!), will start to be an exception. FUD OFF Regards, Sergei. Thanks Peco Applications From Scratch: http://appsfromscratch.berlios.de/ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ gtk-perl-list mailing list gtk-perl-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-perl-list
OFF-TOPIC: Perl...
I know this is not the right place to write this but... I'm afraid of Perl. I love it, I think it's a wonderful language and what to say about CPAN... is uncomparable!. But today, if you want to develop for the the Nokia Smartphones (Symbian), or for the Nintendo DS, or for large systems or for GNOME/GTK, etc... the commom language seems to be Python. Perl6 is comming but may be it's too late. Really sorry for this FUD if somebody thinks that it's what is. :-/ Thoughts are welcome. Peco ___ gtk-perl-list mailing list gtk-perl-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-perl-list
Re: ANNOUCE: Zim
Uohhh!!!. I didn't see the application yet, but I think the idea is wonderfull!! Congratulations! Peco On Wed, 2005-09-28 at 09:22 +0200, Jaap Karssenberg wrote: Greetings, I want to announce a new gtk2-perl application I have been working on last month. Zim is a WYSIWYG text editor written in Gtk2-Perl. It aims at bringing the concept of a wiki to your desktop. For example every page is saved as a text file with wiki markup. Pages can contain links to other pages, and are saved automatically. Creating a new page is as easy as linking to a non-existing page. This tool is intended to keep track of TODO lists or serve as a personal scratch book. Homepage can be found at http://zoidberg.student.utwente.nl/zim/ I have implemented one custom class, the Gtk2::HyperTextView which is derived from TextView but is able to render links. I'm considering releasing this module onto CPAN as a separate package. I also have one question for you people: I tried connecting to the 'insert-at-cursor' signal for Gtk2::Entry but this signal is never emitted. Are there known oddities with this signal or should I report on this? Cheers! -- Jaap [EMAIL PROTECTED] ___ gtk-perl-list mailing list gtk-perl-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-perl-list ___ gtk-perl-list mailing list gtk-perl-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-perl-list
Re: Password entry
On Tue, 2005-08-09 at 15:15 +0700, Beast wrote:
How do I create password entry? (ie. same like Gtk2::Entry but every
chars displayed as *)
Use $text-set_visibility(0)
For example using Glade:
$text=$gladexml-get_widget('entry1');
$text-set_visibility(0);
Hope this help.
Peco
Thanks.
___
gtk-perl-list mailing list
gtk-perl-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-perl-list
Dialog hide/destroy
Hello all. In order to understand how the window widgets works, I created a minor application. One windows with two buttons in order to hide or show another window. All is correct! :-) Now, I'm trying to do the same but using a main window with Menu widget that calls a new dialog window. All seems to be ok, but if I close dialog window (delete_event) and try to re-open again (clicking on the menu of the main one) I get: Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed at ... when I try to show the dialog again. BTW, what it's the different between of using hide/show or directly destroy to control de windows behaviour?. It is always recommended one way to do it?. Is it faster vs memory-lesser? Thanks! Peco ___ gtk-perl-list mailing list gtk-perl-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-perl-list
Re: Dialog hide/destroy
This typically means that you're trying to call -show on a dead
widget. In your delete-event handler, what are you doing? If your
handler returns FALSE, the default handler will destroy the window;
to hide from delete event, you must set up your handler like this:
$window-signal_connect (delete_event = sub {
$_[0]-hide; # hide the window
return TRUE; # tell gtk+ that we handled this event, and
# that it should *not* destroy the window.
});
You're completly right. Thanks!
gtk_widget_hide() unrealizes the widget, which takes it off of the
screen, but does not kill it. gtk_widget_destroy() hides and then
renders unusable the widget; the destroy is explicit in order to
break reference count cycles.
Ok
Whether you reuse or recreate widgets is entirely up to you and the
architecture of your application. If it takes a lot of work to
create a widget, or it should retain state between showings, then
it's likely a good idea to use hide instead of destroy. Destroying
the widget will obviously be the more memory-friendly approach.
There is no best way, in my experience; the answer is, try both
and see which better satisfies your goals.
Ok!
Thanks again.
Peco
--
To me, hajime means the man standing opposite you is about to hit
you with a stick.
-- Ian Malpass, speaking of the Japanese word for the beginning
___
gtk-perl-list mailing list
gtk-perl-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-perl-list
Timers
Hello all.
I'm using the timers:
my $pointer-{timer}=Glib::Timeout-add(1000,\progress_timeout,$label);
All seems to be ok. Each time the progress_timeout function is called,
I'm able to change the value of $label with $pointer-set_text(123);
My issue is that I would like to attach the same timer but to other
widgets, in order to update many of them at the same time. Surely that
it's possible but I didn't find the way :-/
Thanks for any help.
Peco
___
gtk-perl-list mailing list
gtk-perl-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-perl-list
