| Content of these pages are owned and copyrighted by the poster. | |
| Hosted by: |
|
NOTE: This project is currently pretty stale, although there's nothing saying I won't start working on it again when I find the time. -- PeterSchuller (peter.schuller@infidyne.com)
JosNews is an attempt to create a pure Java & JOS USENET Newsreader. Is everyone okey with the name JosNews btw?
Here're some of the features that I had in mind for JosNews:
If you're wondering about the usefulness of support for offline operation, then believe me, when you're in the predicament of not having those US flatrates, staying online going through hundreds of articles can cost big bucks.
Anyway, I'm open to suggestions as to what to do and especially what not to do when it comes to look'n'feel etc. I have two basic suggestions as to how to design the GUI (which reminds me, do we need a TUI for a newsreader? What do you think?).
Suggestion _#1:_
The GUI could be made up of several separate windows. For example, the "main window", that pops up when you start the application, could consist of a list of servers, and a list of newsgroups and/or subscribed newsgroups on that server (those lists could possibly optionally be placed in a separate window also). By clicking on a newsgroup, a new window could pop up displaying a list of articles and an acricle-preview, with the option of opening a separate window for an article. This would be kinda like Netscape Communicator's "Collabra Discussions". Of course, thera are many variants to this.
Suggestion _#2:_
The GUI could consist of one single "main" window, ala most E-Mail UAs out there. One could have a tree view of the different servers and newsgroups, along with a separate list of subscribed newsgroups, to the left, with an article list and an article-preview split on the right. The list of servers doesn't neccessarily have to be a part of the tree either. Server could be chosen in some other manner, as you're not likely to have more than a maximum of a few servers configured.
Suggestiong 1 and 2 are pretty much alike. Suggestiong number 2, could easily be customized by allowing the user to double-click on most "stuff" to create new windows ala suggestion 1. The only difference, really, is the layout of the first, main window that pops up.
I am personally in favor of suggestion number 1 (oops, I meant *2*... Sorry --PeterSchuller)as I think it doesn't add so much "clutter" to the application. You get the feeling that everything's connected, and you don't end up with 20 separate windows...
Thoughts?
--PeterSchuller (peter.schuller@noreva.se)
--DanielHarris
--CarstenEckelmann
| Content of these pages are owned and copyrighted by the poster. | |
| Hosted by: |
|