#68 Merge macros=plugins, make global by default

[ffeuuell]

Firstly, congratulations to everyone for reviving WoaS. It seemed dead for a long time after 0.9.6B. Lots of new features, which I am only starting to explore.

I was afraid I would have to write section-folding for myself, but someone has already done it as a macro.
but ...
I tried twice to make it global, following instructions in WoaS::Help::Macros, and failed. I've been programming for decades - what hope would a non-technical user have?

It seems that macros and plugins are the same. I suggest that you drop all mention of macros, and call everything plugins.

All plugins (macros) should be global by default.
The user should not have to do anything - especially not write code/WSIF.
In theory it is more flexible to have non-global plugins, but who actually needs them? This is a personal note-taking Wiki, not an application suite nor a development environment.

It would be good to import all plugins automatically, instead of making the user get them one by one.
On startup WoaS should load all files from the "plugins/" subdirectory. The user can simply delete any unwanted ones from that subdirectory.
I know that a subdirectory is against the basic idea of everything in one HTML file. But dynamically loading plugins from a subdirectory makes everything so much easier. Less code to write and maintain. User needs to learn nothing except adding or removing plugins from a subdirectory.

(Aside : personally I prefer an "images/" subdirectory rather than embedding images. Embedding just means more code to maintain. Also blocks of Base64 inside the Wiki are a nuisance if you use GIT, or other version control, to keep track of changes.
Given that you release WoaS with subdirectories like examples,macros,plugins anyway - you may as well make subdirs an official feature.)

My suggestion means that you could get rid of several Help pages, which most users cannot understand anyway. You would only need one simple page saying "add or remove plugins from the plugins/ subdirectory".

By the way : why WSIF?
It seems like unnecessary complication and extra code to write and maintain.
Why not load plain text javascript into macro.text internally?
Is it something you had to do for compatibility between browsers? (Please excuse my ignorance, I have only started looking at v0.12.0. I have not explored the forums, etc.)

[FutureBoyNil]

Hello ffeuuell, Macros are, well, macro's and plugin's are pages, that _could_ contain macro's, or other text.
I think plugins have regular expressions so you can slurp in many at once, but you'll have to ask Legolas.
External images are getting there, some branches have {{path/image}} syntax.
WSIF is an interchange format, human readable text, you can edit and import/export. It only contains pages, so is portable across versions and platforms.