Hi During my work on moving some LaTeX specific functions from Geany core to geanyLaTeX plugin I recognized some code which is pretty much HTML/XML specific and might would make sense to move also into a plugin. On first step I was thinking about moving auto_table() out of editor.c, but there are a couple of more things like the automatic closing of XML tags which might would make sense to move into a separate plugin.
Lets give you a short list of advantages/disadvantages I can imagine
off doing such a step:
Advantages:
+ Geany's core is keeping small and as we don't need to care about too
much filetype specific stuff
+ Save some CPU cycles on every change on editor widget for users which
don't use XML/HTML as the check for this types will not be needed
anymore
+ More flexibility in upgrading the fileype specific functions when
realized as a plugin
* Possible more configuration possibilities for user without bloating
Geany's preferences dialogues itself for non-XML/HTML users
Disadvantages
- With a new plugin the user needs to know about and needs to activate
it
- User might think Geany is not support HTML properly as he wasn't
aware of n-1
- Additional overhead on
* coding
* running the plugin through plugin API
Please let me know what you think about.
Cheers,
Frank
--
http://frank.uvena.de/en/
pgpPuq379a9CN.pgp
Description: PGP signature
_______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
