Ticket #326 (accepted Defect)
Running without Type Editor plugin throws an error when clicking a type
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | |
Component: | DeepaMehta Standard Distribution | Version: | 4.0.12 |
Keywords: | Cc: | dgf, Malte | |
Complexity: | 3 | Area: | |
Module: | deepamehta-webclient |
Description
The client-side error (in the browser's error console) is
PluginManagerError: page renderer "dm4.typeeditor.topictype_renderer" is unknown
Solution:
Fallback to the default Topic renderer.
Change History
comment:3 Changed 11 years ago by Malte
Copying the #512 description (more detailed) into this ticket:
As required to build a lightweight distribution showing DeepaMehtas??
potential to end-users (#455).
Without the Type-Editor plugin active, the following commands should be removed:
- New Topic Type
- New Association Type
Exchange any Types Page Renderer with, e.g:
- a list of all the types instance
- without the "Edit" command
So users cannot alter existing type-definition and therewith juggle with my
applications model.
The "Type Editor"-Plugin is definitely a desirable functionality and important
to be delivered to users but we should consider communicating it as advanced
and/or optional freedom.