From: "NYIMI Jose (BMB)" <[EMAIL PROTECTED]>
> > my 2 cents...
> > 
> > Distributed GUI apps are legacy. Write web based software.
> 
> You right !
> That's what I was thinking about ...
> 
> Do you have some reasons in which case "Distributed GUI" will be the
> winner against "Browser Client" ? 

Yeah ... "Browser Client" applications tend to take longer to do 
anything in. The interface cannot contain all the features and rings 
and bells a normal GUI can (unless you use Java and use the browser 
just to download and host the application). Another thing ... browser 
is a general ussage program, therefore it uses much more memory and 
processor power than a small program that only does one thing. Which 
on less equiped computers may mean that the user will spend more time 
waiting. 

I would not want to have write my programs in web browser based 
editor, read my emails in web based mail, listen to my MP3s using a 
web based interface etc. etc. etc.

If the application is something you use twice a week I'd say it would 
be better if it was web based (so you did not have to install 
upgrades almost as often as you use it), if you use it most of the 
time you'd go crazy. (I'm going crazy from the ##%*%@^#%*&$^#$ PVCS 
written in Java, even that is toooo slow and restricted.)

> Should I continue learning Perl/Tk then ? :-)

Depends on what do you need. I think if I needed to do GUI in Perl 
I'd go with wxPerl or maybe gTk. But please don't take this as a 
"wizard's" advice, I have never done any GUI in Perl.

Jenda
=========== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ==========
There is a reason for living. There must be. I've seen it somewhere.
It's just that in the mess on my table ... and in my brain
I can't find it.
                                        --- me


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to