QuteScoop
From X-IvAp
QuteScoop is a platform-independent FSD network status indicator like ServInfo or Gergely Kosa's Dolomynum. It works for VATSIM, IVAO and all 3rd party networks, on Windows, Mac and Linux. QuteScoop is written in C++ using the Qt4 framework and available for free under the GNU General Public License (GPL).
Contents |
Download
Release 1.0.2
Fixes a bug when displaying VATSIM data introduced by changes to the whazzup.txt content
Known Issues:
- Dock windows will disappear after you minimize and then maximize on Windows.
- You have to restart the program before new color settings become effective.
- Color choosers in Preferences set Alpha channel correctly, but do not recall them correctly from the settings
News
1.0.2: Bugfix for VATSIM
Jonas Eberle submitted a patch fixing a problem with displaying VATSIM data. This problem was introduced by some server changes that slightly altered the content of whazzup.txt in a way that QuteScoop could not understand. Thanks Jonas! --Martin 13:37, 6 June 2009 (UTC)
Release 1.0.2
1.0.2 will add the first navigation database support (see Changelog for details). The navigation database is used to display flight routes according to flight plan, which is a pretty cool feature - check the latest screenshots! Some database interaction is also on my list, it will allow you to query the database and hopefully provide a nice interface to create a flight plan. --Martin 13:11, 25 January 2009 (CET)
Spam Protection
Spambots were vandalizing this page, so I had to protect it. If you still want to edit the content, you have to sign in first. Sorry for the inconvenience.--Martin 09:51, 19 August 2008 (CEST)
Source
Source SVN repository is at https://qutescoop.svn.sourceforge.net/svnroot/qutescoop. The trunk folder will always contain the latest bleeding edge source code, which currently also is the most stable version available.
There is currently a bleeding edge branch at https://qutescoop.svn.sourceforge.net/svnroot/qutescoop/branches/jonas_stable.
If you discover a bug, let us know (patches are appreciated).
You can browse (and download tarballs) from http://qutescoop.svn.sourceforge.net/viewvc/qutescoop - thanks to SourceForge!
To compile the sources, you need a working Qt environment on your system, which you can download for free. If you are on Linux, your distribution probably has precompiled Qt development packages you can use.
You can get an easy all-in-one solution through the Qt Creator which is preconfigured and ready set-up in the Qt SDK. With the Qt Creator, open the QuteScoop.pro file and click on "run". Be careful that the comiled program goes to a location where the ./data-directory is directly beyond.
For Mac OS 10.5 change a block in in Tesselator.h:
#ifdef Q_WS_MAC
#define CALLBACK_CAST (GLvoid (*)()) instead of (GLvoid (*)(...))
#define CALLBACK_DECL GLvoid
#endif
Thanks to Stefan Söllner
To bundle the necessary framework for OSX (to distribute your compiled OSX binary) in an easy way you can use the tool provided on http://labs.trolltech.com/blogs/2007/08/23/deploying-mac-applications-without-the-hassle/
Once you have the Qt environment and the source, run qmake in the source directory (it may be necessary to use qmake-qt4, if you have both qt3 and qt4 installed), then make (or, on Windows, mingw32-make). The first will create the Makefile for your system, the second will compile the program using that Makefile.
Screenshots
Screenshots created during development:
Current Development
Changes up to now are listed in the ChangeLog.
Will be in the next release
alpha available in SVN: ./branches/jonas_stable
- Time Warp: Show predicted traffic at a given time in future » ready
- Show booked ATC positions (VATSIM) » ready
- Show "congestion rings" around airports with a certain amount of traffic » ready
- Show prefiled flights in arrival/departure lists » ready
- vroute Flightplan query. All major route databases have been contacted, vroute was the only one that replied. » ready
- Remember and recall multiple Map Positions » ready
- fix display of _FSS stations » ready
Planned features
- Flight planning using the navigation database
Backlog
The backlog is a list of planned features, ordered by importance, for the next few releases. It should give everyone an idea about what to expect when, or what should be done next. If you want to add your own features, add them to the list at the bottom of this list. Do not move entries between lists or within a list.
How to request a feature: If you miss something in the program, add it to the list below, or tell me personally. The list is roughly ordered by priority, but priorities change. When you add an entry, add it at the spot where you think it fits best (the higher the priority, the more to the top it goes).
- Increase text rendering performance
- the location point of the flight can be hidden by the text label
- allow for an easy way to transfer preferences to a second setup
- allow to switch to flat (non-globe) view for rendering performance
- METAR should be visible/accessible from the airport details window.
- [Some easy + powerful way to search for everything in the database: airports, pilots, controllers, observers, ... doesn't have to be one window for pilots, one for ATC, one for airports... could be an all-in-one interface to the database. Put the "airport window" back burner for now] -> implemented
- List of all Airports (separate window)
- Allow sorting by activity of an airport
- List of all Pilots
- List of all Controllers + Observers
- Download compressed whazzup file if available
- Some Sectors (EISN_L) still don't appear, or only as labels
[* Download network Status every now and then to update whazzup locations] -> implemented as being reloaded whenever no valid Whazzup location was found any more.
- VATSIM folk doesn't seem to be fond of ICAO codes.
- Add a way to map NY_APP to KJFK, and MICKEY_GND to KLAX
- Get rid of the NY airport
- Allow mapping many airports to the same sector
- Display all controlled airports for a controller in the controller detail window
- This may be related to above, ORD app & dep is never displayed
- Web-browser like forward/back buttons. If I click on a search result, I want to get back to where I was before
- Display icons in tables (departing, arriving, landed, en route, gnd, twr, app, ctr, obs, friend)
- Allow search for ICAO codes / names / callsigns only
- User can easily turn on/off different layers of information, like Google Earth
- Add Observers to the list of visible layers, don't show them by default
- Different Colors for different ratings
[* allow remembering of multiple map-positions, recall by Key-command] -> implemented
- User can configure which labels show at which zoom level
- User can switch between color schemes
- Apply Qt Stylesheets to skin the application
- Read dolomynum color schemes
- gradually change colors of globe lines (like Dolomynum)
- Check for new data files online
[* Fade in/out display objects as user zooms around (see google earth)] -> partly implemented
- Smooth transitions from one point to another when user clicks on a map object
- Allow user to record a session of whazzup data sets into a directory
- Time-compressed playback of whazzup data from a directory
Missing Features from the Dolomynum Companion, not sorted yet:
- List of all Supervisors
- Implement a way to calculate distance between two points on the map, or between two objects (visually?)
- Show who is in the visibility range of any object (who did just see me mess up that landing?)
- Show METAR, SHORTTAF, TAF for any airport/wx station
Long Term Ideas
- Navigation data
- Flight route planning
Impressum
Author: Martin Domig (martin@domig.net)
Developper: Jonas Eberle (jonas.eberle@gmx.net)
