�ݺ�ߣshows by User: theodorebiadala

�ݺ�ߣshows by User: theodorebiadala / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: theodorebiadala / Mon, 16 Jan 2017 11:17:20 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: theodorebiadala Offline Drupal with progressive web app /slideshow/offline-drupal-with-progressive-web-app-71054822/71054822 offline-first-jp-en-170116111720
Presentation from the "Offline Drupal with progressive web app" session at drupalcamp japan: http://2017.drupalcampjapan.net/]]>
Presentation from the "Offline Drupal with progressive web app" session at drupalcamp japan: http://2017.drupalcampjapan.net/]]> Mon, 16 Jan 2017 11:17:20 GMT /slideshow/offline-drupal-with-progressive-web-app-71054822/71054822 theodorebiadala@slideshare.net(theodorebiadala) Offline Drupal with progressive web app theodorebiadala Presentation from the "Offline Drupal with progressive web app" session at drupalcamp japan: http://2017.drupalcampjapan.net/ <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/offline-first-jp-en-170116111720-thumbnail.jpg?width=120&height=120&fit=bounds" /> Presentation from the "Offline Drupal with progressive web app" session at drupalcamp japan: http://2017.drupalcampjapan.net/

Offline Drupal with progressive web app from Th辿odore Biadala

]]> 2084 6 https://cdn.slidesharecdn.com/ss_thumbnails/offline-first-jp-en-170116111720-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Frontend thunderdome https://fr.slideshare.net/slideshow/frontend-thunderdome/55600352 frontendthunderdome-151128103046-lva1-app6892
The year is 2015, in the wasteland that is the internet frontend community, Decoupled Drupal is all the rage. China, India and the African continent are releasing an army of juggernaut armed with cheap or "outdated" hardware onto the internet. Clients wants single page apps, fancy JS frontend, app-level experience for their next coporate social media extranet, better known as the "corporate cat picture library". This developer stuck in the methane refinery of web development will pit juggernauts against client's obnoxious wishes in… The Frontend Thunderdome. This talk is about putting reality back into the current mass hysteria around full js frontend. It features 5 years old hardware, angular, ember, performance and graphs. ]]>
The year is 2015, in the wasteland that is the internet frontend community, Decoupled Drupal is all the rage. China, India and the African continent are releasing an army of juggernaut armed with cheap or "outdated" hardware onto the internet. Clients wants single page apps, fancy JS frontend, app-level experience for their next coporate social media extranet, better known as the "corporate cat picture library". This developer stuck in the methane refinery of web development will pit juggernauts against client's obnoxious wishes in… The Frontend Thunderdome. This talk is about putting reality back into the current mass hysteria around full js frontend. It features 5 years old hardware, angular, ember, performance and graphs. ]]> Sat, 28 Nov 2015 10:30:46 GMT https://fr.slideshare.net/slideshow/frontend-thunderdome/55600352 theodorebiadala@slideshare.net(theodorebiadala) Frontend thunderdome theodorebiadala The year is 2015, in the wasteland that is the internet frontend community, Decoupled Drupal is all the rage. China, India and the African continent are releasing an army of juggernaut armed with cheap or "outdated" hardware onto the internet. Clients wants single page apps, fancy JS frontend, app-level experience for their next coporate social media extranet, better known as the "corporate cat picture library". This developer stuck in the methane refinery of web development will pit juggernauts against client's obnoxious wishes in… The Frontend Thunderdome. This talk is about putting reality back into the current mass hysteria around full js frontend. It features 5 years old hardware, angular, ember, performance and graphs. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/frontendthunderdome-151128103046-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /> The year is 2015, in the wasteland that is the internet frontend community, Decoupled Drupal is all the rage. China, India and the African continent are releasing an army of juggernaut armed with cheap or "outdated" hardware onto the internet. Clients wants single page apps, fancy JS frontend, app-level experience for their next coporate social media extranet, better known as the "corporate cat picture library". This developer stuck in the methane refinery of web development will pit juggernauts against client's obnoxious wishes in… The Frontend Thunderdome. This talk is about putting reality back into the current mass hysteria around full js frontend. It features 5 years old hardware, angular, ember, performance and graphs.

from Th辿odore Biadala

]]> 1473 5 https://cdn.slidesharecdn.com/ss_thumbnails/frontendthunderdome-151128103046-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Headful drupal /slideshow/headful-drupal/53104788 headfuldrupal-150923111426-lva1-app6891
Video here: https://www.youtube.com/watch?v=9KYzOtAiuqY Headless Drupal certainly is popular, so is fast and maintainable code. This session will talk about JavaScript in general, presenting the latest news about the language and it's ecosystem, and Drupal in particular, exposing how Drupal could benefit from the language's evolution. This session will present news from around the frontend world and will be used to talk about: what developers want Drupal JS to do (or not do!), approaches for the Refactor of Doom (RD) that need to happen for JavaScript to be unit-testable (ES6 modules, patterns, etc.), intermediate steps to make some amount of testing possible prior to the RD, tools aimed at Drupal JS developers (eslint plugins, nodejs utilities for Drupal, etc.) frameworks, how to make decoupled implementations easier (aka. giving back some brains to headless implementations) anything else that is important to you. Core frontend is vastly better than it used to be, so much so that going headless because Drupal is a pain to work with is not an argument that can be made easily. Help us make that argument stronger to prevent people from loosing their head and drive projects to the ground. ]]>
Video here: https://www.youtube.com/watch?v=9KYzOtAiuqY Headless Drupal certainly is popular, so is fast and maintainable code. This session will talk about JavaScript in general, presenting the latest news about the language and it's ecosystem, and Drupal in particular, exposing how Drupal could benefit from the language's evolution. This session will present news from around the frontend world and will be used to talk about: what developers want Drupal JS to do (or not do!), approaches for the Refactor of Doom (RD) that need to happen for JavaScript to be unit-testable (ES6 modules, patterns, etc.), intermediate steps to make some amount of testing possible prior to the RD, tools aimed at Drupal JS developers (eslint plugins, nodejs utilities for Drupal, etc.) frameworks, how to make decoupled implementations easier (aka. giving back some brains to headless implementations) anything else that is important to you. Core frontend is vastly better than it used to be, so much so that going headless because Drupal is a pain to work with is not an argument that can be made easily. Help us make that argument stronger to prevent people from loosing their head and drive projects to the ground. ]]> Wed, 23 Sep 2015 11:14:26 GMT /slideshow/headful-drupal/53104788 theodorebiadala@slideshare.net(theodorebiadala) Headful drupal theodorebiadala Video here: https://www.youtube.com/watch?v=9KYzOtAiuqY Headless Drupal certainly is popular, so is fast and maintainable code. This session will talk about JavaScript in general, presenting the latest news about the language and it's ecosystem, and Drupal in particular, exposing how Drupal could benefit from the language's evolution. This session will present news from around the frontend world and will be used to talk about: what developers want Drupal JS to do (or not do!), approaches for the Refactor of Doom (RD) that need to happen for JavaScript to be unit-testable (ES6 modules, patterns, etc.), intermediate steps to make some amount of testing possible prior to the RD, tools aimed at Drupal JS developers (eslint plugins, nodejs utilities for Drupal, etc.) frameworks, how to make decoupled implementations easier (aka. giving back some brains to headless implementations) anything else that is important to you. Core frontend is vastly better than it used to be, so much so that going headless because Drupal is a pain to work with is not an argument that can be made easily. Help us make that argument stronger to prevent people from loosing their head and drive projects to the ground. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/headfuldrupal-150923111426-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds" /> Video here: https://www.youtube.com/watch?v=9KYzOtAiuqY Headless Drupal certainly is popular, so is fast and maintainable code. This session will talk about JavaScript in general, presenting the latest news about the language and it's ecosystem, and Drupal in particular, exposing how Drupal could benefit from the language's evolution. This session will present news from around the frontend world and will be used to talk about: what developers want Drupal JS to do (or not do!), approaches for the Refactor of Doom (RD) that need to happen for JavaScript to be unit-testable (ES6 modules, patterns, etc.), intermediate steps to make some amount of testing possible prior to the RD, tools aimed at Drupal JS developers (eslint plugins, nodejs utilities for Drupal, etc.) frameworks, how to make decoupled implementations easier (aka. giving back some brains to headless implementations) anything else that is important to you. Core frontend is vastly better than it used to be, so much so that going headless because Drupal is a pain to work with is not an argument that can be made easily. Help us make that argument stronger to prevent people from loosing their head and drive projects to the ground.

Headful drupal from Th辿odore Biadala

]]> 963 6 https://cdn.slidesharecdn.com/ss_thumbnails/headfuldrupal-150923111426-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Accessibility is not for screenreaders /slideshow/web-a11ydrupal/47143658 web-a11y-drupal-150418093332-conversion-gate01
This will be a quick overview of the accessibility problem space to help people realize how important it is and how Drupal can help. We'll see why there is no excuse to not make a website accessible if you're developing for IE8 and under. Topics include: How many people we're talking about What kind of needs have to be addressed by web a11y Which specifications apply to which scenario How to read a11y specifications What can be used to help make a website accessible http://montpellier2015.drupaldays.org/sessions/accessibility-not-screenreaders]]>
This will be a quick overview of the accessibility problem space to help people realize how important it is and how Drupal can help. We'll see why there is no excuse to not make a website accessible if you're developing for IE8 and under. Topics include: How many people we're talking about What kind of needs have to be addressed by web a11y Which specifications apply to which scenario How to read a11y specifications What can be used to help make a website accessible http://montpellier2015.drupaldays.org/sessions/accessibility-not-screenreaders]]> Sat, 18 Apr 2015 09:33:32 GMT /slideshow/web-a11ydrupal/47143658 theodorebiadala@slideshare.net(theodorebiadala) Accessibility is not for screenreaders theodorebiadala This will be a quick overview of the accessibility problem space to help people realize how important it is and how Drupal can help. We'll see why there is no excuse to not make a website accessible if you're developing for IE8 and under. Topics include: How many people we're talking about What kind of needs have to be addressed by web a11y Which specifications apply to which scenario How to read a11y specifications What can be used to help make a website accessible http://montpellier2015.drupaldays.org/sessions/accessibility-not-screenreaders <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/web-a11y-drupal-150418093332-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds" /> This will be a quick overview of the accessibility problem space to help people realize how important it is and how Drupal can help. We'll see why there is no excuse to not make a website accessible if you're developing for IE8 and under. Topics include: How many people we're talking about What kind of needs have to be addressed by web a11y Which specifications apply to which scenario How to read a11y specifications What can be used to help make a website accessible http://montpellier2015.drupaldays.org/sessions/accessibility-not-screenreaders

Accessibility is not for screenreaders from Th辿odore Biadala

]]> 1122 1 https://cdn.slidesharecdn.com/ss_thumbnails/web-a11y-drupal-150418093332-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 javascript for backend developers /slideshow/javascript-for-backend-developers/47143621 js-backend-dev-150418093123-conversion-gate02
This session is aimed at backend developers who — willingly or not — have to write javascript. You know how to develop with your favorite language but this JS thing doesn't make sense. What's the deal with node.js anyway? You'll see enough to navigate the JS world without egg on your face. We'll see major pitfalls of JS and how to avoid them, which tools you can throw at the problem, what's the deal with the DOM, some notions around frontend performance and the direction in which this frontend thing is going. http://montpellier2015.drupaldays.org/sessions/javascript-backend-developers]]>
This session is aimed at backend developers who — willingly or not — have to write javascript. You know how to develop with your favorite language but this JS thing doesn't make sense. What's the deal with node.js anyway? You'll see enough to navigate the JS world without egg on your face. We'll see major pitfalls of JS and how to avoid them, which tools you can throw at the problem, what's the deal with the DOM, some notions around frontend performance and the direction in which this frontend thing is going. http://montpellier2015.drupaldays.org/sessions/javascript-backend-developers]]> Sat, 18 Apr 2015 09:31:23 GMT /slideshow/javascript-for-backend-developers/47143621 theodorebiadala@slideshare.net(theodorebiadala) javascript for backend developers theodorebiadala This session is aimed at backend developers who — willingly or not — have to write javascript. You know how to develop with your favorite language but this JS thing doesn't make sense. What's the deal with node.js anyway? You'll see enough to navigate the JS world without egg on your face. We'll see major pitfalls of JS and how to avoid them, which tools you can throw at the problem, what's the deal with the DOM, some notions around frontend performance and the direction in which this frontend thing is going. http://montpellier2015.drupaldays.org/sessions/javascript-backend-developers <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/js-backend-dev-150418093123-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds" /> This session is aimed at backend developers who — willingly or not — have to write javascript. You know how to develop with your favorite language but this JS thing doesn't make sense. What's the deal with node.js anyway? You'll see enough to navigate the JS world without egg on your face. We'll see major pitfalls of JS and how to avoid them, which tools you can throw at the problem, what's the deal with the DOM, some notions around frontend performance and the direction in which this frontend thing is going. http://montpellier2015.drupaldays.org/sessions/javascript-backend-developers

javascript for backend developers from Th辿odore Biadala

]]> 638 2 https://cdn.slidesharecdn.com/ss_thumbnails/js-backend-dev-150418093123-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Vanilla JS* /slideshow/vanilla-js/39798307 vanillajs-141002083546-phpapp01
Browsers APIs grew up, developers need to acknowledge it and make use of them — when appropriate. If we don't, browsers will stop caring and we're all going to have a bad time. This session will review common Drupal JS patterns found in core, contrib and projects and how they can be simplified (for some definition of simplified), pointing out frequent library abuse on the way. The topic of micro libraries will come up and I'll bring up the topic of hybrid approaches for all of us lazy programmers. We'll talk about where and how to draw the line for using a particular solution (this is a cue for the IE8 talk). Drupal 8 code will be taken as an example. The key concerns throughout the session are performance and maintainability. Unlike fanatics, I want you to be able to use what you learned knowing all the pros and cons. When you decide it's the right thing for you to use, you can trust your choice is the right one in your situation. The future is now! (for some definition of now)]]>
Browsers APIs grew up, developers need to acknowledge it and make use of them — when appropriate. If we don't, browsers will stop caring and we're all going to have a bad time. This session will review common Drupal JS patterns found in core, contrib and projects and how they can be simplified (for some definition of simplified), pointing out frequent library abuse on the way. The topic of micro libraries will come up and I'll bring up the topic of hybrid approaches for all of us lazy programmers. We'll talk about where and how to draw the line for using a particular solution (this is a cue for the IE8 talk). Drupal 8 code will be taken as an example. The key concerns throughout the session are performance and maintainability. Unlike fanatics, I want you to be able to use what you learned knowing all the pros and cons. When you decide it's the right thing for you to use, you can trust your choice is the right one in your situation. The future is now! (for some definition of now)]]> Thu, 02 Oct 2014 08:35:45 GMT /slideshow/vanilla-js/39798307 theodorebiadala@slideshare.net(theodorebiadala) Vanilla JS* theodorebiadala Browsers APIs grew up, developers need to acknowledge it and make use of them — when appropriate. If we don't, browsers will stop caring and we're all going to have a bad time. This session will review common Drupal JS patterns found in core, contrib and projects and how they can be simplified (for some definition of simplified), pointing out frequent library abuse on the way. The topic of micro libraries will come up and I'll bring up the topic of hybrid approaches for all of us lazy programmers. We'll talk about where and how to draw the line for using a particular solution (this is a cue for the IE8 talk). Drupal 8 code will be taken as an example. The key concerns throughout the session are performance and maintainability. Unlike fanatics, I want you to be able to use what you learned knowing all the pros and cons. When you decide it's the right thing for you to use, you can trust your choice is the right one in your situation. The future is now! (for some definition of now) <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/vanillajs-141002083546-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Browsers APIs grew up, developers need to acknowledge it and make use of them — when appropriate. If we don't, browsers will stop caring and we're all going to have a bad time. This session will review common Drupal JS patterns found in core, contrib and projects and how they can be simplified (for some definition of simplified), pointing out frequent library abuse on the way. The topic of micro libraries will come up and I'll bring up the topic of hybrid approaches for all of us lazy programmers. We'll talk about where and how to draw the line for using a particular solution (this is a cue for the IE8 talk). Drupal 8 code will be taken as an example. The key concerns throughout the session are performance and maintainability. Unlike fanatics, I want you to be able to use what you learned knowing all the pros and cons. When you decide it's the right thing for you to use, you can trust your choice is the right one in your situation. The future is now! (for some definition of now)

Vanilla JS* from Th辿odore Biadala

]]> 1143 2 https://cdn.slidesharecdn.com/ss_thumbnails/vanillajs-141002083546-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Web accessibiilty and Drupal /slideshow/web-accessibiilty-and-drupal/38236476 web-a11y-drupal-140821201139-phpapp02
There are many accessibility rules and several sets of accessibility guildelines. Developing an accessible website is hard. Drupal can help you. The most important thing Drupal does for your website, is that by default it makes sure your website is not inaccessible. The road to accessibility is much longer though. We'll step through several processes you can put in place to ensure accessibility of a website. This session will introduce the different accessibility guildelines. What they are, which ones you should pay close attention to and how they apply to a website. We'll see which components of the accessbility rules relates to Drupal as a CMS, which parts relates to editors and webmasters and different tools you can use with Drupal to help you ensure a website stays accessible over time.]]>
There are many accessibility rules and several sets of accessibility guildelines. Developing an accessible website is hard. Drupal can help you. The most important thing Drupal does for your website, is that by default it makes sure your website is not inaccessible. The road to accessibility is much longer though. We'll step through several processes you can put in place to ensure accessibility of a website. This session will introduce the different accessibility guildelines. What they are, which ones you should pay close attention to and how they apply to a website. We'll see which components of the accessbility rules relates to Drupal as a CMS, which parts relates to editors and webmasters and different tools you can use with Drupal to help you ensure a website stays accessible over time.]]> Thu, 21 Aug 2014 20:11:39 GMT /slideshow/web-accessibiilty-and-drupal/38236476 theodorebiadala@slideshare.net(theodorebiadala) Web accessibiilty and Drupal theodorebiadala There are many accessibility rules and several sets of accessibility guildelines. Developing an accessible website is hard. Drupal can help you. The most important thing Drupal does for your website, is that by default it makes sure your website is not inaccessible. The road to accessibility is much longer though. We'll step through several processes you can put in place to ensure accessibility of a website. This session will introduce the different accessibility guildelines. What they are, which ones you should pay close attention to and how they apply to a website. We'll see which components of the accessbility rules relates to Drupal as a CMS, which parts relates to editors and webmasters and different tools you can use with Drupal to help you ensure a website stays accessible over time. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/web-a11y-drupal-140821201139-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> There are many accessibility rules and several sets of accessibility guildelines. Developing an accessible website is hard. Drupal can help you. The most important thing Drupal does for your website, is that by default it makes sure your website is not inaccessible. The road to accessibility is much longer though. We'll step through several processes you can put in place to ensure accessibility of a website. This session will introduce the different accessibility guildelines. What they are, which ones you should pay close attention to and how they apply to a website. We'll see which components of the accessbility rules relates to Drupal as a CMS, which parts relates to editors and webmasters and different tools you can use with Drupal to help you ensure a website stays accessible over time.

Web accessibiilty and Drupal from Th辿odore Biadala

]]> 1505 3 https://cdn.slidesharecdn.com/ss_thumbnails/web-a11y-drupal-140821201139-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Javascript Pulp Fiction /theodorebiadala/javascript-pulp-fiction javascriptpulpfiction-140327123151-phpapp02
If you like or have an interest in: Stories about core process* Stories about lack of core process* Stories about patches* Patches about javascript Drupal 8 This session is for you. While not overly technical, slides may contain traces amount of javascript quirks. * Chronological order of stories and patches not guarenteed . ]]>
If you like or have an interest in: Stories about core process* Stories about lack of core process* Stories about patches* Patches about javascript Drupal 8 This session is for you. While not overly technical, slides may contain traces amount of javascript quirks. * Chronological order of stories and patches not guarenteed . ]]> Thu, 27 Mar 2014 12:31:51 GMT /theodorebiadala/javascript-pulp-fiction theodorebiadala@slideshare.net(theodorebiadala) Javascript Pulp Fiction theodorebiadala If you like or have an interest in: Stories about core process* Stories about lack of core process* Stories about patches* Patches about javascript Drupal 8 This session is for you. While not overly technical, slides may contain traces amount of javascript quirks. * Chronological order of stories and patches not guarenteed . <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/javascriptpulpfiction-140327123151-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> If you like or have an interest in: Stories about core process* Stories about lack of core process* Stories about patches* Patches about javascript Drupal 8 This session is for you. While not overly technical, slides may contain traces amount of javascript quirks. * Chronological order of stories and patches not guarenteed .

Javascript Pulp Fiction from Th辿odore Biadala

]]> 1983 3 https://cdn.slidesharecdn.com/ss_thumbnails/javascriptpulpfiction-140327123151-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 In-depth changes to Drupal 8 javascript /slideshow/java-script-changes2013/28552585 javascript-changes-2013-131123064222-phpapp02
Drupal 8 introduces a lot of changes for javascript: how to add a JS file to a page, how Drupal process the aggregation of JS files, what are the new javascript APIs. We'll be looking into the reasons for those changes. After a quick recap of the changes you need to make to port your JS to Drupal 8, we'll dig into the changes you should embrace as a module maintainer or site developer to make your life, and the web, better. But it's not all pretty, when you want to use some more advanced D8 features with your JS, you have to use messy workarounds. We'll look at a few examples of what happens when Backbone, Drupal and fancy functionalities meet in core and what it'd take to fix the mess.]]>
Drupal 8 introduces a lot of changes for javascript: how to add a JS file to a page, how Drupal process the aggregation of JS files, what are the new javascript APIs. We'll be looking into the reasons for those changes. After a quick recap of the changes you need to make to port your JS to Drupal 8, we'll dig into the changes you should embrace as a module maintainer or site developer to make your life, and the web, better. But it's not all pretty, when you want to use some more advanced D8 features with your JS, you have to use messy workarounds. We'll look at a few examples of what happens when Backbone, Drupal and fancy functionalities meet in core and what it'd take to fix the mess.]]> Sat, 23 Nov 2013 06:42:21 GMT /slideshow/java-script-changes2013/28552585 theodorebiadala@slideshare.net(theodorebiadala) In-depth changes to Drupal 8 javascript theodorebiadala Drupal 8 introduces a lot of changes for javascript: how to add a JS file to a page, how Drupal process the aggregation of JS files, what are the new javascript APIs. We'll be looking into the reasons for those changes. After a quick recap of the changes you need to make to port your JS to Drupal 8, we'll dig into the changes you should embrace as a module maintainer or site developer to make your life, and the web, better. But it's not all pretty, when you want to use some more advanced D8 features with your JS, you have to use messy workarounds. We'll look at a few examples of what happens when Backbone, Drupal and fancy functionalities meet in core and what it'd take to fix the mess. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/javascript-changes-2013-131123064222-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Drupal 8 introduces a lot of changes for javascript: how to add a JS file to a page, how Drupal process the aggregation of JS files, what are the new javascript APIs. We'll be looking into the reasons for those changes. After a quick recap of the changes you need to make to port your JS to Drupal 8, we'll dig into the changes you should embrace as a module maintainer or site developer to make your life, and the web, better. But it's not all pretty, when you want to use some more advanced D8 features with your JS, you have to use messy workarounds. We'll look at a few examples of what happens when Backbone, Drupal and fancy functionalities meet in core and what it'd take to fix the mess.

In-depth changes to Drupal 8 javascript from Th辿odore Biadala

]]> 7551 5 https://cdn.slidesharecdn.com/ss_thumbnails/javascript-changes-2013-131123064222-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Upgrade your javascript to drupal 8 /slideshow/upgrade-your-javascript-to-drupal-8/26539867 updatejs-130925092404-phpapp01
Drupal 8 introduces a lot of changes for javascript: how to add a JS file to a page, how Drupal process the aggregation of JS files, what are the new javascript APIs, what do we mean by mobile-first. This session will focus on showing Drupal developers how to update their javascript from Drupal 7 to 8 by taking an example module and going through all the relevant changes. By the end you'll know what fancy new features Drupal 8 provides you to build rich applications on top of Drupal while keeping mobile devices in mind.]]>
Drupal 8 introduces a lot of changes for javascript: how to add a JS file to a page, how Drupal process the aggregation of JS files, what are the new javascript APIs, what do we mean by mobile-first. This session will focus on showing Drupal developers how to update their javascript from Drupal 7 to 8 by taking an example module and going through all the relevant changes. By the end you'll know what fancy new features Drupal 8 provides you to build rich applications on top of Drupal while keeping mobile devices in mind.]]> Wed, 25 Sep 2013 09:24:04 GMT /slideshow/upgrade-your-javascript-to-drupal-8/26539867 theodorebiadala@slideshare.net(theodorebiadala) Upgrade your javascript to drupal 8 theodorebiadala Drupal 8 introduces a lot of changes for javascript: how to add a JS file to a page, how Drupal process the aggregation of JS files, what are the new javascript APIs, what do we mean by mobile-first. This session will focus on showing Drupal developers how to update their javascript from Drupal 7 to 8 by taking an example module and going through all the relevant changes. By the end you'll know what fancy new features Drupal 8 provides you to build rich applications on top of Drupal while keeping mobile devices in mind. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/updatejs-130925092404-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Drupal 8 introduces a lot of changes for javascript: how to add a JS file to a page, how Drupal process the aggregation of JS files, what are the new javascript APIs, what do we mean by mobile-first. This session will focus on showing Drupal developers how to update their javascript from Drupal 7 to 8 by taking an example module and going through all the relevant changes. By the end you'll know what fancy new features Drupal 8 provides you to build rich applications on top of Drupal while keeping mobile devices in mind.

Upgrade your javascript to drupal 8 from Th辿odore Biadala

]]> 4440 5 https://cdn.slidesharecdn.com/ss_thumbnails/updatejs-130925092404-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 What's up with javascript and Drupal 8 /slideshow/whats-up-with-javascript-and-drupal-8-18919524/18919524 whatsupwithjavascriptanddrupal8-130416070545-phpapp02
This talk will show what has been accomplished in the past year for core javascript and explain what's left for the last few months before code freeze. A few topics you can expect to show up: Performance Which JS library got in core and why Tools and workflow JS clean-up As well as some future-facing questions: New policies for third party JS API changes (PHP and JS) How can contrib deal with JS-related changes What's still missing for D8 There will be mention of some crazy ideas that might work from contrib.]]>
This talk will show what has been accomplished in the past year for core javascript and explain what's left for the last few months before code freeze. A few topics you can expect to show up: Performance Which JS library got in core and why Tools and workflow JS clean-up As well as some future-facing questions: New policies for third party JS API changes (PHP and JS) How can contrib deal with JS-related changes What's still missing for D8 There will be mention of some crazy ideas that might work from contrib.]]> Tue, 16 Apr 2013 07:05:44 GMT /slideshow/whats-up-with-javascript-and-drupal-8-18919524/18919524 theodorebiadala@slideshare.net(theodorebiadala) What's up with javascript and Drupal 8 theodorebiadala This talk will show what has been accomplished in the past year for core javascript and explain what's left for the last few months before code freeze. A few topics you can expect to show up: Performance Which JS library got in core and why Tools and workflow JS clean-up As well as some future-facing questions: New policies for third party JS API changes (PHP and JS) How can contrib deal with JS-related changes What's still missing for D8 There will be mention of some crazy ideas that might work from contrib. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/whatsupwithjavascriptanddrupal8-130416070545-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> This talk will show what has been accomplished in the past year for core javascript and explain what's left for the last few months before code freeze. A few topics you can expect to show up: Performance Which JS library got in core and why Tools and workflow JS clean-up As well as some future-facing questions: New policies for third party JS API changes (PHP and JS) How can contrib deal with JS-related changes What's still missing for D8 There will be mention of some crazy ideas that might work from contrib.

What's up with javascript and Drupal 8 from Th辿odore Biadala

]]> 2052 5 https://cdn.slidesharecdn.com/ss_thumbnails/whatsupwithjavascriptanddrupal8-130416070545-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-theodorebiadala-48x48.jpg?cb=1699393085 http://theodoreb.net https://cdn.slidesharecdn.com/ss_thumbnails/offline-first-jp-en-170116111720-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/offline-drupal-with-progressive-web-app-71054822/71054822 Offline Drupal with pr... https://cdn.slidesharecdn.com/ss_thumbnails/frontendthunderdome-151128103046-lva1-app6892-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/frontend-thunderdome/55600352 Frontend thunderdome https://cdn.slidesharecdn.com/ss_thumbnails/headfuldrupal-150923111426-lva1-app6891-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/headful-drupal/53104788 Headful drupal