You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by Dan Haywood <da...@haywood-associates.co.uk> on 2015/02/02 23:24:32 UTC
Considering merging the Wicket viewer into Core framework
Hi folks,
Over the last few releases we've been slowly rationalizing the various
Maven modules, and for 1.8.0 I'd like to go one further step and merge the
Wicket viewer into core also.
* it's the defacto (human usable) UI for Isis
* the use cases that it supports are to a large extent driving the
evolution of Isis' metamodel
* it simplifies the release process (hopefully will encourage us committers
to do more frequent releases)
>From a user (ie programmer) perspective, the impact will be that some of
the Maven dependencies will change. We'll update the archetypes though to
make it easy to see the changes.
I'll leave this thread open a few days to allow opinions to be aired; if I
hear nothing then will assume lazy consensus.
Thx
Dan
Re: Considering merging the Wicket viewer into Core framework
Posted by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>.
ok for me also.
Cheers,
Oscar
> El 3/2/2015, a las 15:23, Kevin Meyer <ke...@kmz.co.za> escribió:
>
> No objections from me.
> Cheers,
> Kevin
>
> On 2 February 2015 23:24:32 CET, Dan Haywood <da...@haywood-associates.co.uk> wrote:
>> Hi folks,
>>
>> Over the last few releases we've been slowly rationalizing the various
>> Maven modules, and for 1.8.0 I'd like to go one further step and merge
>> the
>> Wicket viewer into core also.
>>
>> * it's the defacto (human usable) UI for Isis
>> * the use cases that it supports are to a large extent driving the
>> evolution of Isis' metamodel
>> * it simplifies the release process (hopefully will encourage us
>> committers
>> to do more frequent releases)
>>
>> From a user (ie programmer) perspective, the impact will be that some
>> of
>> the Maven dependencies will change. We'll update the archetypes though
>> to
>> make it easy to see the changes.
>>
>> I'll leave this thread open a few days to allow opinions to be aired;
>> if I
>> hear nothing then will assume lazy consensus.
>>
>> Thx
>> Dan
>
> --
> Sent from my phone with K-9 Mail.
> Please excuse my brevity.
Óscar Bou Bou
Responsable de Producto
Auditor Jefe de Certificación ISO 27001 en BSI
CISA, CRISC, APMG ISO 20000, ITIL-F
902 900 231 / 620 267 520
http://www.twitter.com/oscarbou <http://www.twitter.com/oscarbou>
http://es.linkedin.com/in/oscarbou <http://es.linkedin.com/in/oscarbou>
http://www.GesConsultor.com <http://www.gesconsultor.com/>
Este mensaje y los ficheros anexos son confidenciales. Los mismos contienen información reservada que no puede ser difundida. Si usted ha recibido este correo por error, tenga la amabilidad de eliminarlo de su sistema y avisar al remitente mediante reenvío a su dirección electrónica; no deberá copiar el mensaje ni divulgar su contenido a ninguna persona.
Su dirección de correo electrónico junto a sus datos personales constan en un fichero titularidad de Gesdatos Software, S.L. cuya finalidad es la de mantener el contacto con Ud. Si quiere saber de qué información disponemos de Ud., modificarla, y en su caso, cancelarla, puede hacerlo enviando un escrito al efecto, acompañado de una fotocopia de su D.N.I. a la siguiente dirección: Gesdatos Software, S.L. , Paseo de la Castellana, 153 bajo - 28046 (Madrid), y Avda. Cortes Valencianas num. 50, 1ºC - 46015 (Valencia). Asimismo, es su responsabilidad comprobar que este mensaje o sus archivos adjuntos no contengan virus informáticos, y en caso que los tuvieran eliminarlos.
Re: Considering merging the Wicket viewer into Core framework
Posted by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>.
ok for me also.
Cheers,
Oscar
> El 3/2/2015, a las 15:23, Kevin Meyer <ke...@kmz.co.za> escribió:
>
> No objections from me.
> Cheers,
> Kevin
>
> On 2 February 2015 23:24:32 CET, Dan Haywood <da...@haywood-associates.co.uk> wrote:
>> Hi folks,
>>
>> Over the last few releases we've been slowly rationalizing the various
>> Maven modules, and for 1.8.0 I'd like to go one further step and merge
>> the
>> Wicket viewer into core also.
>>
>> * it's the defacto (human usable) UI for Isis
>> * the use cases that it supports are to a large extent driving the
>> evolution of Isis' metamodel
>> * it simplifies the release process (hopefully will encourage us
>> committers
>> to do more frequent releases)
>>
>> From a user (ie programmer) perspective, the impact will be that some
>> of
>> the Maven dependencies will change. We'll update the archetypes though
>> to
>> make it easy to see the changes.
>>
>> I'll leave this thread open a few days to allow opinions to be aired;
>> if I
>> hear nothing then will assume lazy consensus.
>>
>> Thx
>> Dan
>
> --
> Sent from my phone with K-9 Mail.
> Please excuse my brevity.
Óscar Bou Bou
Responsable de Producto
Auditor Jefe de Certificación ISO 27001 en BSI
CISA, CRISC, APMG ISO 20000, ITIL-F
902 900 231 / 620 267 520
http://www.twitter.com/oscarbou <http://www.twitter.com/oscarbou>
http://es.linkedin.com/in/oscarbou <http://es.linkedin.com/in/oscarbou>
http://www.GesConsultor.com <http://www.gesconsultor.com/>
Este mensaje y los ficheros anexos son confidenciales. Los mismos contienen información reservada que no puede ser difundida. Si usted ha recibido este correo por error, tenga la amabilidad de eliminarlo de su sistema y avisar al remitente mediante reenvío a su dirección electrónica; no deberá copiar el mensaje ni divulgar su contenido a ninguna persona.
Su dirección de correo electrónico junto a sus datos personales constan en un fichero titularidad de Gesdatos Software, S.L. cuya finalidad es la de mantener el contacto con Ud. Si quiere saber de qué información disponemos de Ud., modificarla, y en su caso, cancelarla, puede hacerlo enviando un escrito al efecto, acompañado de una fotocopia de su D.N.I. a la siguiente dirección: Gesdatos Software, S.L. , Paseo de la Castellana, 153 bajo - 28046 (Madrid), y Avda. Cortes Valencianas num. 50, 1ºC - 46015 (Valencia). Asimismo, es su responsabilidad comprobar que este mensaje o sus archivos adjuntos no contengan virus informáticos, y en caso que los tuvieran eliminarlos.
Re: Considering merging the Wicket viewer into Core framework
Posted by Kevin Meyer <ke...@kmz.co.za>.
No objections from me.
Cheers,
Kevin
On 2 February 2015 23:24:32 CET, Dan Haywood <da...@haywood-associates.co.uk> wrote:
>Hi folks,
>
>Over the last few releases we've been slowly rationalizing the various
>Maven modules, and for 1.8.0 I'd like to go one further step and merge
>the
>Wicket viewer into core also.
>
>* it's the defacto (human usable) UI for Isis
>* the use cases that it supports are to a large extent driving the
>evolution of Isis' metamodel
>* it simplifies the release process (hopefully will encourage us
>committers
>to do more frequent releases)
>
>From a user (ie programmer) perspective, the impact will be that some
>of
>the Maven dependencies will change. We'll update the archetypes though
>to
>make it easy to see the changes.
>
>I'll leave this thread open a few days to allow opinions to be aired;
>if I
>hear nothing then will assume lazy consensus.
>
>Thx
>Dan
--
Sent from my phone with K-9 Mail.
Please excuse my brevity.
Re: Considering merging the Wicket viewer into Core framework
Posted by AR <ha...@gmail.com>.
Hi Martin,
thx, now I understand it. Dependencies changes are not problematic for us,
so I vote: +1.
Am 03.02.2015 um 13:15 schrieb Martin Grigorov <mg...@apache.org>:
> Hi ARI,
>
>> Hi Dan,
>>
>> I have started to promote isis for an internal sales application, which
>> will go productive next week. Our company mainly developing vaadin
>> applications, the next steps to push isis further in our company would be
>> to developing a vaadin viewer. That why I would vote for not merging Wicket
>> into the Core.
>>
>
> Moving Wicket viewer to core means that some Maven groupId and/or
> artifactId will change for the users. Nothing more.
> For Isis developers this is not an actual change.
> For Isis release manager the change will just simplify the process.
>
> For your Vaadin based application this means that you won't add
> wicket-viewer.jar in your dependencies. That's all.
>
>
>>
>> Greetings, ARI (H2000)
>>
>> Am 02.02.2015 um 23:24 schrieb Dan Haywood <da...@haywood-associates.co.uk>:
>>
>>> Hi folks,
>>>
>>> Over the last few releases we've been slowly rationalizing the various
>>> Maven modules, and for 1.8.0 I'd like to go one further step and merge
>> the
>>> Wicket viewer into core also.
>>>
>>> * it's the defacto (human usable) UI for Isis
>>> * the use cases that it supports are to a large extent driving the
>>> evolution of Isis' metamodel
>>> * it simplifies the release process (hopefully will encourage us
>> committers
>>> to do more frequent releases)
>>>
>>> From a user (ie programmer) perspective, the impact will be that some of
>>> the Maven dependencies will change. We'll update the archetypes though
>> to
>>> make it easy to see the changes.
>>>
>>> I'll leave this thread open a few days to allow opinions to be aired; if
>> I
>>> hear nothing then will assume lazy consensus.
>>>
>>> Thx
>>> Dan
>>
>>
Re: Considering merging the Wicket viewer into Core framework
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
OK, thanks for the vote, ARI.
Nice to hear about your plans for a Vaadin viewer... it's something we've
kicked around developing also. Would be very happy to support your company
develop it.
As Martin says, there shouldn't be any major impact if we did this change ;
just reflects the current reality of the Wicket viewer as the defacto
human-usable UI.
If there were a Vaadin viewer of similar fidelity then I would imagine we'd
want to revisit.
Thx
Dan
On 3 February 2015 at 12:15, Martin Grigorov <mg...@apache.org> wrote:
> Hi ARI,
>
> On Tue, Feb 3, 2015 at 1:48 PM, AR <ha...@gmail.com> wrote:
>
> > Hi Dan,
> >
> > I have started to promote isis for an internal sales application, which
> > will go productive next week. Our company mainly developing vaadin
> > applications, the next steps to push isis further in our company would be
> > to developing a vaadin viewer. That why I would vote for not merging
> Wicket
> > into the Core.
> >
>
> Moving Wicket viewer to core means that some Maven groupId and/or
> artifactId will change for the users. Nothing more.
> For Isis developers this is not an actual change.
> For Isis release manager the change will just simplify the process.
>
> For your Vaadin based application this means that you won't add
> wicket-viewer.jar in your dependencies. That's all.
>
>
> >
> > Greetings, ARI (H2000)
> >
> > Am 02.02.2015 um 23:24 schrieb Dan Haywood <dan@haywood-associates.co.uk
> >:
> >
> > > Hi folks,
> > >
> > > Over the last few releases we've been slowly rationalizing the various
> > > Maven modules, and for 1.8.0 I'd like to go one further step and merge
> > the
> > > Wicket viewer into core also.
> > >
> > > * it's the defacto (human usable) UI for Isis
> > > * the use cases that it supports are to a large extent driving the
> > > evolution of Isis' metamodel
> > > * it simplifies the release process (hopefully will encourage us
> > committers
> > > to do more frequent releases)
> > >
> > > From a user (ie programmer) perspective, the impact will be that some
> of
> > > the Maven dependencies will change. We'll update the archetypes though
> > to
> > > make it easy to see the changes.
> > >
> > > I'll leave this thread open a few days to allow opinions to be aired;
> if
> > I
> > > hear nothing then will assume lazy consensus.
> > >
> > > Thx
> > > Dan
> >
> >
>
Re: Considering merging the Wicket viewer into Core framework
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
OK, thanks for the vote, ARI.
Nice to hear about your plans for a Vaadin viewer... it's something we've
kicked around developing also. Would be very happy to support your company
develop it.
As Martin says, there shouldn't be any major impact if we did this change ;
just reflects the current reality of the Wicket viewer as the defacto
human-usable UI.
If there were a Vaadin viewer of similar fidelity then I would imagine we'd
want to revisit.
Thx
Dan
On 3 February 2015 at 12:15, Martin Grigorov <mg...@apache.org> wrote:
> Hi ARI,
>
> On Tue, Feb 3, 2015 at 1:48 PM, AR <ha...@gmail.com> wrote:
>
> > Hi Dan,
> >
> > I have started to promote isis for an internal sales application, which
> > will go productive next week. Our company mainly developing vaadin
> > applications, the next steps to push isis further in our company would be
> > to developing a vaadin viewer. That why I would vote for not merging
> Wicket
> > into the Core.
> >
>
> Moving Wicket viewer to core means that some Maven groupId and/or
> artifactId will change for the users. Nothing more.
> For Isis developers this is not an actual change.
> For Isis release manager the change will just simplify the process.
>
> For your Vaadin based application this means that you won't add
> wicket-viewer.jar in your dependencies. That's all.
>
>
> >
> > Greetings, ARI (H2000)
> >
> > Am 02.02.2015 um 23:24 schrieb Dan Haywood <dan@haywood-associates.co.uk
> >:
> >
> > > Hi folks,
> > >
> > > Over the last few releases we've been slowly rationalizing the various
> > > Maven modules, and for 1.8.0 I'd like to go one further step and merge
> > the
> > > Wicket viewer into core also.
> > >
> > > * it's the defacto (human usable) UI for Isis
> > > * the use cases that it supports are to a large extent driving the
> > > evolution of Isis' metamodel
> > > * it simplifies the release process (hopefully will encourage us
> > committers
> > > to do more frequent releases)
> > >
> > > From a user (ie programmer) perspective, the impact will be that some
> of
> > > the Maven dependencies will change. We'll update the archetypes though
> > to
> > > make it easy to see the changes.
> > >
> > > I'll leave this thread open a few days to allow opinions to be aired;
> if
> > I
> > > hear nothing then will assume lazy consensus.
> > >
> > > Thx
> > > Dan
> >
> >
>
Re: Considering merging the Wicket viewer into Core framework
Posted by Martin Grigorov <mg...@apache.org>.
Hi ARI,
On Tue, Feb 3, 2015 at 1:48 PM, AR <ha...@gmail.com> wrote:
> Hi Dan,
>
> I have started to promote isis for an internal sales application, which
> will go productive next week. Our company mainly developing vaadin
> applications, the next steps to push isis further in our company would be
> to developing a vaadin viewer. That why I would vote for not merging Wicket
> into the Core.
>
Moving Wicket viewer to core means that some Maven groupId and/or
artifactId will change for the users. Nothing more.
For Isis developers this is not an actual change.
For Isis release manager the change will just simplify the process.
For your Vaadin based application this means that you won't add
wicket-viewer.jar in your dependencies. That's all.
>
> Greetings, ARI (H2000)
>
> Am 02.02.2015 um 23:24 schrieb Dan Haywood <da...@haywood-associates.co.uk>:
>
> > Hi folks,
> >
> > Over the last few releases we've been slowly rationalizing the various
> > Maven modules, and for 1.8.0 I'd like to go one further step and merge
> the
> > Wicket viewer into core also.
> >
> > * it's the defacto (human usable) UI for Isis
> > * the use cases that it supports are to a large extent driving the
> > evolution of Isis' metamodel
> > * it simplifies the release process (hopefully will encourage us
> committers
> > to do more frequent releases)
> >
> > From a user (ie programmer) perspective, the impact will be that some of
> > the Maven dependencies will change. We'll update the archetypes though
> to
> > make it easy to see the changes.
> >
> > I'll leave this thread open a few days to allow opinions to be aired; if
> I
> > hear nothing then will assume lazy consensus.
> >
> > Thx
> > Dan
>
>
Re: Considering merging the Wicket viewer into Core framework
Posted by Martin Grigorov <mg...@apache.org>.
Hi ARI,
On Tue, Feb 3, 2015 at 1:48 PM, AR <ha...@gmail.com> wrote:
> Hi Dan,
>
> I have started to promote isis for an internal sales application, which
> will go productive next week. Our company mainly developing vaadin
> applications, the next steps to push isis further in our company would be
> to developing a vaadin viewer. That why I would vote for not merging Wicket
> into the Core.
>
Moving Wicket viewer to core means that some Maven groupId and/or
artifactId will change for the users. Nothing more.
For Isis developers this is not an actual change.
For Isis release manager the change will just simplify the process.
For your Vaadin based application this means that you won't add
wicket-viewer.jar in your dependencies. That's all.
>
> Greetings, ARI (H2000)
>
> Am 02.02.2015 um 23:24 schrieb Dan Haywood <da...@haywood-associates.co.uk>:
>
> > Hi folks,
> >
> > Over the last few releases we've been slowly rationalizing the various
> > Maven modules, and for 1.8.0 I'd like to go one further step and merge
> the
> > Wicket viewer into core also.
> >
> > * it's the defacto (human usable) UI for Isis
> > * the use cases that it supports are to a large extent driving the
> > evolution of Isis' metamodel
> > * it simplifies the release process (hopefully will encourage us
> committers
> > to do more frequent releases)
> >
> > From a user (ie programmer) perspective, the impact will be that some of
> > the Maven dependencies will change. We'll update the archetypes though
> to
> > make it easy to see the changes.
> >
> > I'll leave this thread open a few days to allow opinions to be aired; if
> I
> > hear nothing then will assume lazy consensus.
> >
> > Thx
> > Dan
>
>
Re: Considering merging the Wicket viewer into Core framework
Posted by AR <ha...@gmail.com>.
Hi Dan,
I have started to promote isis for an internal sales application, which will go productive next week. Our company mainly developing vaadin applications, the next steps to push isis further in our company would be to developing a vaadin viewer. That why I would vote for not merging Wicket into the Core.
Greetings, ARI (H2000)
Am 02.02.2015 um 23:24 schrieb Dan Haywood <da...@haywood-associates.co.uk>:
> Hi folks,
>
> Over the last few releases we've been slowly rationalizing the various
> Maven modules, and for 1.8.0 I'd like to go one further step and merge the
> Wicket viewer into core also.
>
> * it's the defacto (human usable) UI for Isis
> * the use cases that it supports are to a large extent driving the
> evolution of Isis' metamodel
> * it simplifies the release process (hopefully will encourage us committers
> to do more frequent releases)
>
> From a user (ie programmer) perspective, the impact will be that some of
> the Maven dependencies will change. We'll update the archetypes though to
> make it easy to see the changes.
>
> I'll leave this thread open a few days to allow opinions to be aired; if I
> hear nothing then will assume lazy consensus.
>
> Thx
> Dan
Re: Considering merging the Wicket viewer into Core framework
Posted by Kevin Meyer <ke...@kmz.co.za>.
No objections from me.
Cheers,
Kevin
On 2 February 2015 23:24:32 CET, Dan Haywood <da...@haywood-associates.co.uk> wrote:
>Hi folks,
>
>Over the last few releases we've been slowly rationalizing the various
>Maven modules, and for 1.8.0 I'd like to go one further step and merge
>the
>Wicket viewer into core also.
>
>* it's the defacto (human usable) UI for Isis
>* the use cases that it supports are to a large extent driving the
>evolution of Isis' metamodel
>* it simplifies the release process (hopefully will encourage us
>committers
>to do more frequent releases)
>
>From a user (ie programmer) perspective, the impact will be that some
>of
>the Maven dependencies will change. We'll update the archetypes though
>to
>make it easy to see the changes.
>
>I'll leave this thread open a few days to allow opinions to be aired;
>if I
>hear nothing then will assume lazy consensus.
>
>Thx
>Dan
--
Sent from my phone with K-9 Mail.
Please excuse my brevity.