Feat: Add link to destination base for trade routes.

[alleged-goose]

It would be a useful browsing feature, when clicking on a trade route in the Trade From tab for example, to have a link or a button somewhere that selects and displays the routes for the destination base, basically switching the current base with the destination one.

[dd84ai]

@alleged-goose this feature already exists. "Trade To" tab already fulfills this role :)

[alleged-goose]

Maybe I didn't make myself clear enough. What I wanted was a button or a link that would send me straight to the routes for the destination base, without having to type the destination manually or switch tabs or anything like that.

[dd84ai]

@alleged-goose but would be the usage case scenario when it would be useful in added in such fashion?
I have some concerns regarding such feature adding due to increased amount of data noticably (Trading routes info is super big), and needing some justification

[alleged-goose]

In my scenario we are only switching the currently selected base to another from the same list, I don't think that would have any impact. It's just a shortcut. I'll try to implement this myself.

[dd84ai]

• Lets assume data issue is not an issue.

There remains a second concern -> How to provide such feature in interface in the way that it will not be confusing to user?

[dd84ai]

We can imagine such shortcut replacing Bottom table with trade routes to destination base, but i am dubious regarding how much it will be confusing to average user. It looks over complex feature in amount of clicks and data navigation.

We have to strive to keep interface to simple one i think, in order to have complexity of interface usage at a low level

[dd84ai]

Also as another concern if button to this base destination will be in Bottom Table too and replacing bottom Table too
It creates lack of interface reliability since user can't click multiple times same thing to achieve same result (Which is present for all other possible buttons in darkstat, as we assume that person will be missclicking multiple times)
It will decrease psychological comfort of interface smoothness if implemented in this way

[dd84ai]

If u have a suggestion how to implement it (where to implement it) with accounting for User Experience to navigate it comfortably, i am all ears.
That's probably biggest breaking point for me for this feature.

[alleged-goose]

Right, so my idea was to simply include this in the right side panel, where the route path is displayed. Making the destination base there clickable. Maybe it could be made clearer by adding some extra text, to indicate that clicking on that will show the trade routes for that destination, like "Trade from this base".

[dd84ai]

ah. So you actually wish to show trade routes FROM another base wish u changed on a run.

But anyway... uh. Infocards showing route info is a huge data when used in static site generation mod.
Like... 3-6 gigabytes huge.

And this data is reused across tabs Trade From, Best Trades, Trade To, Ore Routes, Travel Routes.
To show how to move between all possible destinations
They all use The same data, so i can't add specific thing related to only one tab, it should remain usable for all three.

So... what u suggested is not implementable in this way, unless some big revamp doing, rethinking things considerably.
Which i think is not very justified for a small feature.

[alleged-goose]

I see, maybe there is a way of doing this entirely client side, but I'll have to think about it some more. Thank you for the feedback.

[dd84ai]

@alleged-goose There is also its own opposite option for simplified implementation of this feature...
Going entirely Server side, making this feature working for Live backend server only like it is used for Freelancer Discovery, or when it is used Locally.

If we make an optional switch to use of a generated on a fly infocard with those desired trade routes having embedded link to the base
Question only where you expect this feature to be seen personally? For your own local usage? At some github pages deployed version (darkstat is used for Vanilla and Freelancer Sirius Revival in this way)? Or for Freelancer Discovery?

This approach make simple implementation of your feature but it will be working only for local usage and freelancer disco then

To implement it, we just add extra Endpoint to existing http server, and letting it read infocard name incoming and generating infocard on a fly with all the desired extra stuff. Furiously fast, and no increases to RAM/data usage

[dd84ai]

Usage of this feature for Static Site Generation is not impossible, but depending on Freelancer Mod, amount of generated data will become too large to utilize Github Pages. Usable in SSG mod only for lightweight mods.

[dd84ai]

There is only one drawback to implementing such feature in such way => Increased complexity / less uniform interface.
I estimate the increased complexity will be acceptable i think 🤔
Simple endpoint, and simple if switch, and a bit changed template for Trade route infocard. I think it will be fairly low and simple enough amount of code to add this feature

Also it will be far more simple to implement than at client side, and will be more prefered method.
Client side is treated like hostile environment, adding extra javascript is a thing aimed to be avoided when we can proceed with Golang instead. Adding even 3-5x more Golang is still better than adding 1x Javascript.

with Javascript u would have struggled to modify it anyway, it is already filled with Htmx and making something not standard in it is problematic

So this path of implementation using complete Server Side will be acceptable according to quality aims of the project i think and keep things at expected level

[dd84ai]

That only leaves as concern for me user friendliness of such feature, i would prefer to gather opinions on Freelancer Discovery forum thread what they think about it before having such feature approved for implementation

I have some middle level concern of such feature being not user friendly and/or having too much narrow usage case to be wide useful.
Gathered opinions for demand of this feature will make more comfortable to accept increased complexity for such feature addition.