Hi,
I agree totally with raster, but maybe instead take a look at systems that do it
correctly and take whatever is good from others and implement in e, which is the
obvious thing to do, so obvious I shouldn't bother to mail about it :-D
My tips is to take some looks at BeOS, there are definitl
I've been a bit late, but finally it's here !
I yesterday hit the 60 fps boundary, and I now get a score of at least 1.0 in
the evas demo's test ! (thanks to the memory i bought some weeks ago ... yes,
there's still the memory problem in evas on PPC).
My Altivec patch to evas is quite ready, clea
Hi list !
Using some unusual parameters I bump in the folowing problem:
I am building CVS from CVS, installing it in /usr/local/e.
I put /usr/local/e/bin in PATH, /usr/local/e/lib in ld.so.conf.
_but_ /usr/local/e/include is not in defaut include path.
The problem encountered is configure fails
> take a look at systems that do
> it correctly and take whatever is good from others and implement in e, which
> is the obvious thing to do
Also, I think Jef has some good ideas, even if I find the overall thing
impractical - eg I'd *love* a textbox that could evaluate statements as well as
just
Carsten Haitzler (The Rasterman) wrote:
On Wed, 09 Jun 2004 19:39:43 +0200 Kim Woelders <[EMAIL PROTECTED]> babbled:
Carsten Haitzler (The Rasterman) wrote:
On Tue, 8 Jun 2004 16:42:52 -0400 [EMAIL PROTECTED] babbled:
this is a known issue - try cvs. e16 as of 0.16.6 has been rather confused
about
On Thu, Jun 10, 2004 at 05:19:20PM +0200, [EMAIL PROTECTED] wrote:
> I've been a bit late, but finally it's here !
> I yesterday hit the 60 fps boundary, and I now get a score of at least 1.0 in
> the evas demo's test ! (thanks to the memory i bought some weeks ago ... yes,
> there's still the me
Shish wrote:
take a look at systems that do
it correctly and take whatever is good from others and implement in e, which
is the obvious thing to do
Also, I think Jef has some good ideas, even if I find the overall thing
impractical - eg I'd *love* a textbox that could evaluate statements as we