On 28 Apr 2009, at 01:30, Nicolas Cueto wrote:
Hi Björnke,
Do you know if your chat stack will work
on Rev 2.9?
It should work with rev versions down to at least 2.6.1, prolly even
earlier ones. It's also fully metacard compatible. if you have further
questions, feel free to contact me
I'd be real interested in starting to use / develop for the MC IDE, but
don't want to have to switch between applications. Here are my thoughts on
some future directions for discussion:
1. Separate as many as possible MC IDE components out as standalone
componenets that can be used in any
I have been thinking into a similar direction lately. The main issue
is about how to decide what is a component and what isn't. For example
a script editor contains stuff for debugging, auto-completion (...
sometimes), colorisation, undo handling, etc.
So should a script editor be one
Hello Björnke von Gierke, David, and y'all,
From: Björnke von Gierke b...@mac.com
Subject: Re: IDE Interoperability
See above for context.
The main issue is about how to decide
what is a component and what isn't.
The OPERATIVE word here is DECIDE. There is no BEST-answer
On 27 Apr 2009, at 21:27, Alain Farmer wrote:
Quite right. I'm looking forward to see what you guys come up
with. :-)
What? Us? No way, you do it :P
Bjoernke
--
official ChatRev page:
http://bjoernke.com/runrev/chatrev.php
Chat with other RunRev developers:
go stack URL
2009/4/27 Björnke von Gierke b...@mac.com
I have been thinking into a similar direction lately. The main issue is
about how to decide what is a component and what isn't. For example a script
editor contains stuff for debugging, auto-completion (... sometimes),
colorisation, undo handling,
Hi Björnke,
Do you know if your chat stack will work
on Rev 2.9?
Thanks.
-- Nicolas Cueto
___
metacard mailing list
metacard@lists.runrev.com
http://lists.runrev.com/mailman/listinfo/metacard
Hi Björnke and y'all,
I'm only a lurker on the revInterop list. I listen and react-to some of the
things you're discussing to make Rev interoperable, in-order-to brainstorm,
design, and craft my own xCard-inspired application; authoring system to be
more precise.
My xCard will be a Web-app
