On Saturday 23 September 2006 18:47, Buchanan, Stuart wrote:
> Hi All,
>
> I've written a patch to the MP code that allows text-based chat within the
> simulator.
>
> It provides the following:
> 1) Improved MP property handling. The MP code no-longer assumes all
> properties are floats. Props now turn at the correct RPM, and the MP
> message format now supports strings and integers.
> 2) MP chat. Users can type messages that are displayed to all users within
> MP range. The messages are displayed within a dialog box, and optionally
> to the screen using the current Nasal message system. This allows the
> messages to be TTS'd by festival.
>
> Currently the patch is intentionally simple. There are a couple of obvious
> enhancements that could be made once this is committed:
>
> A) Frequency specific transmissions. Currently everyone in the MP range
> hears all transmissions. It would be better to restrict users to
> transmitting/receiving on their current COM1 frequency. The source code
> requirements for this are already present in this patch (the
> /sim/multiplay/transmission-freq-hz property is exported), but the Nasal
> code is not.
>
> B) Quick-phrases. Typing while flying is not particularly efficient. A
> tree of phrases with click-to-say navigation would be easier to use.
>
> The patch is available from
> http://www.nanjika.co.uk/flightgear/chat.tar.gz
>
> We may want to increment the MP protocol version for this, but I'll leave
> that to other's discretion.
>
> As always, comments are welcome.
Nice patch!
But anyway:
You will actually double the amount of memory that is transmitted for one
property.
While it is good to be able to send different typed properties, I think we
can, with the current scheme, store the properties type in the static
property configuration where we also store the id to property path mapping.
This way we can avoid sending additional data on each property which must be
known on both sides anyway.
In the longer term, I would like to have a dynamic property path/property type
negotiation that is done at the start of a connection. That way we will build
up that currently static 'id to path' map at connection start and send only
the property values in the fast path.
Can you update your patch to avoid transmitting the type?
Greetings
Mathias
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
