K-Meleon :: Extensions

Extensions : K-Meleon Forum

All about K-Meleon extensions.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=disrupted]
the problem isn't due to a secondary macro for a menu, it happened when early extensions used a different wservices.kmm that build the menu differently.

there aren't problems with speciality macros as long as the extensions depending on them use the same speciality macro which is now done with the recent updates and revisions and all extensions using a secondary menu macro do not conflict in anyway or cause any problems. this is exactly the same as using the sendto macro which is provided by default installation, or using the config menu which is built using own macro.. just like there's nothing wrong with using sendto for creating submenus there isn't anything wrong with using a secondary macro for making a predefined  menu. when no extension is using a speciality macro or the sendto macro, no menu will be displayed at all. the only difference between a speciality macro and the sendto is those are installed with extensions and the latter comes with kmeleon

sendto was provided to make it easy for users to write macros without passing a url paramater and speciality macros are provided for macro writers when they prefer to display similar functions under a unified menu.. avoiding the clutter and confusion when everything is right in tools menu or the document context.
while siria's approach is another solution, it isn't practical for writers and is somewhat similar to alain's original speciality macro 'entertainments' which was pprovided for games... the menu was built using a prefs value on startup and then removed when kmeleon was closed.. ensuring that menu can only be drawn when a game macro exists and creating the pref. while that is a good method to limit the menu to their calling macro; it isn't the conventional way for other macro writers to use that same menu.. with the speciality macro you only have to include it in the package and write your macro without worrying about conflicts or weird work arounds.

the speciality macros provide a tidy way of combining similar macros, compare that with firefox where every extension just throws itself in the tools or document menu and the end result you have ugly and confusing menus extending to the height of the browser window and even collapsing.. luckily here, we don't have this problem and we shouldn't since we all work together not only in creating original extensions but making sure they display neatly without cluttering the interface.

extensions are becoming an essential part for most browsers.. purists do exist who demand nothing more that the surfing power but the vast majority want extra functionality at par with other browsers..otherwise, no matter how they prefer kmeleon for its speed and responsiveness; they will look elsewhere or confine kmeleon to 'secondary browser' (when i want to quickly check my email).. limiting its usage to no more than 5% of actual surfing and eventually dropping it all together. the whole idea is they shouldn't feel the need to resolve to firefox when they need extensions, especially useful and justified ones.. surely some do require useless eye candy extensions but we don't cater to those anyways and they can only be satisfied with a manipulative ui like xul and nothing else.

kmeleon maintains its performance with many extensions and macros installed plus the unique and powerful macro language.. there's nothing wrong in taking full advantage of those features

[url=http://kmext.sourceforge.net/macros/speciality/]http://kmext.sourceforge.net/macros/speciality/[/url][/quote]

K-Meleon forum is powered by Phorum.