[Webinar Recording] Polyglot PyCharm for Rich Web Front-ends

The recording of our January 12th webinar, Polyglot PyCharm for Rich Web Front-ends, is now available on JetBrains YouTube Channel. Paul Everitt’s code used in the recording along with the script for each step in the webinar can be found on GitHub.

Polyglot PyCharm for Rich Web Front-ends

Python has long been a staple of web development. In the recent world of “web apps”, though, the browser is playing a larger role. More of the application in a web app is done in JavaScript, in the “frontend”, with Python running UI-less data services in the “backend”. With its IntelliJ/WebStorm foundations, PyCharm can cover modern HTML/CSS/JS workflows. In this webinar, I’ll show building a JS MVC web app talking to a Python backend using REST, all from the perspective of a veteran Python developer.

The list of topics with timing:

00:20 Node Walkthrough
02:22 Webinar Overview
04:40 Repository for code samples
05:10 Flask ToDoMVC Starting Point
08:32 Add “Delete” Button
12:03 Packaging with npm and package.son
21:29 Tooling with aslant
31:45 Automation with npm run scripts
35:10 Move frontend out of backend with CORS
45:00 Pythonic modules with ES6, Babel, and Webpack

Note: The webinar was a huge success. We’ve got a lot of positive feedback in the after-webinar survey. As we hadn’t managed to cover all the topics declared in the webinar plan we decided to fire up another one webinar soon, which is supposed to cover “ES6 Modules with Babel and Webpack” and “Pythonic ES6” topics in more details. Stay tuned for the announcement.

Keep up with the latest PyCharm news on our blog and follow us on Twitter @PyCharm.

The Drive to Develop
– PyCharm team

Comments below can no longer be edited.

2 Responses to [Webinar Recording] Polyglot PyCharm for Rich Web Front-ends

  1. Avatar

    Boris Grishechkin says:

    January 26, 2016

    Thank you for a cool webinar! Though it took me some time to understand the implementation of the MVC architecture in your Todo application setup:
    – a simple http-server (python) on the port 8888 which delivers the content of the “app” folder i.e. the View (html+css) and the Controller (app.js+todo.js)
    – a flask http-server (python) on the port 5000 which delivers the access to the Model (SQLite DB via python SQLAlchemy library), this could run in the cloud as you’ve mentioned.
    – nodejs runtime was used only for the simple “hello world” demo in the beginning, has nothing to do with running the “todo” application. Although its NPM was used further to download and manage javascript modules and their dependencies e.g. jquery.js.
    By the way apparently one needs the professional edition of PyCharm to work with javascript.

    • Avatar

      Paul Everitt says:

      January 26, 2016

      Hi Boris, thanks for the comments. I am working on a writeup that explains the two bullet points you mentioned. Also, I ran out of time just before showing the good part: running the frontend under dev tools which handle auto-reload, etc., The Part 2 of the webinar will do more in the frontend: Webpack for bundling and the dev server and Babel for Pythonic-JS using ES6.

      In the writeup, I will work harder to make the points you are describing.

      If you would like a sneak peak on the writeup, leave a comment and I will get you the link.

Discover more