I'm a little confused about the commercial aspects of the project, however, I guess this is an approach to make the OSS aspects sustainable.
Don't worry. OSS is the priority for the platform. I have a lot of projects built on Total.js, so Total.js can't end in bad hands. I'll continue because it's my work and hobby together.
I think the js ecosystem is reaching a point where vendors cannot charge for their tools anymore.
Not really... Total.js Flow is used in big industry in Slovakia --> 40 M EUR net revenue or OpenPlatform is currently deployed for the first financial customer (revenue +27 mil. EUR) or health service or police. I have a lot of projects but I can't speak about them. Trust me :)
community communicates on https://messenger.totaljs.com ... it's not free but 8 EUR per year is not much :)
Not much, true, but first I need to know what I'm getting myself into without investing too much time. I haven't been able to find any tutorials on how the eco-system hangs together, how to integrate flow or dashboard with existing projects, how the products co-exist and interact (such as calling CMS templates from flow workflows), how to make flow execute in a larger js context such as a web app, how to implement new CMS themes, how to integrate jcomponents (without learning Angular), or how to access node machines from flow.
It's pretty basic stuff but also pretty steep if you're new to the eco system. I guess what I'm missing is something like https://www.youtube.com/watch?v=KH5E2TL-_e8. Slow-paced, talking, explaining and building.
Ok, I've given totaljs a couple of days and I give up. The learning curve is simply too steep. There's lots of help with installation and getting predefined boilerplates up and running – it's the next step that's missing. I can find no documentation whatsoever on switching CMS themes, adding text to a page in the CMS (shouldn't need documentation), connecting flows to dashboard graphs (got a static text working) or connecting Page renderer for that matter.
With that, I wish the project all the luck. Flow is one of the most awesome js tools I've seen, and with the proper documentation (and overall a language overhaul) I'm confident it might turn out to be a really big deal in the js ecosystem.
Hi Christian, yes, learning curve is steep, but IMO not as bad as I've come across before. I think you maybe looking at too much at the same time, let me try and do an overview of Total.js in my experience (I have several live projects with it, see https://pmc.digital for more info):
npm install total.js, have your script
require('total.js')and you're ready to use everything it includes.
If you'd like to give it a go again, don't hesitate to contact me on https://messenger.totaljs.com, Peter (the creator) is always there too, and even if you're not Premium yet, you'll be able to read previous conversations too.
You can't fool time (I think). Big cases need big solutions. With Total.js you can do everything but the apps must be optimized (e.g. Total.js Messenger can't be used for thousand of users because it's optimized for hundred of users). Very important is the entire architecture / design and maybe the framework is the last item in the chain.
It's a pity that we don't have any similar case in our country :-D ... Wisdom says: everything starts with small details, first was wheel and then car. I can say for sure that Total.js Platform is very good platform for development of web apps (my opinion: it's the best). I work on Total.js Platform everyday and more than 6 years.
Let me know if you need help.
Nodejs is low rank for back-end API
Not exactly true. Techempower doesn't contain redeemable values because each author of the "framework"/"technology" optimizes the example for the best performance. But the real cases aren't only
Hello world apps, there are a lot of small details like database, business logic, sessions, etc.. As I said:
framework is the last thing in the chain of some architecture. I agree that a good technology can save a lot of time.
I don't like Express, jQuery and lot of misc
I too, but our client-side library jComponent uses jQuery, but the result is unbelievable: https://componentator.com ... I could replace jQuery but I didn't see any benefit.
index.jsis too big, but not much (it's because of historical reasons)
jsfile is independent module (object), but yes - it's important for clarity and I hate disarranged spaghetti code too
index.jscontains a core of the main funcionallity (I know each line of code and I understand it)
Good to know: you don't need to understand fully source-code, it's complicated for developers who don't have advanced experience with Total.js... You need to understand my thinking and design of Total.js. If you understand then you win. Trust me and trust the framework, I work on it everyday more than 5 years. I have a great team of developers. Let me know if you have any questions.
@PeterKieu yes, but it's a bit complicated. You need to specify https://docs.totaljs.com/latest/en.html#api~global~LOCALIZE and then you can define language directly in Page settings. I think that better is to divide URL of pages according language:
with creating of custom template for each language :-)