Francesco Romani wrote: > - The GUI should be coded in C or in C++. We're already full of > dependencies, so I'm really reluctant to add new _core_ dependencies > (modules are a different story) unless necessary. > If the GUI will be in C or C++, that's another point _against_ a > frontend and in favour of a native approach.
Probably another approach towards getting a GUI (official or not ;)
could be: provide a stable C-API to be bound by scripting languages like
Perl, Python, Ruby etc. So the GUI stuff could be done in an interpreted
language, which makes things easier in my opinion.
Since building the GUI should be optional anyway this adds no _real_
core dependencies. Of course if you like to use the GUI you need to have
the corresponding scripting language runtime envronment installed. But
spoken for the three named above this is no real problem, since they are
very common and available for any modern Unix style operating system.
Just my 2c ;)
Regards,
Jörn
--
sub i($){print$_[0]}*j=*ENV;sub w($){sleep$_[0]}sub _($){i"$p:$c> ",w+01
,$_=$_[0],tr;i-za-h,;a-hi-z ;,i$_,w+01,i"\n"}$|=1;$f='HO';($c=$j{PWD})=~
s+$j{$f."ME"}+~+;$p.="$j{USER}\@".`hostname`;chop$p;_"kl",$c='~',_"zu,".
"-zn,*",_"#,epg,lw,gwc,mfmkcbm,cvsvwev,uiqt,kwvbmvb?",i"$p:$c> ";w+1<<07
pgpINZAjmCcW4.pgp
Description: PGP signature
