[enen92]

Top job as usual.I've been trying to get people to contribute...let's see if the user base increases.

Something fundamental to an addon is the navigation. Having a lot of dialogs means "nothing" if we have no way of integrating that on a logical interface. That being said, I think that appart from teams, effort should be put into leagues. By clicking on a league the only information we can have now is the list of teams that belong to that league.
IMHO a central dialog for a league is imperative. From there we can then navigate to team views, fixtures, league tables, etc.
So similar to teams, the leagues should also present the next and recent matches, league tables and fixtures.

So the navigation (priority) is something like:

Sport -> League/Country -> Teams/Fixtures/next matches/tables -> Players/stadium/etc

json rpc should be able to handle the following options:

-> db_get_sports -> returns sport
-> db_get_leagues/competitions(sport) -> return league/league_id
-> db_get_league(id, method=none) -> returns teams,next matches,previous matches
-> db_get_league(id, method=tables) -> return league table
-> db_get_league(id,method=fixture,parameter=0) -> returns next match for all teams in the league (current week fixture)
-> db_get_league(id,method=fixture,parameter=1) -> returns next fixture
-> db_get_league(id,method=fixture,parameter=-1) -> returns previous fixture

etc

There is probably also the need of a new artwork type for team members view: jersey into png format. That's the only "pretty way" you can show a list of players per team without overflooding the screen. Something like this:





At least it seems that every single user interface does something like this for player_view.
These are only suggestions I also have a bit of difficulty to idealize how the whole user interface should look like.

Cheers