Possible Update
I want to gauge users of this plugin on an update I would like to work on if it is voted as something useful to users. This update would be a large leap in the functionality of this plugin and an overhaul entirely.
What is the current Drop Shadow problem?
Right now, this plugin only supports squared corners and very specific elevation levels. While this can be very useful for those specific use-cases. Roblox has since introduced rounded corners to UIs which completely makes this plugin obsolete once implemented.
What my plan is
While I am aware this plugin has not been updated in a VERY long time, I am also aware (that for some reason) there is an active user base and many users are adding it to their studio every single day.
Due to technical challenges within Roblox I have crafted a very specific plan to implement a feature such as this. In order to accommodate this I would develop a web-service that would receive a request for each drop-shadow (elevation, corner radius, …) and that web service would then handle a 9-slice image generation and utilize OpenCloud API to upload the asset to the catalog and return the assetID (there would also be a cache of previously generated IDs that would be stored in a database so as more users utilize this with different parameters the more there are available)
Would you be interested in this update?
- Yes
- No
0 voters
If you voted YES to the above poll I have another question about a possible technical challenge with my implementation idea. There are two versions of this web-service I am considering, the best idea for me would be the single bot account that handles the assets, however this brings up a challenge with moderation as if you are the first user to generate a specific elevation and radius pairing then you would receive an asset not yer approved meaning you would not be able to see the shadow for a specific time-period.
So my other idea of an implementation would be to utilize OAuth for this application that would allow you to sign in and the web-service would directly upload the assets to your account rather than a bot account. Of course this will bring in concerns for account security, and concerns of asset moderation to your account, in which it would be highly unlikely. (I am also unaware if there are any TOS violations in something like this, which there might, in this case this option would be unable to be implemented)
Anyways, please vote on which implementation you’d be interested in most
- Third-Party Bot Account Handling Assets
- Each User Handling Assets via OAuth
0 voters