widelands-dev team mailing list archive

[Nasenbaer <916545@xxxxxxxxxxxxxxxxxx>]

Alright.  Seems like a good idea to me as well. So what's the best way
to go? When we use asci strings, we do not need an enum...

So should I just write the documentation as "human readable" doxygen in
that protocol file, but without any c++ defines - that makes debugging
of typos harder, as no compile time check for a definition is done - or
should I add #define  IGPCMD_LOGIN "IGPCMD_LOGIN", which makes it some
how doubled and looks weired, but would ensure the gcc checking and
would even ease later changes of a command string if needed for any
reason.

What about the list for discussion?:

 LIST for discussion:
  - some messages are hardly translateable as they are generated dynamically or set during setup time
    like the motd. Others are hardcoded and thus could be translated on client side.
    Pro: users that don't understand english that well will better understand those messages
    Con: users might think they are in the channel for their language and thus might be rude to others
         not writing in their language or just be rude because other people won't answer in their
         mother tounge. JEPP, that's how people are sometimes. Unfortunally
    If we implement this, some INGCMD should just send the number for a certain message and the number will
    lead to a message in this (or a seperate) file.
  - how should the crosswork for this protocol file be done if the metaserver is not written in c/c++ ? <- already cleared up, as we use asci strings
  - what features should be accessible for superusers? I would like to have:
       * set motd
       * announcements (message that is even shown in running games in main stream)
       * kicking of rude players
       * (banning user for a certain time - not sure about that, there was no need before, but who knows?)

-- 
You received this bug notification because you are a member of Widelands
Developers, which is a bug assignee.
https://bugs.launchpad.net/bugs/916545

Title:
  About depending on GGZ packages

Status in Widelands:
  Confirmed
Status in “widelands” package in Debian:
  New

Bug description:
  I noticed a bug report in Debian which basically suggests to drop the
  GGZ packages because it is unmaintained upstreams. Since Widelands
  depends on ggz, this of course affects us there (not to mention Debian
  derivaties like Ubuntu and Linux Mint).

  I know the ggz dependency has been discussed a bit before, but we
  should probably figure out what the long-term plan is.

To manage notifications about this bug go to:
https://bugs.launchpad.net/widelands/+bug/916545/+subscriptions