Hi, On Sun, 17 Jan 2010 16:48:43 +0100 Enrico Tröger <[email protected]> wrote:
> Basically you are completely right about moving filetype specific code > from the core into a plugin. But we also have little specifics for > other filetypes, e.g. auto indenting in Python after typing a colon. Of course, this would also apply to other code. > These little things don't match the requirement to be moved into a > plugin, IMO. Though in case of the HTML/XML features, there is a lot > more stuff which we do so we are talking about a good bunch of code > not only a few lines. Yes. auto_table() was just an example to start with. > Still I think it could become a bit cumbersome for users to enable a > specific plugin to have the functionality they were used to have in > Geany for ages. > And then there is the fact the code in question in used for HTML *and* > XML which are two separate filetypes. How should a user expect that he > have to enable a HTML plugin to get tag auto closing in XML files? I could imagine of get rid off this by doing two things: - Giving the plugin a name. Something like SGMLauto - Establish a configurable connection between filetype and plugin similar ti what emacs is having for its modes. (I know, if this is a valid point, that this is nothing can be done within five minutes) > After all, I rather think we should keep it in the core even though > it's mainly for the better user experience. Yes, this is what I wasn't sure about so I've asked the list - the users ;). Cheers, Frank -- http://frank.uvena.de/en/
pgp6RUpM4JLJB.pgp
Description: PGP signature
_______________________________________________ Geany-devel mailing list [email protected] http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
