You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Tim Van Steenburgh <va...@users.sf.net> on 2014/01/20 16:59:00 UTC
[allura:tickets] Re: #6393 Allow plugins to register new markdown macros
So for this ticket should I just remove the `[[download_button]]` macro from the default wiki page text?
---
** [tickets:#6393] Allow plugins to register new markdown macros**
**Status:** in-progress
**Created:** Tue Jun 25, 2013 04:39 PM UTC by Tim Van Steenburgh
**Last Updated:** Thu Jan 16, 2014 08:20 PM UTC
**Owner:** Tim Van Steenburgh
Right now all of our markdown macros are defined in Allura core, even those that are tool-specific. We should provide a way for plugins to register their own macros with the platform.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #6393 Allow plugins to register new markdown macros
Posted by Tim Van Steenburgh <va...@users.sf.net>.
Yeah, a while ago I added code that allows entrypoints to be overridden by subclasses. See the `iter_entry_points()` docstring in `allura/lib/helpers.py`.
---
** [tickets:#6393] Allow plugins to register new markdown macros**
**Status:** in-progress
**Created:** Tue Jun 25, 2013 04:39 PM UTC by Tim Van Steenburgh
**Last Updated:** Thu Jan 16, 2014 08:20 PM UTC
**Owner:** Tim Van Steenburgh
Right now all of our markdown macros are defined in Allura core, even those that are tool-specific. We should provide a way for plugins to register their own macros with the platform.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #6393 Allow plugins to register new markdown macros
Posted by Dave Brondsema <br...@users.sf.net>.
Seems ok to me, as long as there won't be problems with 2 tools with the same name. I think you figured out some of that before.. disabling the original entry point perhaps? Will the tool name be the same so existing app configs from mongo load the overrided app?
---
** [tickets:#6393] Allow plugins to register new markdown macros**
**Status:** in-progress
**Created:** Tue Jun 25, 2013 04:39 PM UTC by Tim Van Steenburgh
**Last Updated:** Thu Jan 16, 2014 08:20 PM UTC
**Owner:** Tim Van Steenburgh
Right now all of our markdown macros are defined in Allura core, even those that are tool-specific. We should provide a way for plugins to register their own macros with the platform.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #6393 Allow plugins to register new markdown macros
Posted by Tim Van Steenburgh <va...@users.sf.net>.
For now, how about making the default page text a property of the WikiApp? Then we could just subclass and override it in sfx.
---
** [tickets:#6393] Allow plugins to register new markdown macros**
**Status:** in-progress
**Created:** Tue Jun 25, 2013 04:39 PM UTC by Tim Van Steenburgh
**Last Updated:** Thu Jan 16, 2014 08:20 PM UTC
**Owner:** Tim Van Steenburgh
Right now all of our markdown macros are defined in Allura core, even those that are tool-specific. We should provide a way for plugins to register their own macros with the platform.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #6393 Allow plugins to register new markdown macros
Posted by Dave Brondsema <br...@users.sf.net>.
That'd be sufficient in terms of making this have good functionality for standard Allura installs.
For SourceForge to continue to have a `[[download_button]]` in the default content of new wikis, though, we'd have to make the default wiki content configurable. An .ini setting might work but would be lengthy and cumbersome. An overridable template might be nice. Neighborhoods can have a "project template" specified for initial tool configuration and that includes support for `home_text` on a wiki, but then users can't choose their tools at all during project creation, so that's no good. Perhaps a new ticket for this :)
---
** [tickets:#6393] Allow plugins to register new markdown macros**
**Status:** in-progress
**Created:** Tue Jun 25, 2013 04:39 PM UTC by Tim Van Steenburgh
**Last Updated:** Thu Jan 16, 2014 08:20 PM UTC
**Owner:** Tim Van Steenburgh
Right now all of our markdown macros are defined in Allura core, even those that are tool-specific. We should provide a way for plugins to register their own macros with the platform.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.