You are viewing a single comment's thread from:

RE: Developers Take Heed

in #busy6 years ago (edited)

Yeah, I'd find that annoying as well. It sounds like sloppy coding to me. Anything that can be changed by a user should reference a data file that holds user preferences. Then it will get stored - in Windows - in the user's appdata folder. Then the GUI can change the file contents for a different background and run some backgroundRefresh() function.

I'm sure they'll get there once they get further along, but they're probably focusing more on stability.

Sort:  

#readaboutitbeforewritingaboutit
#webnotwindows
Just watched the dlux intro video, and it looks really cool! Still though, there were some things that looked like they should have been included in the interface, like - as you pointed out - a drop-down menu for the background theme with an option for a write-in as well.
Text was moved around, and he had to transcribe the coordinates? An "apply to code" button would be great there.

Still though, I'm sure these changes will come. It takes a genius to write code for idiots, so @dlux-io has to entice more code geniuses into the project before it'll be well polished enough for mainstream use.

Looking forward to trying it out though and seeing where the project goes.

Thanks @taskmaster4450 for sharing info about this dapp.

If you look through our history we're just developing this platform out in the open hoping anybody who wants to use it and make it better can do so for everybody!

Which is also one of the cool parts of these collaborative IDEs -> when I copied and pasted code from somewhere else it just stays there for other people to build on. Of course this can get significantly cleaner... but we're still wondering how people will use it.

Taken from the "Help Wanted" of our web based IDE's

The Aframe inspector which can be accessed with Ctrl+alt+i flushes elements to the dom whenever a user modifies an attribute. An event listener could intercept these and place the results into the glitch editor for permanence. This function can live on build.html. And would instantly open development to non-coders.

Using the above paradigm incorporate programs like A-Painter and Google Blocks in to the IDE to further abstract the creative process.

Build a droplet on menu.html that uploads the asset to IPFS, and places an appropriate <img, video, a-asset-item/ src reference> tag in <assets for the user to build with the aframe inspector

If you build these or anything useful please inform us on steemit.com/@dlux-io or on discord.gg/Beeb38j - SMT tokens are available for contributors

Coin Marketplace

STEEM 0.29
TRX 0.11
JST 0.031
BTC 70287.75
ETH 3955.76
USDT 1.00
SBD 3.66