Hi,
RFE #701 proposes that we should replace the 'Print View' and 'Print View (with Full Texts)' with a 'Print View' Option which should print out the CSS of the page only (i.e. whatever exactly is currently displayed on the page itself).
*I had something in mind about the implementation, but am not able to figure some details. Any help in this regard would be appreciated. *
*Details of implementation:* On clicking the 'Print View' link, it will call a click-handler JQuery function which will get the HTML for the table from the current page, traverse through the HTML.
Then, make a JSON of relevant information such as SQL Query, No. of Rows, Column Heads and then arrays of values in each row *for SQL results* and information such as Table Name, Rows, Type, Collation, Size, Overhead, Comment for *db_structure.php and tbl_structure.php*.
Now, send a POST Request to a PHP file and get the $response (PMA_Response) after making a output with good-looking table and other details and the 'Print' Button.
The main problem I am facing here is that, how should I output the $response ?
I thought of a very-unlike-PMA way: Open a new tab with JS and add HTML to it as
var w = window.open();
$(w.document.body).html($html);
But here I guess there will be difficulty to use PMA_Response with its headers(and do I actually need to use PMA_Response or can I just print the $html_output recieved from PHP file).
or Can I somehow use 'target="print_view" ' and get the $response to be shown onto it ?
Also, please suggest any flaws/ possible problems that I may have missed or if you would suggest a different way.
Thanks.
Hi,
Sorry for my delayed response; it's a holiday weekend here and I was away from the internet all day yesterday.
On 5/23/15 6:29 AM, Deven Bansod wrote:
Hi,
RFE #701 proposes that we should replace the 'Print View' and 'Print View (with Full Texts)' with a 'Print View' Option which should print out the CSS of the page only (i.e. whatever exactly is currently displayed on the page itself).
/I had something in mind about the implementation, but am not able to figure some details. Any help in this regard would be appreciated. /
My first thought when I saw the initial feature request years ago was to make a print view stylesheet (such as [0])that hides the navigation frame, menu bar, etc. At the time, that wasn't a viable option because of the frameset, but with the move to a single page for display it might be possible now. I did not test whether this would actually work for us, but if it does the "Print" button can simply become a javascript function to tell the browser to print rather than opening a whole new plain-formatted page with different rendering. For me, this certainly would be the preferred method if it works.
*Details of implementation:* On clicking the 'Print View' link, it will call a click-handler JQuery function which will get the HTML for the table from the current page, traverse through the HTML.
Then, make a JSON of relevant information such as SQL Query, No. of Rows, Column Heads and then arrays of values in each row *for SQL results* and information such as Table Name, Rows, Type, Collation, Size, Overhead, Comment for *db_structure.php and tbl_structure.php*.
This seems like quite an original idea, I like it so far.
Now, send a POST Request to a PHP file and get the $response (PMA_Response) after making a output with good-looking table and other details and the 'Print' Button.
The main problem I am facing here is that, how should I output the $response ?
I thought of a very-unlike-PMA way: Open a new tab with JS and add HTML to it as
var w = window.open(); $(w.document.body).html($html);
I don't see a problem with that.
But here I guess there will be difficulty to use PMA_Response with its headers(and do I actually need to use PMA_Response or can I just print the $html_output recieved from PHP file).
For print view, avoiding PMA_Response might be okay, especially since I don't see a way to do it with the code you've proposed above.
or Can I somehow use 'target="print_view" ' and get the $response to be shown onto it ?
Hopefully someone else has some thought on this because if it's possible, I don't know off hand.
Also, please suggest any flaws/ possible problems that I may have missed or if you would suggest a different way.
I don't see any shortcomings or obstacles that you haven't already addressed; the javascript code to add HTML makes sense and so on...processing should be fast since we already have the data and are just passing it around as JSON.
I'd love if some other developer has additional thoughts, but so far it sounds pretty good to me.
Thanks.
0 - http://www.smashingmagazine.com/2011/11/24/how-to-set-up-a-print-style-sheet...
Hi, Thanks for the reply.
On Mon, May 25, 2015 at 6:31 PM, Isaac Bennetch bennetch@gmail.com wrote:
Hi,
Sorry for my delayed response; it's a holiday weekend here and I was away from the internet all day yesterday.
On 5/23/15 6:29 AM, Deven Bansod wrote:
Hi,
RFE #701 proposes that we should replace the 'Print View' and 'Print View (with Full Texts)' with a 'Print View' Option which should print out the CSS of the page only (i.e. whatever exactly is currently displayed on the page itself).
/I had something in mind about the implementation, but am not able to figure some details. Any help in this regard would be appreciated. /
My first thought when I saw the initial feature request years ago was to make a print view stylesheet (such as [0])that hides the navigation frame, menu bar, etc. At the time, that wasn't a viable option because of the frameset, but with the move to a single page for display it might be possible now. I did not test whether this would actually work for us, but if it does the "Print" button can simply become a javascript function to tell the browser to print rather than opening a whole new plain-formatted page with different rendering. For me, this certainly would be the preferred method if it works.
Thanks for the link. I will look into it and explore.
*Details of implementation:* On clicking the 'Print View' link, it will call a click-handler JQuery function which will get the HTML for the table from the current page, traverse through the HTML.
Then, make a JSON of relevant information such as SQL Query, No. of Rows, Column Heads and then arrays of values in each row *for SQL results* and information such as Table Name, Rows, Type, Collation, Size, Overhead, Comment for *db_structure.php and tbl_structure.php*.
This seems like quite an original idea, I like it so far.
Now, send a POST Request to a PHP file and get the $response (PMA_Response) after making a output with good-looking table and other details and the 'Print' Button.
The main problem I am facing here is that, how should I output the $response ?
I thought of a very-unlike-PMA way: Open a new tab with JS and add HTML to it as
var w = window.open(); $(w.document.body).html($html);I don't see a problem with that.
But here I guess there will be difficulty to use PMA_Response with its headers(and do I actually need to use PMA_Response or can I just print the $html_output recieved from PHP file).
For print view, avoiding PMA_Response might be okay, especially since I don't see a way to do it with the code you've proposed above.
or Can I somehow use 'target="print_view" ' and get the $response to be shown onto it ?
Hopefully someone else has some thought on this because if it's possible, I don't know off hand.
Also, please suggest any flaws/ possible problems that I may have missed or if you would suggest a different way.
I don't see any shortcomings or obstacles that you haven't already addressed; the javascript code to add HTML makes sense and so on...processing should be fast since we already have the data and are just passing it around as JSON.
I'd love if some other developer has additional thoughts, but so far it sounds pretty good to me.
Thanks for your insight. I have worked out a few things on this lines, will submit a pull request soon and then you can review it.
I am currently using target attribute of form tag. It is deprecated in HTML4 but is re-introduced in HTML5. Till now working fine. Will update you in the PR.
Thanks.
0 -
http://www.smashingmagazine.com/2011/11/24/how-to-set-up-a-print-style-sheet...
One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi Deven,
On 5/25/15 11:25 AM, Deven Bansod wrote:
Hi, Thanks for the reply.
On Mon, May 25, 2015 at 6:31 PM, Isaac Bennetch <bennetch@gmail.com mailto:bennetch@gmail.com> wrote:
> > /I had something in mind about the implementation, but am not able to > figure some details. Any help in this regard would be appreciated. / My first thought when I saw the initial feature request years ago was to make a print view stylesheet (such as [0])that hides the navigation frame, menu bar, etc. At the time, that wasn't a viable option because of the frameset, but with the move to a single page for display it might be possible now. I did not test whether this would actually work for us, but if it does the "Print" button can simply become a javascript function to tell the browser to print rather than opening a whole new plain-formatted page with different rendering. For me, this certainly would be the preferred method if it works.Thanks for the link. I will look into it and explore.
I take it the pure CSS solution didn't work out for you?
Hi Isaac,
On Wed, May 27, 2015 at 5:01 PM, Isaac Bennetch bennetch@gmail.com wrote:
Hi Deven,
On 5/25/15 11:25 AM, Deven Bansod wrote:
Hi, Thanks for the reply.
On Mon, May 25, 2015 at 6:31 PM, Isaac Bennetch <bennetch@gmail.com mailto:bennetch@gmail.com> wrote:
> > /I had something in mind about the implementation, but am not ableto
> figure some details. Any help in this regard would be appreciated./
My first thought when I saw the initial feature request years agowas to
make a print view stylesheet (such as [0])that hides the navigation frame, menu bar, etc. At the time, that wasn't a viable optionbecause
of the frameset, but with the move to a single page for display itmight
be possible now. I did not test whether this would actually work forus,
but if it does the "Print" button can simply become a javascript function to tell the browser to print rather than opening a whole new plain-formatted page with different rendering. For me, this certainly would be the preferred method if it works.Thanks for the link. I will look into it and explore.
I take it the pure CSS solution didn't work out for you?
I would be incorrect if I said, I tried it out completely. But the problem is for printing a specific stylesheet, I would have to do a lot of changes(not that I am scared to do so).
The thing is one would get a print out like the one attached with just few lines of JQuery code i.e. making navigation, floating menubar and other extra things as 'display:none'. Example with just 4-5 changes to 'display:none' is attached (done manually).
But the proper print of #tablelistcontainer would require some work because we would have to skip over the action links (ex. Browse, Structure etc.); Shift the page_content towards center of page and try to accommodate all columns
So, since I had already started out on the method I mentioned in my first mail on this thread I thought let's go forward with it and if it does not work out, I will work over the stylesheet method.
I have submitted a PR[0] with that method, if it seems unsatisfactory, I will try and work over this.
Also, I have expressed a doubt regarding the tbl_printview.php working for mult_submits on the ticket[1].
Any suggestions/ comments over the PR and the doubt in [1] will be very helpful.
Thanks.
[0] : https://github.com/phpmyadmin/phpmyadmin/pull/1697 [1] : http://sourceforge.net/p/phpmyadmin/feature-requests/701/#93d7%E2%80%8B
------------------------------------------------------------------------------
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
On May 27, 2015, at 9:18 AM, Deven Bansod devenbansod.bits@gmail.com wrote:
Hi Isaac,
On Wed, May 27, 2015 at 5:01 PM, Isaac Bennetch bennetch@gmail.com wrote: Hi Deven,
On 5/25/15 11:25 AM, Deven Bansod wrote:
Hi, Thanks for the reply.
On Mon, May 25, 2015 at 6:31 PM, Isaac Bennetch <bennetch@gmail.com mailto:bennetch@gmail.com> wrote:
> > /I had something in mind about the implementation, but am not able to > figure some details. Any help in this regard would be appreciated. / My first thought when I saw the initial feature request years ago was to make a print view stylesheet (such as [0])that hides the navigation frame, menu bar, etc. At the time, that wasn't a viable option because of the frameset, but with the move to a single page for display it might be possible now. I did not test whether this would actually work for us, but if it does the "Print" button can simply become a javascript function to tell the browser to print rather than opening a whole new plain-formatted page with different rendering. For me, this certainly would be the preferred method if it works.Thanks for the link. I will look into it and explore.
I take it the pure CSS solution didn't work out for you?
I would be incorrect if I said, I tried it out completely. But the problem is for printing a specific stylesheet, I would have to do a lot of changes(not that I am scared to do so).
The thing is one would get a print out like the one attached with just few lines of JQuery code i.e. making navigation, floating menubar and other extra things as 'display:none'. Example with just 4-5 changes to 'display:none' is attached (done manually).
I see.
But the proper print of #tablelistcontainer would require some work because we would have to skip over the action links (ex. Browse, Structure etc.); Shift the page_content towards center of page and try to accommodate all columns
So, since I had already started out on the method I mentioned in my first mail on this thread I thought let's go forward with it and if it does not work out, I will work over the stylesheet method.
I understand.
I have submitted a PR[0] with that method, if it seems unsatisfactory, I will try and work over this.
Also, I have expressed a doubt regarding the tbl_printview.php working for mult_submits on the ticket[1].
Handling of this complexity is one of the things that made me reconsider.
Any suggestions/ comments over the PR and the doubt in [1] will be very helpful.
I would like to do some tests before making a decision and having more information to guide you further. I'll work on that in the morning as its bed time here now. In the mean time if you need a task you could of course begin planning or work on your next item or any maintenance you feel is needed on the already submitted ones.
Since you are ahead of your schedule at the moment I don't think this should be a problem at all to have some delay on this task.
Thanks.
[0] : https://github.com/phpmyadmin/phpmyadmin/pull/1697 [1] : http://sourceforge.net/p/phpmyadmin/feature-requests/701/#93d7%E2%80%8B
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-- Regards, Deven Bansod
<localhost _ localhost _ aaa _ phpMyAdmin 4.5.pdf>
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Re-sending the message w/o the attached pdf, because last message was caught in moderation because of its size.
Hi Isaac,
On Wed, May 27, 2015 at 5:01 PM, Isaac Bennetch bennetch@gmail.com wrote:
Hi Deven,
On 5/25/15 11:25 AM, Deven Bansod wrote:
Hi, Thanks for the reply.
On Mon, May 25, 2015 at 6:31 PM, Isaac Bennetch <bennetch@gmail.com mailto:bennetch@gmail.com> wrote:
> > /I had something in mind about the implementation, but am not ableto
> figure some details. Any help in this regard would be appreciated./
My first thought when I saw the initial feature request years agowas to
make a print view stylesheet (such as [0])that hides the navigation frame, menu bar, etc. At the time, that wasn't a viable optionbecause
of the frameset, but with the move to a single page for display itmight
be possible now. I did not test whether this would actually work forus,
but if it does the "Print" button can simply become a javascript function to tell the browser to print rather than opening a whole new plain-formatted page with different rendering. For me, this certainly would be the preferred method if it works.Thanks for the link. I will look into it and explore.
I take it the pure CSS solution didn't work out for you?
I would be incorrect if I said, I tried it out completely. But the problem is for printing a specific stylesheet, I would have to do a lot of changes(not that I am scared to do so).
The thing is one would get a print out like the one attached with just few lines of JQuery code i.e. making navigation, floating menubar and other extra things as 'display:none'. Example with just 4-5 changes to 'display:none' is attached (done manually).
But the proper print of #tablelistcontainer would require some work because we would have to skip over the action links (ex. Browse, Structure etc.); Shift the page_content towards center of page and try to accommodate all columns
So, since I had already started out on the method I mentioned in my first mail on this thread I thought let's go forward with it and if it does not work out, I will work over the stylesheet method.
I have submitted a PR[0] with that method, if it seems unsatisfactory, I will try and work over this.
Also, I have expressed a doubt regarding the tbl_printview.php working for mult_submits on the ticket[1].
Any suggestions/ comments over the PR and the doubt in [1] will be very helpful.
Thanks.
[0] : https://github.com/phpmyadmin/phpmyadmin/pull/1697 [1] : http://sourceforge.net/p/phpmyadmin/feature-requests/701/#93d7%E2%80%8B%E2%8...
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi Deven,
On 5/25/15 11:25 AM, Deven Bansod wrote:
Hi, Thanks for the reply.
On Mon, May 25, 2015 at 6:31 PM, Isaac Bennetch <bennetch@gmail.com mailto:bennetch@gmail.com> wrote:
Hi, Sorry for my delayed response; it's a holiday weekend here and I was away from the internet all day yesterday. On 5/23/15 6:29 AM, Deven Bansod wrote: > Hi, > > RFE #701 proposes that we should replace the 'Print View' and 'Print > View (with Full Texts)' with a 'Print View' Option which should print > out the CSS of the page only (i.e. whatever exactly is currently > displayed on the page itself). > > /I had something in mind about the implementation, but am not able to > figure some details. Any help in this regard would be appreciated. / My first thought when I saw the initial feature request years ago was to make a print view stylesheet (such as [0])that hides the navigation frame, menu bar, etc. At the time, that wasn't a viable option because of the frameset, but with the move to a single page for display it might be possible now. I did not test whether this would actually work for us, but if it does the "Print" button can simply become a javascript function to tell the browser to print rather than opening a whole new plain-formatted page with different rendering. For me, this certainly would be the preferred method if it works.Thanks for the link. I will look into it and explore.
I've done some exploring with the CSS solution, and thought I'd share my thoughts, although they're incomplete at this time.
I had some success so far with making the following changes to CSS (which I would expect to be reflected in a print stylesheet, which should be loaded after the other stylesheets to override any duplicated directives). There are obviously some unwanted elements remaining, but this looks like the beginnings of a decent print view.
Note that for development purposes, I like to leave the "print" stylesheet set for screen display, that way I can view what it will look like without constantly going to the print preview feature of my browser. Once it looks good on my screen, I set the stylesheet to @media print{} and check it in the actual print preview. It's not a sure thing of how it will look when rendered for printing, but helps me get close without wasting a lot of time in the print dialog.
Here are the changes I made so far:
#page_content { position: absolute; left: 0; top: 0; width: 100%; float: none; /* float:none is a work around for a Gecko-based bug when printing more than one page; see http://bugzilla.mozilla.org/show_bug.cgi?id=104040 and https://bugzilla.mozilla.org/show_bug.cgi?id=129941 -- this may actually be resolved, finally, but doesn't seem to hurt anything and old habits die hard */ }
pma_navigation { display: hidden; }
floating_menubar { display: hidden; }
pma_console_container { display: hidden;
page_nav_icons { display: hidden; }
Hi Isaac,
On Fri, May 29, 2015 at 12:11 AM, Isaac Bennetch bennetch@gmail.com wrote:
Hi Deven,
On 5/25/15 11:25 AM, Deven Bansod wrote:
Hi, Thanks for the reply.
On Mon, May 25, 2015 at 6:31 PM, Isaac Bennetch <bennetch@gmail.com mailto:bennetch@gmail.com> wrote:
Hi, Sorry for my delayed response; it's a holiday weekend here and I was away from the internet all day yesterday. On 5/23/15 6:29 AM, Deven Bansod wrote: > Hi, > > RFE #701 proposes that we should replace the 'Print View' and> View (with Full Texts)' with a 'Print View' Option which should> out the CSS of the page only (i.e. whatever exactly is currently > displayed on the page itself). > > /I had something in mind about the implementation, but am not ableto
> figure some details. Any help in this regard would be appreciated./
My first thought when I saw the initial feature request years agowas to
make a print view stylesheet (such as [0])that hides the navigation frame, menu bar, etc. At the time, that wasn't a viable optionbecause
of the frameset, but with the move to a single page for display itmight
be possible now. I did not test whether this would actually work forus,
but if it does the "Print" button can simply become a javascript function to tell the browser to print rather than opening a whole new plain-formatted page with different rendering. For me, this certainly would be the preferred method if it works.Thanks for the link. I will look into it and explore.
I've done some exploring with the CSS solution, and thought I'd share my thoughts, although they're incomplete at this time.
I had some success so far with making the following changes to CSS (which I would expect to be reflected in a print stylesheet, which should be loaded after the other stylesheets to override any duplicated directives). There are obviously some unwanted elements remaining, but this looks like the beginnings of a decent print view.
Note that for development purposes, I like to leave the "print" stylesheet set for screen display, that way I can view what it will look like without constantly going to the print preview feature of my browser. Once it looks good on my screen, I set the stylesheet to @media print{} and check it in the actual print preview. It's not a sure thing of how it will look when rendered for printing, but helps me get close without wasting a lot of time in the print dialog.
Thanks for sharing. This seems like a good strategy. I was indeed wasting a lot of time there.
Here are the changes I made so far:
#page_content { position: absolute; left: 0; top: 0; width: 100%; float: none; /* float:none is a work around for a Gecko-based bug when printing more than one page; see http://bugzilla.mozilla.org/show_bug.cgi?id=104040 and https://bugzilla.mozilla.org/show_bug.cgi?id=129941 -- this may actually be resolved, finally, but doesn't seem to hurt anything and old habits die hard */ }
pma_navigation { display: hidden; }
floating_menubar { display: hidden; }
pma_console_container { display: hidden;
page_nav_icons { display: hidden; }
Yes. I had made almost the same changes in the pdf print that I had sent on the mailing list in this thread previously except the first one.
Thanks for a great head start. I will also continue to look into it. And try to find a simpler way to not include specific elements.
I was thinking of adding a class-related css like
.print_ignore { display:none; }
into the print.css and then adding this class dynamically to these 'not-to-be-printed' elements (by may be parsing the HTML and adding class on pre-decided basis, for ex. we don't need action buttons so add this class to these <td>) while printing.
I will post an update when I get to something significant.
Thanks.
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
On 5/28/15 10:44 PM, Deven Bansod wrote:
Hi Isaac,
On Fri, May 29, 2015 at 12:11 AM, Isaac Bennetch <bennetch@gmail.com mailto:bennetch@gmail.com> wrote:
Hi Deven, On 5/25/15 11:25 AM, Deven Bansod wrote: > Hi, > > Thanks for the reply. > > On Mon, May 25, 2015 at 6:31 PM, Isaac Bennetch <bennetch@gmail.com <mailto:bennetch@gmail.com> > <mailto:bennetch@gmail.com <mailto:bennetch@gmail.com>>> wrote: > > Hi, > > Sorry for my delayed response; it's a holiday weekend here and I was > away from the internet all day yesterday. > > On 5/23/15 6:29 AM, Deven Bansod wrote: > > Hi, > > > > RFE #701 proposes that we should replace the 'Print View' and 'Print > > View (with Full Texts)' with a 'Print View' Option which should print > > out the CSS of the page only (i.e. whatever exactly is currently > > displayed on the page itself). > > > > /I had something in mind about the implementation, but am not able to > > figure some details. Any help in this regard would be appreciated. / > > My first thought when I saw the initial feature request years ago was to > make a print view stylesheet (such as [0])that hides the navigation > frame, menu bar, etc. At the time, that wasn't a viable option because > of the frameset, but with the move to a single page for display it might > be possible now. I did not test whether this would actually work for us, > but if it does the "Print" button can simply become a javascript > function to tell the browser to print rather than opening a whole new > plain-formatted page with different rendering. For me, this certainly > would be the preferred method if it works. > > > Thanks for the link. I will look into it and explore. I've done some exploring with the CSS solution, and thought I'd share my thoughts, although they're incomplete at this time. I had some success so far with making the following changes to CSS (which I would expect to be reflected in a print stylesheet, which should be loaded after the other stylesheets to override any duplicated directives). There are obviously some unwanted elements remaining, but this looks like the beginnings of a decent print view. Note that for development purposes, I like to leave the "print" stylesheet set for screen display, that way I can view what it will look like without constantly going to the print preview feature of my browser. Once it looks good on my screen, I set the stylesheet to @media print{} and check it in the actual print preview. It's not a sure thing of how it will look when rendered for printing, but helps me get close without wasting a lot of time in the print dialog.Thanks for sharing. This seems like a good strategy. I was indeed wasting a lot of time there.
It was a learning experience and an exercise in thinking of a unique solution, so not truly "wasted" time.
Here are the changes I made so far: #page_content { position: absolute; left: 0; top: 0; width: 100%; float: none; /* float:none is a work around for a Gecko-based bug when printing more than one page; see http://bugzilla.mozilla.org/show_bug.cgi?id=104040 and https://bugzilla.mozilla.org/show_bug.cgi?id=129941 -- this may actually be resolved, finally, but doesn't seem to hurt anything and old habits die hard */ } pma_navigation { display: hidden; } floating_menubar { display: hidden; } pma_console_container { display: hidden; page_nav_icons { display: hidden; }Yes. I had made almost the same changes in the pdf print that I had sent on the mailing list in this thread previously except the first one.
Indeed.
Thanks for a great head start. I will also continue to look into it. And try to find a simpler way to not include specific elements.
I was thinking of adding a class-related css like
.print_ignore { display:none; }
into the print.css and then adding this class dynamically to these 'not-to-be-printed' elements (by may be parsing the HTML and adding class on pre-decided basis, for ex. we don't need action buttons so add this class to these <td>) while printing.
I don't think it will be needed to do this on a dynamic basis, since the @media print stylesheet will only affect the printing we can give any undesirable sections the appropriate class or style definition as part of the HTML when the page loads rather than adding it dynamically.
I'm eager to see what you come up with!
I will post an update when I get to something significant.
Thanks.
------------------------------------------------------------------------------ _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net <mailto:Phpmyadmin-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel-- Regards, Deven Bansod ** *mailto:f2012316@pilani.bits-pilani.ac.in*
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-
Deven Bansod -
Isaac Bennetch