Posted by aaron1234nz on March 14, 2009 at 12:02am
Jump to:
| Project: | Charts |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Hi,
I'm the maintainer of the fusioncharts module for Drupal. I recently had an interesting issue appear on my issue queue a couple of weeks ago. It appears that my module has the same name as your fusioncharts submodule. http://drupal.org/node/382532
We should work out a way of resolving this issue. As far as I can see the options are for either you or me to rename our modules for for the two modules to combine in some way.
what are your thoughts?
regards
Aaron
Comments
#1
this is an interesting issue
There are too many chart related modules and that slows down the development.
Would it be possible to have some collaboration between these projects? Like a small fusioncharts project dependency? And the cck and views integration could be done with the charts module dependency.
dependency tree:
-fusioncharts
--charts
---chartfield (fusioncharts_cck)
---chartview (fusioncharts_views) the views integration probably should not be a submodule, this should be part of the charts module
#2
Heh, this has been driving me nuts this morning too :)
#3
Aaron,
sorry for taking so long to reply. Well, i would be glad to merge projects. Charts module is focused on set a default input data for all chart solutions. It benefits developers and users, since if they are not happy with their current charts, they can change it without any modification.
I would be happy to remove FusionCharts integration from default Charts module if you integrate it on your module and maintain it. All basic functions are already present, and you can add new functionalities.
waiting for your reply.
regards,
massa
#4
Hi Massa,
I've been working on other things for the last while so haven't done much with fusioncharts for a while. Hopefully when I get version 2 of matrix stable, I'll get back into fusioncharts again.
I'm happy to merge your code into my module. One thing I noticed last time I looked at your code, is that you have only implemented single-series charts. I've implememted all of the multi-series charts as well - so I'll have to have a think about the best way to merge the API's. Then there's the large range of chart options as well which are on a chart-by-chart basis.
Anyway, I'll give it some proper thought and probably contact you with some questions when I get going again.
Aaron
#5