[Kst] KJSEmbed

[Barth Netterfield]

Any particular reason we can't remove it from 1.0?  It is completely 
undocumented, and not even close to a stable interface, so in fact removing 
from 1.0 is probably the correct approach (so changes won't trigger 2.0...)

We can add it back in once we have defined the bindings, in a feature release.

cbn

On Tuesday 23 November 2004 18:05, George Staikos wrote:
>    Unfortunately I just discovered that KJSEmbed has not been keeping
> binary or source compatibility.  This means that we have to keep our own
> copy in Kst.  In some ways, this may not be so bad though, since there are
> quite some bugs in the older versions, including one that affects us and is
> not fixed yet.  It means more maintenance (merging in their fixes
> periodically), but fewer headaches with bug reports.  I'll import a copy of
> the tree once I merge the HFI branch.