Jani Tiainen wrote: > - Plugins are hard to install due great variety of ways to install them. > Direct dropping of EGG-file, easy_install variations, using setup.py etc.
All of these are basically the same thing. They all revolve around Python's disutils packages which is meant for installing python packages. Plugins are just that, python packages. They can go anyplace a python packages can go. Additionally, you can place the egg files in the environment's `plugins` directory. Single file plugins are not technically python packages, so they must go in the environment's `plugins` directory. > - There is not end user friendly collection of plugins. Trac-Hacks is > excellent site in count but to find something there is a bit painful, > even more painful is trying to determine quality of plugin since there > is no review or stats mechanism. There is work being done to trac-hacks to make easier to find good plugins. > - Do-it-as-a-plugin mentality. There is load of small requests to have > small functionality, usually in core. Usually you get arrogant-appearing > response 'Not in Trac can be done as a plugin'. It's unfortunate that the "can be done as a plugin" is seen as an arrogant response. Trac "core" is simple a plugin framework with plugins for wiki, tickets, roadmap, admin, and source browsing. The response "can be done as a plugin" is meant as an indicator that it can be done. Plugins also provide an excellent method for eventual integration with "core". If someone has a plugin for a popular feature, it's much easier to take that proven code and integrate it. > Plugins are pretty heavyweight solution, so why there couldn't be > simpler scripting interface to Trac? Basically you could write what old > macros were directly through web page and they get executed when needed. > This is just an idea. I've no clue is it really feasible or would it > provide any additional value. Heavyweight in that you need to know some python and the trac interfaces you desire to use. However, creating a single file plugin, subclassing WikiMacroBase to create a macro, isn't really what I would call "heavyweight" I highly doubt that creating a scripting language and exposing it via a web editor will ever become part of trac. For one, why create a scripting language when python is already an excellent one. Creating another scripting language, specific for trac, is just one more thing for people to learn. -John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
