Hi Dark,

Obviously, I don't know  much more than you at this point about their
objectives, goals, or programming skills, but I did have some of the
same concerns. I know firsthand that supporting more than one platform
and device is pretty complicated, down right painful, for even a
skilled developer so in that sense they cast their net too wide. There
is no realistic way for them to support every PC, smartphone, tablet,
and other devices on the market, and they probably should have stuck
to the most popular ones and left Blackberry and a couple of others
go. There isn't much of a market there for blind users, and the
accessibility isn't all that great for the platform to bother with it.
I would say even smaller than the blind Linux community.

However, that is drifting away from the point. The basic point here is
they have not made it known what languages, toolkits, etc they plan to
use so even if they wanted to they might not be able to support
certain platforms or multiple platforms anyway. No matter what
language, toolkits, etc they do decide upon there is pros and cons
with all of them, and there is no one-size fits all solution. I get
the feeling they are casting their net pretty wide because they know
very little to nothing about the audio game community, and what
devices, operating systems,
and technologies we use.



On 10/10/14, dark <[email protected]> wrote:
> Hi Tom.
>
> Good point about the operating systems, though in their defense sinse they
> were listing operating systems for phones such as blackberry which I don't
> believe are the least accessible, I suspect they don't know much about vi
> access to operating systems and that linux would even be an option. This
> does however raise a more worrying question, sinse as you've said yourself
> writing games for different os frequently means different code, different
> libraries and components and what not, so given that they've listed all
> these different operating systems some of which might or might not be
> accessible, what are their coding skills actually in?
>
>
> I suppose they could be doing something like writing the game in something
> very cross platform like Python, but even then it would need adapting for
> different opterating systems.
>
> Again, I'd be much happier if these people either came and asked the
> community directly, or at least just made a general enough form to let
> people express actual opinions rather than tick boxes and give one word
> answers.
>
> aZagreus sits inside your head,
> Zagreus lives among the dead,
> Zagreus sees you in your bed,
> And eats you when you're sleeping.
>
> Zagreus at the end of days,
> Zagreus lies all other ways,
> Zagreus comes when time's a maze,
> And all of history's weeping.
>
> Zagreus taking time apart.,
> Zagreus fears the hero heart,
> Zagreus seeks the final part,
> The reward that he is reaping.
>
> Zagreus sings when all is lost,
> Zagreus takes all those he's crossed,
> Zagreus wins and all is cost,
> The hero's hearts he's keeping.
>
> Zagreus seeks the hero's ship,
> Zagreus needs the web to rip,
> Zagreus sups time at a drip,
> And life aside, he's sweeping.
> ll the best,
>
> dark.
>
>
> ---
> Gamers mailing list __ [email protected]
> If you want to leave the list, send E-mail to
> [email protected].
> You can make changes or update your subscription via the web, at
> http://audyssey.org/mailman/listinfo/gamers_audyssey.org.
> All messages are archived and can be searched and read at
> http://www.mail-archive.com/[email protected].
> If you have any questions or concerns regarding the management of the list,
> please send E-mail to [email protected].
>

---
Gamers mailing list __ [email protected]
If you want to leave the list, send E-mail to [email protected].
You can make changes or update your subscription via the web, at
http://audyssey.org/mailman/listinfo/gamers_audyssey.org.
All messages are archived and can be searched and read at
http://www.mail-archive.com/[email protected].
If you have any questions or concerns regarding the management of the list,
please send E-mail to [email protected].

Reply via email to