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
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?
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.
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.
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...
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.
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 🙂👍
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.
@@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 :)
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.
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.
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?
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.
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# .
@@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
@@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?
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.
