@anonymous-matomo-user opened this Issue on February 23rd 2011

hi guys, after some customer feedback i started to rework the piwik guy.
Therefore i wrote a plugin to show the idea.
All code is extjs3 based but should be easily convertable to extjs4.
The Sample Code runs with piwik 1.1.1.
The colors are completly changeable.

@anonymous-matomo-user commented on February 23rd 2011

Attachment: dateselector

@anonymous-matomo-user commented on February 23rd 2011

Attachment: dashboard

@anonymous-matomo-user commented on February 23rd 2011

Attachment: other panel

@anonymous-matomo-user commented on February 23rd 2011

Attachment: integration in TYPO3

@anonymous-matomo-user commented on February 23rd 2011

i used extjs 3 because it's stable (extjs4 will be released later this year)

@robocoder commented on February 23rd 2011 Contributor

Thanks for the suggestion Kay.

I think this idea can either be added to #2097 or considered a use case for the theming plugin. (I'll leave as a separate ticket in the meantime.)

re: extjs: we don't plan to add/use extjs in core because we're moving away from GPL-only JavaScript. (fdd2div and Superfish are the last two.)

@anonymous-matomo-user commented on February 24th 2011

mhmm ok.

extjs is not GPL only - there also developer licenses for non gpl projects.

the big advantage would be the integrated chart support without using flash -> this way piwik could be the very first web analytics software which runs on android and IOs Hardware without flash.

which license is planned to be used for piwik if other Gpl software is removed?

@robocoder commented on February 24th 2011 Contributor

which license is planned to be used for piwik if other Gpl software isremoved?

We're only planning to remove fdd2div and superfish. Piwik will still be GPLv3 or above.

Removing the GPL-only javascript isn't a commercial vs noncommercial decision, or features of extjs vs jquery. The problem is a question of compliance for users:

1) Stallman considers the act of "serving of javascript to the browser" to be a form of conveyance covered by the GPL (not just the Affero GPL under network interaction)
2) Piwik minifies the JavaScript and license headers may be stripped

If someone offers a publicly, hosted Piwik, it can be argued (because the FSF hasn't clarified its stance) that users have to provide links and notices to the original, unminified JavaScript source, in order to be fully GPL compliant.

@anonymous-matomo-user commented on February 24th 2011

mhmm, i've seen it in tine20.org (GPL) the compress the JS but let the comments intact.
Or they use the compressed scripts which have comments and let them untouched even if the concat all the files to one.

Feel free to ask the sencha guys (owners of extjs) what they think.
Probably this is a solution.
With ExtJS the GUI can be blazing fast and it's much more easy to deploy extjs apps in only js, than the ugly jQuery html mix - which is of course a bit easier with jQuery UI

I don't wanna force or blame you - but there must be a reason why many complex opensource projects (e.g TYPO3, Tine20.org) use ExtJS with compression ;)

Is it possible to provide a link to Stallmans considerations? - Thanks in Advice.

@robocoder commented on February 24th 2011 Contributor

Search for Stallman's article, "The JavaScript Trap".

The definition of "conveyance" is defined in the GPL license text, and is repeated in Sencha's FAQ. (Mind you, Sencha's interpretation might be more strict, presuming a motivation to sell more commercial licenses.)

@anonymous-matomo-user commented on February 24th 2011

he adds a convention for releasing free js programm.

http://www.gnu.org/philosophy/javascript-trap.html (end of page)

building this in the compressor should do the job with any included GPL licensed JS Code. Additionally the complete code of piwik is available through the officical piwik.org page - so I can't see a problem?

Anyway any JS which is included in Piwik is under the GPL - isn't it? - So there will be the same problem - or not?


@robocoder commented on February 25th 2011 Contributor

We completed an extensive licensing review, so this isn't going to change.

Piwik's overall license is GPLv3 or later. This is unchanged. Third-party components are licensed separately. We select the license that's compatible with GPLv3. The component's license is not changed by Piwik's use of the GPLv3.

Piwik-specific JS is either BSD (e.g., piwik.js) or GPLv3 by default. When these are served by the web server, we do not consider this to be conveyance because it is only a fragment of Piwik (as opposed to a verbatim copy). This is also our view for third-party JS, but some have argued that this is conveyance -- an interpretation that conflicts with ours.

@anonymous-matomo-user commented on February 25th 2011

thanks for clearification.

That interpretation sounds strange ...especially that all other webapplications would have that problem too.

@robocoder commented on February 25th 2011 Contributor

I can't speak for the developers of other web applications. Projects should do their own due diligence.

Even if we ignored the conveyance issue, or used a workaround like a third-party CDN to serve extjs, we've already noted elsewhere that it would be too much effort to switch from jquery to another framework.

@mattab commented on April 28th 2011 Member

let's reopen when there is a mockup (JPG only no code needed) that would look good

This Issue was closed on April 28th 2011
Powered by GitHub Issue Mirror