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