| Q: SSE questions [message #64800] |
Tue, 11 January 2005 23:34  |
Eclipse User |
|
|
|
Originally posted by: constantine.plotnikov.gmail.com
I would like to use SSE to build editor for GTL (Generalized Term
Language) project (see download section sf.net/projects/xc4j for older
prototype and documentation). The idea of the project is to create
something like SGML (from framework structure point of view rather than
from syntax one), however more suitable for programming languages.
From limited documentation that is available it looks like structure of
SSE framework fits GTL requirements very well. Initially planned design
over core eclipse classes had many properties similar to what is
described in newsgroup posts. I already have lexer and pull parser that
are able to parse entire document and document fragments. The parser
allows building a tree of regions from text.
I have the following questions:
1. Is SSE framework supposed to be used in such scenario? I found
references to XML and JSP in org.eclipse.wst.sse.core plugin. Also
org.eclipse.wst.sse.core.documentTypes extension point that as I
understand is supposed to be generic contains funny attributes like
isHTML and isWML (they are used in html plugin). Also HTML, XML, DTD
plugins are somewhat aware of each other. It confuses me a bit.
2. Is it a good time to start using SSE in prototype-level projects? It
was mentioned that there will be major changes in extension points for
M3. How serious changes that affect code will be?
3. Is it possible to outline basic steps that should be undertaken when
creating the editor? For example CSS editor implementation has more than
50 packages and it is not completely clear which are CSS specific. I
would like to get a brief information on the following:
a. List of logical components and extension points that should be
implemented with dependencies. I would also like to know which
components are optional and what are the consequences of omitting them.
b. Major SSE interfaces that should be implemented and their role and
description of (possibly abstract) reusable implementations.
Constantine
|
|
|
| A: SSE questions [message #65207 is a reply to message #64800] |
Thu, 13 January 2005 06:58  |
 David Williams
Messages: 722
Registered: July 2009 |
Senior Member |
|
|
On Wed, 12 Jan 2005 05:34:40 +0600, Constantie Plotnikov <constantine.plotnikov@gmail.com> wrote:
> 1. Is SSE framework supposed to be used in such scenario? I found references to XML and JSP in org.eclipse.
> wst.sse.core plugin.
Yes, could be used for any "structured language". The presence of XML and JSP in there is historical (we used to be one big honking plugin since not need to have seperate) and temporary ... a major work effort over next few months is to refactor and refactor and redesign and redesign, so that sort of contamination won't be necessary.
> Also org.eclipse.wst.sse.core.documentTypes extension point that as I understand is supposed to be generic
> contains funny attributes like isHTML and isWML (they are used in html plugin). Also HTML, XML, DTD plugins > are somewhat aware of each other. It confuses me a bit.
Me too.
> 2. Is it a good time to start using SSE in prototype-level projects? It was mentioned that there will bemajor changes in
> extension points for M3. How serious changes that affect code will be?
Its a *great* time to start. Yes, there will be changes, and yes, you'll be frustrated by them, but we will try to be very sensitive to "co-developers" and at a minimum provide some guidence of what changes from one milestone to the next. Very few of the core concepts will change, just things like which argruments are used, what type of object is returned, probably some interfaces will go away in favor of Abstract classes, for example. The reason its a *great* time, though, is that its the time your needs and insights into what's proper and what's not would have the most impact.
> 3. Is it possible to outline basic steps that should be undertaken when creating the editor? For example CSS editor
> implementation has more than 50 packages and it is not completely clear which are CSS specific. I would like to get a
> brief information on the following:
>a. List of logical components and extension points that should be implemented with dependencies. I would also like to know
> which components are optional and what are the consequences of omitting them.
>b. Major SSE interfaces that should be implemented and their role and description of (possibly abstract) reusable
> implementations.
>
This kind of documentation and simpler editor examples will be forthcoming ... a little from us, a little from others, and hopefully a lot from community like you :) Some docs will be available by M3 2/27, and some by M4.
|
|
|
| Re: A: SSE questions [message #77420 is a reply to message #65207] |
Sat, 26 February 2005 19:31 |
| Eclipse User |
|
|
|
Originally posted by: constantine.plotnikov.gmail.com
David Williams wrote:
>> 3. Is it possible to outline basic steps that should be undertaken
>> when creating the editor? For example CSS editor
>> implementation has more than 50 packages and it is not completely
>> clear which are CSS specific. I would like to get a
>> brief information on the following:
>> a. List of logical components and extension points that should be
>> implemented with dependencies. I would also like to know
>> which components are optional and what are the consequences of
>> omitting them.
>> b. Major SSE interfaces that should be implemented and their role and
>> description of (possibly abstract) reusable
>> implementations.
>>
>
> This kind of documentation and simpler editor examples will be
> forthcoming ... a little from us, a little from others, and hopefully a
> lot from community like you :) Some docs will be available by M3 2/27,
> and some by M4.
I have just downloaded WTP M3 SDK. I have not yet found documentation or
examples on website or in sources. Are they available?
Constantine
|
|
|
Powered by
FUDForum. Page generated in 0.03927 seconds
] 
Search
Help
Register
Login
Home
