Page 1 of 1

Automatically display .NFO attachments in internal viewer

Posted: Thu Sep 08, 2005 5:38 pm
by Sauron99
Option to automatically display .NFO, .TXT, .??? attachments using an internal text viewer similar to the internal .JPG viewer.

Posted: Tue Nov 01, 2005 8:41 pm
by Sauron99
Any interest in this proposed feature?

Posted: Tue Nov 01, 2005 9:01 pm
by Josef K
I've mentioned this before. I think at the time there were more pressing matters to attend to, though, so it's worth bringing this up again just to remind Alex in case he (hopefully) feels like incorporating this into UE.

Posted: Thu Nov 03, 2005 10:42 pm
by Bert
I also like to see a nfo viewer which views in terminal 9pt. font, and a text viewer.

Posted: Fri Nov 04, 2005 3:01 pm
by alex
if you set the right file association (open with and then check the always use the selected program... checkbox) doubleclicking the icon will open the file, e.g. an external nfo viewer.

but now yes i'm trying to work on more complex matters since smaller things i can do later in parallel.

the article view is designed for a single font right now.

Posted: Wed Nov 09, 2005 8:08 pm
by voripteth
I would to see a built-in viewer for .NFO files as well.

Posted: Wed Nov 09, 2005 9:17 pm
by Sauron99
alex wrote:if you set the right file association (open with and then check the always use the selected program... checkbox) doubleclicking the icon will open the file, e.g. an external nfo viewer.
That is what I do now. I have .NFO files associated to ultraedit and it works great but I would love to see it built in to UE so that I don't have to launch an external application each time.

Posted: Wed Nov 09, 2005 10:51 pm
by Josef K
I have .NFOs associated with DAMN NFO Viewer which has been much faster to startup since UltraEdit started using Armadillo.

The point with .NFOs, though, is that they are just text files so why not be able to display them inline? For that matter, why not be able to display .TXT files inline as well? I wouldn't be that bothered about seeing .NFOs in the most suitable font because all I'm interested in is seeing the relevant information quickly - not admiring ASCII art. Perhaps display the icon (for launching with an external app) and then the raw .NFO itself underneath inline would do for most people?

Posted: Thu Nov 10, 2005 7:27 am
by alex
maybe i'll just add an edit box to display certain types of files inline, i think the mechanism is already there, i remember MIME articles might be encoded and they are still displayed directly. either the icon won't be displayed, but when you press 'save attachments' it will save the attachment or i leave both the icon and the text. also an option would be possible to see it inline and as an icon (to switch from context menu).

i'm just now 'switching context' from the search service (the good thing it just runs and runs without any trouble, simple programs are easier to write), i want to delve a bit into the topic of more effective bug handling in principle so i have some strategy working against the odds but i'll try to add inline viewing in some small release towards v1.2

Posted: Thu Nov 10, 2005 12:11 pm
by Bert
An internal viewer just works much faster.

Now i have to double click the NFO file, a external program is launched an has to be closed when done. If i accidentely click 1 pixel outside the NFO icon, a new tab is opend first so even more clicks needed.

Opening NFO is just a very frequently used operation in newsgroups.
So just using alt-spacebar to view it directly would be the best way I guess. For TXT files the same story.

Posted: Sat Nov 12, 2005 8:10 pm
by ilias
I think this is a great idea. Very time-saving and click-saving feature.

Viewing NFOs is something that a Usenet user does all the time. I mean all the time. The easier this becomes, the better it is.

If an article just contains an .nfo file, and the user double-clicks to open the article, then he has to do another double-click to open the .nfo. Instead, UE can say "Ok, this contains *only* an .nfo and nothing else, so let's open that directly", saving the intermediate double-click.

It would save a LOT of double-clicks, believe me :) Mouse manufacturers and doctors treating carpal syndroms won't be happy--they may sue you Alex, be careful :)

Cheers.