The problem with PHP/ASP/ASP.NET is that you have a lot of different configurations and versions that you need to support. With node we have lot more control over the environment and the server is build-in.
With PHP we always had to check which version is installed, are the required PHP modules installed on the server, which database drivers are installed, what server does it run on (nginx doesn’t support htaccess files which we use for routing). With node we don’t have this problem, we bundle all the required modules directly with it and we choose which modules we are going to use.
Yeah, I figured that was the case. NodeJS is clearly the way forward. I’m just realising I need to be using that ASAP or I’ll be missing out on features. I’m about to start another project so the logical thing is to go with NodeJS for it but should I wait until v3 stable is released or is it safe to use at this beta 4 stage?
How do we convert existing html pages to .ejs pages without losing any of the required dependencies / files e.g. css and dmx references?
What actually is included in this current beta function I don’t want to be wasting my time trying to figure why something is not working or submitting bug reports if the functionality is not supported in this version? What is incomplete and just wont work?
I’ve found the beta very interesting because it is allowing me to take a deeper look at how Wappler has designed the solution and will most probably give me an edge in the future. It also has allowed me to make the right questions and provide interesting feedback. But it does require time, constant rebuilding and researching. Time that if you don’t want to spend I would just recommend you to wait for the final version.
If you have static html files, just move them to the views folder and rename it to .ejs. If you use the same folder structure as in the public folder then it should work directly and all dependencies also. You will need to create routes for them to make them reachable.
A partial is normally a piece of code that you are planning on reusing throughout your app, but is not common to all your app.
But adding a partial to a layout makes it available to all the pages that use that layout. Are you planning on using several layout files where some will have a partial and others won’t?
Are you planning on using several layout files where some will have a partial and others won’t?
Something like that yes, im still really having a hard time understanding layouts, routing etc.
My goal is to have a single page type app with no refreshing on navigation.
app.com/ this would be the main page left empty
then I will have some pages like app.com/settings for logged in users.
And I would like dynamic page for profiles. app.com/{profileid}
In bubble have one main page "/id" then I use collapse/hide conditions for all the sub/fake pages displayed by the url paths. I find building with bubble much more intuitive then here sadly.
