Making the item link go to the market details instead of the normal show
info would greatly reduce the amount of typing needed.
As it is now I check eve-central for possible items to trade, looking them
up in the eve market browser on several price check characters to export
logs, typing in the name of the item into the search bar each time.
I.e. I go to my price check char at my destination and search, say, 5 items.
Then I log into my char at my origin station to search those same 5 items.
Navbot calculates that I should only buy 3 of those 5 items.
So I do another search to get to those 3 items and buy them. Having typed a
name of an item 13 times in total for the single trip that is represented
in this example. As you may realise, I can't copy paste the names. And as
you may also realise, the number of items to be looked up is usually double
or more than the amount as used in the example, per trip.
Having the name of the item in both the results list and the available
reports list go to market details (instead of item info) would greatly
reduce the amount of typing needed, as I will have to type in the name of
the item only once and not 2 or 3 times.
why search 3 times?:
1. search item in destination station and export log (item name entry required)
2. search item in origin station and export log (item name entry required)
3. search relevant items as calculated by navbot to buy for trade (item
name entry required)
after enhancement only 1 search needed:
1. search item in destination station and export log (item name entry required)
2. click on logged item in navbot while in origin station and export log
3. click on relevant item as calculated by navbot to directly go to market
details to buy for trade
benefits in short:
- Enhancement reduces amount of typing needed by at least 50%, thus saving
a load of time.
- Reduces name errors due to typing, less chance of unmatching logs.
- Apparently easy to program (I know of other people who changed ETF in 5
minutes to link the item to the market details), but I don't know how to do
this myself.
Original issue reported on code.google.com by MTassar...@gmail.com on 21 Apr 2010 at 7:57
Original issue reported on code.google.com by
MTassar...@gmail.comon 21 Apr 2010 at 7:57