Can different outlines share same sections?
-
-
- shenk
- Hero Rocketeer
- Posts: 424
- Thanks: 11
-
Before gantry 5, templates have different overrides, which share many common settings with a Default one, for those setteings that are different than those of the Default, you can just check the setting and change it. In gantry 5, there seems no way to do something like this.
For example, I use a 'Default' outline for most of my pages, for homepage, I duplicate 'Default' outline and rename it to 'home'. Now when I want to change the topbar where I have a logo particle and menu particle in it, I have to change both the 'Default' outline and 'home' outline. This doesn't feel good. Did I miss something?
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
shenk wrote:
Now when I want to change the topbar where I have a logo particle and menu particle in it, I have to change both the 'Default' outline and 'home' outline. This doesn't feel good. Did I miss something?
I'm not understanding the issue?
In Gantry 4 I would have "rt_templateName Default MASTER" that would use the default logo settings.
Now I want to use a custom logo on the About Us page.
So I create a duplicate of the MASTER and call my template override "rt_templateName - AboutUs" and here I change to a custom logo.
In Gantry 5 I would have "rt_templateName Default" that would use the default logo particle.
Now I want to use a custom logo particle on the About Us page.
So I create a duplicate of the Default and call my new template Outline "rt_templateName - AboutUs" and here I add a new logo particle.
So it would seem the process is the same for both Gantrys.
-
-
-
- shenk
- Hero Rocketeer
- Posts: 424
- Thanks: 11
-
Maybe some symbolic javascript codes will make it easy to explain
var myLogoParticle = "customLogoParticle"; var defaultOutline = { logoParticle: myLogoParticle, otherPropertyA: 'something', otherPropertyB: 'something' }; var homeOutline = { logoParticle: myLogoParticle, otherPropertyA: 'something else', otherPropertyB: 'something else' }
In the above code, the two objects(defaultOutline and homeOutline) are sharing same logoParticle value, which is stored in a variable `myLogoParticle`, if I wanna change the value of property `logoParticle` for both objects, I will only have to modify one place, the first line .
Now back to my case. I'm not wanting to have different logo particles on different pages, insteadly, I want them to be same. Thats not hard to understand, for a normal site, the logo particle in every outline should be same, lets call it 'myLogoParticle'. Besides logo, different outlines have different other settings, I call them otherPropertyA/B. In gantry 4, to have `homeOutline` display same logo with `defaultOutline` while display different `otherProperties`, we can keep logo setting intact and check settings for otherProperties so we can edit it. This way, if I later decide to change a logo picture for the whole site, I only have to modify one place, which is the `defaultOutline`, where `myLogoParticle` is actually stored.
But in gantry 5, I can't find a way to let different outlines share a same section. So what happens? Lets say my site has used 5 different outlines, they all of course have same logo particle, not by some good sharing mechanism, but by me duplicating the default outline 4 times. Now if I decide to change the logo picture for my whole site, I awkwardly find myself having to manually change it for all 5 outlines!! Insteadly, in gantry 4 I only have to modify one place. This can't be intended by the grand gantry 5 framework! It is either I miss something or gantry 5 has a serious flaw. - Last Edit: 9 years 8 months ago by shenk.
-
-
-
- Matias Griese
- Sr. Rocketeer
- Posts: 249
- Thanks: 104
- Lead Developer
-
Right now the short anser is that if you want to use the same particle in multiple outlines, use module position and assign particle module to that position.
It's really not a flaw; it's something that you can implement by using Joomla modules and as such we decided not to implement the functionality into Gantry itself, at least not right away. There are some plans to improve on this, but there are also some other features and fixes that right now cannot be worked around and as such are higher priority.
As we are moving to other platforms which do not implement modules or have very restricted support for those, we will need to take a look on this feature and implement it on our own. Some of these features will integrate deeply to Joomla, others not that much. -
The following users have thanked you: shenk
- Gantry 5, enjoy!
-
-
-
- shenk
- Hero Rocketeer
- Posts: 424
- Thanks: 11
- Reading you reply, I start to feel the particles are useless. Pratically, because of this issue I mention in the main thread, I've changed the logo particle to a custom html module. To me particles are just gantry version of modules, yet they don't have the flexibility and extensibility the regular modules have. Having read the documentation repeatedly and carefully, I can see the gantry team has put a lof of efforts on this new particle system, so there must be some advantages (or potential advantage in the future?) that I overlooked. What are they?
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
shenk wrote:
Reading you reply, I start to feel the particles are useless. Pratically, because of this issue I mention in the main thread, I've changed the logo particle to a custom html module. To me particles are just gantry version of modules, yet they don't have the flexibility and extensibility the regular modules have. Having read the documentation repeatedly and carefully, I can see the gantry team has put a lof of efforts on this new particle system, so there must be some advantages (or potential advantage in the future?) that I overlooked. What are they?
As for myself I like to have options especially in creating content. Particles are important to me because they fall outside the constraints of Joomla's module positions.
-
Time to create page: 0.059 seconds