|
Thank you. Some issues with such "sniffing" are
performance and user transparency.
There are two levels of performance concern: 1) A
plugin that wishes to dynamically decide must be instantiated. 2) The plugin may
then read resources, like your web.xml example, including the resource in
question. If the plugin is allowed to "catch and release," to use a fishing
metaphor, the next plugin in line would be instantiated, multiplying the
concerns by the number of eligible plugins.
If plugins are allowed to decide at runtime which
editor to invoke, what of the desires of the user? The user clearly says "Use
editor X for extension .abc," but file foo.abc is opened up in editor Y because
some plugin thought it knew better.
The need for sniffing of some sort is easy to
demonstrate. For example, it is impossible to correctly decide the encoding of
an XML document without reading a portion of the document. But how much of
it should be pluggable?
Bob
----- Original Message -----
Sent: Monday, April 28, 2003 12:09
PM
Subject: RE: [pde-dev] Resources/Editors
Binding via Runtime Logic
A couple of things
are a basis for the decisions:
- Referring to a
Web.xml to read out referenced resources and bind them to a particular
editor for modification
- Also looking at the
extensions of project classes to extend the editor for an alternate method
of editing
Thanks!
-----Original
Message-----
From: pde-dev-admin@xxxxxxxxxxx
[mailto:pde-dev-admin@xxxxxxxxxxx] On
Behalf Of Bob Foster
Sent: Monday, April 28, 2003 11:49
AM
To:
pde-dev@xxxxxxxxxxx
Subject:
Re: [pde-dev] Resources/Editors Binding via Runtime Logic
Upon what does that logic base its
decisions? What is its input?
----- Original Message -----
Sent: Monday,
April 28, 2003 10:16 AM
Subject:
[pde-dev] Resources/Editors Binding via Runtime
Logic
I've been reading up on plugin extensions and
it seems that editors can be attached to resources via extension or by file
name. I would like to find a way to bind an editor or modify the
decorator of a resource based on logic contained in java code (pulled from
another config file particular to a plugin).
If anyone has any suggestions or knows of an open
source plugin that I could dive into the source of, it would be greatly
apprechiated.
---
Incoming mail is certified Virus Free.
Checked by
AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.476 / Virus
Database: 273 - Release Date: 4/24/2003
---
Outgoing mail is certified Virus Free.
Checked by
AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.476 / Virus
Database: 273 - Release Date:
4/24/2003
| 