GWT 历史问题

发布于 2024-11-17 17:01:01 字数 171 浏览 2 评论 0原文

关于后/前项目功能,什么被认为是一个好的设计。 我的意思是 - 用户只能通过后退/前进浏览器按钮浏览应用程序,或者在应用程序中也有后退按钮,混合它(浏览器后退和应用程序后退按钮)是一个好习惯吗?或者 GWT History 足以成为应用程序中唯一的导航器?

我很高兴听到不同的意见和方法。

谢谢

What is consider as a good design regarding back/forward project capabilities.
I mean - uses are able to navigate through the application only via back/forward browser buttons or to have also and back buttons in the application , is it a good practice to mix it (browser back and application back buttons) ? Or GWT History is good enough to be the only navigator in the application?

I will be glad to hear different opinions and approaches.

Thanks

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(5

吃不饱 2024-11-24 17:01:01

GWT 历史管理是一种使应用程序的不同状态与地址 URL 匹配并使用侦听器接收 URL 更改通知的方法。

这是一个允许标准后退/前进以有意义的方式工作的技术

现在我们谈论一个设计,“后退”/“前进”按钮在您的应用程序中真的有用吗?

这取决于您的应用程序的用途。如果它是某种带有一组步骤的向导,那么是的,您的应用程序中将有后退/前进按钮。

如果这是一个更传统的用户界面,不,你将不会有/后退。您将拥有将用户发送到新视图的链接/按钮,以及允许转到用户想要的任何视图/屏幕的某种主导航。仅支持后退/前进仅使用浏览器。

GWT history management is a way to make different states of your application matches with the address URL and use listeners to be notified of URL changes.

This is a technical thing that allow standard back/forward to work in a meaningfull way.

Now we speak about a design, does a "back"/"forward" button really usefull inside your application?

Well this depend of what your application do. if it is some sort of wizard with a set of steps, then yes you'll have back/forward buttons in your application.

If this a more conventionnal UI, no you will not have/back forward. You will have link/button sending the user to new views, and some sort of main navigation allowing to go to any view/screen the user want to. Only support for back/forward would be using the browser only.

屌丝范 2024-11-24 17:01:01

我的观点是,GWT History 用于模仿应用程序已有的功能。因此,当您执行操作时,它们会留下用户可以追溯的痕迹。

My perspective is that GWT History is used to mimic the already-existing features of your application. So when you perform actions, they leave a trail that the user can trace back.

百思不得你姐 2024-11-24 17:01:01

根据 Web 应用程序场景,最好通过浏览器后退和前进按钮进行导航。为什么要重新发明轮子呢?

正如该设施支持的所有浏览器一样。
我还在开发一个由 gwt 支持的大型应用程序。系统中的历史记录由历史记录令牌管理。您可以从 此处

我从过去两年开始就致力于 gwt 的历史管理,它工作得很好。
您可以使用导航系统来满足内部面板导航要求。但是对于浏览器,我建议您使用其自己的设施。

As per the web application secenerio,It is more preferable to navigate through the browser back and forward buttons.Why to reinvent the wheel?

As all browser supported by this facility.
I am also working on a large application supported by the gwt.History in the system is managed by the History token.You can have a look on it from here.

I am working from last two years with history management of gwt ans it is working fine.
You can have your navigation systems for the inner panel navigation requirement.But for the browser I suggest you to use its own facility.

仙气飘飘 2024-11-24 17:01:01
  1. 我不会在您的应用程序中提供单独的后退/前进功能,因为人们习惯使用浏览器的后退/前进按钮。这不会添加任何功能,只会让人们感到困惑。

  2. GWT 历史记录封装了浏览器的历史记录功能,因此其执行方式与浏览器本机历史记录功能完全相同。

  1. I wouldn't have a separate back/forward functionality in your app, since people are used to using browser's back/forward buttons. This would not add any function, just confuse people.

  2. GWT History wraps browsers' history functionality so it will perform exactly like browsers native history functionality.

朕就是辣么酷 2024-11-24 17:01:01

始终基于浏览器的历史记录。

  1. 如果您仅支持内部历史记录(并且不支持基于浏览器的历史记录),则当您的用户向后导航时,浏览器会将他们从您的应用程序中带走。
  2. 如果您支持内部历史记录和基于浏览器的历史记录,您的用户可能不会清楚按内部或基于浏览器的后退键的效果。

我想不出 Web 应用程序支持内部和基于浏览器的历史记录导航的实例。

我能想到的最接近的是提供面包屑,但这些仅与几种类型的应用程序相关。

Browser-based history all the way.

  1. If you only support internal history (and don't support browser-based history), when your users navigate back the browser will take them away from your application.
  2. If you support both internal and browser-based history your users probably will not be clear of the effect of pressing internal or browser-based back key.

I cannot think of an instance where a web-application supports internal and browser-based history navigation.

The closest I can think of is when breadcrumbs are provided, but these relate to only a few types of application.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文