[
https://issues.apache.org/jira/browse/ISIS-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836962#comment-13836962
]
Jeroen van der Wal edited comment on ISIS-620 at 12/2/13 9:51 PM:
------------------------------------------------------------------
Disabling the back button is not such a bad idea. But there is still an issue
to be solved from a usability point of view I think.
Consider this code in the service menu:
{code}
public class Products {
public Product newProduct(...) {
...
return product;
}
}
{code}
When the user selects the option "New Product" from the "Products" menu and
fills the required parameters (using a modal window) it gets directed to the
new product. If the user is happy with the result he wants to go back to to
previous context and therefore presses the browser back button. If we take away
the back button he (or she) is left in a dead-end street.
I can see few solutions to avoid this, each with it's own shortcomings:
# make the new product visible as a tab with an option to close it
-- one of the reasons we've moved from tabs to the bookmark pop-out is that a
lot of tabs will be created when working with the application
# make the new product another modal window
-- not consistent with the overall ui experience
# redirect to a collection of products
-- user has to search for the product again to review it
-- putting ui flow in the domain model is IMHO not a good thing
Love to hear your suggestions.
was (Author: jcvanderwal):
Disabling the back button is not such a bad idea. But there is still an issue
to be solved from a usability point of view I think.
Consider this code in the service menu:
public class Products {
public Product newProduct(...) {
...
return product;
}
}
When the user selects the option "New Product" from the "Products" menu and
fills the required parameters (using a modal window) it gets directed to the
new product. If the user is happy with the result he wants to go back to to
previous context and therefore presses the browser back button. If we take away
the back button he (or she) is left in a dead-end street.
I can see few solutions to avoid this, each with it's own shortcomings:
# make the new product visible as a tab with an option to close it
-- one of the reasons we've moved from tabs to the bookmark pop-out is that a
lot of tabs will be created when working with the application
# make the new product another modal window
-- not consistent with the overall ui experience
# redirect to a collection of products
-- user has to search for the product again to review it
-- putting ui flow in the domain model is IMHO not a good thing
Love to hear your suggestions.
> When editing an entity twice a concurrency exception is thrown
> --------------------------------------------------------------
>
> Key: ISIS-620
> URL: https://issues.apache.org/jira/browse/ISIS-620
> Project: Isis
> Issue Type: Bug
> Components: Viewer: Wicket
> Affects Versions: viewer-wicket-1.3.1
> Reporter: Jeroen van der Wal
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.4.0
>
>
> When editing an entity twice a concurrency exception is thrown when using the
> backspace (browser back) anywhere in the application.
> To reproduce:
> * load fixtures
> * open arbitrary todo
> * click edit, change description, click save
> * again, click edit, change description, click save
> The result:
> sven attempted to update TODO:L_23, however this object has since been
> modified by sven at Mon Dec 02 18:13:13 CET 2013 [3 vs 2]
--
This message was sent by Atlassian JIRA
(v6.1#6144)
