Items tree list organization

[Wapu Kashuken]

I know the way eve presents its items database, but would it be hard to redo the tree locally in evanova such that it branches like the in-game market.

Just a thought since that's what people are accustomed to. I understand it will most likely take a while to accomplish.

[Evanova Android]

A tree view like we are used to from Eve or other OS isn't an applicable UI Pattern on Android. First. because of device sizes and because it is not a great workflow (Android design language is usually for less clutter on screen). The recommended approache is using the "ExpandableListView" like in the assets.

The item categories could show groups as drop-down views, but then we will need to load a new screen for those groups with drop-downs anyway. I am not sure it would be great to use because of the amount of scrolling that it may require.

And yes, it would require quite some changes which I am not really willing to. I will park this idea for the future.

[Wapu Kashuken]

Perhaps a mis-communication on my end. I mentioned tree, you said "ExpandableListView".

What I'm refering to is essentially the same since your current items catalog is a nested ExpandableListView. I didn't mean to suggest a change in the storage (tree vs. ExpandableListView) but rather the hierarchical organization such that the nested ExpandableListView is organized like the in-game market.

I know that this would require more coding on your part as most if not all containers would be manually mapped (unless there is a CCP provided list already in market hierarchy).

My primary example that provides the justification for this is go find "Plex". We know where it is in the market, but in the general items list it is under accessories. Likewise, many other items are not in places we are used to finding them. This is most likely CCPs fault in the way they make their data available out of game, but in game people utilize the market to search for items/info.

Anywho, food for thought if you get the time in a future release.

[Evanova Android]

I see what you mean.

The CCP datadump slices the item in categories ("Drone", "Module"), then groups ("Electronic Warfare Drone", "Fighter Drone", ...) then types ("DragonFly", "Einherji", ...)

The Evanova database picks up the "item" categores, types, etc. not the "market groups" and such, displaying items using that specific model.

Not using the market group is likely what causes what is described here.