Podcasts about responsive images

In 24 kurzen Podcast Folgen nehmen wir euch mit durch den devslove.it Adventskalender. Heute geht es weiter mit dem Adventskalender-Türchen Nr. 4 und ein paar Infos zum Thema Responsive Images.---devslove.ithttps://de.linkedin.com/in/alexander-bürnerhttps://de.linkedin.com/in/dominik-laubehttps://podcast.devslove.ithttps://www.instagram.com/devslove.it---CreditsSchnitt: Treppenhaus, Benjamin Grimmeisen https://www.instagram.com/treppenhausstudioFotografie: Marcel Bürner, https://www.instagram.com/ma.burner

Got a Minute? Website owner checkout today's episode of The Guy R Cook Report podcast - show notes for this episode are @ https://bit.ly/3j9GH72 ----more---- Support this podcast You can also subscribe via Apple Podcasts, Google Podcasts, or Spotify. To listen to an audio podcast via the Apple Podcasts button, click on it, mouse over the title of the episode and click Play. Open Apple Podcasts to download and subscribe to podcasts. . vDomainHosting, Inc 3110 S Neel Place Kennewick, WA 509-200-1429 I help goal oriented business owners that run established companies to leverage the power of the internet - Contact Guy R Cook @ https://guycook.wordpress.com/start-with-a-plan/ | Information Kit Support this podcast The Website Design Questionnaire https://guycook.wordpress.com/start-with-a-plan/ In the meantime, go ahead follow me on Twitter: @guyrcookreport Click to Tweet Be a patron of The Guy R Cook Report. Your help is appreciated.   #theguyrcookreport https://www.patreon.com/guyrcook #uncleguy #theguyrcookreport Thanks for listening, viewing or reading the show notes for this episode.

A 48. adásban Gábor megosztotta velünk a Java híreket, Tibi az ujjlenyomatlopásról mesélt. Szó volt még arról is, hogy mennyire nehéz saját CSS-in-JS megoldást írni. A végén még beszéltünk a reszponzív képek kiszolgálásának lehetőségeiről is. Résztvevők: Edu Gábor Tibi Tartalom: 00:04:10 – Ujjlenyomatlopás 00:10:15 – CSS-in-JS from Scratch 00:25:58 – Responsive images Szintet lépett az […]

Panel: Charles Max Wood (DevChat T.V.) Special Guests: Aaron Gustafson In this episode, the Chuck talks with Aaron Gustafson who is a web-standards and accessibility advocate working at Microsoft. Aaron and Chuck talk about PWAs and the ins and outs of these progressive web apps. Check out today’s episode to hear more! Show Topics: 0:36 – Chuck: Our guest is Aaron, say HI! 0:41 – Aaron: Hi! I have been working on the web for 20 plus years. I am working on the Edge team for accessibility among other things. I have done every job that you can do on the web. 1:08 – Chuck: That is one of OUR publications? 1:14 – Aaron: No the communities. I joined the staff as editor in chief for 1.5 year now. It’s a nice side project to do. 1:36 – Chuck: I thought it was a commercial thing. 1:40 – Aaron: No it’s volunteer. 1:52 – Chuck: Talk about your web background? 2:02 – Aaron: I remember the first book I got (title mentioned). My first job on the web (cash) I was the content manager in Florida and this was in 1999. Gel Macs just came out. I relocated from FL to CT and worked for other companies. I got into CSS among other things. It’s been a wild ride and done it all. 3:52 – Chuck: Let’s talk about web standards? 4:05 – Aaron: It depends on the organization and what the spec is and where it originates. It’s interesting to see how HTML developed back in the day. When standardization started working then everything started to converge. Everything is a little different now. Some specs come out from companies that... (Apple, Responsive Images, and Grid are mentioned among other things.) 7:37 – Chuck: We set up to talk about PWAs. Where did PWAs come from? 7:57 – Aaron: Modern web design, best web applications. Being secure. One of the underpinnings came out from Google and they have been supporters of that. Firefox is working on installation as well. The Chrome implementation is weird right now, but it becomes an orphaned app. It’s like the old chrome apps where in Windows you can install from the Microsoft store. But the case of Chrome you don’t have to go through the store. 10:14 – Chuck asks a question. 10:24 – Aaron answers. 11:53 – Chuck: What makes it a progressive web app rather than a regular website? 12:05 – Aaron: The definition is running on HTPS and... Aaron defines the terms that Chuck asks at 11:53. 12:43 – Aaron: Of course you can push forward if it makes sense from the baseline. 12:56 – Chuck: We have an Angular podcast, and we talked about PWAs and nobody had a good definition for it. 13:18 – Aaron. 13:22 – Chuck: What are the pros of having a PWA? Let’s start with the basics first. 13:33 – Aaron: The ability to control how you react to the network. We development is challenging maybe in other areas because of the lack of control and how your code gets to your users. Any special needs that YOU might have. Aaron goes into detail on this topic. 17:14 – Chuck: Is the service worker the star for PWAs? 17:20 – Aaron: In a way, kind of. Aaron goes into detail on this topic. Share 2 is mentioned, too. 19:42 – Chuck: If the service worker intermediates between the browser and the page / Internet would it make sense to have your worker have it load and then load everything else? Cause you have those Web Pack now. 20:14 – Aaron: Some people would consider it but I wouldn’t necessarily. I am not a fan for that. If anything goes wrong then nothing loads. I remember back when... 22:23 – Aaron: That is a lot of overhead. 22:34 – Chuck: I am wondering what is the best practice? How do you decide to pull in a service worker and then move into more complicated issues? 22:53 – Aaron: Progressive Web App where they talk about their evolution about this. 25:17 – Advertisement – Fresh Books! Code: DEVCHAT. 26:25 – Chuck: In order to be a PWA you don’t need to have a push notification. 26:38 – Aaron: I don’t think anyone would want a push notification from me. 27:12 – Chuck: What features do PWAs have? 27:18 – Aaron: Features? None of them really, other than push notifications, it’s just standard it’s going to make an App feel more App “y”. If that’s something you want to do. It’s up to you to determine that. There is going to be like push notifications – sending person new updates about the order. If you were a new site you want to make sure you are not doing a push notifications on everything cause that would be too much. Exercising care with the capabilities with what the users are doing on your computer. This is a person that you are dealing with. We need to seem less needy. Give users control of how they want to use it. For example, Twitter will give you that control per user. 30:56 – Chuck: Could you also do it for different parts of the page? 31:01 – Aaron: It’s different scopes. Your servicer worker has different scopes and it needs to be in the root folder or the JavaScript folder. You can have different workers but they will come from different scopes. 31:32 – Chuck gives a hypothetical example. 31:50 – You can do a bunch of different service workers. 32:11 – Chuck: This is why we create different hierarchies in our code. 32:26 – Chuck: Is there a good point where people can be more informed with PWAs? 32:40 – Aaron: PWA stats website and Twitter account with Cloud 4. 33:22 – Chuck asks a question. 33:26 – Aaron: Yes. If you are a photographer you don’t want to cash all of your photos on someone’s hard drive. We have to be good stewards of what is operating on people’s hard drives. Even something as simple as a blog can benefit from being a PWA. 35:01 – Chuck: Are there new things that are being added to a PWA? 35:12 – Aaron: A new feature is the background sync. Aaron: What is native and what is web? 36:33 – Chuck: Yeah it can detect a feature in your machine. Dark mode is... 36:48 – Aaron: It would be nice to see things standardized across the board. 37:00 – Chuck: How does this play into Electron or Android or...? Do those need to be PWAs? 37:16 – Aaron: It depends on what you are building. So I talked with people through Slack and they want total control. If you r desire is to shift the same experience then Electron can make a lot of sense. They will have to pay a premium, though, your users. If you are aware of that then go the Electron route. But for most cases then Electron might be overkill for you. You don’t need that extra overhead. 39:55 – Aaron continues. Aaron: I think the major benefit of PWA is... 41:15 – Chuck: The other angle to that is that in an Electron app does it make sense to use a PWA things? 41:23 – Aaron: Yes that makes sense. 41:34 – Unless for some reason you need to unlock into an older version, which I hope is not the case b/c of security reasons. 41:55 – Aaron continues. 42:34 – Chuck: Where can we find you? 42:35 – Aaron mentions Twitter and other sites. See Links! 43:02 – Advertisement – Get A Coder Job! Links: Ruby on Rails Angular PWA States Website PWA Twitter Electron Aaron’s Website Aaron’s LinkedIn Aaron’s Twitter Aaron’s GitHub Aaron’s YouTube Channel Aaron’s Medium Get A Coder Job Charles Max Wood’s Twitter Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI   Picks: Aaron Home Going by Yaa Gyasi Zeitoun What is the What Affect Conf. Charles Armada

Panel: Charles Max Wood (DevChat T.V.) Special Guests: Aaron Gustafson In this episode, the Chuck talks with Aaron Gustafson who is a web-standards and accessibility advocate working at Microsoft. Aaron and Chuck talk about PWAs and the ins and outs of these progressive web apps. Check out today’s episode to hear more! Show Topics: 0:36 – Chuck: Our guest is Aaron, say HI! 0:41 – Aaron: Hi! I have been working on the web for 20 plus years. I am working on the Edge team for accessibility among other things. I have done every job that you can do on the web. 1:08 – Chuck: That is one of OUR publications? 1:14 – Aaron: No the communities. I joined the staff as editor in chief for 1.5 year now. It’s a nice side project to do. 1:36 – Chuck: I thought it was a commercial thing. 1:40 – Aaron: No it’s volunteer. 1:52 – Chuck: Talk about your web background? 2:02 – Aaron: I remember the first book I got (title mentioned). My first job on the web (cash) I was the content manager in Florida and this was in 1999. Gel Macs just came out. I relocated from FL to CT and worked for other companies. I got into CSS among other things. It’s been a wild ride and done it all. 3:52 – Chuck: Let’s talk about web standards? 4:05 – Aaron: It depends on the organization and what the spec is and where it originates. It’s interesting to see how HTML developed back in the day. When standardization started working then everything started to converge. Everything is a little different now. Some specs come out from companies that... (Apple, Responsive Images, and Grid are mentioned among other things.) 7:37 – Chuck: We set up to talk about PWAs. Where did PWAs come from? 7:57 – Aaron: Modern web design, best web applications. Being secure. One of the underpinnings came out from Google and they have been supporters of that. Firefox is working on installation as well. The Chrome implementation is weird right now, but it becomes an orphaned app. It’s like the old chrome apps where in Windows you can install from the Microsoft store. But the case of Chrome you don’t have to go through the store. 10:14 – Chuck asks a question. 10:24 – Aaron answers. 11:53 – Chuck: What makes it a progressive web app rather than a regular website? 12:05 – Aaron: The definition is running on HTPS and... Aaron defines the terms that Chuck asks at 11:53. 12:43 – Aaron: Of course you can push forward if it makes sense from the baseline. 12:56 – Chuck: We have an Angular podcast, and we talked about PWAs and nobody had a good definition for it. 13:18 – Aaron. 13:22 – Chuck: What are the pros of having a PWA? Let’s start with the basics first. 13:33 – Aaron: The ability to control how you react to the network. We development is challenging maybe in other areas because of the lack of control and how your code gets to your users. Any special needs that YOU might have. Aaron goes into detail on this topic. 17:14 – Chuck: Is the service worker the star for PWAs? 17:20 – Aaron: In a way, kind of. Aaron goes into detail on this topic. Share 2 is mentioned, too. 19:42 – Chuck: If the service worker intermediates between the browser and the page / Internet would it make sense to have your worker have it load and then load everything else? Cause you have those Web Pack now. 20:14 – Aaron: Some people would consider it but I wouldn’t necessarily. I am not a fan for that. If anything goes wrong then nothing loads. I remember back when... 22:23 – Aaron: That is a lot of overhead. 22:34 – Chuck: I am wondering what is the best practice? How do you decide to pull in a service worker and then move into more complicated issues? 22:53 – Aaron: Progressive Web App where they talk about their evolution about this. 25:17 – Advertisement – Fresh Books! Code: DEVCHAT. 26:25 – Chuck: In order to be a PWA you don’t need to have a push notification. 26:38 – Aaron: I don’t think anyone would want a push notification from me. 27:12 – Chuck: What features do PWAs have? 27:18 – Aaron: Features? None of them really, other than push notifications, it’s just standard it’s going to make an App feel more App “y”. If that’s something you want to do. It’s up to you to determine that. There is going to be like push notifications – sending person new updates about the order. If you were a new site you want to make sure you are not doing a push notifications on everything cause that would be too much. Exercising care with the capabilities with what the users are doing on your computer. This is a person that you are dealing with. We need to seem less needy. Give users control of how they want to use it. For example, Twitter will give you that control per user. 30:56 – Chuck: Could you also do it for different parts of the page? 31:01 – Aaron: It’s different scopes. Your servicer worker has different scopes and it needs to be in the root folder or the JavaScript folder. You can have different workers but they will come from different scopes. 31:32 – Chuck gives a hypothetical example. 31:50 – You can do a bunch of different service workers. 32:11 – Chuck: This is why we create different hierarchies in our code. 32:26 – Chuck: Is there a good point where people can be more informed with PWAs? 32:40 – Aaron: PWA stats website and Twitter account with Cloud 4. 33:22 – Chuck asks a question. 33:26 – Aaron: Yes. If you are a photographer you don’t want to cash all of your photos on someone’s hard drive. We have to be good stewards of what is operating on people’s hard drives. Even something as simple as a blog can benefit from being a PWA. 35:01 – Chuck: Are there new things that are being added to a PWA? 35:12 – Aaron: A new feature is the background sync. Aaron: What is native and what is web? 36:33 – Chuck: Yeah it can detect a feature in your machine. Dark mode is... 36:48 – Aaron: It would be nice to see things standardized across the board. 37:00 – Chuck: How does this play into Electron or Android or...? Do those need to be PWAs? 37:16 – Aaron: It depends on what you are building. So I talked with people through Slack and they want total control. If you r desire is to shift the same experience then Electron can make a lot of sense. They will have to pay a premium, though, your users. If you are aware of that then go the Electron route. But for most cases then Electron might be overkill for you. You don’t need that extra overhead. 39:55 – Aaron continues. Aaron: I think the major benefit of PWA is... 41:15 – Chuck: The other angle to that is that in an Electron app does it make sense to use a PWA things? 41:23 – Aaron: Yes that makes sense. 41:34 – Unless for some reason you need to unlock into an older version, which I hope is not the case b/c of security reasons. 41:55 – Aaron continues. 42:34 – Chuck: Where can we find you? 42:35 – Aaron mentions Twitter and other sites. See Links! 43:02 – Advertisement – Get A Coder Job! Links: Ruby on Rails Angular PWA States Website PWA Twitter Electron Aaron’s Website Aaron’s LinkedIn Aaron’s Twitter Aaron’s GitHub Aaron’s YouTube Channel Aaron’s Medium Get A Coder Job Charles Max Wood’s Twitter Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI   Picks: Aaron Home Going by Yaa Gyasi Zeitoun What is the What Affect Conf. Charles Armada

Panel: Charles Max Wood (DevChat T.V.) Special Guests: Aaron Gustafson In this episode, the Chuck talks with Aaron Gustafson who is a web-standards and accessibility advocate working at Microsoft. Aaron and Chuck talk about PWAs and the ins and outs of these progressive web apps. Check out today’s episode to hear more! Show Topics: 0:36 – Chuck: Our guest is Aaron, say HI! 0:41 – Aaron: Hi! I have been working on the web for 20 plus years. I am working on the Edge team for accessibility among other things. I have done every job that you can do on the web. 1:08 – Chuck: That is one of OUR publications? 1:14 – Aaron: No the communities. I joined the staff as editor in chief for 1.5 year now. It’s a nice side project to do. 1:36 – Chuck: I thought it was a commercial thing. 1:40 – Aaron: No it’s volunteer. 1:52 – Chuck: Talk about your web background? 2:02 – Aaron: I remember the first book I got (title mentioned). My first job on the web (cash) I was the content manager in Florida and this was in 1999. Gel Macs just came out. I relocated from FL to CT and worked for other companies. I got into CSS among other things. It’s been a wild ride and done it all. 3:52 – Chuck: Let’s talk about web standards? 4:05 – Aaron: It depends on the organization and what the spec is and where it originates. It’s interesting to see how HTML developed back in the day. When standardization started working then everything started to converge. Everything is a little different now. Some specs come out from companies that... (Apple, Responsive Images, and Grid are mentioned among other things.) 7:37 – Chuck: We set up to talk about PWAs. Where did PWAs come from? 7:57 – Aaron: Modern web design, best web applications. Being secure. One of the underpinnings came out from Google and they have been supporters of that. Firefox is working on installation as well. The Chrome implementation is weird right now, but it becomes an orphaned app. It’s like the old chrome apps where in Windows you can install from the Microsoft store. But the case of Chrome you don’t have to go through the store. 10:14 – Chuck asks a question. 10:24 – Aaron answers. 11:53 – Chuck: What makes it a progressive web app rather than a regular website? 12:05 – Aaron: The definition is running on HTPS and... Aaron defines the terms that Chuck asks at 11:53. 12:43 – Aaron: Of course you can push forward if it makes sense from the baseline. 12:56 – Chuck: We have an Angular podcast, and we talked about PWAs and nobody had a good definition for it. 13:18 – Aaron. 13:22 – Chuck: What are the pros of having a PWA? Let’s start with the basics first. 13:33 – Aaron: The ability to control how you react to the network. We development is challenging maybe in other areas because of the lack of control and how your code gets to your users. Any special needs that YOU might have. Aaron goes into detail on this topic. 17:14 – Chuck: Is the service worker the star for PWAs? 17:20 – Aaron: In a way, kind of. Aaron goes into detail on this topic. Share 2 is mentioned, too. 19:42 – Chuck: If the service worker intermediates between the browser and the page / Internet would it make sense to have your worker have it load and then load everything else? Cause you have those Web Pack now. 20:14 – Aaron: Some people would consider it but I wouldn’t necessarily. I am not a fan for that. If anything goes wrong then nothing loads. I remember back when... 22:23 – Aaron: That is a lot of overhead. 22:34 – Chuck: I am wondering what is the best practice? How do you decide to pull in a service worker and then move into more complicated issues? 22:53 – Aaron: Progressive Web App where they talk about their evolution about this. 25:17 – Advertisement – Fresh Books! Code: DEVCHAT. 26:25 – Chuck: In order to be a PWA you don’t need to have a push notification. 26:38 – Aaron: I don’t think anyone would want a push notification from me. 27:12 – Chuck: What features do PWAs have? 27:18 – Aaron: Features? None of them really, other than push notifications, it’s just standard it’s going to make an App feel more App “y”. If that’s something you want to do. It’s up to you to determine that. There is going to be like push notifications – sending person new updates about the order. If you were a new site you want to make sure you are not doing a push notifications on everything cause that would be too much. Exercising care with the capabilities with what the users are doing on your computer. This is a person that you are dealing with. We need to seem less needy. Give users control of how they want to use it. For example, Twitter will give you that control per user. 30:56 – Chuck: Could you also do it for different parts of the page? 31:01 – Aaron: It’s different scopes. Your servicer worker has different scopes and it needs to be in the root folder or the JavaScript folder. You can have different workers but they will come from different scopes. 31:32 – Chuck gives a hypothetical example. 31:50 – You can do a bunch of different service workers. 32:11 – Chuck: This is why we create different hierarchies in our code. 32:26 – Chuck: Is there a good point where people can be more informed with PWAs? 32:40 – Aaron: PWA stats website and Twitter account with Cloud 4. 33:22 – Chuck asks a question. 33:26 – Aaron: Yes. If you are a photographer you don’t want to cash all of your photos on someone’s hard drive. We have to be good stewards of what is operating on people’s hard drives. Even something as simple as a blog can benefit from being a PWA. 35:01 – Chuck: Are there new things that are being added to a PWA? 35:12 – Aaron: A new feature is the background sync. Aaron: What is native and what is web? 36:33 – Chuck: Yeah it can detect a feature in your machine. Dark mode is... 36:48 – Aaron: It would be nice to see things standardized across the board. 37:00 – Chuck: How does this play into Electron or Android or...? Do those need to be PWAs? 37:16 – Aaron: It depends on what you are building. So I talked with people through Slack and they want total control. If you r desire is to shift the same experience then Electron can make a lot of sense. They will have to pay a premium, though, your users. If you are aware of that then go the Electron route. But for most cases then Electron might be overkill for you. You don’t need that extra overhead. 39:55 – Aaron continues. Aaron: I think the major benefit of PWA is... 41:15 – Chuck: The other angle to that is that in an Electron app does it make sense to use a PWA things? 41:23 – Aaron: Yes that makes sense. 41:34 – Unless for some reason you need to unlock into an older version, which I hope is not the case b/c of security reasons. 41:55 – Aaron continues. 42:34 – Chuck: Where can we find you? 42:35 – Aaron mentions Twitter and other sites. See Links! 43:02 – Advertisement – Get A Coder Job! Links: Ruby on Rails Angular PWA States Website PWA Twitter Electron Aaron’s Website Aaron’s LinkedIn Aaron’s Twitter Aaron’s GitHub Aaron’s YouTube Channel Aaron’s Medium Get A Coder Job Charles Max Wood’s Twitter Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI   Picks: Aaron Home Going by Yaa Gyasi Zeitoun What is the What Affect Conf. Charles Armada

Panel: Charles Max Wood (DevChat T.V.) Special Guests: Aaron Gustafson In this episode, the Chuck talks with Aaron Gustafson who is a web standards and accessibility advocate working at Microsoft. Aaron and Chuck talk about PWAs and the ins and outs of these progressive web apps. Check out today’s episode to hear more! Show Topics: 0:36 – Chuck: Our guest is Aaron, say HI! 0:41 – Aaron: Hi! I have been working on the web for 20 plus years. I am working on the Edge team for accessibility among other things. I have done every job that you can do on the web. 1:08 – Chuck: That is one of OUR publications? 1:14 – Aaron: No the communities. I joined the staff as editor in chief for 1.5 year now. It’s a nice side project to do. 1:36 – Chuck: I thought it was a commercial thing. 1:40 – Aaron: No it’s volunteer. 1:52 – Chuck: Talk about your web background? 2:02 – Aaron: I remember the first book I got (title mentioned). My first job on the web (cash) I was the content manager in Florida and this was in 1999. Gel Macs just came out. I relocated from FL to CT and worked for other companies. I got into CSS among other things. It’s been a wild ride and done it all. 3:52 – Chuck: Let’s talk about web standards? 4:05 – Aaron: It depends on the organization and what the spec is and where it originates. It’s interesting to see how HTML developed back in the day. When standardization started working then everything started to converge. Everything is a little different now. Some specs come out from companies that... (Apple, Responsive Images, and Grid are mentioned among other things.) 7:37 – Chuck: We set up to talk about PWAs. Where did PWAs come from? 7:57 – Aaron: Modern web design, best web applications. Being secure. One of the underpinnings came out from Google and they have been supporters of that. Firefox is working on installation as well. The Chrome implementation is weird right now, but it becomes an orphaned app. It’s like the old chrome apps where in Windows you can install from the Microsoft store. But the case of Chrome you don’t have to go through the store. 10:14 – Chuck asks a question. 10:24 – Aaron answers. 11:53 – Chuck: What makes it a progressive web app rather than a regular website? 12:05 – Aaron: The definition is running on HTPS and... Aaron defines the terms that Chuck asks at 11:53. 12:43 – Aaron: Of course you can push forward if it makes sense from the baseline. 12:56 – Chuck: We have an Angular podcast, and we talked about PWAs and nobody had a good definition for it. 13:18 – Aaron. 13:22 – Chuck: What are the pros of having a PWA? Let’s start with the basics first. 13:33 – Aaron: The ability to control how you react to the network. We development is challenging maybe in other areas because of the lack of control and how your code gets to your users. Any special needs that YOU might have. Aaron goes into detail on this topic. 17:14 – Chuck: Is the service worker the star for PWAs? 17:20 – Aaron: In a way, kind of. Aaron goes into detail on this topic. Share 2 is mentioned, too. 19:42 – Chuck: If the service worker intermediates between the browser and the page / Internet would it make sense to have your worker have it load and then load everything else? Cause you have those Web Pack now. 20:14 – Aaron: Some people would consider it but I wouldn’t necessarily. I am not a fan for that. If anything goes wrong then nothing loads. I remember back when... 22:23 – Aaron: That is a lot of overhead. 22:34 – Chuck: I am wondering what is the best practice? How do you decide to pull in a service worker and then move into more complicated issues? 22:53 – Aaron: Progressive Web App where they talk about their evolution about this. 25:17 – Advertisement – Fresh Books! Code: DEVCHAT. 26:25 – Chuck: In order to be a PWA you don’t need to have a push notification. 26:38 – Aaron: I don’t think anyone would want a push notification from me. 27:12 – Chuck: What features do PWAs have? 27:18 – Aaron: Features? None of them really, other than push notifications, it’s just standard it’s going to make an App feel more App “y”. If that’s something you want to do. It’s up to you to determine that. There is going to be like push notifications – sending person new updates about the order. If you were a new site you want to make sure you are not doing a push notifications on everything cause that would be too much. Exercising care with the capabilities with what the users are doing on your computer. This is a person that you are dealing with. We need to seem less needy. Give users control of how they want to use it. For example, Twitter will give you that control per user. 30:56 – Chuck: Could you also do it for different parts of the page? 31:01 – Aaron: It’s different scopes. Your servicer worker has different scopes and it needs to be in the root folder or the JavaScript folder. You can have different workers but they will come from different scopes. 31:32 – Chuck gives a hypothetical example. 31:50 – You can do a bunch of different service workers. 32:11 – Chuck: This is why we create different hierarchies in our code. 32:26 – Chuck: Is there a good point where people can be more informed with PWAs? 32:40 – Aaron: PWA stats website and Twitter account with Cloud 4. 33:22 – Chuck asks a question. 33:26 – Aaron: Yes. If you are a photographer you don’t want to cash all of your photos on someone’s hard drive. We have to be good stewards of what is operating on people’s hard drives. Even something as simple as a blog can benefit from being a PWA. 35:01 – Chuck: Are there new things that are being added to a PWA? 35:12 – Aaron: A new feature is the background sync. Aaron: What is native and what is web? 36:33 – Chuck: Yeah it can detect a feature in your machine. Dark mode is... 36:48 – Aaron: It would be nice to see things standardized across the board. 37:00 – Chuck: How does this play into Electron or Android or...? Do those need to be PWAs? 37:16 – Aaron: It depends on what you are building. So I talked with people through Slack and they want total control. If you r desire is to shift the same experience then Electron can make a lot of sense. They will have to pay a premium, though, your users. If you are aware of that then go the Electron route. But for most cases then Electron might be overkill for you. You don’t need that extra overhead. 39:55 – Aaron continues. Aaron: I think the major benefit of PWA is... 41:15 – Chuck: The other angle to that is that in an Electron app does it make sense to use a PWA things? 41:23 – Aaron: Yes that makes sense. 41:34 – Unless for some reason you need to unlock into an older version, which I hope is not the case b/c of security reasons. 41:55 – Aaron continues. 42:34 – Chuck: Where can we find you? 42:35 – Aaron mentions Twitter and other sites. See Links! 43:02 – Advertisement – Get A Coder Job! Links: Ruby on Rails Angular PWA States Website PWA Twitter Electron Aaron’s Website Aaron’s LinkedIn Aaron’s Twitter Aaron’s GitHub Aaron’s YouTube Channel Aaron’s Medium Get A Coder Job Charles Max Wood’s Twitter Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI Picks: Aaron Home Going by Yaa Gyasi Zeitoun What is the What Affect Conf. Charles Armada

Panel: Charles Max Wood (DevChat T.V.) Special Guests: Aaron Gustafson In this episode, the Chuck talks with Aaron Gustafson who is a web standards and accessibility advocate working at Microsoft. Aaron and Chuck talk about PWAs and the ins and outs of these progressive web apps. Check out today’s episode to hear more! Show Topics: 0:36 – Chuck: Our guest is Aaron, say HI! 0:41 – Aaron: Hi! I have been working on the web for 20 plus years. I am working on the Edge team for accessibility among other things. I have done every job that you can do on the web. 1:08 – Chuck: That is one of OUR publications? 1:14 – Aaron: No the communities. I joined the staff as editor in chief for 1.5 year now. It’s a nice side project to do. 1:36 – Chuck: I thought it was a commercial thing. 1:40 – Aaron: No it’s volunteer. 1:52 – Chuck: Talk about your web background? 2:02 – Aaron: I remember the first book I got (title mentioned). My first job on the web (cash) I was the content manager in Florida and this was in 1999. Gel Macs just came out. I relocated from FL to CT and worked for other companies. I got into CSS among other things. It’s been a wild ride and done it all. 3:52 – Chuck: Let’s talk about web standards? 4:05 – Aaron: It depends on the organization and what the spec is and where it originates. It’s interesting to see how HTML developed back in the day. When standardization started working then everything started to converge. Everything is a little different now. Some specs come out from companies that... (Apple, Responsive Images, and Grid are mentioned among other things.) 7:37 – Chuck: We set up to talk about PWAs. Where did PWAs come from? 7:57 – Aaron: Modern web design, best web applications. Being secure. One of the underpinnings came out from Google and they have been supporters of that. Firefox is working on installation as well. The Chrome implementation is weird right now, but it becomes an orphaned app. It’s like the old chrome apps where in Windows you can install from the Microsoft store. But the case of Chrome you don’t have to go through the store. 10:14 – Chuck asks a question. 10:24 – Aaron answers. 11:53 – Chuck: What makes it a progressive web app rather than a regular website? 12:05 – Aaron: The definition is running on HTPS and... Aaron defines the terms that Chuck asks at 11:53. 12:43 – Aaron: Of course you can push forward if it makes sense from the baseline. 12:56 – Chuck: We have an Angular podcast, and we talked about PWAs and nobody had a good definition for it. 13:18 – Aaron. 13:22 – Chuck: What are the pros of having a PWA? Let’s start with the basics first. 13:33 – Aaron: The ability to control how you react to the network. We development is challenging maybe in other areas because of the lack of control and how your code gets to your users. Any special needs that YOU might have. Aaron goes into detail on this topic. 17:14 – Chuck: Is the service worker the star for PWAs? 17:20 – Aaron: In a way, kind of. Aaron goes into detail on this topic. Share 2 is mentioned, too. 19:42 – Chuck: If the service worker intermediates between the browser and the page / Internet would it make sense to have your worker have it load and then load everything else? Cause you have those Web Pack now. 20:14 – Aaron: Some people would consider it but I wouldn’t necessarily. I am not a fan for that. If anything goes wrong then nothing loads. I remember back when... 22:23 – Aaron: That is a lot of overhead. 22:34 – Chuck: I am wondering what is the best practice? How do you decide to pull in a service worker and then move into more complicated issues? 22:53 – Aaron: Progressive Web App where they talk about their evolution about this. 25:17 – Advertisement – Fresh Books! Code: DEVCHAT. 26:25 – Chuck: In order to be a PWA you don’t need to have a push notification. 26:38 – Aaron: I don’t think anyone would want a push notification from me. 27:12 – Chuck: What features do PWAs have? 27:18 – Aaron: Features? None of them really, other than push notifications, it’s just standard it’s going to make an App feel more App “y”. If that’s something you want to do. It’s up to you to determine that. There is going to be like push notifications – sending person new updates about the order. If you were a new site you want to make sure you are not doing a push notifications on everything cause that would be too much. Exercising care with the capabilities with what the users are doing on your computer. This is a person that you are dealing with. We need to seem less needy. Give users control of how they want to use it. For example, Twitter will give you that control per user. 30:56 – Chuck: Could you also do it for different parts of the page? 31:01 – Aaron: It’s different scopes. Your servicer worker has different scopes and it needs to be in the root folder or the JavaScript folder. You can have different workers but they will come from different scopes. 31:32 – Chuck gives a hypothetical example. 31:50 – You can do a bunch of different service workers. 32:11 – Chuck: This is why we create different hierarchies in our code. 32:26 – Chuck: Is there a good point where people can be more informed with PWAs? 32:40 – Aaron: PWA stats website and Twitter account with Cloud 4. 33:22 – Chuck asks a question. 33:26 – Aaron: Yes. If you are a photographer you don’t want to cash all of your photos on someone’s hard drive. We have to be good stewards of what is operating on people’s hard drives. Even something as simple as a blog can benefit from being a PWA. 35:01 – Chuck: Are there new things that are being added to a PWA? 35:12 – Aaron: A new feature is the background sync. Aaron: What is native and what is web? 36:33 – Chuck: Yeah it can detect a feature in your machine. Dark mode is... 36:48 – Aaron: It would be nice to see things standardized across the board. 37:00 – Chuck: How does this play into Electron or Android or...? Do those need to be PWAs? 37:16 – Aaron: It depends on what you are building. So I talked with people through Slack and they want total control. If you r desire is to shift the same experience then Electron can make a lot of sense. They will have to pay a premium, though, your users. If you are aware of that then go the Electron route. But for most cases then Electron might be overkill for you. You don’t need that extra overhead. 39:55 – Aaron continues. Aaron: I think the major benefit of PWA is... 41:15 – Chuck: The other angle to that is that in an Electron app does it make sense to use a PWA things? 41:23 – Aaron: Yes that makes sense. 41:34 – Unless for some reason you need to unlock into an older version, which I hope is not the case b/c of security reasons. 41:55 – Aaron continues. 42:34 – Chuck: Where can we find you? 42:35 – Aaron mentions Twitter and other sites. See Links! 43:02 – Advertisement – Get A Coder Job! Links: Ruby on Rails Angular PWA States Website PWA Twitter Electron Aaron’s Website Aaron’s LinkedIn Aaron’s Twitter Aaron’s GitHub Aaron’s YouTube Channel Aaron’s Medium Get A Coder Job Charles Max Wood’s Twitter Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI Picks: Aaron Home Going by Yaa Gyasi Zeitoun What is the What Affect Conf. Charles Armada

Adam och Kristoffer samtalar om de bästa sessionerna från Drupalcon. Diskussion om keynotes. På plats i Wien gjordes även intervjuer med Johanna och Andreas från Lunds Universitet och Tomas från Digitalist. Vi diskuterar även Drupal(con) Europe 2018. Länkar till moduler, webbplatser och tjänster vi pratade om i detta avsnitt: Dagens avsnitt Drupalcon Vienna 2017 Driesnote Monique J. Morrow Everyone Has Something to Share Responsive Images and Art Direction in Drupal 8 State of the media initiative The Layout Initiative Estimates are dead, long live forecasting! Drush 9 - Lean and Modern Lunds Universitet Lunds Data Central LDC Commerce 2.x: Lessons learned 10 Ways Drupal 8 Is More Secure Digitalist DrupalEurope - Hello World!

Добрый день уважаемые слушатели. Представляем новый выпуск подкаста RWpod. В этом выпуске: Ruby Refinery CMS 4.0.0 Released with Rails 5.1 support, Brakeman 4.0 Released, yield_self in Ruby 2.5 и CSV::Row#each etc. return enumerator when no block given Decide For Yourself If Rails Is Actually Dying, What Did I Learn After Going Eighteen Months Without Rails и Kernel#fork broken in MacOS 10.13 High Sierra. Puma and Unicorn are affected Do. Or Do Not. There Is No Try - Object#try Considered Harmful, Nullalign - a tool to detect missing non-null constraints in Rails projects и Creating a Basic Gem JavaScript React v16.0, React 16: A look inside an API-compatible rewrite of our frontend UI library и Relicensing the GraphQL specification setImmediate() vs nextTick() vs setTimeout(fn,0) – in depth explanation, Fundamentals of Responsive Images, Essential Image Optimization (ebook) Draggable - lightweight, responsive, modern drag & drop library, Lozad.js: Performant Lazy Loading of Images и Technical and non-technical guide for rocking your coding interview Conferences Ruby Meditation #18

Eric Portis joins me to dig into the world of responsive images. We start at the basics. Responsive images are specifically images in HTML and exist because of a desire for better performance. Images are probably the biggest culprit in the overall weight of websites. If we can avoid sending too many pixels across the network, we should. After all, a screen that is only 720 pixels wide doesn’t need a 2000 pixel wide image, even if it’s a 2x … Read article “#155: Responsive Images, WordPress, and Cloudinary”

We're getting up to speed with the fascinating world of web frontend performance. Concatenation, compression, optimization and more delivered in one speedy package this week! Kenneth, Kevin & Len are joined by Mannuel Ferreira, a web designer and developer from Superbalist.com. Mannuel shares with us some practical experiences he's had at his current job making Superbalist fast, as well as the work he did at World Wide Creative on a recent relaunch of the IOL website. Mannuel has a lot to share with practical tips and tricks to help all of us make our websites performant. Follow Mannuel online: - http://themwebs.me - https://twitter.com/manidf - https://github.com/manidf Here are some resources mentioned during the show: * PageSpeed Insights - https://developers.google.com/speed/pagespeed/insights/ * Website Speed Test - http://tools.pingdom.com/fpt/ * SpeedCurve - https://speedcurve.com/ * Load Google Fonts asynchronously for page speed - http://bit.ly/1QTsiYh * Understanding the critical rendering path - http://bit.ly/22fjmnf * Quick guide to webfonts via @font-face - http://bit.ly/1nJJALE * Google Web Font Loader Events - http://bit.ly/1RhP6D7 * Font Face Observer - http://bit.ly/1TJywME * HTML5's async Script Attribute - http://bit.ly/1RhPhOR * Gulp - http://gulpjs.com/ * Bourbon - http://bourbon.io/ * Neat - http://neat.bourbon.io/ * How to optimize your site with GZIP compression - http://bit.ly/250Kplk * Grunt: The JavaScript task runner - http://gruntjs.com/ * webpack module bundler - https://webpack.github.io/ * broccoli.js - http://broccolijs.com/ * Working with quotas on mobile browsers - http://bit.ly/1pqd9DV * Mobile Browser Cache Limits, Revisited - http://bit.ly/1S0xwR6 * CSS Transitions - http://bit.ly/1pqdwhC * Add two variables using jQuery - http://bit.ly/1pHxe8D * fetch API - https://davidwalsh.name/fetch * A window.fetch polyfil from Github - https://github.com/github/fetch * Essential reading list for getting started with Service Workers - http://bit.ly/1Ln7MPJ * Offline First! - http://offlinefirst.org/ * Leverage Browser Caching - http://bit.ly/1U2dIkd * HTTP/2 - https://http2.github.io/ * HTTP/2 on CloudFlare - https://www.cloudflare.com/http2/ * HTTP/2 on Akamai - https://http2.akamai.com/ * HTTP/2 on nginx - http://bit.ly/1QSQicL * HTTP/2 on Apache httpd - http://bit.ly/1RhP3an * Forgo JS packaging? Not so fast - http://bit.ly/1pqdsyp * HTML5 picture element - http://mzl.la/1RiKzKs * Built-in Browser Support for Responsive Images - http://bit.ly/1P92DoY * Picturefill: a responsive image polyfill - https://scottjehl.github.io/picturefill/ * How to avoid duplicate downloads in responsive images - http://bit.ly/1Mj60tv * Modernizr - https://modernizr.com/ * Responsive logos with SVG - http://bit.ly/1RiKOoP * CSS Only Image Preloading - http://bit.ly/1SO01Uj * Prefetching, preloading, prebrowsing - http://bit.ly/1S0xMPS * HTML5 Link Prefetching - http://bit.ly/1RKeL1x * AngularJS Server Side Rendering - https://github.com/saymedia/angularjs-server * From AngularJS to React: The Isomorphic Way - http://bit.ly/1QSQcC1 * Ember FastBoot - https://github.com/tildeio/ember-cli-fastboot * AMP (Accelerated Mobile Pages) Project - https://www.ampproject.org/ * Designing for Performance - http://designingforperformance.com/ And finally our picks Kevin: - statsd - https://github.com/etsy/statsd - Chrome Developer Tools - https://developer.chrome.com/devtools Kenneth: - High Performance Browser Networking - http://chimera.labs.oreilly.com/books/1230000000545 Mannuel: - CSS Stats - http://cssstats.com/ - Big Rig - https://github.com/GoogleChrome/big-rig - SpeedCurve - https://speedcurve.com/pricing/ Thanks for listening! Stay in touch: * Socialize - https://twitter.com/zadevchat & http://facebook.com/ZADevChat/ * Suggestions and feedback - https://github.com/zadevchat/ping * Subscribe and rate in iTunes - https://itunes.apple.com/za/podcast/zadevchat-podcast/id1057372777

This is a replay of the live broadcast with Jason Tucker, Jonathan Denwood, Jacob Arriola, and Bridget WillardThe post EP013 – Responsive Images & Documentation -#WPblab appeared first on WPwatercooler. See acast.com/privacy for privacy and opt-out information.

This week on WPwatercooler we'll be discussing WordPress 4.4 – New Default Theme Twenty Sixteen, Responsive Images, post embeds, REST API, terms meta and other awesome nuggets.Show airs Dec 21 at 11:00 AM PST /  12:00 PM MST / 1:00 PM CST /  2:00 PM EST /  7:00 PM UTCShow Notes* Version 4.4 – WordPress Codex* Hogg Blog – Sunrises, sunsets, EDM* How to use responsive image support in WordPress 4.4* Using the new REST API in WordPress 4.4* WordPress › Changes to fields output by comment_form in WordPress 4.4 – Make WordPress Core* WordPress – TinyMCE Advanced « WordPress Plugins[LISTATTENDEES event_identifier=”ep167-discussing-wordpress-4-4-dec-21-2015-5-567788187dcbe” show_gravatar=”true”] See acast.com/privacy for privacy and opt-out information.

Welcome to the Post Status Draft podcast, which you can find on iTunes and via RSS for your favorite podcatcher. Brian and his co-host, Joe Hoyle, a co-founder and the CTO of Human Made, discuss some of today’s hottest, current WordPress news. In this episode of Draft, Joe and Brian discuss Google’s AMP project for Accelerated Mobile Page loading, and what it means for WordPress. They also go in-depth on WordPress’s upcoming core support for handling responsive images. Topics & Links Google's AMP AMP How AMP works WordPress AMP plugin AMP on Neiman Lab: What publishers need to know Responsive Images (starts at 35 minutes in) Responsive images merge Merge Proposal Plugin version

You know about responsive images. It’s about the image syntax in HTML. If you give it the right information in the right syntax, you can get the browser to download just exactly the right image it needs, without giving it too much or too little image data. It’s fantastic for performance. You know that to get the most out of responsive images you should polyfill it with Picturefill. You download it, you include it on your page. You have … Read article “#141: Getting the Images and Numbers for Responsive Images”

Welcome to Episode 43 of Apply Filters. Today we dig into Backpress, a PHP library of some of the core functionality of WordPress. Backpress grew out of the core of WP and is now the muscle behind GlotPress, a popular web-based software translation tool. However, the future of this tool is in question. The post Episode 43 – Backpress, Responsive Images, and Post Type Labels for Featured Images appeared first on Apply Filters.

Welcome to Episode 43 of Apply Filters. Today we dig into Backpress, a PHP library of some of the core functionality of WordPress. Backpress grew out of the core of WP and is now the muscle behind GlotPress, a popular web-based software translation tool. However, the future of this tool is in question. The post Episode 43 – Backpress, Responsive Images, and Post Type Labels for Featured Images appeared first on Apply Filters.

In this episode, we discuss commercial plugins on GitHub, welcome screens after updates, comparing similar plugins, responsive images, and more. The post Episode 39 – Commercial Plugins on GitHub, Welcome Screens, Comparing Plugins, Responsive Images appeared first on Apply Filters.

In this episode, we discuss commercial plugins on GitHub, welcome screens after updates, comparing similar plugins, responsive images, and more. The post Episode 39 – Commercial Plugins on GitHub, Welcome Screens, Comparing Plugins, Responsive Images appeared first on Apply Filters.

It's time to start using responsive images on our websites. You specify multiple files in your image HTML. Browsers download the best one for a user's screen size or context. Improve image quality. Save bandwidth. Make sites load faster. Jason Grigsby joins Jen Simmons to explain all the details.

Der ewig optimistische Sonnenschein Schepp und Miese-Peter nahmen für diese Revision verschiedene neue Produkte unter die Lupe, die Webentwicklern in Zukunft Arbeit abnehmen (für Responsive Images) oder (in Form einer neuen IE-Version) aufbürden könnten. Außerdem gibt es reichlich Links. Schaunotizen [00:00:21] Responsive Images Specification and Real-World Scenarios Von den Machern von WURFL (einer Datenbank rund […]

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about the latest in web design, web development, HTML 5, front end development, and more.

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about the latest in web design, web development, HTML 5, front end development, and more.

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about the latest in web design, web development, HTML 5, front end development, and more.

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about the latest in web design, web development, HTML 5, front end development, and more.

Scott Jehl and Jeffrey Zeldman discuss the picture element: a container for multiple images. Making the emerging W3C standard picture element work in today's browsers. Polyfills and progressive enhancement. Responsible responsive design. Shim versus polyfill; srcset versus picture; the prefix wars. Balancing company projects and open source, community projects. Picturefill is a responsive images polyfill approach that web designers and developers can use today. Scott Jehl is a web designer and developer who works with the bright folks at Filament Group, where he creates websites and applications for a range of clients (including the 2012 responsive design of the Boston Globe). He is an active contributor to the open source community, frequently releasing ideas and projects on Github; a jQuery team member (most recently leading the development of the jQuery Mobile project); and the co-author of Designing With Progressive Enhancement (New Riders: 2010)

Scott Jehl and Jeffrey Zeldman discuss the picture element: a container for multiple images. Making the emerging W3C standard picture element work in today’s browsers. Polyfills and progressive enhancement. Responsible responsive design. Shim versus polyfill; srcset versus picture; the prefix wars. Balancing company projects and open source, community projects. Picturefill is a responsive images polyfill approach that web designers and developers can use today. Scott Jehl is a web designer and developer who works with the bright folks at Filament Group, where he creates websites and applications for a range of clients (including the 2012 responsive design of the Boston Globe). He is an active contributor to the open source community, frequently releasing ideas and projects on Github; a jQuery team member (most recently leading the development of the jQuery Mobile project); and the co-author of Designing With Progressive Enhancement (New Riders: 2010)

I’m probably a bit rare in that I rather enjoyed trying to keep up on the responsive images thing. It’s an interesting problem that bred lots of interesting solutions. The whole thing is starting to wrap up now though, now that the official solutions are: and friends with srcset and sizes The problem is: I don’t really get it. I thought the original picturefill was pretty simple. List a bunch of sources with media queries. First one to … Read article “#133: Figuring Out Responsive Images”

This week we're super lucky to be joined by Mat Marquis, chair of the Responsive Images Community Group, staffer on A List Apart and much more. Mat has been pushing for a solution to responsive images for ever and finally we're almost at the point at which we can say we have a solution with .

SVG is one of several image formats for the web — one that has superpowers that the others don't. When would you want to use SVG & what can you do with it? Doug Schepers joins Jen Simmons to tell all.

PodLuolan uumenista kantautuu jälleen kerran ääntä. Tällä kertaa Olli saatiin tynnyristä ulos ja ääni on laadukkaampaa. Kova yritys oli tiivistää jakson mittaa ja melkein siinä onnistuttiinkin. Oletko turvassa - XP:n tuki päättyy Windows XP:n tuki päättyy 8.4.2014 ja sitä myöten saamme jättää jäähyväiset toivon mukaan myös Internet Explorer 8:lle. Innolla odotamme miten tämä näkyy käytännön tasolla ja jäämme odottamaan Vistan tuen päättymistä vuonna 2017. Picture-elementin implementointi Blinkiin Responsive Images Comunity Group (RICG) on häärinyt picture elementin kanssa. Nyt ollaan ilmeisesti päästy yhteisymmärrykseen tuosta ja pitäisi implementoida selaimoottoreihin. Yoav Weiss niminen kaveri (freelancer) on pistänyt pystyyn Indie GoGo:hon kamppiksen, jossa tavoitteena on kerätä 10 000 dollaria jotta Picture elementti saadaan mahdollisimman nopeaa Blinkiin (ja sitä myöten Chrome + Opera). Ja tavoitehan on täytetty. Lisärahoituksella kehittäjä lupasi ottaa mm. element queryt harkintaan/työn alle! Picture srcset kuvallisesti Mikäli picture-elementin todellinen hyöty on hieman epäselvä niin Eric Portis tarjoaa kuvallisen selityksen miten homma tulee toimimiaan. Element queryn tila vuonna 2014 Tab Atkins kertoilee hieman element queryistä. Tai itseasiassa päivittää tilanteen ja odotettavissa olevat haasteet. VagrantPress Jos Wordpressin päälle kehittäminen kiinnostaa ja sen haluaa saada mahdollisimman kevyesti ylös on Vagrantpress näppärä paketti siihen. Koneella pitää olla asennettuna Vagrant (Win, Mac, linux) jonka jälkeen otetaan klooni github-reposta. Myös VirtualBox on hyvä asentaa. Tämän jälkeen komennetaan vagrant up ja loppu on automaagista. Ensimmäisellä kerralla tulee olla verkkoyhteys mutta jälkeenpäin onnistuu ilman yhteyttä. Wordpress API Edellisessä jaksossa puhuttiin Hypermedia API:sta, joten tämä on hyvää jatkoa sille. WP API tarjoaa JSON-pohjaisen REST-rajapinnan Wordpressille. Plugin on aika geneerinen mutta kohtalaisen helposti laajennettavissa eri projekteihin. Tarvittaessa jopa toiminnallisen proton backend on mahdollista tämän avulla saada nopeasti pystyyn. WPML Mikäli Wordpress on tarve saada monikieliseksi on WPML siihen oiva työkalu. Hyvin pitkälle kaikki Wordpressissä on lokalisoitavissa. Ja suoraan Wordpressin backendistä. WP-toolset WP-Toolset tarjoaa useita eri työkaluja tehokkaaseen Wordpressin säätöön.

Responsive images are one of those easy to solve issues, just add max-width:100%, but end up being one of the most difficult things to do perfectly. This week I look at your different options to approach RWD images and the best way forward for you.

このページをウェブブラウザで見る: リンク 今週はゲストに@masakiishitaniさんを迎えた、みたいもんスペシャル。ライフログの歴史からひらくPCバッグの現状、CP+の感想など気になる話題を2時間たっぷりお届けします。 audio 要素はサポートされていません Download MP3 (57.7MB) 今週のニュース 単語が目に飛び込んできてすごい速度で文章を読めるようになる「Spritz」 - GIGAZINE 【未来すぎヤバい】あなたの脳機能を倍増「オーバークロック」させるデバイス『foc.us』がついに。鳥肌が止まらない・・・ Google、モジュール式携帯Project Araを2015年発売。最小構成50ドルからお好みで組み合わせ - Engadget Japanese New Gesture-Recognition Tech Lets You Control Your Phone in Your Pocket 3594-140226 OS X Mavericks 10.9.2 アップデイトでFaceTime オーディオできるようになった: shiology Reports say OS X 10.9.2 breaks AirPlay Mirroring, and other news for Feb. 28, 2014 Breaking Apple News, Tips and Reviews from The Unofficial Apple Weblog 仮想通貨ビットコインに関する史上最大の事件TOP6 : ギズモード・ジャパン 日テレがHuluを買う理由 Huluが日本事業を売る理由 ひとりぶろぐ » iPhone 5sのバーストモードで撮影した写真から、手ぶれが一番少ない写真を簡単に選ぶ方法 GitHubがハックし放題なテキストエディタ「Atom」のベータ版をリリース : ギズモード・ジャパン 「Sleipnir 5.1」公開、タブを見つけやすくする新機能を追加 - [モ]Modern Syntax Chromium Blog: Chrome 34: Responsive Images and Unprefixed Web Audio 震災から 3 年、キオクと復興の今～ 写真とストリートビューでたどる震災と復興の 3 年間。 パリミキとセカイカメラ開発者がタッグ、「雰囲気メガネ」 田村淳＆つるの剛士　お台場APPSラボ - フジテレビ 歌うキーボード　ポケット・ミク VOCALOID内蔵のループ・シーケンサー！ 電卓型の新しい音系ガジェット「VOCALOOP」が発表！ 今週のネタ(みたいもん特集) インターネットのこの10年を考えるための最高のアーカイブ、インターネット白書が無料公開 ひらくPCバッグのインタビュー記事2本掲載、そしてやっと発送できましたのお知らせ SIGMA「dp quattro」シリーズのデザインの源流はディーター・ラムスにあり CP+2014：FUJIブース、X-T1はずっと触っていたいデジカメ、あとずっと撮っていたい感じのモデルさんは「竹下明希」さんでした memoto改めNarrative Clipがついに届いたぞ！やっぱりこいつは最高のライフログカメラ！:[mi]みたいもん！ CP+2014：製品での自信がブース設計に現れたソニーブース、4KハンディカムAX-100！これはいつか欲しい:[mi]みたいもん！ 公開 CP+2014：オリンパスブース「山岸 伸×舞川あいくトークライブ」超ガチな写真トークに大満足:[mi]みたいもん！ 今週のガジェット 3592-140224 shio的真打ちカメラはシグマDPシリーズ、そしてdpシリーズへ: shiology IFTTT / Automatic Channel 指の動きだけで完全操作！　魔法のような指輪型ウェアラブルガジェット「Ring」がプレオーダーを開始 : ギズモード・ジャパン 次週予告・告知 遂に念願のpodcast対応をした第9回目の放送はいかがだったでしょうか？番組中に紹介したネタのリンクは http://backspace.fm から参照してください。 番組内容に関するフィードバックやリクエストなどもお気軽にコメント頂けると励みになります。 来週もよろしくお願いします！

Mat Marquis, chair of the W3C Responsive Images Community Group, sits down with Zeldman to discuss guidelines for responsive images in multi-device design. The two web designers discuss the history, theory, and multi-leveled challenge of responsive images, the path to standardization, and what browsers will do next. The goal of a “responsive images” solution is to deliver images optimized for the end user's context, rather than serving the largest potentially necessary image to everyone. Unfortunately, this hasn't been quite so simple in practice as it is in theory.

Mat Marquis, chair of the W3C Responsive Images Community Group, sits down with Zeldman to discuss guidelines for responsive images in multi-device design. The two web designers discuss the history, theory, and multi-leveled challenge of responsive images, the path to standardization, and what browsers will do next. The goal of a “responsive images” solution is to deliver images optimized for the end user’s context, rather than serving the largest potentially necessary image to everyone. Unfortunately, this hasn’t been quite so simple in practice as it is in theory.

Yhteys PodLuolasta avautuu jälleen. Aiheena on JavaScript ja sen käyttö. Tarvitseeko aina sitä jQuerya pukata ensimmäisenä projektiin kiinni? Tähän vastaavat Tommi ja Olli. Shownotes Trendi meillä ja maailmalla tuntuu olevan pois jQueryn käytöstä. Ollaanko siirtymässä samanlaiseen tilanteeseen kuin Flashin kanssa oli jokunen vuosi takaperin? Ei sitä jQueryä kaikkeen tarvitse, selaintuki javascriptillä on jo aika hyvä ja useimmiten puhtaalla js:llä pärjää. You might not need jQuery Writing A Better JavaScript Library For The DOM Introducing Live Extensions For Better-DOM: What They Are And How They Work A Dive Into Plain JavaScript Chrome 34 ja Opera 21 kytkevät img srcset -tuen päälle. Vaihtoehtoja kuitenkin on tarjolla One Solution To Responsive Images https://src.chromium.org/viewvc/blink?revision=166264&view=revision Explaining The Last Clause of the src-n Grammar Podcast haluaa kehittyä. Palautetta tarvitaan. Vastaa kyselyymme.

Olli ja Tommi keräävät vuoden 2013 pääasiat ja merkittävimmät jutut nippuun kommenttie kera. Lisäksi otetaan katsaus vuoteen 2000… siis 2014. Vuoden viimeisen podcastin myötä tarjoillaan pitkä pläjäys käsikirjoittamatonta materiaalia. Ja ohjaajan versiona. Linkkejä http://tabatkins.github.io/specs/respimg/Overview.html http://calendar.perfplanet.com/2013/breaking-the-pagespeed-barrier-with-bootstrap/ http://bradfrostweb.com/blog/post/designing-in-the-open/

Wenn es keine Themen gibt, macht man sich einfach welche. So luden Schepp, Peter und Stefan kurzerhand den Anselm ein und sprachen über Responsive Images (Anselm ist zufällig Experte auf dem Gebiet) sowie Verträge und Geschäftspraktiken im Webentwickler-Alltag. Schaunotizen [00:00:20] Responsive Images Anselm ist seit Anbeginn der Zeiten mit den Thema Responsive Images befasst und […]

Diese Woche war mal wieder ein Gast im Working Draft dabei: Sven Wolfermann gab sich die Ehre ein wenig über seine Projekte und Erfahrungen mit Responsive Images und vielem mehr Preis zu geben. [00:01:09] News 3 Jahre Working Draft! Uns gibt es drei Jahre, und wir sind cool. Danke an Mama! Firefox 25 veröffentlicht Firefox […]

The debate around responsive images has been raging for about two years with seemingly limited traction from browser makers. Like anything Web, turns out that this problem is not as simple to solve as it first appears. To understand the complexities, we need to pop the hood of a browser and see how resources are requested without waiting for layout. Once we understand how a browser's handle image loading, we can then start discussing possible solutions — of which there are many right now on the table. It may turn out that we have most of the bits we need to do responsive images, but a standardised (in-browser) solution may still be needed. More info at: https://fronteers.nl/congres/2013/sessions/responsive-images

The debate around responsive images has been raging for about two years with seemingly limited traction from browser makers. Like anything Web, turns out that this problem is not as simple to solve as it first appears. To understand the complexities, we need to pop the hood of a browser and see how resources are requested without waiting for layout. Once we understand how a browser's handle image loading, we can then start discussing possible solutions — of which there are many right now on the table. It may turn out that we have most of the bits we need to do responsive images, but a standardised (in-browser) solution may still be needed. More info at: https://fronteers.nl/congres/2013/sessions/responsive-images

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about Responsive Images and HTML5 Form Inputs.

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about Responsive Images and HTML5 Form Inputs.

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about Reflections, Mobile Typography and Responsive Images.

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about Reflections, Mobile Typography and Responsive Images.

This week I talk to Mat Marquis about responsive images, the main and picture element, jQuery Mobile and the Burrito Bomber.

Auf der beyond tellerrand haben wir den Open Web Standards Evangelisten Bruce Lawson von Opera getroffen und ihn Fragen zu Webstandards, Responsive Images, Operas Beteiligung an neuen Spezifikationen und zu seinen grandiosen Hut gestellt.

Responsive images are the hot topic this year and we are finally getting to an end. An editor's draft has been written for the W3C. But now you might wanna now, where we go and what to use. I'll give you a quick overview. And show how it could work on devices. More info at: https://fronteers.nl/congres/2012/jam-session/the-road-to-responsive-images-anselm-hannemann

Responsive images are the hot topic this year and we are finally getting to an end. An editor's draft has been written for the W3C. But now you might wanna now, where we go and what to use. I'll give you a quick overview. And show how it could work on devices. More info at: https://fronteers.nl/congres/2012/jam-session/the-road-to-responsive-images-anselm-hannemann

Diesmal haben sich Hans, Rodney und Kahlil zum schnacken getroffen. [00:00:29] Responsive Images – Editor’s Draft Responsive Images – Editor’s Draft Responsive Bilder haben jetzt auch einen Working Draft. Schaunotizen [00:01:14] Stick your landings! position: sticky lands in WebKit – HTML5Rocks Updates `position: sticky` ist im Webkit gelandet gelandet und wir beschreiben was das macht […]

What's the best way to handle responsive images? There's been a lot of discussion flying around over the last many months, big debates and fast changes… where have we landed? What's coming in the future? Responsive Images Community Group chair Mat Marquis joins Jen Simmons to sort it all out.