Hi David,
This is a very interesting, getting back to the first principles. The idea
of a separate "tab through the fields type of thing" View Model to 'give
birth' to an object does make good sense to me, it fills that purpose and
that purpose only. The whole issue of 'edit mode' on a domain
Dan,
I mean the context of the application.
The idea is the following:
We package the application using mvn package, where we get the war file the
application.
In this case we have the simpleapp.war file, which deployed in an
application server.
So far so good.
The wicket viewer works fine,
Hi,
Just to add an architectural perspective - I think you are all right and all
wrong at the same time ;).
Dan is absolutely right if he constrains his comments to Domain Objects (which
I believe is the case).
I think the framework should enforce the Naked Object principles (which are in
turn
Which context? There are many...
On 25 May 2016 9:58 pm, "Pedro Alba" wrote:
> Hi.
> I could help with an explanation of how the context of an application is
> changed in isis apache.
>
> Thank you.
> --
>
> [image: Logo]
>
> *Pedro Antonio Alba *
> *Senior Development
Dan,
After a quick look, I can see why you are considering nowicket. I particularly
like these features:
- DDD and NO incorporated too. In line with ISIS.
- Keep the automatic generation of forms from model ISIS concept.
- You customize forms by using HTML, instead of a domain specific language
Hi.
I could help with an explanation of how the context of an application is
changed in isis apache.
Thank you.
--
[image: Logo]
*Pedro Antonio Alba *
*Senior Development Analyst*
Tel: (57) 1 703 17 77
Cel: (57) 301 3379810
E-mail: pedro.a...@ticxar.com
Calle 93 # 19b - 66 Ofc 202
Bogotá D.C.,
Good input, thanks.
My experience both with Estatio (4 years) but also with the big Naked
Objects system in Ireland (12 years) is that actions only is good enough in
the vast majority of cases ; and where bulk input is genuinely needed, then
we can usually address it with a little lateral
Hello. I have to agree with Steve and Hector. In my experience creating
and implementing ERP and large Merchandise Management systems, the
ability to change all fields within a TAB combined with in-line row
entry and editing is a must in a system where you handle a large volume
of transactional
thanks Joerg
On Wed, May 25, 2016 at 9:21 PM, Dan Haywood
wrote:
> Thanks for checking this out, Joerg.
>
> Cheers,
> Dan
> On 25 May 2016 08:41, "Rade, Joerg / Kuehne + Nagel / Ham GI-DP" <
> joerg.r...@kuehne-nagel.com> wrote:
>
> > I just logged in
Thanks for checking this out, Joerg.
Cheers,
Dan
On 25 May 2016 08:41, "Rade, Joerg / Kuehne + Nagel / Ham GI-DP" <
joerg.r...@kuehne-nagel.com> wrote:
> I just logged in successfully.
>
> There is 'a' red GUI element labeled "Create | v" which actually consists
> of a Button 'Create' and a
Thanks a lot for the explanation and links, Dan. I think I understand this
a bit better now (missed the fact that there needs to be an additional
properties-file for the component-html file etc. -- complete wicket "noob"
here). As soon as I am "geared up" for github-pull requests I hope I can
I just logged in successfully.
There is 'a' red GUI element labeled "Create | v" which actually consists of a
Button 'Create' and a Dropdown 'v'.
Both have their own set of actions.
You have to press the Button when you want to raise an issue.
I recall that I was puzzled with this design as
12 matches
Mail list logo