I am new to Wicket, I have seen that it has Ajax related components.
When it generates JavaScript at the client side, is this JavaScript code cross-browser compatible?
Wicket Ajax's capabilities have been rated A (cross browser compatible) in this article. Although a bit outdated, it still remains true.
Don't forget that you can also integrate jQuery, Script.aculo.us or any of the other "big" JavaScript libraries with Wicket.
Related
I am trying to find the official documentation for the supported browser list for IdentityServer3. Does anyone know a link or such? I have been crawling the official documentation and have not found a full list as of yet.. Hopefully, I have just over looked it.
If you mean the default views, they utilize the following js libs - so you're better off the browser support for these:
=> source code, external js libs
Angular 1.3.1
Boostrap 3.0.3
jQuery 1.11
When that is said, all views can be overriden and implemented by you - so you can decide yourself what your browser support level is.
To quote Brock Allen on what's the intended default browser support
We don't support deprecated browsers. IIRC we agreed to IE9 and above. In fact much of the login or consent pages won't work for you if you're in IE7 I'd imagine.
=> source of quote
I visited new GWT website and noticed that after clicking on tree items - link is changing without adding hash (for example, http://www.gwtproject.org/books.html). I know how to do url routing using hashes, but how URL routing is made in GWT website (and possibly can be made)?
Thanks in advance.
It's commonly called HTML5 PushState. A new way of dealing with the browser history by changing the URL without necessarily reloading the page. By listening on popstate events you can dynamically change your page just like using the hashtag method, with the benefit of having cleaner URLs and out of the box crawlability.
Have a look at the gwt website source. Internally uses the GQuery library (jQuery port for GWT) that leverages such pushState methodology.
EDIT: If you want to take benefit of pushState right from GWT (since it does not natively support it), you can also have a look at Johannes Barop's pushState project.
I'm looking to setup the GWT-Validation Framework (client side for now) in our application, but I'm not clear from the docs what pieces I need and what goes where?
We are using GWT 2.1 and MVP. I have the inherits entry for Validation in the gwt.xml, but what goes actually goes into the View, Activity, etc... I'm not aware of any tutorials available.
Any help would be appreciated!
Aftermath:
At the time when I was trying to use it, GWT 2.1 wasn't compatible with the GWT-Validation framework. After doing more reading I found this out. I don't know if that is still the case.
I assume you are referring to the validation framework in GWT and not the gwt-validation library? If that's the case, here is a page that describes how you can do bean validation: http://code.google.com/p/google-web-toolkit/wiki/BeanValidation. If you are actually referring to the gwt-validation library, here is a page that describes how to use it:
http://code.google.com/p/gwt-validation/wiki/ConceptOfOperations
Here is a link that gives some information about the GWT Validation Framework, GWT-Validator and the authors solution, the GWT-Validation library. It is a good synopsis of the issues and why he wrote the new library with some code snippets.
The GWT Validation Library.
I want to design a website using GWT. This is my understanding of how GWT pages will be delivered to the client browser - When the user puts in the URL into her browser she receives all the static HTML + GWT javascript, and then the javascript queries the server for the dynamic page content and adds it to the DOM. eg - For a blog page the content of the blog is queried by the javascript. is my understanding correct?
If I know that the content will surely be a part of the page(add does not depend on user clicking an expand button etc.), Will it be more efficient if the blog content was a part of the HTML initially served? Something that could be done by using a templating engine like django.
Is there a way to make a templating mechanism in GWT?
Yes, putting your content into the HTML will reduce the number of round trips the client makes to your server. It also means that the blog content won't have to wait for your GWT javascript to load before it can be displayed.
GWT itself isn't useful for a template system, but most servers that run GWT servlets will also support JSP pages. GWT works fine with these pages, you just need to put the GWT script tag in as usual. You will no doubt be able to find a ready-made templating solution but rolling your own is not too hard.
I saw a tweet today referring to the MVCHTML5 helpers on Codeplex. I'm wondering if
Anybody has tried this out yet?
Does it add any real significant benefit over the default HTML helpers?
What are the actual HTML5 aspects of this library?
I would definitely recommend checking it (I am a little biased as I wrote it!).
But it's just a simple DLL that you include in your MVC project and it will give you all the benefits of HTML5 input types. If the browser doesn't support it - it will just fall back to a normal textbox.
To answer your questions though, it only adds a benefit if you are looking to add HTML5 functionality to your application or website. It uses the exact same syntax and the normal HTML helpers that ASP.net MVC comes with, but this just makes life easier if you are looking to add HTML5 functionality to your site.
Here is another link regarding HTML5 and the input types: http://diveintohtml5.ep.io/
I've just been trying it out, it doesn't seem to support the Required DataAnnotations for unobtrusive client side validation