ACARS / CPDLC and VATSIM Cross the Pond
Wed, 2009-06-03 01:53 — Anonymous
I've dropped you in it Hoppie... see
http://forums.vatsim.net/viewtopic.php?f=6&t=40595&p=301542#p301542
John
I've dropped you in it Hoppie... see
http://forums.vatsim.net/viewtopic.php?f=6&t=40595&p=301542#p301542
John
Thanks John
It looks like nobody wants components, they rather redevelop everything from scratch all the time. And include another MCDU, another protocol, another website, and another simulator, all in one .dll module.
You are right, no-one wants
You are right, no-one wants components.
So make them think they are not getting components! :)
To be honest I understand that 90% of the market don't care about technical details and that modularity has advantages, they want a simple solution. The trick is to have a techincal product at the back end and then package a it to appeal to this market... in fact this was my point in PSX about allowing for addons to be managed from within the addon manager, rather than having to switch to / change focus to the other application...
I might have a look at building an installer for MSFS that bundles the broker, MCDU etc into one with default settings, as well as a scripted front end to 'manage' the apps. Manually running multiple programs is more complicated than running one - we can abstract this by automating it, so it's still doing that, but it's invisible to the end user.
This should actually be quite trivial to do now that I think about it - I know some tricks :P
Will get back to you :)
One Single App
I've had the same idea for a while, but lack the time to do it. The way I "wrap" the Tcl apps allows for pretty easy combination in one fake big application.
The major part is probably that the MCDU will never appear in the 3D flight deck of MSFS. And I fear that this is the killer. Never mind it is not practical to have to zoom in etc., people apparently want that one-big-screen experience.
J
Post new comment