You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by Boris Toninski <bo...@orangedot.bg> on 2014/12/16 19:22:38 UTC
Edit data without having to click on the "Update" button
Hi guys,
what I have seen till now in the demos is that when you open a form for
a entity, all fields are disabled. You have to firs click on the edit
button to edit the properties.
Is this the recommended way of using Isis. Would there be some problems
or difficulties if the form is ready to be edited when opened?
Thanks in advance!
Re: Edit data without having to click on the "Update" button
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
On 16 December 2014 at 21:48, GESCONSULTOR <o....@gesconsultor.com> wrote:
>
> Sorry about expressing my opinion here :)
>
>
Please do continue to do so :-)
> I've always love the way Jora works, editing each field without needing
> the update button.
>
s/Jora/Jira ... presumably
> That way it shouldn't be needed to always implement actions, as the
> property setter can be intercepted by ISIS as the setter is wrapped inside
> the viewer.
>
>
I'm not suggesting that we get rid of property setters either. And yes,
the modifyXxx and clearXxx are the places to put additoinal business logic
(they represent the API, while the getter/setter is really the SPI for the
viewer and for the objectstore).
So Isis as a platform needs to support this use case.
But it's also worth noting that with Estatio we've found ourselves moving
away from property setters, to the extent that we (or rather, Jeroen)
eventually got rid of them altogether. One reason is that there are,
indeed, many quite complex use cases in that product. But the other reason
we got rid of them is also very interesting, I think: to drive out the user
requirements.
To backfill on this a bit... Estatio didn't start out with an empty
database, rather data was migrated (via Isis' REST API, in fact) from the
legacy packaged system. Originally Jeroen started out leaving things as
editable, but discovered that the users used the app somewhat like a
spreadsheet, so that the business rules would remain in their heads. By
making the data immutable, it forced the discussion of "why do you want to
edit the data"... from which the real objectives could be gleaned. The
point being, of course, that if an action was required, then it could be
implemented and deployed very quickly (often the same business day).
> Actions would only be needed for complex use cases, such as updating
> multiple properties or entities from it.
>
> if a modifyXXX or clearXXXis present it would execute custom logic without
> needing and explicit action.
>
> Do you agree?
>
>
But yes, this is also a use case we should support.
One gap though is that we don't yet capture @Command for property edits, so
we don't get the same richness of profiling/auditing, nor do we get the
ability to execute such edits "in the background". Perhaps that's less
important.
Also... for completeness, Isis / Naked Objects has always also supported
the concept of mutable collections; it's just that the Wicket viewer has
never implemented them (the Restful Objects viewer does, though). In code
these correspond to addToXxx and removeFromXxx supporting methods (along
with hideXxx, disableXxx, also validateAddToXxx and validateRemoveFromXxx).
> I think it's really interesting to discuss it here as it would be a
> completely new paradigm.
>
>
Certainly having the ability to edit a single field at a time would be a
better user experience. Don't think it's a new paradigm though, just a
better UI to an old concept.
Cheers
Dan
> Thanks for raising this question.
>
>
> > El 16/12/2014, a las 21:59, Dan Haywood <da...@haywood-associates.co.uk>
> escribió:
> >
> > @Boris,
> > Although being able to edit properties is initially convenient, what
> we've
> > found "in real life" (that is, Estatio) is that most if not all
> operations
> > should be modelled as actions.
> >
> > Using actions allows you to more accurately capture the use cases/goals
> of
> > the user. They also support @Command and @PublishedAction which are
> great
> > for both auditing/profiling and also system-to-system integration
> > scenarios.
> >
> > But did I misunderstand your question, please say...
> >
> >
> > @Martin
> > In ISIS-784 [1] we discussed an enhancement so that each property could
> be
> > edited by itself, rather than placing the entire form into an edit mode.
> > On that ticket is a link to a widget library that I think you found?
> > Anyway, I'm still keen on that, I think Jeroen is too.
> >
> >
> > Cheers
> > Dan
> >
> >
> > [1] https://issues.apache.org/jira/browse/ISIS-784
> >
> >> On 16 December 2014 at 20:28, Martin Grigorov <mg...@apache.org>
> wrote:
> >>
> >> Hi,
> >>
> >> I have asked myself the same question recently.
> >>
> >> Martin Grigorov
> >> Wicket Training and Consulting
> >> https://twitter.com/mtgrigorov
> >>
> >> On Tue, Dec 16, 2014 at 8:22 PM, Boris Toninski <
> >> boris.toninski@orangedot.bg
> >>> wrote:
> >>>
> >>> Hi guys,
> >>>
> >>> what I have seen till now in the demos is that when you open a form
> for a
> >>> entity, all fields are disabled. You have to firs click on the edit
> >> button
> >>> to edit the properties.
> >>>
> >>> Is this the recommended way of using Isis. Would there be some problems
> >> or
> >>> difficulties if the form is ready to be edited when opened?
> >>>
> >>> Thanks in advance!
> >>
>
Re: Edit data without having to click on the "Update" button
Posted by GESCONSULTOR <o....@gesconsultor.com>.
Sorry about expressing my opinion here :)
I've always love the way Jora works, editing each field without needing the update button.
That way it shouldn't be needed to always implement actions, as the property setter can be intercepted by ISIS as the setter is wrapped inside the viewer.
Actions would only be needed for complex use cases, such as updating multiple properties or entities from it.
if a modifyXXX or clearXXXis present it would execute custom logic without needing and explicit action.
Do you agree?
I think it's really interesting to discuss it here as it would be a completely new paradigm.
Thanks for raising this question.
> El 16/12/2014, a las 21:59, Dan Haywood <da...@haywood-associates.co.uk> escribió:
>
> @Boris,
> Although being able to edit properties is initially convenient, what we've
> found "in real life" (that is, Estatio) is that most if not all operations
> should be modelled as actions.
>
> Using actions allows you to more accurately capture the use cases/goals of
> the user. They also support @Command and @PublishedAction which are great
> for both auditing/profiling and also system-to-system integration
> scenarios.
>
> But did I misunderstand your question, please say...
>
>
> @Martin
> In ISIS-784 [1] we discussed an enhancement so that each property could be
> edited by itself, rather than placing the entire form into an edit mode.
> On that ticket is a link to a widget library that I think you found?
> Anyway, I'm still keen on that, I think Jeroen is too.
>
>
> Cheers
> Dan
>
>
> [1] https://issues.apache.org/jira/browse/ISIS-784
>
>> On 16 December 2014 at 20:28, Martin Grigorov <mg...@apache.org> wrote:
>>
>> Hi,
>>
>> I have asked myself the same question recently.
>>
>> Martin Grigorov
>> Wicket Training and Consulting
>> https://twitter.com/mtgrigorov
>>
>> On Tue, Dec 16, 2014 at 8:22 PM, Boris Toninski <
>> boris.toninski@orangedot.bg
>>> wrote:
>>>
>>> Hi guys,
>>>
>>> what I have seen till now in the demos is that when you open a form for a
>>> entity, all fields are disabled. You have to firs click on the edit
>> button
>>> to edit the properties.
>>>
>>> Is this the recommended way of using Isis. Would there be some problems
>> or
>>> difficulties if the form is ready to be edited when opened?
>>>
>>> Thanks in advance!
>>
Re: Edit data without having to click on the "Update" button
Posted by Boris Toninski <bo...@orangedot.bg>.
Thanks Dan
On 12/17/2014 12:08 PM, Dan Haywood wrote:
> OK, well we'll aim for ISIS-784. The user experience should be similar to
> using JIRA, I think... click in the field you want to edit, and just that
> becomes editable. Click away and it'll save.
>
> Cheers
> Dan
>
>
> On 17 December 2014 at 10:03, Boris Toninski <bo...@orangedot.bg>
> wrote:
>> ISIS-784 looks really nice. May be we can use it if it is implemented.
>>
>> Here is the scenario I was trying to explain. I'm using the TODO demo as
>> example.
>>
>> 1. Open the TODO demo
>> 2. From menu select "ALL TO DOs"
>> 3. Pick any todo and click on the icon near its description.
>> 4. A page displaying the selected todo properties is opened.
>> Currently the user has to click on the EDIT button in order to start
>> editing the fields.
>> What we may need is the form to be opened directly in editing mode, so the
>> user do not have to click on the "EDIT" button first.
>>
>> Thanks,
>> Boris
>>
>>
>> On 12/17/2014 11:19 AM, Dan Haywood wrote:
>>
>>> On 17 December 2014 at 09:12, Boris Toninski <boris.toninski@orangedot.bg
>>> wrote:
>>>
>>>>
>>>> Would it be possible to implement it?
>>>>
>>> Could you spell out exactly what you envisage. Is it any different from
>>> what we describe in ISIS-784 [1] ?
>>>
>>> - If yes, tell us what's needed. Pictures/sketches/screenshots etc would
>>> be helpful.
>>>
>>> - If not, and ISIS-784 would suffice, then I imagine we'll be implementing
>>> that ticket in the next few months. One of the nice things about Isis is
>>> that there is no impact to the domain code, so it needn't impact your
>>> development timelines.
>>>
>>> Thx
>>> Dan
>>>
>>>
>>>
>>>
>>> [1] https://issues.apache.org/jira/browse/ISIS-784
>>>
>>>
>>>
>>> If yes is there any risk of doing it. I suppose this way of using it is
>>>> not tested so much, so may be some problems can appear. Also what
>>>> features
>>>> we will lose, you mentioned about auditing/profiling.
>>>>
>>>> Thanks,
>>>> Boris
>>>>
>>>>
>>>> On 12/16/2014 10:59 PM, Dan Haywood wrote:
>>>>
>>>> @Boris,
>>>>> Although being able to edit properties is initially convenient, what
>>>>> we've
>>>>> found "in real life" (that is, Estatio) is that most if not all
>>>>> operations
>>>>> should be modelled as actions.
>>>>>
>>>>> Using actions allows you to more accurately capture the use cases/goals
>>>>> of
>>>>> the user. They also support @Command and @PublishedAction which are
>>>>> great
>>>>> for both auditing/profiling and also system-to-system integration
>>>>> scenarios.
>>>>>
>>>>> But did I misunderstand your question, please say...
>>>>>
>>>>>
>>>>> @Martin
>>>>> In ISIS-784 [1] we discussed an enhancement so that each property could
>>>>> be
>>>>> edited by itself, rather than placing the entire form into an edit mode.
>>>>> On that ticket is a link to a widget library that I think you found?
>>>>> Anyway, I'm still keen on that, I think Jeroen is too.
>>>>>
>>>>>
>>>>> Cheers
>>>>> Dan
>>>>>
>>>>>
>>>>> [1] https://issues.apache.org/jira/browse/ISIS-784
>>>>>
>>>>> On 16 December 2014 at 20:28, Martin Grigorov <mg...@apache.org>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>> I have asked myself the same question recently.
>>>>>>
>>>>>> Martin Grigorov
>>>>>> Wicket Training and Consulting
>>>>>> https://twitter.com/mtgrigorov
>>>>>>
>>>>>> On Tue, Dec 16, 2014 at 8:22 PM, Boris Toninski <
>>>>>> boris.toninski@orangedot.bg
>>>>>>
>>>>>> wrote:
>>>>>>> Hi guys,
>>>>>>>
>>>>>>> what I have seen till now in the demos is that when you open a form
>>>>>>> for
>>>>>>> a
>>>>>>> entity, all fields are disabled. You have to firs click on the edit
>>>>>>>
>>>>>>> button
>>>>>> to edit the properties.
>>>>>>> Is this the recommended way of using Isis. Would there be some
>>>>>>> problems
>>>>>>>
>>>>>>> or
>>>>>> difficulties if the form is ready to be edited when opened?
>>>>>>> Thanks in advance!
>>>>>>>
>>>>>>>
>>>>>>>
Re: Edit data without having to click on the "Update" button
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
OK, well we'll aim for ISIS-784. The user experience should be similar to
using JIRA, I think... click in the field you want to edit, and just that
becomes editable. Click away and it'll save.
Cheers
Dan
On 17 December 2014 at 10:03, Boris Toninski <bo...@orangedot.bg>
wrote:
>
> ISIS-784 looks really nice. May be we can use it if it is implemented.
>
> Here is the scenario I was trying to explain. I'm using the TODO demo as
> example.
>
> 1. Open the TODO demo
> 2. From menu select "ALL TO DOs"
> 3. Pick any todo and click on the icon near its description.
> 4. A page displaying the selected todo properties is opened.
> Currently the user has to click on the EDIT button in order to start
> editing the fields.
> What we may need is the form to be opened directly in editing mode, so the
> user do not have to click on the "EDIT" button first.
>
> Thanks,
> Boris
>
>
> On 12/17/2014 11:19 AM, Dan Haywood wrote:
>
>> On 17 December 2014 at 09:12, Boris Toninski <boris.toninski@orangedot.bg
>> >
>> wrote:
>>
>>>
>>>
>>> Would it be possible to implement it?
>>>
>>
>> Could you spell out exactly what you envisage. Is it any different from
>> what we describe in ISIS-784 [1] ?
>>
>> - If yes, tell us what's needed. Pictures/sketches/screenshots etc would
>> be helpful.
>>
>> - If not, and ISIS-784 would suffice, then I imagine we'll be implementing
>> that ticket in the next few months. One of the nice things about Isis is
>> that there is no impact to the domain code, so it needn't impact your
>> development timelines.
>>
>> Thx
>> Dan
>>
>>
>>
>>
>> [1] https://issues.apache.org/jira/browse/ISIS-784
>>
>>
>>
>> If yes is there any risk of doing it. I suppose this way of using it is
>>> not tested so much, so may be some problems can appear. Also what
>>> features
>>> we will lose, you mentioned about auditing/profiling.
>>>
>>> Thanks,
>>> Boris
>>>
>>>
>>> On 12/16/2014 10:59 PM, Dan Haywood wrote:
>>>
>>> @Boris,
>>>> Although being able to edit properties is initially convenient, what
>>>> we've
>>>> found "in real life" (that is, Estatio) is that most if not all
>>>> operations
>>>> should be modelled as actions.
>>>>
>>>> Using actions allows you to more accurately capture the use cases/goals
>>>> of
>>>> the user. They also support @Command and @PublishedAction which are
>>>> great
>>>> for both auditing/profiling and also system-to-system integration
>>>> scenarios.
>>>>
>>>> But did I misunderstand your question, please say...
>>>>
>>>>
>>>> @Martin
>>>> In ISIS-784 [1] we discussed an enhancement so that each property could
>>>> be
>>>> edited by itself, rather than placing the entire form into an edit mode.
>>>> On that ticket is a link to a widget library that I think you found?
>>>> Anyway, I'm still keen on that, I think Jeroen is too.
>>>>
>>>>
>>>> Cheers
>>>> Dan
>>>>
>>>>
>>>> [1] https://issues.apache.org/jira/browse/ISIS-784
>>>>
>>>> On 16 December 2014 at 20:28, Martin Grigorov <mg...@apache.org>
>>>> wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> I have asked myself the same question recently.
>>>>>
>>>>> Martin Grigorov
>>>>> Wicket Training and Consulting
>>>>> https://twitter.com/mtgrigorov
>>>>>
>>>>> On Tue, Dec 16, 2014 at 8:22 PM, Boris Toninski <
>>>>> boris.toninski@orangedot.bg
>>>>>
>>>>> wrote:
>>>>>>
>>>>>> Hi guys,
>>>>>>
>>>>>> what I have seen till now in the demos is that when you open a form
>>>>>> for
>>>>>> a
>>>>>> entity, all fields are disabled. You have to firs click on the edit
>>>>>>
>>>>>> button
>>>>>
>>>>> to edit the properties.
>>>>>>
>>>>>> Is this the recommended way of using Isis. Would there be some
>>>>>> problems
>>>>>>
>>>>>> or
>>>>>
>>>>> difficulties if the form is ready to be edited when opened?
>>>>>>
>>>>>> Thanks in advance!
>>>>>>
>>>>>>
>>>>>>
>
Re: Edit data without having to click on the "Update" button
Posted by Boris Toninski <bo...@orangedot.bg>.
ISIS-784 looks really nice. May be we can use it if it is implemented.
Here is the scenario I was trying to explain. I'm using the TODO demo as
example.
1. Open the TODO demo
2. From menu select "ALL TO DOs"
3. Pick any todo and click on the icon near its description.
4. A page displaying the selected todo properties is opened.
Currently the user has to click on the EDIT button in order to start
editing the fields.
What we may need is the form to be opened directly in editing mode, so
the user do not have to click on the "EDIT" button first.
Thanks,
Boris
On 12/17/2014 11:19 AM, Dan Haywood wrote:
> On 17 December 2014 at 09:12, Boris Toninski <bo...@orangedot.bg>
> wrote:
>>
>>
>> Would it be possible to implement it?
>
> Could you spell out exactly what you envisage. Is it any different from
> what we describe in ISIS-784 [1] ?
>
> - If yes, tell us what's needed. Pictures/sketches/screenshots etc would
> be helpful.
>
> - If not, and ISIS-784 would suffice, then I imagine we'll be implementing
> that ticket in the next few months. One of the nice things about Isis is
> that there is no impact to the domain code, so it needn't impact your
> development timelines.
>
> Thx
> Dan
>
>
>
>
> [1] https://issues.apache.org/jira/browse/ISIS-784
>
>
>
>> If yes is there any risk of doing it. I suppose this way of using it is
>> not tested so much, so may be some problems can appear. Also what features
>> we will lose, you mentioned about auditing/profiling.
>>
>> Thanks,
>> Boris
>>
>>
>> On 12/16/2014 10:59 PM, Dan Haywood wrote:
>>
>>> @Boris,
>>> Although being able to edit properties is initially convenient, what we've
>>> found "in real life" (that is, Estatio) is that most if not all operations
>>> should be modelled as actions.
>>>
>>> Using actions allows you to more accurately capture the use cases/goals of
>>> the user. They also support @Command and @PublishedAction which are great
>>> for both auditing/profiling and also system-to-system integration
>>> scenarios.
>>>
>>> But did I misunderstand your question, please say...
>>>
>>>
>>> @Martin
>>> In ISIS-784 [1] we discussed an enhancement so that each property could be
>>> edited by itself, rather than placing the entire form into an edit mode.
>>> On that ticket is a link to a widget library that I think you found?
>>> Anyway, I'm still keen on that, I think Jeroen is too.
>>>
>>>
>>> Cheers
>>> Dan
>>>
>>>
>>> [1] https://issues.apache.org/jira/browse/ISIS-784
>>>
>>> On 16 December 2014 at 20:28, Martin Grigorov <mg...@apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have asked myself the same question recently.
>>>>
>>>> Martin Grigorov
>>>> Wicket Training and Consulting
>>>> https://twitter.com/mtgrigorov
>>>>
>>>> On Tue, Dec 16, 2014 at 8:22 PM, Boris Toninski <
>>>> boris.toninski@orangedot.bg
>>>>
>>>>> wrote:
>>>>>
>>>>> Hi guys,
>>>>>
>>>>> what I have seen till now in the demos is that when you open a form for
>>>>> a
>>>>> entity, all fields are disabled. You have to firs click on the edit
>>>>>
>>>> button
>>>>
>>>>> to edit the properties.
>>>>>
>>>>> Is this the recommended way of using Isis. Would there be some problems
>>>>>
>>>> or
>>>>
>>>>> difficulties if the form is ready to be edited when opened?
>>>>>
>>>>> Thanks in advance!
>>>>>
>>>>>
Re: Edit data without having to click on the "Update" button
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
On 17 December 2014 at 09:12, Boris Toninski <bo...@orangedot.bg>
wrote:
>
>
>
> Would it be possible to implement it?
Could you spell out exactly what you envisage. Is it any different from
what we describe in ISIS-784 [1] ?
- If yes, tell us what's needed. Pictures/sketches/screenshots etc would
be helpful.
- If not, and ISIS-784 would suffice, then I imagine we'll be implementing
that ticket in the next few months. One of the nice things about Isis is
that there is no impact to the domain code, so it needn't impact your
development timelines.
Thx
Dan
[1] https://issues.apache.org/jira/browse/ISIS-784
> If yes is there any risk of doing it. I suppose this way of using it is
> not tested so much, so may be some problems can appear. Also what features
> we will lose, you mentioned about auditing/profiling.
>
> Thanks,
> Boris
>
>
> On 12/16/2014 10:59 PM, Dan Haywood wrote:
>
>> @Boris,
>> Although being able to edit properties is initially convenient, what we've
>> found "in real life" (that is, Estatio) is that most if not all operations
>> should be modelled as actions.
>>
>> Using actions allows you to more accurately capture the use cases/goals of
>> the user. They also support @Command and @PublishedAction which are great
>> for both auditing/profiling and also system-to-system integration
>> scenarios.
>>
>> But did I misunderstand your question, please say...
>>
>>
>> @Martin
>> In ISIS-784 [1] we discussed an enhancement so that each property could be
>> edited by itself, rather than placing the entire form into an edit mode.
>> On that ticket is a link to a widget library that I think you found?
>> Anyway, I'm still keen on that, I think Jeroen is too.
>>
>>
>> Cheers
>> Dan
>>
>>
>> [1] https://issues.apache.org/jira/browse/ISIS-784
>>
>> On 16 December 2014 at 20:28, Martin Grigorov <mg...@apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> I have asked myself the same question recently.
>>>
>>> Martin Grigorov
>>> Wicket Training and Consulting
>>> https://twitter.com/mtgrigorov
>>>
>>> On Tue, Dec 16, 2014 at 8:22 PM, Boris Toninski <
>>> boris.toninski@orangedot.bg
>>>
>>>> wrote:
>>>>
>>>> Hi guys,
>>>>
>>>> what I have seen till now in the demos is that when you open a form for
>>>> a
>>>> entity, all fields are disabled. You have to firs click on the edit
>>>>
>>> button
>>>
>>>> to edit the properties.
>>>>
>>>> Is this the recommended way of using Isis. Would there be some problems
>>>>
>>> or
>>>
>>>> difficulties if the form is ready to be edited when opened?
>>>>
>>>> Thanks in advance!
>>>>
>>>>
>
Re: Edit data without having to click on the "Update" button
Posted by Boris Toninski <bo...@orangedot.bg>.
Hi Dan, thanks for replying.
I understand the benefits you have mentioned about not using direct
editing, but my concern is that the team which will use the tool we are
developing may insist to have it. So I'm wondering what options we will
have with Ixis. Would it be possible to implement it? If yes is there
any risk of doing it. I suppose this way of using it is not tested so
much, so may be some problems can appear. Also what features we will
lose, you mentioned about auditing/profiling.
Thanks,
Boris
On 12/16/2014 10:59 PM, Dan Haywood wrote:
> @Boris,
> Although being able to edit properties is initially convenient, what we've
> found "in real life" (that is, Estatio) is that most if not all operations
> should be modelled as actions.
>
> Using actions allows you to more accurately capture the use cases/goals of
> the user. They also support @Command and @PublishedAction which are great
> for both auditing/profiling and also system-to-system integration
> scenarios.
>
> But did I misunderstand your question, please say...
>
>
> @Martin
> In ISIS-784 [1] we discussed an enhancement so that each property could be
> edited by itself, rather than placing the entire form into an edit mode.
> On that ticket is a link to a widget library that I think you found?
> Anyway, I'm still keen on that, I think Jeroen is too.
>
>
> Cheers
> Dan
>
>
> [1] https://issues.apache.org/jira/browse/ISIS-784
>
> On 16 December 2014 at 20:28, Martin Grigorov <mg...@apache.org> wrote:
>> Hi,
>>
>> I have asked myself the same question recently.
>>
>> Martin Grigorov
>> Wicket Training and Consulting
>> https://twitter.com/mtgrigorov
>>
>> On Tue, Dec 16, 2014 at 8:22 PM, Boris Toninski <
>> boris.toninski@orangedot.bg
>>> wrote:
>>>
>>> Hi guys,
>>>
>>> what I have seen till now in the demos is that when you open a form for a
>>> entity, all fields are disabled. You have to firs click on the edit
>> button
>>> to edit the properties.
>>>
>>> Is this the recommended way of using Isis. Would there be some problems
>> or
>>> difficulties if the form is ready to be edited when opened?
>>>
>>> Thanks in advance!
>>>
Re: Edit data without having to click on the "Update" button
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
@Boris,
Although being able to edit properties is initially convenient, what we've
found "in real life" (that is, Estatio) is that most if not all operations
should be modelled as actions.
Using actions allows you to more accurately capture the use cases/goals of
the user. They also support @Command and @PublishedAction which are great
for both auditing/profiling and also system-to-system integration
scenarios.
But did I misunderstand your question, please say...
@Martin
In ISIS-784 [1] we discussed an enhancement so that each property could be
edited by itself, rather than placing the entire form into an edit mode.
On that ticket is a link to a widget library that I think you found?
Anyway, I'm still keen on that, I think Jeroen is too.
Cheers
Dan
[1] https://issues.apache.org/jira/browse/ISIS-784
On 16 December 2014 at 20:28, Martin Grigorov <mg...@apache.org> wrote:
>
> Hi,
>
> I have asked myself the same question recently.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Tue, Dec 16, 2014 at 8:22 PM, Boris Toninski <
> boris.toninski@orangedot.bg
> > wrote:
> >
> > Hi guys,
> >
> > what I have seen till now in the demos is that when you open a form for a
> > entity, all fields are disabled. You have to firs click on the edit
> button
> > to edit the properties.
> >
> > Is this the recommended way of using Isis. Would there be some problems
> or
> > difficulties if the form is ready to be edited when opened?
> >
> > Thanks in advance!
> >
>
Re: Edit data without having to click on the "Update" button
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
I have asked myself the same question recently.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Dec 16, 2014 at 8:22 PM, Boris Toninski <boris.toninski@orangedot.bg
> wrote:
>
> Hi guys,
>
> what I have seen till now in the demos is that when you open a form for a
> entity, all fields are disabled. You have to firs click on the edit button
> to edit the properties.
>
> Is this the recommended way of using Isis. Would there be some problems or
> difficulties if the form is ready to be edited when opened?
>
> Thanks in advance!
>