Thanks for this sweet module,
I am exporting my views tabular results through feed displays as excel file, successfully using the following module:
http://drupal.org/project/views_export_xls
From an excel point of view, what matters is the unique coloring of rows based on certain data content rulez.
Here come a handy module "Views Table highlighter", it does a great job within the drupal site itself, but falls short when I would like to export to excel maintaining the same themed rows.
This shortage is because of two reasons:
1) the table highlighter classes do not show up in the exported excel file
2) No CSS style sheet is even externally referenced from within the exported excel file (which is actually a normal html ascii file)
But, your module shines here, because:
1) Looking into the exported excel file, I could see the "Class=odd" or "Class=even".
You see what i mean, you are almost there.
Only few doable inches are left behind before making exporting themed tables into excel a reality.
Hope we hear a good news soon.
With Regards
Comments
Comment #1
deviantintegral commentedInteresting problem, but I'm not sure this module is actually responsible for what you're seeing. Does the exported view data somehow get run through an input filter?
Comment #2
bakr commentedYou pointed the the right logical problem.
There exists no correlation between the two Views Displays (Page & Feed) as such the color filtering will not be equally handled through both displays.
I am cross-linking this subject under the Excel Export Module to thrive discussion.
With Regards
Bakr
Comment #3
deviantintegral commentedSo, if you use a Page display, the output is being filtered? Not really a bad thing, just... unexpected. Where would you select the input filter for the display output?
Comment #4
bakr commentedI was wondering that no extra effort to be done on the view module, it is more of a better integration issue between already exising modules
- Views
- Table Highlighter
- Excel Exporter (of a highlted and color table)
But rather, an extra code to handle (re-laying) the filteration of the tabular html output so as to inject the necessary css classes into the excel-exportable feed display.
That is the thought in the first place.
Comment #5
deviantintegral commented