QuteScoop
From X-IvAp
QuteScoop is a platform-independent status indicator like ServInfo for VATSIM, IVAO and any other FSD network. It is based on Gergely Kosa's Dolomynum, but written in C++ using the Qt4 framework - it runs on Windows, Mac and Linux.
Contents |
Download
Release 1.0.0
- QuteScoop 1.0.0 for Windows | Mirror
- QuteScoop 1.0.0 for Mac | Mirror (Universal Binary)
- Linux:
- QuteScoop 1.0.0 for Linux | Mirror (Debian/Ubuntu package)
- Data package (required) | Mirror (Debian/Ubuntu package)
- (with Ubuntu Gutsy Gibbon (7.10) first install the data pacakage, second the main program. Otherwise the installation of the main program is not possible)
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.
News
Release 1.0.0
It took a bit longer than expected, but a lot of minor issues were ironed out for the now available Release 1.0.0 version. Unfortunately it is not possible to include VATSIM voice support, due to licensing restrictions on the side of VATSIM. There also are some known issues with this version (see above), but all in all I think the current source code is worth being released as 1.0.0 before new year's eve. Linux packages (.deb format) will be available soon. --85.127.144.235 12:59, 29 December 2007 (CET)
Download
Source
You can download a current tarball with the sources here: QuteScoop Source Code
Source SVN repository is at http://gaia.linuxpunk.org/qutescoop. The trunk folder will always contain the latest bleeding edge source code, which currently also is the most stable version available. If you discover a bug, let me know (patches are appreciated).
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.
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.
Binaries (Development snapshots)
- QuteScoop for Windows | Mirror (Version 1.0.1)
- QuteScoop for Mac | Mirror (Universal Binary, Version 1.0.1)
Screenshots
Screenshots created during development:
Current Development
ChangeLog
Changes up to now are listed in the ChangeLog.
1.0.1
- Fixed a crash bug with user defined network that provide little data in whazzup.txt (MCDU in this case)
Planned after release
- Flight plan plotting according to planned route
- Include X-Plane navigation database
- Provide some interface to the database (allow search, do not search that database from the search dock)
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
- 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
- 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
- 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
- User can configure which labels show at which zoom level
- User can switch between color schemes
- Read dolomynum color schemes
- gradually change colors of globe lines (like Dolomynum)
- Support reading of IvAe data
- Check for new data files online
- Fade in/out display objects as user zooms around (see google earth)
- 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
- Show FIR boundaries even if controller is offline
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
- 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)
