Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [technology-pmc] Sapphire

Hi Konstantin,

Am 10.06.2010 22:07, schrieb Konstantin Komissarchik:
> We welcome your feedback on this proposal.

I think the scope needs to be more precise and limiting. Note, it is not
set for lifetime and can be adapted as the project evolves.

For example, this is too generic:

> This project will be focused on identifying ways to significantly
> speed up UI development while simultaneously improving quality,
> maintainability and consistency.

It basically opens the project to *anything* UI development related.
Also the next sentence is too open IMHO.

> Some of the key deliverables:

>From reading the proposals it sounds like point 1 and 3 should be *the*
key deliverables but not _some_.

I'd also like you to consider how others can adopt/benefit from
Sapphire. For example, can you imaging that you (initially) just focus
on the SWT renderer? This would leave room for others to work on
different renderers.

The most issue I have is a goal of delivering "A compact and easy to
learn modeling framework tailored to the needs of UI writers." That
really sounds like a second modeling framework and you admit it in the
sentence below.

>From reading "Relation to EMF" it sounds like EMF does not serve the
needs of UI developers very well. Do you know that EMF is powering e4?
e4 initially also started with their own modeling framework
implementation but soon discovered and learned that EMF does serve their
needs very well.

Can you elaborate a bit more on the differences to EMF and why EMF is
not sufficient?

-Gunnar


-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/


Back to the top