Page 1 of 1
Major update of MAIW functionality at The Owl's Nest
Posted: 01 Sep 2009, 22:44
by gsnde
I have enhanced the information and functionality of the MAIW package reference drastically. Both airports and country are listed for each package (as requested many times

) .
You can sort and filter the list the same way like you can do with the
Military Aircraft Reference. You sort by clicking on the table header. You filter by entering the filter value in the yellow field above the respective column and press Enter. This way you can for example filter out all packages with Mirages or all packages containing the airport KADW.
Here you go....
Posted: 02 Sep 2009, 22:39
by gsnde
Deadly silence... Should I better revert to the old version then?

Posted: 02 Sep 2009, 23:15
by lewis
After a quick look, I find this reference tool very useful and easy to use. Will look further into it, but so far, you got a winning system. Cheers, Lewis
Posted: 03 Sep 2009, 01:46
by Joecoastie
Not "deadly silence". People are too busy looking to comment !
Thanks for the work!
Joe
Posted: 03 Sep 2009, 03:48
by Victory103
Joecoastie wrote:Not "deadly silence". People are too busy looking to comment !
Thanks for the work!
Joe
Exactly, its almost like you get "paid" to do this. Great work!
Posted: 03 Sep 2009, 05:44
by Firebird
Well I have just got around to looking at this and it works pretty well.
The only way I think that it could be improved, i.e. provide even more useful info, is if you had a column which provided a list of MAIW scenery, or scenery enhancements supplied.
Useful I think as nowhere else would you find this info, not on Robert-Jan Oosterloo's site for example.
Posted: 03 Sep 2009, 08:02
by gsnde
Firebird wrote:Well I have just got around to looking at this and it works pretty well.
The only way I think that it could be improved, i.e. provide even more useful info, is if you had a column which provided a list of MAIW scenery, or scenery enhancements supplied.
Useful I think as nowhere else would you find this info, not on Robert-Jan Oosterloo's site for example.
A good idea, Steve. I have add it to the enhancement list (the only thing I don't like is that it sounds like a lot of investigation work...

)
Easier to realize and something I will implement sooner is one suggestion out of the AIG forum. The idea is to indicate packages that are obsolete because an update has been released.
Posted: 03 Sep 2009, 11:37
by Firebird
Martin,
Maybe we shouldn't use the term 'obsolete' maybe we should use 'historic' as there are always people that like retro packages. Maybe terming them historic with a year would be better. After all every package is going to be retro sometime.
You never know in 10 years time when we have 500 packages, and a few mental breakdowns, it may prove very useful.
Posted: 03 Sep 2009, 12:04
by Garysb
Firebird wrote:
You never know in 10 years time when we have 500 packages, and a few mental breakdowns, it may prove very useful.
Will that be FSXX then or still with FS9
Gary
Posted: 03 Sep 2009, 12:49
by Firebird
If we are lucky, FS9.2

Posted: 03 Sep 2009, 14:06
by gsnde
Steve,
You are most likely right here, just let me confirm this (and you know I am very retro and still want a Beale / Kadena / Mildenhall AFB package full of Habus more than anything else

).
I was talking about such packages like
==> Elmendorf AFB Complete AI Package & Elmendorf Air Force Base Version 2.0
==> German Air Force Eurofighter Complete AI Package & German Air Force Eurofighter Update Complete AI Package
where the second packages requires the de-installation of the first one. Are you saying that from a retro perspective someone might want to have the first package and not the updated version? At least for the German Eurofighter the readme is not really detailed about what changes a user will have due to the update. And for Elmendorf it sound more like an enhancement than you would loose anything.
But anyhow, I like your suggestion better to indicate that an update is available.
Posted: 03 Sep 2009, 14:50
by Firebird
Ah a man who can see the attraction of this.
At the moment I think that you are right, for the moment I think you should stick to the v2 stuff like Langley and what you have already stated.
However obvious other candidates exist, such as the Holloman F-117 package. Maybe when we have more time and inclination we can simply amend the Docs with a Retro logo and re-title the package. That however is a discussion for another day.
Posted: 04 Sep 2009, 05:21
by Firebird
Martin,
have you noticed that your preview pic of the Grand Forks docs is just blue?
Posted: 04 Sep 2009, 08:07
by gsnde
Firebird wrote:Martin,
have you noticed that your preview pic of the Grand Forks docs is just blue?
I know

Since I am using the free WebSnapr service there is nothing I can do about it but hope for an re-index. I am looking for an alternative already.
Posted: 05 Sep 2009, 06:41
by gsnde
I have (at least temporarily disabled the websnapr connection). They seem to have some issues, because trying to fetch the previews made The Owl's Nest crawl.
Re: Major update of MAIW functionality at The Owl's Nest
Posted: 18 Jun 2011, 12:18
by gsnde
Thank you, Biggles. This is actually the third version of The Owl's Nest.