I need to develop a web application, i have two choices
mvc3 straight forward implementation
using HTML5
i want to know whether HTML5 can be used as part of .net web application architecture or not?
Reasons:
there is no official support of HTML5 server controls like
Now IE 9 was launched but how good it supports HTML5
I found in internet that there is installation for HTML5 helper, but how reliabale it is?
I need guidance on the HTML5 and .net and if any tutorials in this combination.
Thanks in advance
Standards are based on implementation, not invention. If Microsoft wants to wait till HTML5 spec is finished, they will be waiting a long time. Meanwhile, modern browsers have implemented large portions of the spec and are moving forward.
With that in mind, how can one expect ASP.NET to contain elements of HTML5 and related technologies if Microsoft doesn't believe in its usage right now? In our small business, this is the reason we would never use it.
Microsoft always argument that HTML5 isn't fully finished. Then ASP.NET cannot be totally rewriten to follow it. Makes some sense, but...
You can do it by yourself: http://stephenwalther.com/blog/archive/2011/01/11/building-an-html5-app-with-asp-net.aspx.
But I realy believe that ASP.NET MVC is more flexible to it task.
Your question is pretty open-ended. What do you want out of HTML5? If you're just looking for controls, you run into a roadblock that ASP.Net web forms won't render the new HTML 5 input types with placeholders and custom keyboards like URL Input, Email input canvas, etc. I made an open-source project to make these plug and play with Web Forms.
If you're looking for other parts of the spec, pay special attention to whether or not the markup "fails gracefully". If you can optimize the experience with HTML5, but still keep a baseline quality for older browsers, I say go for it!
Related
I defied all conventional knowledge, and wrote my HTML5 site first. Now I am writing the HTML4 site and adding a script which detects old browsers. The question I have is mainly regarding web safe fonts. I am aware that it is best practice to use HTML instead of images of pretty text, for the benefit of SEO. However, since the HTML5 website exists with the HTML in the headers, I wonder if it is safe to use images to represent those headers in the HTML4 version of the site. Simply put, will my web client's indexing suffer? I feel that the HTML5 version will ensure good ranking, but I wanted to put it to the community and get an opinion.
Second question, should I create the more accessible version in HTML4 or XHTML?
Finally, is there a simpler way to make a new site backwards compatible, and still be able to make use of newer technology?
After a fair amount of research, I found that it is not so unusual to create a site in HTML5, and implement items for the purpose of graceful degradation.
At this site: spacebug.com/gracefully-detect-old-browsers-and-fallback-from-html5/, the authors recommend not using PHP user agent variables to detect browser capability. It says that there are too many user agents and that headers change, etc. Check out the link for their in-depth explanation. It offers that the right way to do it is to use javascript to check for certain capabilities. Since my purpose is to either render it in HTML5 or render it in XHTML, this makes my life pretty simple.
Once I found that javascript was the way to go, a simple Google search led me to this site: diveintohtml5.info/detect.html. This offers a number of methods for detecting browser functionality as it relates to HTML5.
For those who are not as savvy with the code, or for those who are looking for a quick solution, the second website also offers a link to modernizr.com, which is an "open-source MIT licensed javascript library that detects support for many HTML5 and CSS3 features."
So, thank you all for your input. I have learned a great deal from this experience, and I am hoping it will make everything much more user friendly and efficient.
Happy developing!
Kat
I am having trouble finding a clear answer on this one. I have an ASP.NET 4.0 Silverlight app, but recently a ton of users are complaining about not being able to use the site on mobile devices and Linux distro's. The app is built on MVVM architecture, and thus we are considering changing the UI to alleviate the complaints. We are leaning toward HTML5, but I'm not sure if this is even technically possible with ASP.NET 4.0. I've seen some posts saying that HTML5 only works with javascript code behinds, and that with ASP.NET 4.5 HTML5 support will be added. Am I understanding this correctly? Maybe it would make more sense to just go with an ASPX UI, what are the advantages of HTML5 over .ASPX? Any help is appreciated.
HTML5 is a set of client-side technologies.
ASP.Net is a server-side technology.
They have nothing to do with each-other.
However, it will be easier in ASP.Net MVC.
You would replace what is currently in the Silverlight plugin that runs in the users browser with some html and javascript instead.
It is not technically possible with ASP.NET 4.0. ASP.NET certainly needs the upgrade in order to handle any HTML5-producing code behind or 'plug-ins.' I second the notion of ASP.NET MVC. Also it seems you are comparing a car to gasoline when you ask the advantages of HTML5 over ASPX.
HTML5 works in conjunction with Javascript on the client side. You can still use ASP.NET to process data and deliver content server side. Here are some quick links.
http://visualstudiomagazine.com/articles/2011/09/01/pfcov_html5.aspx
http://mvchtml5.codeplex.com/ (I know it's mvc, but it might be helpful regardless.)
I'm really surprised where somebody telling that all the C# code of the ViewModel and xaml code behind replace with Javascript . Is is possible ? Where in MVVM architecture code are huge and all are responsible for higher task(like communicate with service layer or database).
Is it possible to convert all C# code in JavaScript.
Even I have seen if a JavaScript function take over 25 lines than it becomes some clumsy fro developer to understand . Simple or small functionality can easy develop with javaScript .
C# is very standard and object oriented language ,to develop LOB it has great role but Javascript is not too much .
I'm think Using asp.net mvc is nice to use HTML5 , see we just need to change UI page look using HTML5 but rest of application functionality should remain Same .
I want to make an application for J2ME phones.
In that application I want to use HTML5,
how I can do this?
I worked on LWUIT. Does LWUIT support HTML5?
Or give me any other browser info.
LWUIT/Codename One support HTML5 but not on J2ME.
There's no built-in HTML5 (or any HTML version, for that matter) parser or renderer in J2ME. There's some sort of HTML viewer support in the LWUIT library, but I suspect it is reasonably limited in general, and also in particular regarding specifically HTML5 support. In any case, research LWUIT and see if it is enough for your needs or not (hard to say without knowing your real/actual requirements).
It is also not very practical to write your own HTML parser and renderer (especially if you also need to be able to handle CSS and JavaScript). In essence, you'd have to write your own complete web browser in J2ME.
You can, of course, use platformRequest() to launch the default browser, but not that many mobile phones have HTML5 support yet.
If you also manage the server-side (where the HTML5 pages come from), and all you really need is the data, then write the server code to return/send the data to your J2ME MIDlet as either XML or JSON, which are much easier to handle.
Or do you know of anyone working on one? I've been checking all the stuff you can do with HTML 5 here and some other sites and is amazing. I think such a big library should have some IDE with intellisense and easy documentation (like when you press F1 on Visual Studio while a symbol is highlighted) and all that stuff. And if there is not then I should probably start working on one :).
Most of known IDEs and their latest version, like Netbeans, Eclipse, Dreamweaver, support natively HTML5. You can find more info and pick one according to your preferences.
There are numerous HTML 5 IDEs, it's important to not necessarily separate current web technologies with HTML5 as they are really are very close to being one and the same. For example, the latest version of Adobe's tool offer support for HTML5, as well as other IDEs such as Aptana. Unfortunately, the HTML5 spec is not done yet so there will be discrepancies between browsers, which a builder could work around, but will put a lot of onus on you.
Alternatively, there are numerous client and server-side frameworks that abstract HTML5 and some of its features, each of these have varying levels of support, a builder, and intellisense. For example, I'm a co-founder of the NOLOH development platform (http://www.noloh.com), which abstracts away browser differences and supports HTML5 transparently to you the developer, allowing you to concentrate on your application and functionality without worrying about the plumbing. We also have what's known as "code stubs" that you can add to any IDE most IDEs and get intellisense/auto-complete functionality. We also have a visual builder in the works that should be out relatively soon.
Whatever you pick, just make sure you're comfortable with it, but you definitely don't want to re-invent the wheel here.
You should definitely try HTML5 Builder.
Try this, HTML5 Boilerplate
if you are looking for something that builds mobile sites or ads html5 builder, maybe you could try http://mobdis.com.
I'm confused by the discussion and advancement both of a new version of HTML and a new version of XHTML. Are they competitors? If so, what is likeliest to be the adopted future of the web? If not, what is the differing non-competing purpose for each?
Are we due to have a BluRay/HDVD battle here? Is there ultimately any clear decision? I fear a future where browsers pick and choose among the easiest and/or flashiest features of each to implement, leaving web developers trying to sort out the lowest common denominator for any new web app.
HTML 5 is meant for web applications whereas XHTML2 is meant for documents. From the HTML 5 working draft:
XHTML2 defines a new HTML vocabulary with better features for hyperlinks, multimedia content, annotating document edits, rich metadata, declarative interactive forms, and describing the semantics of human literary works such as poems and scientific papers.
However, it lacks elements to express the semantics of many of the non-document types of content often seen on the Web. For instance, forum sites, auction sites, search engines, online shops, and the like, do not fit the document metaphor well, and are not covered by XHTML2.
[HTML5] aims to extend HTML so that it is also suitable in these contexts.
XHTML2 and [HTML5] use different namespaces and therefore can both be implemented in the same XML processor.
XHTML2 and HTML5 are competing standards, they both purport to be the next iteration of HTML.
It is pretty clear that HTML5 is going to win, since it has support by the browser vendors.
XHTML2 is effectively dead. Since w3c(HTMLWG) accepted WHATWG's proposal the work has stopped on XHTML2 (even before that, since the last working draft for xhtml2 is from 2006).
In my opinion HTML5 will be the next dominant format. XHTML is just too unforgiving to be used in a web environment (you can't have the page fail on every small error...).
HTML5 is shaping up to be quite the treat for web developers - a formal spec for the CANVAS element, native drag-and-drop API, an offline storage API, server notifications API (push model), a formal content editing API and much more. If they can deliver even half of what they are proposing to, it will be a major advancement for web applications.
From what I was able to find in a quick google search, I would suggest that these are indeed competing standards. Both are attempting to advance web technology but are following different paths to do so.
For a pretty thorough treatment of the matter you might look at these two links:
http://xhtml.com/en/future/x-html-5-versus-xhtml-2/
http://www.cmswire.com/cms/industry-news/setting-the-standards-html-5-vs-xhtml-2-002032.php
Ultimately it's whatever is supported by browser makers. HTML 5 is feature rich, but the final draft may be years off. There are inherent difficulties in implementing things like audio and video support in 4(+) major rendering engines, and having them all behave the same way. Even validation would be a chore. Most browsers besides IE support the canvas element and SVG, but they still only represent about 25% of the market. With IE still commanding 75-80% of the market share, users who don't use or are oblivious to alternatives will be unable to use more advanced features, giving designers a tough decision.
IE8 is only finally implementing support which other browsers have had for users, meaning that the IE user base will always lag in compatibility. While HTML 5 is a nice idea, I think proprietary solutions such as Flash/AIR and Google Gears will continue to provide standardized support for the rich features HTML 5 provides. The biggest problem really is standardization - you have to design a website with the greatest percentage of users in mind as possible. There is hope, however. A Mozilla developer made a canvas plugin for IE - we could potentially see an open-source IE add-on that brings it up to a certain standard, that users could install much like Flash.
To Microsoft's credit they are being very open with IE8 and Windows 7 development (see their project blogs), so there is the possibility that more proactive IE development will accelerate adoption of HTML 5.
The W3C allowed the xhtml2 working group's charter to expire in 2009. Their resources were rolled into the html5 working group. The html5 spec contains a section entitled The XHTML Syntax.