Christian Boos wrote:
> Christopher Lenz wrote:
> > Hey all,
> >
> > I'm going to work on integration the WebAdmin plugin into Trac proper
> > the next days. This shouldn't cause much of a disruption, so I don't
> > think a branch is needed.
> >
> > My plan is to:
> >   * move trac/scripts/admin.py to trac/admin/console.py
> >   * move the main WebAdmin components into trac/admin/api.py and trac/
> > admin/web_ui.py
> >   * move the ticket admin components into trac/tickets/admin.py
>
> Great! I thought this was somehow dependent on the setuptools branch,
> but apparently I was wrong.
> So does this mean that the WebAdmin will not be a plugin anymore, but
> will be part of the core components?
> I thought that maybe it could become simply a "bundled" plugin.
...

from a design point of view, this _could_ be possibly the correct way
to go.

[The 'eclipse' framework does it this way: 'plugin bundles' define
essentially a product on top of the framework].

Just a tiny "core" would exist (trac-framework, /trac/* ), and every
functional unit would become a plugin (e.g.
/trac/bundles/<unit-name>/plugins)

In context of the WebAdmin, the plan of C.Lenz to integrate it into the
core application framework _seems_ correct, because other functional
units (Ticket System etc.) provide functionality to the (central)
"Admin" part of the framework.

"move the ticket admin components into trac/tickets/admin.py" is for
sure correct, because the functionality belongs to the functional unit
"tickets".

The decision "Bundled Plugin" or "Integrate to Core" depends mainly on
how far the plugin-architecture of trac should go in future.

It _could_ be positive to start with the WebAdmin to implement
everything based on plugins (e.g. within a folder /product/ or
something else).

The other option would be, to move the WebAdmin to 'trac/admin' as
suggested, and to refactor the whole code to a later point (after
planning the plugin/bundle/product architecture).

.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" 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-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to