Community
Participate
Working Groups
I understand this isn't a very environmentally friendly request, but some of us still do code reviews the old fashioned way. Printing a large number of files from within Eclipse is not a happy task. If you want to print a file, you must open it, and request it be printed (usually using Ctrl-P). We should be able to support printing of files without having to open them. What I would love to be able to do is to select a large number of resources (not just simple files projects & folders too) and hit print. That would queue up a massive print job that printed all of the files I had selected recursively searching the folders for more to print. In a perfect world, a registered editor would handle the printing for a given resource. This would allow content specific printing/formatting.
This is an interesting idea that will be deferred until development resources become available to consider this enhancement.
Reopen for investigation
This feature could be implemented by the community.
*** Bug 8017 has been marked as a duplicate of this bug. ***
Reassigning to Nick since he is taking ownership of Navigator
*** Bug 87470 has been marked as a duplicate of this bug. ***
*** Bug 15510 has been marked as a duplicate of this bug. ***
Dani, I don't think this bug belongs with Navigator (or CommonNavigator) as it requires underlying print support to format and print files that may not be associated with editors. And as far as I know that does not exist anywhere. I would guess the best place for that is something like Platform Text. Certainly the part of hooking the print mechanism up to the CN is a part of this, but that part is done in the patch to bug 15510. So I'm going to give this to Text for now, and if that's not the right place then you can move it somewhere else (except back to Navigator/CNF).
>So I'm going to give this to Text It doesn't belong to text as the selected file might be a diagram, image or something else. There needs to be a print action in Platform (UI) that can be extended by clients (e.g. depending on the content type).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
