When you tell people to change one of the core routines of a root someone else distributes, you should probably also tell them that when the routine gets updated, as this one surely will, soon, they will lose their changes.
Much better approach: Ask me to add a callback where you want to be able to extend one of the core routines. I usually try to accomodate these requests if I possibly can.
Indeed, I ought to put a big disclaimer on all the various hacks that I've put out for core OPML code: that it's liable to change and it's for advanced users only.
Invert it and you'll see a big compliment - that Frontier is cool enough that it's extremely easy to change the core routines.
2006-08-28EDT12:51:35+00:00
#
Invert it and you'll see a big compliment - that Frontier is cool enough that it's extremely easy to change the core routines.
It's not a new thing Tom, and I don't see it as a compliment or not a compliment, but as a headache for users. I care about them, and I don't like to see them led into something that absolutely won't work.
2006-08-28EDT13:03:14+00:00
#
Dave: I've added a warning on the top of all the hacks that edit core routines. It says:
"IMPORTANT NOTICE: The following code, like all my hacks, is experimental. When you update the Editor, it's likely to be removed. Use with care! --Tom"
2006-08-28EDT16:10:59+00:00
#
"IMPORTANT NOTICE: The following code, like all my hacks, is experimental. When you update the Editor, it's likely to be removed. Use with care! --Tom"
