[Phoenix] Validation and Datatype Guided Content Assist
Andreas Wuest
awuest at student.ethz.ch
Sat Sep 9 01:50:42 CEST 2006
Hi
On 8.9.2006 15:04 Uhr, Andreas Wuest wrote:
> Hi
>
> On 8.9.2006 14:15 Uhr, Comiotto Thomas wrote:
>
>> Hi all,
>>
>> Regarding the basic infrastructure for adding validation and CA
>> support to ulysses (what was the name again?) - could this be
>> approached by moving this functionality out to optional extensions?
>> Since the schema related code a. tends to be complex b. available
>> components tend to be platform dependant and b. several approaches can
>> be taken CA support, I think it would make sense to allow users to
>> plug in third party vendor implementations of choice that deal with
>> schema support. Extensions to the extension if you will. This approach
>> would also make our own (yet to be written) components reusable for
>> other extension developpers of course.
>>
>> WDYT?
>
> Sure, we can do that.
In fact, we've already discussed that in the
http://wyona.com/pipermail/phoenix/2006-July/000224.html thread.
The problem is that we first have to agree on a common interface.
Everything else is easy. In fact, here is the plan:
1. Agree on a common validation and content assist interface
2. Create an XPIDL file representing this interface
3. Write JS components which implement this interface
4. Package them up as an extension
Via the wonders of LiveConnect, we could e.g. easily build a component
which uses Jing as a validator.
All you need for building a component is to write the interface file
used by all components implementing this interface. You'll also need to
write additional interfaces for all the types used of course.
Then, you create the type library by using xpidl (you'll have to build
the Mozilla SDK on your machine to first build the xpidl tool, since it
is platform-specific).
Afterwards, you are ready to go. :)
--
Kind regards,
Andi
More information about the Phoenix
mailing list