#149 new
August

Flesh out what we mean by "plugin architecture"

Reported by August | May 30th, 2011 @ 04:55 PM | in Basic Infrastructure [Concerto2]

While I've had some great discussions with Brian M. on what sort of plugin architecture we'll look to create and how it might work, we need to get this written down and into practice. How will plugins manifest themselves? Where will they go? What capabilities will they have access to? How would one go about writing one?

Comments and changes to this ticket

  • Brian Michalski

    Brian Michalski June 1st, 2011 @ 12:12 AM

    I see a few areas where plugins will be able to supplement, replace, or otherwise alter current functionality -

    • Kinds of content (i.e. video support plugin). This is mostly done, at least from the upload perspective, but it will need to be taken into account when we get serious with the content display code (both CMS and Screen ends of it).
    • Supplemental view blocks. There was discussion of being able to supplement views with additional modules to link to integrate other services, potentially of the social nature, into some key views. We'll have to identify what these key view blocks are...
    • Supplemental data. We've identified a base set of data required for the system to work, but people might want to add a field to some of our forms and tie in additional data. I haven't extensively thought about what forms make sense to offer this on, but clearly content, screen, and user seem like a good start. What other models make sense?
    • Alter select behaviors. Content rotation is the largest feature that comes to mind here, where someone might want to plugin a scheduling system or other rotation algorithm. What else could people want to override?

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Concerto is an open source digital signage system that makes it easy to engage a large community of people with graphical and text-based announcements, bulletins, and other messages... but enough about us, you came here to get involved.
<br />
If you think you've <b>found a bug in Concerto</b>, please click 'Create new ticket' and let us know about it.
<br />
Looking to peek at our source code? Head to <a href="https://github.com/concerto/concerto_v1">https://github.com/concerto/concerto_v1</a> (Concerto version 1) or <a href="https://github.com/concerto/concerto">https://github.com/concerto/concerto</a> (Concerto version 2).
<br />
Our getting started guide is available here: <a href="https://github.com/concerto/concerto/wiki/Getting-Involved">https://github.com/concerto/concerto/wiki/Getting-Involved</a>.

Tags

Pages