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 <[email protected]> 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 <
[email protected]
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!
