On Thu, 23 Aug 2007 08:19:51 +1000, David Seikel wrote:
Thanks, Kim and David:
Am I missing something obvious or is this not a workable combination.
Um... e16 should be compatible with just about anything, but engage
seems to be somewhat less functional than it has been.
EFL APIs move
On Thu, 23 Aug 2007 10:15:35 + (UTC) Peter [EMAIL PROTECTED] babbled:
On Thu, 23 Aug 2007 08:19:51 +1000, David Seikel wrote:
Thanks, Kim and David:
Am I missing something obvious or is this not a workable combination.
Um... e16 should be compatible with just about anything,
On Thursday, 23 August 2007, at 10:15:35 (+),
Peter wrote:
I think that if engage standalone is to survive, it will have to
fork off the existing modular project and become independent. Next,
it will have to have a standardized, non-eap-style, method of
accessing programs and objects.
On Thu, 23 Aug 2007 16:51:38 -0400, Michael Jennings wrote:
snip...
It's free software. If you think you know what needs to be done, do it.
Michael
Well, I don't use e17 and don't know EFL, so I would not know what needs
to be done. I don't think porting it to gtk or qt is worth the
On Thu, 23 Aug 2007 21:17:11 + (UTC) Peter [EMAIL PROTECTED] babbled:
On Thu, 23 Aug 2007 16:51:38 -0400, Michael Jennings wrote:
snip...
It's free software. If you think you know what needs to be done, do it.
Michael
Well, I don't use e17 and don't know EFL, so I would not
On Wed, 22 Aug 2007 22:37:29 +0200 Kim Woelders [EMAIL PROTECTED] wrote:
Peter wrote:
I realize engage standalone is deprecated. So, before anything, is
engage compatible with e16? e16 uses composite and I tried starting
engage with - m 1 -C 1 options. It does seem, to draw a large
I realize engage standalone is deprecated. So, before anything, is engage
compatible with e16? e16 uses composite and I tried starting engage with -
m 1 -C 1 options. It does seem, to draw a large rectangular area at the
bottom. It does show white areas and mouse over shows applications that
