Nice, keep them going more Nuxt content the better!
@user-ib6uk3ng4d12 күн бұрын
Thank you so much, been digging with modular architecture in nuxt for a long time and things were getting complicated, but your 5 minute video totally helped me, Subscribe and like from me bro, keep releasing videos!
@ruslantimurziyev32213 күн бұрын
There is no building /dist with ssr. npm run build generating standard spa dist
@mahsamrz57875 күн бұрын
Yeah it's not complete don't use this
@YellowPanamka14 күн бұрын
Nice
@alexanderkim724122 күн бұрын
Not released yet, and won't be during this year 99% :D
@martinarce813829 күн бұрын
That was neat! Thank you!
@creative.money_euАй бұрын
Please make one more video to explain how this can be useful on a architecture, where multiple projects (deployed on multiple domains) can share a components "layer" with each other. This is a *really* useful feature which other ecosystems dont have to my knowledge and it will surely benefit a lot of people and make Nuxt even more attractive. I subscribed for it, would be amazing
@michaelpeters9551Ай бұрын
This is all really interesting.. how could we have a base collection of these global files and then have these layers override those global components? Does one layer's components override a layer higher up in the tree? If we can achieve this with layers then this is really exciting
@M-lt6kxАй бұрын
If you create a component/composable/page etc with the same name in a higher layer it will override the existing one.
@codingwithmartin3177Ай бұрын
Not sure what you mean by that. The idea of Nuxt layers is to "extend" layers not override them. Can you share your use case?
@nyambeАй бұрын
I thought layers in Nuxt meant a different thing. Layers allows you to share components with other installations, we are not talking about the same thing. Correct?
@M-lt6kxАй бұрын
In simple terms, your final app will be all your layers merged together. The end result might be your 'top layer' app using components/utilities provided in some lower layers or like in the video an app where pages and their functionality are separated via layers and merged to create an app with multiple pages.
@nyambeАй бұрын
@@M-lt6kx I understand what you are talking about but I thought layers was something else. I have a ui layer that other Nuxt installations can use. Pnpm monorepo manages all layers. That is how they worked in Nuxt 3. Maybe they are ditching this concept
@codingwithmartin3177Ай бұрын
@nyambe Layers can be used for multiple purposes. Yes, one way is to share them among projects. But they cal also be used to implement a DDD/modular architecture. Take a look at the official docs.
@overnightmaresАй бұрын
is it ok to have layers outside the "my-app" folder? Imagine I have 2 apps: app1 and app2. Both share some common functionality. Can I have a structure like /layers/ , /app1/ , /app2/ ? And do I need pnpm to make this work or any package manager would do it? Thanks.
@M-lt6kxАй бұрын
Your layers can be anywhere. In any folder locally, in an npm package or in another git repo. Any of the supported package managers will allow this.
@Joan-kr1joАй бұрын
Oh makes sense with the new folder structure. I was trying to create a new project and when I did enable the compatibility version my app broke because didn't have the app folder. Thank you.
@bulverismoАй бұрын
thanks,
@nonefvnfvnjnjnjevjenjvonej33842 ай бұрын
just pointless meanderings in the javascript land. they keep changing things for no reason. instead they should selectively ignore things not being changed such as node modules... i dont know why javascript devs lap it up...
@codingwithmartin3177Ай бұрын
Why do you care what JavaScript devs do?
@nonefvnfvnjnjnjevjenjvonej3384Ай бұрын
@@codingwithmartin3177 i like technology as a whole. dont want my bethrens suffering
@ayushmanbt2 ай бұрын
this awfully reminds me of django and the apps concept
@QueeeeenZ2 ай бұрын
Nuxt also has an upcoming multi-app feature which is for micro frontends. But layers is simply a way to group your monorepo app into logical features and it's completely optional.
@viesturs.knopkens2 ай бұрын
Sounds like a very useful feature, that you can have different config files for each layer. Although I have to think about a little bit when in real life I would use that - e.g. one layer uses Pinia, one Vuex? Or one Bootstrap, but another Tailwind? 😊 But in general I like the idea 🙂👍
@QueeeeenZ2 ай бұрын
Layers is more about grouping your app into logical units like "users", "settings", "sales", "blog", "auth" etc. So you can work on your "settings" feature and find all files related to settings in that layer. This is especially useful in larger apps with bigger teams where one team or developer might work on settings feature, another developer can work on users etc. without conflicts. It also gives the app nice, clean structure.
@viesturs.knopkens2 ай бұрын
@@QueeeeenZ Yes, I understand the layers concept and agree with you, but my comment was meant more on "each layer can have its own config" - I was wondering how often in real life I would need a different config file for each layer :) But I don't insist that there aren't use cases for that, especially for large apps :)
@QueeeeenZ2 ай бұрын
Oh, I see what you mean. I have created large scale apps with layers and I have never needed to specify a different config for each layer. The only difference between layer configs was to specify where to find imports, components etc. because it's a different directory for each layer.
@norbertabone91573 ай бұрын
Great !
@sasaostrouska8885 ай бұрын
Many thanks Martin, this is very nice and simple explanation. I loved it. If you could expand that topic by adding stuff like how to use more gobjects and how they communicate between them or pass info from one to another would be very nice.
@maclaurinrocha28818 ай бұрын
I have a lot of difficulty understanding how glib and gobject work, could you do something simple like starting an inventory control just so I can start any project here at home?
@maclaurinrocha28818 ай бұрын
Would you please make more videos like this using glib and gobject in gtk4?
@user-td8yq7kc8k8 ай бұрын
why did you stop this series. it was an appreciated start.
@jorgmuller31108 ай бұрын
Thanks. But what's the use of OOP without inheritance and polymorphic behaviour aka vtable virtual functions...
@batner6 ай бұрын
That is the whole thing about GObject, they give you a framework to create inheritance, polymorphism, even introspection and then use it to implement GTK, which is a high level GUI framework. The thing is that there is no automatic way to create vtables as in C++, you do it in code yourself during class init. For example Inheritance is done with structs where the parent pointer is the first member of the current class struct. So you can cast a pointer to your object to a pointer to parent class object without anything breaking. So methods/functions that expect a parent object instance can work seamlesly on a your current object.
@DeafMan19839 ай бұрын
Great explanation! I will port to C#, but i have already tested with DeafMan1983.Interop.GTK4 but still in the development. And i got a successful window from gtk_application_window_new, etc and I am developer of C# .
@FlanPoirot Жыл бұрын
this was extremely helpful but the "uhmmm" throughout the video is incredibly annoying/distracting. I had to push thru to watch the entire thing
@Turjak_art Жыл бұрын
Another feminist that is upset about nothing...
@FlanPoirot Жыл бұрын
@@Turjak_art what does this have to do with feminism? and this is valuable criticism that improves his communication and let's his ideas/content be conveyed more clearly. this is basic communication skills
@Turjak_art Жыл бұрын
@@FlanPoirot because you're a weak minded person that had such a hard time I feel so sorry hearing that you had to push thru.... Crying about this little issue must be hard for you. did you survive it?
@anuragyadav7913 Жыл бұрын
good content
@alexmercerind Жыл бұрын
gobject is single handedly making world a difficult place. who wants to use gtk & learn a separate programming paradigm just for doing it
@paherbst524 Жыл бұрын
i completely agree. i tried using gtk for some test utilities i needed, and quickly decided to move on to Qt. Following a tutorial is fine, but when i can't look at glib's documention and understand it, then there's a big problem. you'd think all the money and time from RH that goes into g-stuff that this would be better. i dont understand how g-stuff is popular.
@sonukumarkeshri46963 жыл бұрын
Hey join this , www.scaler.com/event/coding-interviews-dynamic-programming?rcy=1&rce=f6cd5eeb1984