Concerning languages, the longer the list is, the better. The only condition is that the translation is complete or as near to completion as possible.

Concerning plugins, there are features, developped as plugins, that should be in core. They are plugins just as a matter of architecture choice, but they deserve to be in the core product.

I'm not agree at all!
We should keep at least english, french, italian and spanish... (I'm not sure that nederland is necessary)

For plugins, We should keep:
- Add Index
- Admin Advice
- Admin Multi View
- C13y
- Event Tracer
- Language Swich
- LocalFiles Editor

P@t wrote:

I'm not agree at all!
We should keep at least english, french, italian and spanish... (I'm not sure that nederland is necessary)

For plugins, We should keep:
- Add Index
...
- LocalFiles Editor

If piwigo.net become international, we have to center our work on the english language. You say that nederland is not necessary. Nederland is as necessary as french or italian.

One definition of plugin is to provide service "On demand"
About plugins you cite:
-> Add index is not necessary. It should be include with synchronisation functionality
-> Admin advice is not necessary. It's used to help a small part of our customers
-> Admin multi view is not necessary. You can use 2 differents navigator with 2 users.
-> C13y ????? I don't know this plugin at this time
-> Event Tracer is not necessary. Only developpers use it
-> Language Switch is not nesessary. Most of Piwigo galeries has only one language
-> Local files editor is not necessary. This plugin is used by users who want to custom their templates without Vim or Emacs (for barbarians)

VDigital talk about RV DB integrity. This plugin is not neccessary. PWG is powerful. Database is not corrupted ;-)

Distributing plugins with web application is like distribute IE with Windows.

VDigital wrote:

Themes could be removed.
Languages could be removed by the webmaster.

An graphical interface in the admin part to activate/Deactivate and Delete (to even install)

template/themes

and

Languages

would be can be one more

VDigital wrote:

But risky this time.
;-)

Not these days Ci yes but for the future less to risk that suppression by ftp

Possibility of preventing the admin that certain user uses theme or language.

To propose to him to reallocate with the user, theme and language by defect

VDigital wrote:

If you go in that way Laurent, I am not sure Synchro is needed as well.
Does Internet need pictures? Do pictures need Internet?
Plugins could be removed.
Themes could be removed.
Languages could be removed by the webmaster.

What is the best?

8-)

The idea of this discussion come from this article where PWG is considerated as "usine à gaz".

To answer your comments, synchro is needed because you can not manage images without collecting information first.
Internet partially need pictures because pictures are part of communication system.
Images doesn't need internet, they only need one support between many. Photographer chooses his support.

My viewpoint is (but I don't know if it's the best):
-> Do it simple
-> Let the user choose the plugins he needs, don't impose them

Stripy says that newbies appreciates a default collection of plugins and themes and he is right.
I complete saying that experts appreciates to not surcharge the downloads.

This is why I suggest a basic pack vs a full pack.

Last edited by laurent.duretz (2008-10-06 12:01:02)

laurent.duretz wrote:

To answer your comments, synchro is needed because you can not manage images without collecting information first.

This is another topic, but ron and z0rglub have proved we can do without it.

More I have in mind another simple trick to remove our constraint (whilst synchro functionality available): a future improvement.

8-)