Almost 150 years ago on October 8, 1871, the Great Fire of Chicago began in a small dwelling on "the west side"  of the city. Two days later, as the conflagration finally died down, the Chicago Tribune printed a brief two-page issue, its first since the disaster began. Its own home offices devastated by the fire, after detailed descriptions of the destruction, the paper declared "CHICAGO SHALL RISE AGAIN." Discover more about how the nation responded to the news through our Research Guide and read more about it in the Chicago Tribune!

Converter and Fire Refining Practices Symposium (2005 : San Francisco, Calif.)

Global Conference on Extractive Metallurgy (1st : 2018 : Ottawa, Ont.)

Chief Minister Y.S. Jagan Mohan Reddy on Friday wrote to Life Insurance Corporation of India (LIC) Chairman M.R. Kumar urging him to immediately settl

They also helped evacuate people from the affected area

The panelists talk about Firefox OS with Jason Weathersby.

Join AJ, Aimee, and Joe as they discuss Mozilla Firefox Developer Tools with Jason Laster. Jason just started working at Mozilla since March. But even before that, he has been working on Chrome's dev tool extension called Marionette. That's when he discovered that the browser is an open source that anyone can play with. Now, he is working on a new debugger in Firefox. Tune in!

Maximiliano Firtman is a mobile web developer from Buenos Ares, Argentina. He has been a developer for 24 years and his most recent focus has been on progressive web apps, or PWAs. Steve and Max reflect on the technologies they were using when they first got started in web development and talk about their experience with mobile development. One area that Max emphasized was bringing the web into the mobile space. They discuss the progression of web access on mobile and some of the available tools. Max notes that responsible design has a very high cost in web performance for mobile devices, which requires unique approaches. They discuss some of the issues with latency in mobile, even on 4G. The solution to this latency is PWAs.

Progressive web apps are a set of best practices to create web apps that are installable. They can work offline at high speeds on several operating systems. Once installed, it looks like any other app on the system. Max delves into more details on how it works. He talks about how the resources for your application are managed. He assures listeners that it’s just a website that’s using a new API, they’re not changing the way the web works, and that when that API is there, the app can be installed. It will also generally use your default browser. Steve and Max discuss how local data is stored with PWAs. To write PWAs, you can use Angular, React, JavaScript, or Vue, and it’s a pretty transparent process. Max talks about some common tools used for local storage and some of the PWAs he’s worked on in the past. The benefit of using PWAs is that they generally run faster than regular web apps. To get started, Max advises listeners to install one and start exploring.

Panelists

• Steve Edwards

Guest

• Maximiliano Firtman

Sponsors

• G2i

____________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

____________________________________________________________

Links

• Progressive Web Apps

• Appsco.pe

• IndexedDB

• Max's site

Picks

Steve Edwards:

• The Club

Maximiliano Firtman:

• Llama

• Follow Max on Twitter

My JavaScript Story this week welcomes Maximiliano Firtman. Maximiliano Firtman is a mobile web developer from Buenos Ares, Argentina. He has been a developer for 24 years and his most recent focus has been on progressive web apps.

Maximiliano started coding when he was 11 years old by creating games and digital magazines. He got into web development by learning HTML in college.

Host: Charles Max Wood

Joined By Special Guest: Maximiliano Firtman

Sponsors

• Sentry use the code “devchat” for 2 months free on Sentry small plan

• CacheFly

______________________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

______________________________________

Links

• JSJ 415: Progressive Web Apps with Maximiliano Firtman

• Maximiliano Firtman Website

• Maximiliano Firtman Twitter

Picks

Maximiliano Firtman:

• Using Trusted Web Activities

Charles Max Wood:

• Generation Z Unfiltered by Tim Elmore

Mass, Jeffrey P

Chapman, Elwood N

Mazur, Gail

On the face of it the Fifa World Cup is all about quality football, generally recognised as the greatest sporting showpiece on earth.

Hayden Library - TP248.2.B73 2019

Online Resource

Míguez, Néstor Oscar

Schreiner, Patrick, author

Chilton, Bruce, author

King, Karen L., author

Wright, N. T. (Nicholas Thomas), author

Nir, Rivḳah, author

Tyson, Paul G., author

Taking a “mobile first” approach to web development poses some challenges if you need to provide a “desktop” experience for legacy versions of IE. Using a CSS pre-processor like Sass can help.

As of Sass 3.2, there is another way of catering for IE, described by Jake Archibald.

One aspect of a “mobile first” approach to development is that your styles are usually gradually built up from a simple base. Each new “layer” of CSS adds presentational adjustments and complexity, via CSS3 Media Queries, to react to and make use of additional viewport space. However, IE 6/7/8 do not support CSS3 Media Queries. If you want to serve IE 6/7/8 something more than just the base CSS, then you need a solution that exposes the “enhancing” CSS to those browsers.

Popular existing options

An existing option is the use of a CSS3 Media Query polyfill, such as Respond.js. However, there are some drawbacks to this approach (see the project README), such as the introduction of a JavaScript dependency and the XHRing of your style sheets, which may introduce performance or cross-domain security issues. Furthermore, adding support for CSS3 Media Queries is probably not necessary for these legacy browsers. The main concern is exposing the “enhancing” CSS.

Another method, which Jeremy Keith has described in his post on Windows mobile media queries, is to use separate CSS files: one basic global file, and an “enhancing” file that is referenced twice in the <head> of the document. The “enhancing” file is referenced once using a media attribute containing a CSS3 Media Query value. This prevents it being downloaded by browsers (such as IE 6/7/8) which do not support CSS3 Media Queries. The same file is then referenced again, this time wrapped in an IE conditional comment (without the use of a CSS3 Media Query value) to hide it from modern browsers. However, this approach becomes somewhat cumbersome, and introduces multiple HTTP requests, if you have multiple breakpoints in your responsive design.

Getting Sass to help

Sass 3.1 provides some features that help make this second approach more flexible. The general advantages of the Sass-based approach I’ve used are:

1. You have full control over how your style sheets are broken up and reassembled.
2. It removes the performance concerns of having to reference several separate style sheets for each breakpoint in the responsive design, simply to cater for IE 6/7/8.
3. You can easily repeat large chunks of CSS in separate compiled files without introducing maintenance problems.

The basic idea is to produce two versions of your compiled CSS from the same core code. One version of your CSS includes CSS3 @media queries and is downloaded by modern browsers. The other version is only downloaded by IE 6/7/8 in a desktop environment and contains no CSS3 @media queries.

To do this, you take advantage of the fact that Sass can import and compile separate .scss/.sass files into a single CSS file. This allows you to keep the CSS rules used at any breakpoint completely separate from the @media query that you might want it to be a part of.

This is not a CSS3 Media Query polyfill, so one assumption is that IE 6/7/8 users will predominantly be using mid-size screens and should receive styles appropriate to that environment. Therefore, in the example below, I am making a subjective judgement by including all the breakpoint styles up to a width of 960px but withholding those for any breakpoints beyond that.

The ie.scss file imports numerous other files, each containing a layer of CSS that builds upon the previous each layer of CSS. No CSS3 @media queries are contained within the files or the ie.scss file. It then compiles to a single CSS file that is designed to be served only to IE 6/7/8.

// ie.scss

@import "base";
@import "320-up";
@import "480-up";
@import "780-up";
@import "960-up";

The style.scss file imports the code for each breakpoint involved in the design (including any beyond the limit imposed for legacy versions of IE) but nests them within the relevant CSS3 @media query. The compiled version of this file is served to all browsers apart from IE 6/7/8 and IEMobile.

// style.scss

@import "base";
@media (min-width:320px) {
    @import "320-up"; }
@media (min-width:480px) {
    @import "480-up"; }
@media (min-width:780px) {
    @import "780-up"; }
@media (min-width:960px) {
    @import "960-up"; }
@media (min-width:1100px) {
    @import "1100-up"; }

The resulting CSS files can then be referenced in the HTML. It is important to hide the ie.css file from any IE-based mobile browsers. This ensures that they do not download the CSS meant for desktop versions of IE.

<!--[if (gt IE 8) | (IEMobile)]><!-->
<link rel="stylesheet" href="/css/style.css">
<!--<![endif]-->

<!--[if (lt IE 9) & (!IEMobile)]>
<link rel="stylesheet" href="/css/ie.css">
<![endif]-->

This Sass-enabled approach works just as well if you need to serve a basic style sheet for mobiles without CSS3 Media Query support, and prevent those devices from downloading the CSS used to adapt the layout to wider viewports. For example, you can avoid importing base.scss into the ie.scss and style.scss files. It can then be referenced separately in the HTML.

<link rel="stylesheet" href="/css/base.css">
<link rel="stylesheet" href="/css/style.css" media="(min-width:320px)">

<!--[if (lt IE 9) & (!IEMobile)]>
<link rel="stylesheet" href="/css/ie.css">
<![endif]-->

You’ll notice that I didn’t wrap the style.css reference in a conditional comment to hide it from legacy versions of IE. It’s not necessary this time because the value of the media attribute is not understood by legacy versions of IE, and the style sheet will not be downloaded.

In different circumstances, different combinations of style sheets and media attribute values will be more appropriate.

Summary

Even if you want to don’t want to use any of the Sass or SCSS syntax, the pre-processor itself can help you to write your CSS in a “mobile first” manner (with multiple breakpoints), provide a “desktop” experience for IE 6/7/8, and avoid some of the performance or maintenance concerns that are sometimes present when juggling the two requirements.

I’m relatively new to using Sass, so there may be even better ways to achieve the same result or even to prevent the inclusion of IE-specific CSS unless the file is being compiled into a style sheet that only IE will download.

All 1,111 passengers underwent thermal screening at the station before departing for Basti in U.P.

Plenert, Gerhard Johannes, author

Stegmann, Juan Pablo

Crainer, Stuart

Phillips, Michael, author

Kaynak, Hale, 1956-

Heskett, James L

Hall, Richard, 1944- author

O'Keeffe, Niamh

Interview with Robert A. Tessler, MD, MPH, and Frederick P Rivara, MD, MPH, authors of Trends in Firearm Injury and Motor Vehicle Crash Case Fatality by Age Group, 2003-2013

Interview with Krisda Hirschman Chaiyachati, MD, MPH, MSHP, author of Assessment of Inpatient Time Allocation Among First-Year Internal Medicine Residents Using Time-Motion Observations, and Christopher Moriates, MD, author of A Modern Snapshot of the Daily Work of Medical Interns—The Burden of Indirect Patient Care

Interview with Michael A. Vella, MD, and Mark J. Seamon, authors of Long-term Functional, Psychological, Emotional, and Social Outcomes in Survivors of Firearm Injuries

The bank's total revenue jumped 33 per cent YoY to Rs 1,522 crore from Rs 1,148 crore reported in Q4FY19, while its net interest income came in at Rs 1,021 crore, up 38 per cent YoY from Rs 739 crore

Microsoft is one of the leaders in the cloud computing segment segment, besides Alphabet (Google) and Amazon, making the stock attractive