<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ivan Krstić wrote:
<blockquote cite="mid4546AC09.8030608@solarsail.hcs.harvard.edu"
type="cite">
<pre wrap="">Teus Benschop wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Yes, I agree that ideally
Bibledit should become a "native" sugar applications, but probably in a
later stage.
</pre>
</blockquote>
<pre wrap=""><!---->
This brings forward a more general question about how we want to deal
with legacy apps. They work now with manual tinkering, but without a
concrete model of how to deal with them, they simply won't work once we
start implementing the security features.
</pre>
</blockquote>
Implementing security features to block legacy applications, that
sounds frightening to me. That means no application will run on Sugar
unless it is fully compliant. Friends, what are you doing to us, legacy
developers? :)<br>
<br>
Teus.<br>
</body>
</html>