https://linen.dev logo
Join Discord
Powered by
# ceramic
  • a
    a user might add the file extension
  • a
    do you think it would be wise to just quietly remove that if a someone does add it?
  • b
    personally, i think i would try and allow a few different options... is there a "list" or something similar on 
    ceramic.App.app.scenes.main.assets
  • a
    none that is publicly available, but might be private
  • b
    just spit-balling, but it might be nice to allow: 
    HAXEUI_CORE__CHECK_BLUE
    , 
    /haxeui-core/check-blue.png
    , 
    /root/assets/haxeui-core/check-blue.png
    (with and without .png)... but i dont know how much effort any of that is, if there is no list it could be a pain since it might not be easy (or performant) to check "all the things"
  • a
    ohh, it's static!
  • a
    and its a map
  • a
    so easy to just to call 
    exists
  • a
    I can scan the key and the path with extension it seems
  • b
    cool - then i would decide on one format "you think is right" (or more likely to be used), but allow for other formats... i mean, thats how i would go about it anyway 🙂
  • a
    I don't think 
    HAXEUI_CORE__CHECK_BLUE
    would be that intuitive
  • b
    i tend to agree, even though its the more "ceramic" one
  • a
    whereas haxeui's "standard" is pretty much filepaths
  • a
    so a user may default to 
    assets/folder/image.png
  • b
    or by the looks of it just 
    folder/image
  • a
    which would be wrong, but, I guess i could check if a user entered assets manually
  • a
    or add the proper way to a readme
  • b
    yeah, i would personally allow for a few different combinations, is seems easy enough to check since its a map... but well, its all up to you ofc 🙂
  • a
    I think i'll stick to the ceramic key, cause i'd like to add the ceramic filepath method as well anyway
  • a
    what i should be able to do though, is if a user is scanning the assets directory, just do a once over the asset list and make sure they're not trying to double load the same file
  • b
    @ambitious-knife-25690 I think you should accept an 
    Assets
    object as parameter when you init a haxe ui hierarchy
  • b
    So the user has control whether the assets objects comes from a scene, a custom assets object, the global App.assets etc...
  • b
    nice idea... you could always default to that main one if its not specified... fyi, this could be an option in ToolkitOptions
  • b
    (which is used in Toolkit.init)
  • b
  • b
    (from haxeui-kha)
  • b
  • a
    ooo good idea, i'll do that inplace of my "internal" assets object idea
  • a
    Follow up question, is there a way to handle loading?
  • a
    I'm a bit confused by the loading setup
1...818283...124Latest