I think that a simple addition to minimalist would be to extend the @include
field (which currently only accepts wildcard notation to include several pages)
to support the NOT operator, so you could have a module that applies to every
page but some you already know it.
For example: i have a module that blocks all images, flash and colorful CSS and
i have it always on at work (when i need to check something on the net and
don't want to attract too much attention), but when i go to GMail or Drive the
pages are nearly unusable (especially Drive), so i need to activate/deactivate
it every time...
A simple NOT operator would suffice to fix this and allow a more complex
configuration on modules.
Additionally, you could just parse the single comma separated @includes with a
regexp matcher and add even more possibilities (without needing to write any
code!) but then the syntax for writing the @includes would be more complex too.
Thanks,
Riversilk
Original issue reported on code.google.com by rivers...@gmail.com on 5 Aug 2013 at 8:13
Original issue reported on code.google.com by
rivers...@gmail.com
on 5 Aug 2013 at 8:13