On 4/1/11 12:02 AM, Eddie Epstein wrote:
On Thu, Mar 31, 2011 at 2:08 PM, Jörn Kottmann<[email protected]> wrote:
Since it only supports text it can only show text sofas, if there is an
image or
whatever sofa type, the user needs a different Cas Editor implementation
which can
deal with it.
But other than not displaying sofa data for non-text sofas, the
base Cas Editor should allow browsing all other view content, yes?
Not sure I understand you, you mean the editor should display
some message that the sofa is incompatible, but then still all the views
around
the editor should be able to show the feature structures, etc. of that
cas view?
Jörn