Feature Proposal: It would be an improvement if the ExcelImportExportPlugin handles excel tables without having a foswiki form defined
The need to define a foswiki form for every single excel file you want to get rendered as an foswiki table is really inefficient and time-killing.
Description and Documentation
At current state the plugin only handles excel data if a corresponding foswiki form exists. We need a feature to render every excel table as an foswiki table even if there is no foswiki form defined first. That feature affects the excel2table function of the plugin in first place.
-- Contributors: SvenHess
- 04 Jun 2009
I have already implemented that feature by request from some colleagues. It causes nice feedback and I would like to share it with the community. So what's the next step?
- 04 Jun 2009
The modification policy of the plugin is PleaseFeelFreeToModify
, so the next step is first: upload your fully backward compatible version to the plugins home topic, and second: apply for svn-access.
- 05 Jun 2009
Hi Franz, the svn-access has already been granted. But isn't it necessary to create an new task first before uploading it to svn? That's why I have started with that feature proposal to create a new task afterwards.
- 08 Jun 2009
We only need feature proposals for core features and for changes to plugin behavior on the plugins that are shipping with Foswiki (the so called default plugins).
All othere plugins are either Feel Free plugins where you can go ahead. Or Contact Author First where you need an agreement with the original author before you can go ahead (if he is still an active developer).
So what you need to do is to open an Enhancement task in Tasks
web and start coding and check in to SVN
using this ItemXXXX
: as the prefix of your check in messages.
I am putting this proposal as accepted to get it out of the queue.
- 09 Jun 2009