neo

background info: the demo app is located inside the App Worker. the drag events get triggered in main, while the handlers live within the App Worker scope. I was sceptical at first, how the performance for a custom drag&drop implementation would work out. Best to use Chrome (some polishing left for FF & Safari). The TouchSensor is next on my todo list. You can find the code here: https://github.com/neomjs/neo/blob/dev/src/main/addon/DragDr... https://github.com/neomjs/neo/tree/dev/src/main/draggable https://github.com/neomjs/neo/blob/dev/src/dialog/Base.mjs

The project is deeply inspired by the Google Calendar as well as the native MacOS Calendar. This is a very early preview version: I started this project a week ago, so please don't expect it to be functional yet. I think it will take 2-3 more weeks to get finished. Based on neo.mjs, it is multithreaded out of the box. What you can do already: Switch the theme. Open the Settings Container, change settings for the weekly view. Ideally with the Weekly View as the active Card to see the delta updates. I will add infinite scrolling for all views soon (similar to the DateSelector at the top left). Drag & Drop for Events, mobile support and creating, editing & removing Events are on the todo list. You can take a look into the source code here: https://github.com/neomjs/neo/tree/dev/src/calendar The Calendar is already pretty extensible & configu

Loading a framework just once for multiple Browser Windows. Moving entire Component Trees around Windows (just the vdom, no new JS instances). DomEvents still work out of the box (no need to add new listeners or modify existing ones). https://github.com/neomjs/neo

Again: super early stage, not fully functional yet. The version inside the video is not deployed to the online examples yet (will add it once ready). You can just clone the neomjs/neo repo and try it locally if you like to. What I did was opening: https://github.com/neomjs/neo/tree/dev/apps/sharedcovid (index.html) inside a first browser window and then opening: https://github.com/neomjs/neo/tree/dev/apps/sharedcovid2 inside the second window. we could spawn new popup windows as well. working on the dom event support next, after moving components around. it might be an easy fix just adjusting the appName config of the moved cmp tree, otherwise i need to look into the postMessages routing. gutt feeling: 2-3 more days.

Ha, I know the feeling. Rich & I started with the workers implementation back in 2015. No console errors ;) What was a huge help is the remotes API (remote method access). example: https://github.com/neomjs/neo/blob/dev/src/main/addon/Styles... createStyleSheet() is defined inside this class which (optionally) runs inside the main thread and is exposed as a remote method to the App worker. Now, when you are working inside the App worker scope, you can simply use it as a promise: Neo.main.addons.Stylesheet.createStyleSheet(opts).then(data) { // do something }

The main goal was to make the build processes as easy as possible for you. The new build all program will use: https://github.com/neomjs/neo/blob/dev/buildScripts/webpack/... https://github.com/neomjs/neo/blob/dev/buildScripts/webpack/... https://github.com/neomjs/neo/blob/dev/buildScripts/webpack/... https://github.com/neomjs/neo/blob/dev/buildScripts/webpack/... and pass command line options or inputs from the inquirer interface. The sub-programs do support command line options or provide a visual interface as well. Under the hood this is triggering a big amount of webpack based tasks. The package.json now got a lot smaller & more intuitive. As mentioned before, the main thread addons are in place now as well, so it got very easy to connect the webworkers driven UI framework neo.mjs to other libs or frameworks. https://medium.com/@tobia

In case you are not familiar with neo.mjs yet, it is a new UI framework which runs inside a web worker to use multi threading to the fullest. https://github.com/neomjs/neo I just finished the main thread addons, so this is my highlight for the week. In case you want to work with other libraries or tools which need to include their own scripts, you can now do this with adding addons to the main thread. Examples are highlight js, showdown, Google Analytics. Each addon got an optional entry point: onDomContentLoaded, where you can import new scripts or stylesheets as needed. You can expose methods to other workers (in most cases to the app worker) to directly use them as promises. Choosing which addons you want to use is convenient: Just drop each one into the Neo.config (e.g. https://github.com/neomjs/neo/blob/dev/apps/realworld/index....)