So, I as creating this rough interface for testing out my blog intake.
copious-blog-entries
And, I was using Electron at first. But, I ran into a version problem. For instance, it was not obvious how to use fs/promises from node.js. But, then I tried NW.js and things got really smooth. I like the way the code is partitioned better to. Getting the debugger up in a separate window is nice, too. But, with NW, if you restart your app window, the debugger starts over as well. So, that's something they could fix. But, I was dead in the water with Electron, so I am living with it.
But, it would be great to have an IDE, especially one that does not impose some fat stack of components on a project and also allows use of vanilla JS when and where it is wanted.
Do you guys think you can make something like LiveCode?
I also have nascent tools in my alpha-copious repository for selecting code to into templates. Later the templates are populated with page specific code.
So, the work flow is supposed to go like this:
basic universal code -> select which part of that rides with a page -> generate to templates and modules -> template to an actual indexed page ... (with inserted html snippets and controls to initiate lazy loading of other components, which may as well be vanilla js and HTML as anything - but making a nice control over components such as Svelte components would be nice.)
So, some of this has to do with getting pages up with just enough code, with lazy loading of components onto a page as a user makes selections. That there is cached JS in modules or separate files is not to be ignored. But, my thoughts are that a page should not depend on preexisting assets in a browser and will load more weighty ones as the user gets more interested and involved with a page. Later, if the assets are there and the user comes back to it, then great - the speed up is good. Of course, there is version caching - a consistent mess. And, finally JS should WASM up easily with good use of service workers and IndexDB and other user located data state storage.
So, I as creating this rough interface for testing out my blog intake. copious-blog-entries
And, I was using Electron at first. But, I ran into a version problem. For instance, it was not obvious how to use fs/promises from node.js. But, then I tried NW.js and things got really smooth. I like the way the code is partitioned better to. Getting the debugger up in a separate window is nice, too. But, with NW, if you restart your app window, the debugger starts over as well. So, that's something they could fix. But, I was dead in the water with Electron, so I am living with it.
But, it would be great to have an IDE, especially one that does not impose some fat stack of components on a project and also allows use of vanilla JS when and where it is wanted.
Do you guys think you can make something like LiveCode?
I also have nascent tools in my alpha-copious repository for selecting code to into templates. Later the templates are populated with page specific code.
So, the work flow is supposed to go like this: basic universal code -> select which part of that rides with a page -> generate to templates and modules -> template to an actual indexed page ... (with inserted html snippets and controls to initiate lazy loading of other components, which may as well be vanilla js and HTML as anything - but making a nice control over components such as Svelte components would be nice.)
So, some of this has to do with getting pages up with just enough code, with lazy loading of components onto a page as a user makes selections. That there is cached JS in modules or separate files is not to be ignored. But, my thoughts are that a page should not depend on preexisting assets in a browser and will load more weighty ones as the user gets more interested and involved with a page. Later, if the assets are there and the user comes back to it, then great - the speed up is good. Of course, there is version caching - a consistent mess. And, finally JS should WASM up easily with good use of service workers and IndexDB and other user located data state storage.