Every Wednesday, new courses and workshops are added to the growing Treehouse Library! Read more about the two new courses added this week and get the scoop on what’s coming later this month. Start learning to code today with your free trial on…
The post What’s New at Treehouse: Bootstrap 4 & ASP.NET appeared first on Treehouse Blog.
Whether you’re learning to code online, at a bootcamp, or in-person, there’s one supplementary resource that we recommend to accompany your learning: books. But with so many programming books to choose from (a Google search brings up over 12 million…
The post 25 Programming Books for the Aspiring Developer appeared first on Treehouse Blog.
The electronic age has certainly made life simpler.
Even before we found the need to be connected, electronic devices have become a supplement to our daily lives. The simple word processor and spreadsheet on the way-overpriced home computers helped make communication easier to read and reduced errors with pencil and paper computations.
In the previous article, we moved one step closer to our working web application by building our service provider layer that acts as an abstraction of our order management web service. With this foundation set, we are ready to complete the last layer in our web application: the User Interface (UI) layer.
Implementing the UI Layer
The first step in implementing our UI layer is to reflect upon the UI design we created in Part 1. In this design, we created two main components: (1) an order list component and (2) a save order component. While the latter component is abstracted into a single component, we are actually designing it to perform two separate tasks: (1) create a new order and (2) edit an existing order. This double-duty derives from the fact that components for creating a new order and editing an existing order look identical, with a few important caveats:
If you’ve been paying attention, you will have noticed that HTML5 Boilerplate 6.0.0 came out a few weeks ago. If not, it did. 6.0.1 has since been released. It was a long time coming and I’m super happy to have it shipped. It was a lot of fun. Working with a project like this invariably […]
HTML tables are great for displaying data in tabular form and when implemented can also support features like sorting, paging, and filtering records. You may need to interact with the table to get its data when a table cell is clicked. So in this quick post, we’ll look at how to get the table cell […]
Last time, we looked over the various HTML parsers you can consider when working with Java. This time, we’ll examine a couple of popular C# libraries worth considering as we examine their features, benefits, and drawbacks when processing HTML.
The ultimate angle brackets parser library parsing HTML5, MathML, SVG and CSS to construct a DOM based on the official W3C specifications.
HTML is a markup language with a simple structure. It would be quite easy to build a parser for HTML with a parser generator. Actually, you may not even need to do that if you choose a popular parser generator, like ANTLR. That is because there are already available grammars ready to be used.
HTML is so popular that there is even a better option: using a library. It is easier to use and usually provides more features, such as a way to create an HTML document or support easy navigation through the parsed document. For example, usually, it comes with a CSS/jQuery-like selector to find nodes according to their position in the hierarchy.
What do you do when you need a widget-like functionality? At present, there is a whole generation of developers who, as a rule, are googling for ready-made jQuery plugins. Can’t we do better than that? With the advances of web-components, we are expected to compose UIs from these building blocks. They are many. One can find one for almost any task. They are highly customizable. One can reuse the functionality, but with your own original representation. They are isolated. One doesn’t need to worry about the collisions in the compound system. But in reality, the APIs required by true web-components still have poor support in user-agents. One has to load an emulator library like Polymer. When it comes to component-based frameworks, one can painlessly import a component or rather go with a set like Material UI. But what would you say about standardized, library/framework-agnostic solution with not dependencies? Interesting that with HTML 5.1 and HTML 5.2 we get a number of new functional elements, solving classic developer tasks such as dialog, expandables, date pickers, and others. At the time of writing this article, the support for spec among browsers isn’t that good, but the elements can be polyfilled where it lacks. Let’s see what’s available and how we can use it.
Expandables With Summary/Details
A pair of elements, details and summary, were introduced in HTML 5.1 and are now widely supported. They implement a disclosure widget that can be adopted for collapse, dropdown menus, tree navigation, and other tasks. By default, any child elements of details except summary are hidden. As one clicks summary, the properties of open details change to true and the hidden content comes into view. To put it in practice, we made the following HTML:
Meta tags are those HTML tags that appear in the
section of HTML documents, and they act as behind-the-scenes settings that can be interpreted by the web browser to help render the website correctly, or by search engines to help them process certain information that aids your ranking (SEO).
Let’s take a look at all of the meta tags that are relevant in 2017, as you’d be quite surprised at how many of them have been deprecated. If there’s a meta tag you don’t see here, it’s highly likely that you don’t need it anymore.