Menu - auto build entry for all installed

[sundevil01010101]

My wish is the menu would auto build entries for every block or plugin installed and then you can create subheadings and regroup things.

Possible?

[Jachym]

Hi Terry,

- blocks: not sure about this, the Menu does not include blocks
- plugins: this is difficult, this is how it used to be, it is technically easy for me to do this, but the problem is that it was always the case that person 1 thought it should go under tab 1, person 2 thought it would better suit tab 2 etc etc and it was impossible to come up with a solution that would work for all.

But Im opened to suggestions... adding a plugin automatically to the menu in a specified place is not a problem. But do people want this?

[Luc]

When it is a matter of 'all or nothing' I prefer to create the menu entries manually for those 5% of plugins I want to see on another place than they are on the Meteotemplate demo site.

[Jeffm5690]

I struggled at the beginning with this. I still do. It is quite easy to adjust but oftentimes I have a difficult time deciding even for myself, where items belong. Maybe it would be nice for some to have a “default” where plugins will go if you choose a default menu? This may be helpful for beginners and novice users. I think I have learned over time how to do this and it is much easier.

[Jachym]

Yes, I see what you mean, but don't forget it is not just about the actual tab.

More importantly it is also the case that I would have to decide the order of them in a particular tab and their placement (columns in individual tabs). This becomes problematic, it is hard to explain, but I will try.

Imagine we have Tab 1 and plugins 1, 2, 3 4 and the fixed menu has those 4 in tab 1.

Now let's say that Tab 1 has 3 columns and I think 1,2 look good (fit) column 1, plugin 3 column 2 and plugin 4 column 3

Then the hierarchy would be like this:
Tab 1:
- column 1:
- plugin 1
- plugin 2
- column 2:
- plugin 3
- column 3:
- plugin 4

Now of course there would be more plugins which is why they cannot be in just one column, the above example is a simplification.

But now imagine what would happen if that particular person only had plugins 3 and 4. This means they would have a blank column 1... which obviously would look bad. Adding the plugins randomly (or to the end) is also not ideal because some might be more important and only using the order in which they were installed would not be ideal.

So the more you think about it the trickier it gets. This would only work if I made a specific order for every single possible combination of plugins there is. Which would be currently 154! (not 154....154!)...

But again, if you can think of a solution.... thats what this forum is for

[Jachym]

So... did we get to any conclusion as to what would be the best way of doing this?

The only options I can think of are:
1. keep things the way they are now
2. revert back to the original mechanism, where each plugin has its fixed place (chosen by me), but without the need to add them manually to the menu

Any other ideas?

[Johnny]

1. keep things the way they are now
2. revert back to the original mechanism, where each plugin has its fixed place (chosen by me), but without the need to add them manually to the menu

If it makes it easier to do use plugins (but less customisable) I'd go for option 2

[Jachym]

OK, but keep in mind that this will mean that all plugins will be in fixed places in the menu (where I decide they fit best) and there might be gaps in case you have one, but not the other plugin (given they have fixed positions)

[Johnny]

Let's get a lot more views on this to get a balanced decision.

[John B]

Hmm. I think that I prefer the existing system. Changing to a fixed-position seems rather confining, unless I'm misunderstanding the thrust of the discussion. To take away the ability to stick plug-ins wherever the user wishes seems, to me anyway, a retrograde step and takes away some of the 'charm' of the template as it now stands.

Certainly the first attempt to install a plug-in and amending the menus can be daunting, but that's only because of lack of familiarity. Careful reading of Jáchym's instructions (and following them) is, of course, essential and initially seems confusing but once it's understood - read them a few times and let them sink in - it is really quite simple.

So, to make it clear, I would be disappointed if the suggestion be adopted, unless I can be convinced otherwise, which is unlikely.

A quick thanks to Jáchym for providing this avenue for discussion; it's marvellous.

[wxthomson]

I vote for keeping things as they are.

[gillesroszak]

I also vote for keeping things as they are.

[Pavel]

I also vote for keeping things as they are.

[Gus]

Things as they are works well for me.
Gus

[Jeffm5690]

My official vote is to leave as-is.

[Jachym]

OK, thats what I would prefer as well.

No change in Meteotemplate 16.0 Onion

[Jeffm5690]

Onion????

[Johnny]

Hi Jeff,

It's the working name until its finalised.

John

[Jachym]

Hehe

yes, pre-release versions have a code name of a vegetable. Final one will be a fruit (already decided, but I wont tell)

[Jeffm5690]

Great because onion “stinks” LOL.

[Jachym]

Great because onion “stinks” LOL.

That's true Jeff, the final one will be called Durian, look it up if you don't know it

[Jeffm5690]

I learned something new! Very interesting and high calories - averaging 885 calories per fruit!!!

[Johnny]

Great because onion “stinks” LOL.

That's true Jeff, the final one will be called Durian, look it up if you don't know it

Whilst in Penang myself and some friends took shelter from a thunderstorm (under a large galvanised roof), whilst waiting there a man ran out of a doorway and threw this fruit (Durian) at a kind of alter. We were all a little surprised by his behaviour, anyway the rain eased off and we made our way back to the hotel.

When we got back we all noticed a putrid smell about us, we didn't realise at the time that the fruit contents had splashed on our clothing - we all had to change and shower as the smell was so bad.

We noticed later that you would often see stickers in shop windows showing the spiky fruit with a no entry sign on - it really does smell that bad, but apparently tastes very nice.

[Jachym]

Btw... for some airlines it is even forbidden to take on board because if someone started eating it or cut it inside the plane in the air, there is no way away from it