Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 18:37
    ziemek99 commented #425
  • 18:29
    saschanaz commented #425
  • 18:21
    ziemek99 closed #425
  • 18:21
    ziemek99 commented #425
  • 18:21
    ziemek99 labeled #425
  • 18:16
    ziemek99 reopened #504
  • 18:16
    ziemek99 reopened #505
  • 18:16
    ziemek99 reopened #501
  • 18:15
    ziemek99 reopened #503
  • 18:07
    ziemek99 labeled #543
  • 18:07
    ziemek99 labeled #543
  • Jan 18 09:25
    ziemek99 commented #544
  • Jan 18 09:23
    ziemek99 commented #544
  • Jan 18 09:22
    ziemek99 commented #544
  • Jan 18 09:17
    ziemek99 labeled #544
  • Jan 18 08:35
    ziemek99 closed #209
  • Jan 18 08:35
    ziemek99 commented #209
  • Jan 18 08:35
    ziemek99 labeled #209
  • Jan 03 23:35
    Maniues opened #13
  • Dec 15 2021 13:11
    ziemek99 closed #481
The Jared Wilcurt
@TheJaredWilcurt
Leo Izen
@thebombzen
why do you keep calling it flif.exe
Simanto Rahman
@Simanto_Rahman_twitter
Does flif have any base API documentation that I can use to Marshall into C#?
And also, what happened to the original implementation?
C# i mean
The Jared Wilcurt
@TheJaredWilcurt
@thebombzen Differentiate between the file format/encoding, the project, the source code, and the built binary.
Node-FLIF uses a pre-built win32 .exe file for windows and flif-wasm for OSX/Linux. It use's node commands to run the executable and it converts the JavaScript Object of options that are passed in into command line arguments
Simanto Rahman
@Simanto_Rahman_twitter

Now as you're the maintainer of FLIF, I wanted to make a managed encoder decoder based on the original ones. Managed would mean its usable across the mobile, web and standalone platforms via C#

Or do you think using native binaries might be better?

Jon Sneyers
@jonsneyers
I have been working on a new image format
Pieter Wuille
@sipa
oh!
Jon Sneyers
@jonsneyers
one that would be good for @mlyle's use case
it is called FUIF
Stephan Vedder
@feliwir
fuif?
Are there any benchmarks?😄
Jon Sneyers
@jonsneyers
it's still a work in progress, I have some preliminary results of course but there's still a lot of tweaking to be done
FUIF is a bit of a pretentious name: Free Universal Image Format
it uses stuff from FLIF, but it's designed with lossy in mind
Stephan Vedder
@feliwir
Is the page down?
Jon Sneyers
@jonsneyers
yeah it looks like jpeg.org is down for some reason, anyway it's the JPEG XL call for proposals for a next-gen image format
Jon Sneyers
@jonsneyers
(it's a pretentious name, but it has a nice meaning in Dutch, and also it has the essential feature of ambiguous pronunciation)
Stephan Vedder
@feliwir
JPEG XL?
Pieter Wuille
@sipa
jonsneyers: i've given up on teaching people to pronounce the ui in my last name :)
The Jared Wilcurt
@TheJaredWilcurt
jpeg.org is back up, but that link is 404
The Jared Wilcurt
@TheJaredWilcurt
now the link is working
Stephan Vedder
@feliwir
it doesn’t mention fuif though
Stephan Vedder
@feliwir
it doesn’t go into details at all
Simanto Rahman
@Simanto_Rahman_twitter
I have been trying to get ImageSharp to include FLIF to their supported formats. Only problem is the licensing. They are using Apache2.0 and FLIF encoder is under GPLv3 I believe. As soon as the community finishes the encoder for production level use, other projects can start putting it into their framworks.
I myself am unable to utilize FLIF server side due to the same reason.
Stephan Vedder
@feliwir
Just use MIT license for FLIF
problem solved
GPL sucks😂
The Jared Wilcurt
@TheJaredWilcurt
I'm using MIT for node-flif however it ships with a copy of a built flif.exe and also uses flif-wasm which uses ISC. So I'm not sure how all that works
Zoey Riordan
@ZoeyR
Sadly the encoding-side of flif doesn't really have a specification on how the maniac tree is trained or I would be able to work on an MIT/Apache2.0 licensed encoder.
Stephan Vedder
@feliwir
I‘d totally contribute aswell to a C/C++ encoder
But i won’t contribute to GPL stuff
Zoey Riordan
@ZoeyR
Unfortunately my project is Rust so you'd be at a bit of a disadvantage.
Simanto Rahman
@Simanto_Rahman_twitter
Im still enthusiastic about managed implementations. I talked to one of the main contributors of ImageSharp and their only hiccup was the licensing. They use apache 2.0 for Image Sharp and the encoder is under full power of GNU Public License (which is definitely understandable). I personally am trying to implement the entire FLIF basics into ImageSharp just to play around with it on my personal (non-commercial) projects.
Zoey Riordan
@ZoeyR
@Simanto_Rahman_twitter yeah the licensing gets a bit interesting. If there was a formal spec for the encoding process then there wouldn't be much of an issue since you could just implement according to the spec and avoid using any of the existing code, which should allow you to license it however you want. However, since there is no spec, the code itself is the documentation so its much more of a gray area.
Simanto Rahman
@Simanto_Rahman_twitter
Well once the development process finishes, a formal Spec would do the trick wont it?
Zoey Riordan
@ZoeyR
right, although it would be nice if there was a rough spec right now for encoding, there already is for decoding.
Pieter Wuille
@sipa
generally specifications define the format, not so much the procedure for creating
because implementers are free to use whatever algorithm, as long as the result is a valid file
Zoey Riordan
@ZoeyR
I suppose, although training the maniac tree seems like a big part of the benefit of FLIF.
Pieter Wuille
@sipa
right... but also probably the place where the biggest improvements can be found
Simanto Rahman
@Simanto_Rahman_twitter
Btw the FLIFSharp link in readme is broken and the project no longer exists
The Jared Wilcurt
@TheJaredWilcurt
made a PR to remove it
Simanto Rahman
@Simanto_Rahman_twitter
Great I'm waiting for the project to reach maturity and updated license to implement them in a library like ImageSharp which should be neat because it will be fully managed and pretty close to the native speed through the optimization effort of ImageSharp's internal mechanism.
Simanto Rahman
@Simanto_Rahman_twitter
#519 still seems to be an open issue. Are we still open on that discussion?