the last issue (emf.edit dependency) seems to be hard to resolve.
I therefore suggest the following as a pragmatic solution:
1. We do the checkpoint build now, which is compatible with Luna.
As there were no blocking issues, are we ready to go? @Paul: Could
you trigger this?
2. We configure a tycho build producing an update site for the
core e4 tools only (I would do this)
3. We get the e4 tools (only the editor) on board of Mars (I would
take care of this)
Are there any objections, opinions?
Best Regards
Jonas
Am 30.07.2014 14:25, schrieb Lars Vogel:
> @Lars:
In general I would love, if the tools are moved to PDE and
thereby become part of Mars. If you need any help, please let
me know.
AFAIK, it is not possible to produce releases from an
incubation project. SWTBot is according to the website
and the projects list a mature project.
As stated before, I would be able to spend effort on
this item.
@Lars: In general I would love, if the tools are moved
to PDE and thereby become part of Mars. If you need any
help, please let me know.
However, when we dicussed this possibility over one year
ago, there was the concern, that it is not so easy
anymore for the existing e4 committers to work on the
tools unless they all become committer, which in turn
the PDE team might not like.
Being an incubation project does not
really exclude to produce a 1.0 release…
SWTBot is a 2.2.1 and is developed as an
incubation project… So having a e4 tools
1.0 is possible...
I think that creating a new project
will not really change the result.. But
changing the way to work on it
probably…
As Lars said, we work on this project
on our spare time. This is the life of
this kind of project. No problem about
that for me. We try to do our best to
achieve a good product. But even if we
do our best, a direction must be defined
more clearly. Today bugs are opened more
for personal reasons (i would like to
see this like this) or for urgency,
rather than for global or strategical
reasons. May be some bugs could be
identified as ‘strategic' and they would
open a discussion about it… We could may
be schedule 2 or 3 strategic bugs per
release ? And in our bugzilla queries we
could have them as a common goal besides
our personal bugs.
Something that could be more
efficient also, would be to schedule a
real physical meeting during each
eclipse con since we are almost all
attending. We could prepare a set of
issues to be discussed… Today this kind
of meeting is hold by BOF where the
subjects are not really defined and the
BOF itself is organized if we want/think
to organize it (during last Econ US I
asked for one but it was not really
scheduled).
As Jonas said, the discussion about
the dialogs in model has been done a
year ago, but it must continue to know
what we can do with it… The new
discussion could be in one of the issues
of this meeting after speaking about it
on mailing list...
And to finish, integrating E4 stuff
in the mars PDE would be probably a good
idea
About a new e4
tools project? I think that is
not necessary, we could
graduate e4 tools also from
the existing project. The
issue IMHO is that that we
need a new project but that no
one does real work on this
item at the moment.
FYI - I plan to integrate
the e4 project wizard for
Mars into PDE.
The second
issue has been
discussed a
year ago with
no result. But
I agree that
having the
tools in an
incubation
state and
additionally
not in the
release train
is bad for the
adoption. As
the e4 project
is an
incubation
project, it
cannot produce
1.0 releases.
The options
were to move
them to PDE or
the platform,
but there was
never a
conclusion to
this.
I would like
to suggest a
third
solution:
create a new
e4 tools
project. This
would enable
us to graduate
the e4 tools
easily, keep
all existing
(and
interested)
comitters and
join the
release train.
I would be
willing to
drive this, if
everybody
agrees.
I am on
holidays and
cannot test
the new
release...
Some
remarks anyway
:
As tom
said, I think
the
dialogs/windows
node is really
confusing and
dialogs are
not usable as
it is today.
It would be
really
interesting to
start a new
discussion on
this topic as
soon as
possible to
find together
an operational
and efficient
solution. It
should
probably not
appear as it
is now in the
stable
version..
Another
remark
concerns the
release number
.. Are the e4
platform and
tools always
considered as
incubation
projects ? In
this case
industry will
not adopt it
easily.. It is
really the
moment to have
a 1.0 e4 tools
version. I
know it is
psychological
but it is
important.
For input
parts I don ´t
remeber the
discussion
which led to
their
deprecation.
But AFAIK it
would be
possible to
find them by
annotation
analysis
(input part is
a part having
a method
@Persist) ?
This could be
a new api on
partservice to
get them ?
I
did some
testing and I
think we can
'release'
this. We can
address Tom's
concerns along
the way. I
tested also
the live
editor and did
not notice any
freezing.
The editor
currently
allows to add
dialogs &
wizards who
are
provisional
APIs,
shouldn't the
tooling show
this to the
user?
Same goes for
InputPart
which is
marked as
deprecated -
although I
voted
against that
deprecation -
and should be
shown like
this!
I also just
fixed a minor
problem with
CompositePart
part which now
allows you to
set the title,
icon, ... .
Tom
On 23.07.14
18:00, Lars
Vogel wrote:
> It is not
yet solved,
but Steven
found a
workaround. I
recently
noticed
> that
keybinding for
cut and paste
are also not
working. I
think we need
> to fix
that least the
keybinding
thing. I plan
to look at
that next week
> (if no
one else fixes
it before
that).
>
> Best
regards, Lars
>
>
>
2014-07-22
15:59
GMT+02:00 Paul
Webster <pwebster@xxxxxxxxxxxxxxxxxxx
>
<mailto:lars.vogel@xxxxxxxxx>>
wrote:
>
>
Hi,
>
> I
gave the e4
tools a quick
test and if I
open the "Live
model
>
editor" the
IDE freezes
(reacts very
slowly). Can
someone
retest?
>
>
Bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=439511
> I
think we
should wait
with
publishing the
tools to the
market
>
place until
this is fixed.
>
>
>
What's the
status of
this? It's
holding up our
0.16 stable
checkpoint.
>
>
Later,
> Paul
>
> --
> Paul
Webster
> Hi
floor. Make
me a sammich!
- GIR
>
>
_______________________________________________
>
e4-dev mailing
list