ab0d133294
**About the pull request** Radial menu's replaced with TGUI window for all plumbing RCD's https://user-images.githubusercontent.com/110812394/204481973-8f6d62c0-9288-4165-bce7-ee8bfec95bee.mp4 **Why it's good for the game** **1. Faster Navigation** - Old System: It had 3 radial menus' ->To select type of device to build ->To select the colour of fluid ducts ->To select the layer of devices 3 menus for one system makes navigation between them annoying for e.g.: to create a red fluid duct of layer 5 you have to open all these 3 menus & cycling through the radial menu by clicking the next button is time consuming when you have a large number of items - New System: with just one window open it's as simple as 3 clicks and your done just like the RPD **2. Always available** - Old System: When you select an option inside a radial menu the menu closes so you have to reopen it again to change a setting - New System: open the window drag it to the side and it will always be there for you **3. Just easier for our eyes** - Old System: Moving my eyes in a circle across the menu only to find out i have to click Next and circle my eyes again honestly makes my head spin - New System: The menu options are small enough to be viewed all at once & helps me see what I need more easily **4. Consistency** Both the RPD & plumbing all have similar concepts i.e., pipes, devices, layers & colours it only makes sense they should have similar interfaces. Also categorizing the items into tabs can help with explaining what each item does **Conclusion** Just because the radial menu looks attractive shouldn't mean it must be used everywhere, it only makes sense to use it when the number of options of an item is small enough to be displayed on the screen all at once for e.g., modules in a Mod suit. If the user has to click the next button to cycle through the item's, it defeats the purpose of the radial menu and makes the user work more to find his settings **Side Note :** removed unused code in RapidPipeDispenser.js **ChangeLog** 🆑 add: plumbing constructor TGUI, just like Rapid Pipe Dispensers del: plumbing constructor radials code: categories for each item /🆑 Co-authored-by: Mothblocks <35135081+Mothblocks@users.noreply.github.com> Co-authored-by: Jeremiah <42397676+jlsnow301@users.noreply.github.com> Co-authored-by: Time-Green <timkoster1@hotmail.com>
Asset cache system
Framework for managing browser assets (javascript,css,images,etc)
This manages getting the asset to the client without doing unneeded re-sends, as well as utilizing any configured cdns.
There are two frameworks for using this system:
Asset datum:
Make a datum in asset_list_items.dm with your browser assets for your thing.
Checkout asset_list.dm for the helper subclasses
The simple subclass will most likely be of use for most cases.
Call get_asset_datum() with the type of the datum you created to get your asset cache datum
Call .send(client|usr) on that datum to send the asset to the client. Depending on the asset transport this may or may not block.
Call .get_url_mappings() to get an associated list with the urls your assets can be found at.
Manual backend:
See the documentation for /datum/asset_transport for the backend api the asset datums utilize.
The global variable SSassets.transport contains the currently configured transport.
Notes:
Because byond browse() calls use non-blocking queues, if your code uses output() (which bypasses all of these queues) to invoke javascript functions you will need to first have the javascript announce to the server it has loaded before trying to invoke js functions.
To make your code work with any CDNs configured by the server, you must make sure assets are referenced from the url returned by get_url_mappings() or by asset_transport's get_asset_url(). (TGUI also has helpers for this.) If this can not be easily done, you can bypass the cdn using legacy assets, see the simple asset datum for details.
CSS files that use url() can be made to use the CDN without needing to rewrite all url() calls in code by using the namespaced helper datum. See the documentation for /datum/asset/simple/namespaced for details.