Re: [campsite-dev] Menu name for plugins/modules? - Newscoop Development Discussions on Sourcefabric Forum

import

On Wed, 2005-08-17 at 12:50 +0200, Paul Baranowski wrote:
> We are going to be integrating the poll and the phorum plugins into
> campsite...I'm wondering what the main menu name for these should be?
>
> Plugins?
> Modules?
> Extensions?
> Mambots?
>
> Or should we add these under "content"?
>
> - Paul

Module/addon/extension/plugin sounds the same to me.

Question is, whether we want to differ in future between level of
integration.

What I mean is:
If you design the addon properly, so that they can interact with each
part of admin interface, we can have only addons.
If you design something, that cannot interact with admin interface, we
can call it addon, but than we need extensions too Smile

Thinking in general, Admin interface should contain a place in each
form, that allows some addon to place its buttons or forms there.
Than in addon definition file we can have a section describing which
areas should be populated with addon and addon should than be able to
design forms in its interface for each section.

Example: zone in admin interface "article edit" - poll can have special
file zone_article_edit.php somewhere putting code to the proper area
Admin interface will know location of these files so it is easy to
include them for all active addons

That way you can make addon completly independent and it can be
accessible from any level of admin interface.

You can also decide to simplify thing and decide, that in menu you have
only Addons button, than select proper addon and open its admin
interface. This is easier for campsite developers for sure, but editor
must leave article editation to assign poll which is not very nice to
him.

You can also make a special poll extension that is conected to admin
interface and not to make this as general principe, but in my eyes it is
wrong way to go.

So call it whatever you wish, but make addons powerfull rather than
simple.

Ondra

------------------------------------------
Posted to Phorum via PhorumMail

import

This is a multipart message in MIME format.
--=_alternative 004945C285257060_=
Content-Type: text/plain; charset="us-ascii"

Ideally, we should be able to file them wherever they logically belong,
i.e. under whichever heading. If this is not possible/too much work, let's
file them under Tools (Micz suggested this in a chat where I warned him
about his missing the theme in his first reply).

Ondra Koutek
17/08/2005 08:00 AM
Please respond to campsite-dev

To: campsite-dev@campware.org
cc:
Subject: Re: [campsite-dev] Menu name for plugins/modules?

On Wed, 2005-08-17 at 12:50 +0200, Paul Baranowski wrote:
> We are going to be integrating the poll and the phorum plugins into
> campsite...I'm wondering what the main menu name for these should be?
>
> Plugins?
> Modules?
> Extensions?
> Mambots?
>
> Or should we add these under "content"?
>
> - Paul

Module/addon/extension/plugin sounds the same to me.

Question is, whether we want to differ in future between level of
integration.

What I mean is:
If you design the addon properly, so that they can interact with each
part of admin interface, we can have only addons.
If you design something, that cannot interact with admin interface, we
can call it addon, but than we need extensions too Smile

Thinking in general, Admin interface should contain a place in each
form, that allows some addon to place its buttons or forms there.
Than in addon definition file we can have a section describing which
areas should be populated with addon and addon should than be able to
design forms in its interface for each section.

Example: zone in admin interface "article edit" - poll can have special
file zone_article_edit.php somewhere putting code to the proper area
Admin interface will know location of these files so it is easy to
include them for all active addons

That way you can make addon completly independent and it can be
accessible from any level of admin interface.

You can also decide to simplify thing and decide, that in menu you have
only Addons button, than select proper addon and open its admin
interface. This is easier for campsite developers for sure, but editor
must leave article editation to assign poll which is not very nice to
him.

You can also make a special poll extension that is conected to admin
interface and not to make this as general principe, but in my eyes it is
wrong way to go.

So call it whatever you wish, but make addons powerfull rather than
simple.

Ondra

--=_alternative 004945C285257060_=
Content-Type: text/html; charset="us-ascii"

Ideally, we should be able to file them wherever they logically belong, i.e. under whichever heading. If this is not possible/too much work, let's file them under Tools (Micz suggested this in a chat where I warned him about his missing the theme in his first reply).

Ondra Koutek <kouteko@tol.org>

17/08/2005 08:00 AM

Please respond to campsite-dev

To: campsite-dev@campware.org

cc:

Subject: Re: [campsite-dev] Menu name for plugins/modules?

On Wed, 2005-08-17 at 12:50 +0200, Paul Baranowski wrote:

> We are going to be integrating the poll and the phorum plugins into

> campsite...I'm wondering what the main menu name for these should be?

>

> Plugins?

> Modules?

> Extensions?

> Mambots?

>

> Or should we add these under "content"?

>

> - Paul

Module/addon/extension/plugin sounds the same to me.

Question is, whether we want to differ in future between level of

integration.

What I mean is:

If you design the addon properly, so that they can interact with each

part of admin interface, we can have only addons.

If you design something, that cannot interact with admin interface, we

can call it addon, but than we need extensions too Smile

Thinking in general, Admin interface should contain a place in each

form, that allows some addon to place its buttons or forms there.

Than in addon definition file we can have a section describing which

areas should be populated with addon and addon should than be able to

design forms in its interface for each section.

Example: zone in admin interface "article edit" - poll can have special

file zone_article_edit.php somewhere putting code to the proper area

Admin interface will know location of these files so it is easy to

include them for all active addons

That way you can make addon completly independent and it can be

accessible from any level of admin interface.

You can also decide to simplify thing and decide, that in menu you have

only Addons button, than select proper addon and open its admin

interface. This is easier for campsite developers for sure, but editor

must leave article editation to assign poll which is not very nice to

him.

You can also make a special poll extension that is conected to admin

interface and not to make this as general principe, but in my eyes it is

wrong way to go.

So call it whatever you wish, but make addons powerfull rather than

simple.

Ondra

--=_alternative 004945C285257060_=--

------------------------------------------
Posted to Phorum via PhorumMail

import

I feel Mitch answer and original question diferently.
In short, Paul asked where to put modules in menu structure and how to
call it.
In my eyes this depends on the structure of module and on the way you
wish to manipulate with them.

choices:

1) Add menu "modules" and list all modules below.
If you select module, you will get a list of actions (remove/admin/....
i do not what else)

2) In Configuration add new value "modules" which opens "modules
administration" that will alow you to install/remove module
In Menu just list moduiles and selecting module goes directly to
administration

I vote for 2)

The name of the_thing_that_was_not_named are equal as I wrote before Smile

Ondra

On Wed, 2005-08-17 at 15:20 +0200, sava.tatic@mdlf.org wrote:
>
> Ideally, we should be able to file them wherever they logically
> belong, i.e. under whichever heading. If this is not possible/too much
> work, let's file them under Tools (Micz suggested this in a chat where
> I warned him about his missing the theme in his first reply).
>

------------------------------------------
Posted to Phorum via PhorumMail

import

This is a multipart message in MIME format.
--=_alternative 004B98AA85257060_=
Content-Type: text/plain; charset="us-ascii"

what we are talking here is what heading will the user go to access a
particular moudule/plugin/tool functionality. I don't think 2.4 will have
anything in terms of fancy module/plugin handling.

Your points are otherwise well taken. I am sure Paul and Mugur are taking
note.

Sava

Ondra Koutek
17/08/2005 09:40 AM
Please respond to campsite-dev

To: campsite-dev@campware.org
cc:
Subject: Re: [campsite-dev] Menu name for plugins/modules?

I feel Mitch answer and original question diferently.
In short, Paul asked where to put modules in menu structure and how to
call it.
In my eyes this depends on the structure of module and on the way you
wish to manipulate with them.

choices:

1) Add menu "modules" and list all modules below.
If you select module, you will get a list of actions (remove/admin/....
i do not what else)

2) In Configuration add new value "modules" which opens "modules
administration" that will alow you to install/remove module
In Menu just list moduiles and selecting module goes directly to
administration

I vote for 2)

The name of the_thing_that_was_not_named are equal as I wrote before Smile

Ondra

On Wed, 2005-08-17 at 15:20 +0200, sava.tatic@mdlf.org wrote:
>
> Ideally, we should be able to file them wherever they logically
> belong, i.e. under whichever heading. If this is not possible/too much
> work, let's file them under Tools (Micz suggested this in a chat where
> I warned him about his missing the theme in his first reply).
>

--=_alternative 004B98AA85257060_=
Content-Type: text/html; charset="us-ascii"

what we are talking here is what heading will the user go to access a particular moudule/plugin/tool functionality. I don't think 2.4 will have anything in terms of fancy module/plugin handling.

Your points are otherwise well taken. I am sure Paul and Mugur are taking note.

Sava

Ondra Koutek <kouteko@tol.org>

17/08/2005 09:40 AM

Please respond to campsite-dev

To: campsite-dev@campware.org

cc:

Subject: Re: [campsite-dev] Menu name for plugins/modules?

I feel Mitch answer and original question diferently.

In short, Paul asked where to put modules in menu structure and how to

call it.

In my eyes this depends on the structure of module and on the way you

wish to manipulate with them.

choices:

1) Add menu "modules" and list all modules below.

If you select module, you will get a list of actions (remove/admin/....

i do not what else)

2) In Configuration add new value "modules" which opens "modules

administration" that will alow you to install/remove module

In Menu just list moduiles and selecting module goes directly to

administration

I vote for 2)

The name of the_thing_that_was_not_named are equal as I wrote before Smile

Ondra

On Wed, 2005-08-17 at 15:20 +0200, sava.tatic@mdlf.org wrote:

>

> Ideally, we should be able to file them wherever they logically

> belong, i.e. under whichever heading. If this is not possible/too much

> work, let's file them under Tools (Micz suggested this in a chat where

> I warned him about his missing the theme in his first reply).

>

--=_alternative 004B98AA85257060_=--

------------------------------------------
Posted to Phorum via PhorumMail

import

--- sava.tatic@mdlf.org wrote:
> Ideally, we should be able to file them wherever they logically belong,
> i.e. under whichever heading. If this is not possible/too much work,
Not possible in 2.3.1

Mugur

> let's file them under Tools (Micz suggested this in a chat where I warned him

> about his missing the theme in his first reply).
>
> Ondra Koutek
> 17/08/2005 08:00 AM
> Please respond to campsite-dev
>
>
> To: campsite-dev@campware.org
> cc:
> Subject: Re: [campsite-dev] Menu name for plugins/modules?
>
>
> On Wed, 2005-08-17 at 12:50 +0200, Paul Baranowski wrote:
> > We are going to be integrating the poll and the phorum plugins into
> > campsite...I'm wondering what the main menu name for these should be?
> >
> > Plugins?
> > Modules?
> > Extensions?
> > Mambots?
> >
> > Or should we add these under "content"?
> >
> > - Paul
>
> Module/addon/extension/plugin sounds the same to me.
>
> Question is, whether we want to differ in future between level of
> integration.
>
> What I mean is:
> If you design the addon properly, so that they can interact with each
> part of admin interface, we can have only addons.
> If you design something, that cannot interact with admin interface, we
> can call it addon, but than we need extensions too Smile

>
> Thinking in general, Admin interface should contain a place in each
> form, that allows some addon to place its buttons or forms there.
> Than in addon definition file we can have a section describing which
> areas should be populated with addon and addon should than be able to
> design forms in its interface for each section.
>
> Example: zone in admin interface "article edit" - poll can have special
> file zone_article_edit.php somewhere putting code to the proper area
> Admin interface will know location of these files so it is easy to
> include them for all active addons
>
> That way you can make addon completly independent and it can be
> accessible from any level of admin interface.
>
> You can also decide to simplify thing and decide, that in menu you have
> only Addons button, than select proper addon and open its admin
> interface. This is easier for campsite developers for sure, but editor
> must leave article editation to assign poll which is not very nice to
> him.
>
> You can also make a special poll extension that is conected to admin
> interface and not to make this as general principe, but in my eyes it is
> wrong way to go.
>
> So call it whatever you wish, but make addons powerfull rather than
> simple.
>
> Ondra
>
>
>
>

____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs

------------------------------------------
Posted to Phorum via PhorumMail

import

Hey, guys, this is about restoring the very simple "API" we had in 2.1 version
in order for phorum plugin to work. This work is done for 2.3.1 so there won't
be any major changes. The plugins must add their items in a separate menu
entry, we don't have the API to do complex things yet (like
adding/removing/configuring plugins). This API takes much more work than what
we can do for 2.3.1.

Mugur

--- Ondra Koutek wrote:
> I feel Mitch answer and original question diferently.
> In short, Paul asked where to put modules in menu structure and how to
> call it.
> In my eyes this depends on the structure of module and on the way you
> wish to manipulate with them.
>
> choices:
>
> 1) Add menu "modules" and list all modules below.
> If you select module, you will get a list of actions (remove/admin/....
> i do not what else)
>
> 2) In Configuration add new value "modules" which opens "modules
> administration" that will alow you to install/remove module
> In Menu just list moduiles and selecting module goes directly to
> administration
>
> I vote for 2)
>
> The name of the_thing_that_was_not_named are equal as I wrote before Smile

>
> Ondra
>
> On Wed, 2005-08-17 at 15:20 +0200, sava.tatic@mdlf.org wrote:
> >
> > Ideally, we should be able to file them wherever they logically
> > belong, i.e. under whichever heading. If this is not possible/too much
> > work, let's file them under Tools (Micz suggested this in a chat where
> > I warned him about his missing the theme in his first reply).
> >
>
>
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

------------------------------------------
Posted to Phorum via PhorumMail

import

Sorry, my mistake.
I thought you are not planing 2.3.1 but king about 2.4 which should have
modules done.
Ondra

On Wed, 2005-08-17 at 09:11 -0700, Mugur Rus wrote:
> Hey, guys, this is about restoring the very simple "API" we had in 2.1 version
> in order for phorum plugin to work. This work is done for 2.3.1 so there won't
> be any major changes. The plugins must add their items in a separate menu
> entry, we don't have the API to do complex things yet (like
> adding/removing/configuring plugins). This API takes much more work than what
> we can do for 2.3.1.

------------------------------------------
Posted to Phorum via PhorumMail

import

Ondra, you are mistaken, the plugin API is not scheduled for 2.4.

Mugur

--- Ondra Koutek wrote:
> Sorry, my mistake.
> I thought you are not planing 2.3.1 but king about 2.4 which should have
> modules done.
> Ondra
>
> On Wed, 2005-08-17 at 09:11 -0700, Mugur Rus wrote:
> > Hey, guys, this is about restoring the very simple "API" we had in 2.1
> version
> > in order for phorum plugin to work. This work is done for 2.3.1 so there
> won't
> > be any major changes. The plugins must add their items in a separate menu
> > entry, we don't have the API to do complex things yet (like
> > adding/removing/configuring plugins). This API takes much more work than
> what
> > we can do for 2.3.1.
>
>
>

____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs

------------------------------------------
Posted to Phorum via PhorumMail

Howdy, Stranger!

Categories

Poll

Top Posters