| 2 suggestions for XSD [message #61013] |
Mon, 09 May 2005 11:34  |
Eclipse User |
|
|
|
Originally posted by: adamNoSpam_._NoSPAMsoftfab.com
1) What schema.
Many schemas I have to work with are at the end of a long chain of
schemas i.e. I might be working on a schema which incudes a schema which
itself includes a schema etc.etc.
When you are then using the schema viewer & you get to an element which
is some distance into the model/tree you then have no idea which actual
schema contains the definition. What would be very usefull would be the
ability to see which actual schema contains a chosen type.
e.g. in the properties view you could include a further textbox which
says which schema this type resides in.
2) An example going all the way from XSD to a GEF editor.
I am looking at creating an XSD editor for an object model which is
expressed in XML. At present there is a tutorial for how to create an
EMF model from an xsd, and there are tutorials for how to create a GEF
editor from an EMF, but it would be usefull to have a tutorial where one
starts with an XSD & progresses right through to the GEF editor.
Preferably this would include best practice advice wrt how to separate
out the different levels such that if a schema changes then how to
ensure that only the minimal amount of work/refactoring will need to
occur at the GEF level.
Adam
|
|
|
| Re: 2 suggestions for XSD [message #61039 is a reply to message #61013] |
Mon, 09 May 2005 11:49  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Adam,
The WTP project provides a better XML Schema editor than the XSD
project. XSD just provides a simple/sample editor (that I have no time
to make better) whereas WTP is providing a "real tool". They'll be more
able to make improvements based on your suggestions. (Ideally the
editor would let you see all the sources and you could see any object
selected its source view.)
The new GMF project is looking at the second issue of better edit
support for GEF-based views for EMF model instances. Again, support for
GEF is something our team would love to have done but just don't have no
time to contain...
Adam Flinton wrote:
> 1) What schema.
>
> Many schemas I have to work with are at the end of a long chain of
> schemas i.e. I might be working on a schema which incudes a schema
> which itself includes a schema etc.etc.
>
> When you are then using the schema viewer & you get to an element
> which is some distance into the model/tree you then have no idea which
> actual schema contains the definition. What would be very usefull
> would be the ability to see which actual schema contains a chosen type.
>
> e.g. in the properties view you could include a further textbox which
> says which schema this type resides in.
>
>
> 2) An example going all the way from XSD to a GEF editor.
>
> I am looking at creating an XSD editor for an object model which is
> expressed in XML. At present there is a tutorial for how to create an
> EMF model from an xsd, and there are tutorials for how to create a GEF
> editor from an EMF, but it would be usefull to have a tutorial where
> one starts with an XSD & progresses right through to the GEF editor.
>
> Preferably this would include best practice advice wrt how to separate
> out the different levels such that if a schema changes then how to
> ensure that only the minimal amount of work/refactoring will need to
> occur at the GEF level.
>
> Adam
|
|
|
| Re: 2 suggestions for XSD [message #61108 is a reply to message #61039] |
Tue, 10 May 2005 10:36 |
| Eclipse User |
|
|
|
Originally posted by: adamNoSpam_._NoSPAMsoftfab.com
Ed Merks wrote:
> Adam,
>
> The WTP project provides a better XML Schema editor than the XSD
> project. XSD just provides a simple/sample editor (that I have no time
> to make better) whereas WTP is providing a "real tool". They'll be more
> able to make improvements based on your suggestions. (Ideally the
> editor would let you see all the sources and you could see any object
> selected its source view.)
>
OK I'll post that suggestion to the wtp group.
> The new GMF project is looking at the second issue of better edit
> support for GEF-based views for EMF model instances. Again, support for
> GEF is something our team would love to have done but just don't have no
> time to contain...
>
>
Fair enough
Adam
|
|
|
| Re: 2 suggestions for XSD [message #595439 is a reply to message #61013] |
Mon, 09 May 2005 11:49 |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Adam,
The WTP project provides a better XML Schema editor than the XSD
project. XSD just provides a simple/sample editor (that I have no time
to make better) whereas WTP is providing a "real tool". They'll be more
able to make improvements based on your suggestions. (Ideally the
editor would let you see all the sources and you could see any object
selected its source view.)
The new GMF project is looking at the second issue of better edit
support for GEF-based views for EMF model instances. Again, support for
GEF is something our team would love to have done but just don't have no
time to contain...
Adam Flinton wrote:
> 1) What schema.
>
> Many schemas I have to work with are at the end of a long chain of
> schemas i.e. I might be working on a schema which incudes a schema
> which itself includes a schema etc.etc.
>
> When you are then using the schema viewer & you get to an element
> which is some distance into the model/tree you then have no idea which
> actual schema contains the definition. What would be very usefull
> would be the ability to see which actual schema contains a chosen type.
>
> e.g. in the properties view you could include a further textbox which
> says which schema this type resides in.
>
>
> 2) An example going all the way from XSD to a GEF editor.
>
> I am looking at creating an XSD editor for an object model which is
> expressed in XML. At present there is a tutorial for how to create an
> EMF model from an xsd, and there are tutorials for how to create a GEF
> editor from an EMF, but it would be usefull to have a tutorial where
> one starts with an XSD & progresses right through to the GEF editor.
>
> Preferably this would include best practice advice wrt how to separate
> out the different levels such that if a schema changes then how to
> ensure that only the minimal amount of work/refactoring will need to
> occur at the GEF level.
>
> Adam
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Powered by
FUDForum. Page generated in 0.03183 seconds
] 
Search
Help
Register
Login
Home
