# ceramic
- a
ambitious-knife-25690
02/27/2023, 1:34 PMahh, i'm referring to if a user does something like
or maybe even a web urlfile://C... - b
bright-gpu-74537
02/27/2023, 1:34 PM - a
ambitious-knife-25690
02/27/2023, 1:34 PMi think for these cases it makes sense to load the image - b
bright-gpu-74537
02/27/2023, 1:34 PMfile:// will use imageFromBytes, so will http:// - b
bright-gpu-74537
02/27/2023, 1:35 PMdefault will attempt that method above (first internal to the framework, then from haxe resource bytes) - a
ambitious-knife-25690
02/27/2023, 1:37 PMokay. did not expect that to "just work" - b
bright-gpu-74537
02/27/2023, 1:37 PMsure, you implemented imageFromBytes... so, done... everything that uses that (like http, file) will just work - b
bright-gpu-74537
02/27/2023, 1:40 PMremember once you implement "a few" (im sure you realise its not a few 🙂 ) anchor points into haxeui-core then the rest of the framework just does its thing... its doesnt care (or know) what ceramic is... it just says "ive got some bytes can you turn that into an image", it also doesnt really know what an image is, or how to display it, thats also delegated... - b
bright-gpu-74537
02/27/2023, 1:41 PMso i guess its more like "ive got some bytes can you turn that into what you think is an image" and then later "that thing you said is an image, here it is, can you display here" - a
ambitious-knife-25690
02/27/2023, 1:41 PMi was thinking "i've gotta add this stuff to ceramic's asset obj" lol - b
bright-gpu-74537
02/27/2023, 1:42 PMnaw, bytes, something internal to the framework and "from image data" (ie, texture) - b
bright-gpu-74537
02/27/2023, 1:42 PMi think you've done all that except the last - b
bright-gpu-74537
02/27/2023, 1:42 PM
- and that should be super simple to implement for you / ceramicToolkitAssets.instance.imageInfoFromImageData - b
billowy-waiter-28954
02/27/2023, 1:43 PM@ambitious-knife-25690 Could be useful: https://github.com/ceramic-engine/ceramic-samples/blob/master/http-image/src/MainScene.hx - a
ambitious-knife-25690
02/27/2023, 1:44 PMokay, url works - a
ambitious-knife-25690
02/27/2023, 1:44 PMbut local path doesn't - b
bright-gpu-74537
02/27/2023, 1:45 PMis the file defo there? - a
ambitious-knife-25690
02/27/2023, 1:45 PMyeah - b
bright-gpu-74537
02/27/2023, 1:46 PMah, actually, i was wrong, it is a different function:Toolkit.assets.imageFromFile - b
bright-gpu-74537
02/27/2023, 1:46 PMi feel like that could be using from bytes as its default impl though - a
ambitious-knife-25690
02/27/2023, 1:46 PMahah, and for that I have a previous hacky temp solution implemented - b
bright-gpu-74537
02/27/2023, 1:47 PMim actually not really sure why that functions exists... i might drop it... ill have to check the other backends first though - b
billowy-waiter-28954
02/27/2023, 1:48 PMCopy codehaxe var bytes = ceramic.Files.getBytes('your/file/path') - a
ambitious-knife-25690
02/27/2023, 1:48 PMohhh..... - b
bright-gpu-74537
02/27/2023, 1:48 PMoh, actually the default impl does use image from bytes... its just that you overrode it - a
ambitious-knife-25690
02/27/2023, 1:48 PMi just sent
and the image didn't load anywaycallback(null) - b
bright-gpu-74537
02/27/2023, 1:49 PMCopy codehaxe public function imageFromFile(filename:String, callback:ImageInfo->Void) { #if sys if (isAbsolutePath(filename) == false) { var parts = haxe.io.Path.normalize(Sys.programPath()).split("/"); parts.pop(); filename = parts.join("/") + "/" + filename; } filename = haxe.io.Path.normalize(filename); if (sys.FileSystem.exists(filename) == false) { callback(null); } try { Toolkit.assets.imageFromBytes(sys.io.File.getBytes(filename), callback); } catch (e:Dynamic) { trace("Problem loading image file: " + e); callback(null); } #else trace('WARNING: cant load from file system on non-sys targets [${filename}]'); callback(null); #end } - b
bright-gpu-74537
02/27/2023, 1:49 PMwell, you still overrode that default impl in the AssetsBase class - a
ambitious-knife-25690
02/27/2023, 1:49 PMoohh it's implemented by default?