• Complain

Jarrod Overson - Developing Web Components: UI from jQuery to Polymer

Here you can read online Jarrod Overson - Developing Web Components: UI from jQuery to Polymer full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2015, publisher: OReilly Media, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

Jarrod Overson Developing Web Components: UI from jQuery to Polymer
  • Book:
    Developing Web Components: UI from jQuery to Polymer
  • Author:
  • Publisher:
    OReilly Media
  • Genre:
  • Year:
    2015
  • Rating:
    4 / 5
  • Favourites:
    Add to favourites
  • Your mark:
    • 80
    • 1
    • 2
    • 3
    • 4
    • 5

Developing Web Components: UI from jQuery to Polymer: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "Developing Web Components: UI from jQuery to Polymer" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

Although web components are still on the bleeding edgebarely supported in modern browsersthe technology is also moving extremely fast. This practical guide gets you up to speed on the concepts underlying W3Cs emerging standard and shows you how to build custom, reusable HTML5 Web Components.

Regardless of your experience with libraries such as jQuery and Polymer, this book teaches JavaScript developers the DOM manipulations these libraries perform. Youll learn how to build a basic widget with vanilla JavaScript and then convert it into a web component thats semantic, declarative, encapsulated, consumable, and maintainable. With custom components, the Web can finally fulfill its potential as a natively extensible application platform. This book gets you in at the right time.

  • Understand core concepts (such as normal flow and positioning, and Z-index) for properly positioning, dragging, and resizing elements
  • Explore UI concepts and patterns typically abstracted away by Dojo, jQuery UI, Kendo UI, and other libraries
  • Dive into the W3C standard and convert your working widget example into a fully functioning web component
  • Learn how to encapsulate, package, and deploy your web components with Googles Polymer framework

Jarrod Overson: author's other books


Who wrote Developing Web Components: UI from jQuery to Polymer? Find out the surname, the name of the author of the book and a list of all author's works by series.

Developing Web Components: UI from jQuery to Polymer — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Developing Web Components: UI from jQuery to Polymer" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
Developing Web Components

by Jarrod Overson and Jason Strimpel

Copyright 2015 Jarrod Overson and Jason Strimpel. All rights reserved.

Printed in the United States of America.

Published by OReilly Media, Inc. , 1005 Gravenstein Highway North, Sebastopol, CA 95472.

OReilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://safaribooksonline.com). For more information, contact our corporate/institutional sales department: 800-998-9938 or corporate@oreilly.com .

  • Editors: Simon St.Laurent and Brian Anderson
  • Production Editor: Colleen Lobner
  • Copyeditor: Rachel Head
  • Proofreader: Charles Roumeliotis
  • Indexer: Wendy Catalano
  • Interior Designer: David Futato
  • Cover Designer: Ellie Volckhausen
  • Illustrator: Rebecca Demarest
  • February 2015: First Edition
Revision History for the First Edition
  • 2015-02-06: First Release

See http://oreilly.com/catalog/errata.csp?isbn=9781491949023 for release details.

The OReilly logo is a registered trademark of OReilly Media, Inc. Developing Web Components, the cover image, and related trade dress are trademarks of OReilly Media, Inc.

While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights.

978-1-491-94902-3

[LSI]

Preface
Why We Wrote This Book

Web development has not stopped evolving since I stumbled into the field over 13 years ago. If anything, the rate at which it is evolving is increasing. If you take a look at the investment that Google has made in Polymer and web components, it is probably safe to bet that web components will play a large role in web development in the near future as browsers implement more support for them. There are still some issues that need to be addressed, such as search engine optimization (SEO) concerns, but I do not think web components are going away, and I dont think this is bad. The introduction of web components (or a similar standard for extending, packaging, encapsulating, and importing discrete UI components) is long overdue in web development. Even if you do not put all your stock in web componentsfor example, lifting back the curtain and seeing how the Great Oz accomplishes his UI wizardry, making an element draggablethey can be very useful.

Glenn Vanderburg said, Developers should always understand one layer of abstraction below their everyday work. I agree with this statement, and I would argue that widget libraries, jQuery plugins, and even jQuery are the levels of abstraction at which most frontend engineers operate on a daily basis. The level just below that consists of the DOM manipulations these libraries perform, and the DOM and its native APIs. Understanding precisely what these libraries are doing will enable you to write more efficient code on a daily basis and prepare you for the great awakening.

Inevitably, there will come a time when one of these libraries does not fit nicely into the use case with which your product manager or information architect has gifted youat which point, you either sink or swim. I for one would have preferred to have some swimming lessons before my day arrived, but I was not that fortunate.

I was tasked with making a fixed-width portal product fluid-width, and all of the portlets resizable. Sounds easy, right? I was informed that this had been attempted more than once before, and that previous developers had failed and said it was impossible. Well, that was encouraging. On top of this, Internet Explorer 9 had just hit the market, and due to technical debt we were running three different versions of jQuery and two different versions of jQuery UI, none of which worked well with IE9. So, before I could even start the resizing work I had to move to a single version of jQuery and jQuery UI that played nicely with IE9. You might think that moving to a single version of each library would be a simple process, but I quickly realized why we had accumulated the massive technical debt. We were running a myriad of jQuery plugins ranging from bad to awful in quality and old to ancient in web time. In addition to breaking our code, the upgrade broke the majority of these plugins. This required upgrading and patching several plugins, and replacing others. This in turn involved an intimate knowledge of the DOM, which I did not have. I console logged, reverse engineered, and consumed Stack Overflow until I had solved every problem. This was all before I could even get started on the column resizing and portlet changes.

Next, I got some ridiculous requirement that the portlet column resizing had to look precisely like a mock that had already been approved. It also had to behave just as the approved specification described. There was not a plugin in existence that would meet these requirements. Marvelous. I got to write my own.

Once I had that spaghetti code written, I had to make all the portlets and every widget resizable. All of these events had to be timed properly, and nothing could spill out of containers while resizing. setTimeout and I began a love affair that still continues to this day.

If you can relate to this story, then you likely have your own. If so, like me, you probably hacked something together that was a hodgepodge of Stack Overflow responses and miscellaneous jQuery plugins held together by some glue code you wrote that have 100 different branches to account for all the anomalies that occurred due to your lack of understanding. I have been there, and it is not fun. This experience is why I wrote this book.

In addition to not drowning, there are some other benefits to understanding how the lower-level parts of UI components function:

  • It allows you to define an API that makes sense to youjQuery plugins are not everyones cup of tea.

  • It gives you full control over the entire stack, which makes debugging easier and allows you to decide at what layer a change should occur.

  • It allows you to decide which features are important and to limit your footprint in cases where file size is of great concern (e.g., mobile applications).

  • It allows you to make optimizations that fit your applications and use cases.

Lastly, I think that it is every frontend engineers job to understand the DOM and vanilla JavaScript. This understanding, and the ability to design solutions, is what sets frontend engineers apart from frontend developers.

What This Book Is

The primary goal of this book is to provide the foundational knowledge required to develop and deploy web components. It is intended to be an introduction and to inspire, not to be an exhaustive resource on the subject matter. This foundational knowledge has been divided into four parts, preceded by a general introduction to web components and the areas we will tackle in this book. Each of these sections and their chapters will build upon a working code example.

Part I, UI Core Concepts

The first part covers core concepts such as cloning nodes, rendering layers, stacking contexts, and

Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «Developing Web Components: UI from jQuery to Polymer»

Look at similar books to Developing Web Components: UI from jQuery to Polymer. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «Developing Web Components: UI from jQuery to Polymer»

Discussion, reviews of the book Developing Web Components: UI from jQuery to Polymer and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.