hide the edit button in settings

[endoanaconda]

No description provided.

[Klap-in]

You are also changing stuff in the cloud syntax.
Please provide descriptions of your changes, and their use cases.

Why should I hide the edit button?
Thanks.

[endoanaconda]

sorry, I've mixed up the two commits, cloudcount is in an other pull req. this one is only about the added flag for hiding the editbutton in settings

Why should I hide the edit button?
1st:I dont want it to be seen for all users
2nd: using the edit button removed some of my content, didn't get why, but it does. I'd rather like to edit the raw data

[Klap-in]

Personally, I'm not enthusiastic about this config setting. It adds one more config setting, for something that should the same as editing raw text but in a more user friendly manner.

@splitbrain what is your opinion?

btw what kind of content is removed by the entry editor?

[endoanaconda]

• I don't see the problem by having a choice in settings.
• I prefere to edit in plaintext, some users might use the editbutton, this results in diffrent versions of the dataset (see below)

what kind of content is removed/changed by the entry editor

• when I group the datafields into logical blocks, with an extra empty line in between, this gets removed
• in consequence I have some pages (where edit button has been used) with no logical-blocks, the ones I change in plaintext remain in the same style. search and replace gets pretty annoying
  if i want to do mass changes over all files

example what I mean with logical blocks: Imagine you have 30 fields, then you want do give it some structure, so I started using logical blocks

field1 : abc
field2 : abc
field3 : abc

field4 : abc
field5 : abc
field6 : abc

field7 : abc
field8 : abc
field9 : abc
field10 : abc