rvelices wrote:

Just not to forget. I think we should not deliver with the RC/final release the plugins under svn... Some do not work, some work just in some cases, etc...

Absolutely!!!


On my side, these will be embedded in Piwigo:
Admin Advices     1.8     Give you an advice on the administration page. (Piwigo team)     Deactivate
Language Switch     1.8     Switch to another language from flags on your gallery home page. (Piwigo team)     Install Delete

Swift Theme Creator will be externalized from trunk.
8-)

From my point of view, stable plugins could stay in trunk.

A new version of them can be distributed in Extensions (with another name or NOT! but with all issues managed).

If same name take care of:
- Piwigo upgrade could downgrade an Extension plugin.
If another name:
- Two # plugins should NOT have same configuration parameters.

In your cases:
A stable "LocalFiles Editor" SHould be kept in trunk.
A stable "Extended description" Could be kept in trunk.

P@t, you have to manage the points.
8-)

P@t wrote:

Ok... I will remove Extended Description from trunk.
With the new plugins manager, it will be easy to install it.

For LocalFiles Editor, I will update it to work with template extention.
I have one question: do I keep Editarea (the Syntax highlighter)?
It's released under LGPL license and his author is agree to distribut it with pwg.
Does everybody like this javascript editor? Vincent, I remember that you disabled it on your site...
Last version is chrome compatible.

Editarea is too slow with large personal plugin (reason to disable it).

Anyway, some ideas:
- Currently don't Edit Admin themes (could be in a later release),
- Don't Edit Admin templates (no immediate request for that I think),
- Keep in mind that some public templates cannot be template-extension (I think slideshow.tpl mainly).
- If template-extension editing is not available with the official distributed release, no doubt you could distibute it by a later extension delivery (release).
- About javascript editor, did you check if jQuery have one plugin to do it?
- What is the current size of Editarea? Could help to decide.

8-)

rvelices wrote:

Just a precision: we can leave everything under svn (if the author wants it) - this is not the issue. The issue is delivering plugins with the piwigo official release the team acknowledge that these plugins work in all possible configurations, are optimized and there are no security holes inside ...

+1

If we can, it will be super.
Pierrick? or Mathias?
8-)

VDigital wrote:

rvelices wrote:

Just a precision: we can leave everything under svn (if the author wants it) - this is not the issue. The issue is delivering plugins with the piwigo official release the team acknowledge that these plugins work in all possible configurations, are optimized and there are no security holes inside ...

+1

If we can, it will be super.
Pierrick? or Mathias?
8-)

Yes we can: we can remove the unmaintained plugins on branches/branch-2_0 but keep them on trunk. Does it answer your question?

VDigital wrote:

P@t,
Have a look to markItUp! Universal markup editor.
8-)

It's seem to be a great application, but it's not a syntax highlighter...
It's really not usefull in LocalFiles Editor ;-)

I already try another Syntax highlighter scripts, and my conclusion is that editarea is the best.
Most of scripts have a lot of bugs (especially with copy/paste functions, like codepress).
Editarea is already compatible with chrome in the latest version.

Editarea size is 180Ko (script, language files and icons)

The question is... does LocalFiles Editor need a syntax highlighter?

Last edited by P@t (2008-09-17 00:36:36)

Today should be 2.0.0RC2 day, but it's a bit too short (at least for me and pLoader, we should propose 2.0.0RC2 tomorrow saturday 4th, Octobre 2008).

The big question now is "when 2.0.0?". 2.0.0 needs the new website, and we are late on the website I'm afraid. So I propose to add a 2.0.0RC3 next week and to postpone 2.0.0 to 2008-10-17. Is it OK for you?

rvelices wrote:

'!?@'*;:.</. - does it also mean no 2.0 branch until 10-17?

No. 2.0.0 official announce and piwigo.org website are "marketing" related events. We can say that on 2008-10-10, we create the branch if you want (and so you can have branch 2.0 unders SVN on your website).

rvelices wrote:

is that web site really going to be ready for 10-17 or just maybe ?

I'm waiting for mathiasm feedback about this. I don't know if he as succeeded to integrate stripy layout into Drupal (that's the main point I think). On my side, I have to provide the "priority 1" pages : homepage (easy), requirements, features, download page, etc.