Keybindings database

The database for all apps sounds fine, but as someone said: can go out of

What about creating a team to define the alias and descriptions?

When a coder needs a new alias, he ask the team. The team solves the
petition by defining a new alias or choosing an old (I hope that coders will
search first, so answers of this kind are scarce) or saying that alias must
be local only. This way the database grows, but not insanelly.

While the resolution is taken, the coder waits or uses a temporary alias.


[Uummm, a team that non 100% coders can handle]


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]