Chromium already supports all the different operating systems by itself, and thus the browser plugin supports all operating systems; there just aren't releases for it that aren't on mac currently, and faruton's been busy with life things to make builds (that and the build server is currently down as of this posting). Besides, I still might do some API breakage, and so it's probably best to wait before making full official releases of the browser plugin for the multiplatform build until the multiplatform build is itself officially released for windows.
Furthermore, I would like to note that the project is designed not to have unnecessary dependencies like Qt floating around everywhere just for the sake of convenience. The only thing in our project that uses Qt is the user interface, and that's actually an optional part of the repository; other user interfaces will probably be out there that use the back-end that won't use or won't want to use Qt, thus depending on Qt in other places unnecessarily puts extra burden upon them. This is what I call Qt-creep. People go "oh, but you're already using Qt over there, why not use it for this or that over here and over there as well?" without realizing the consequences of such a statement. This is one of the biggest dependency traps I've seen good programmers fall in to, and one of the reasons I dislike Qt as a whole despite it being a pretty decent UI toolkit. Avoid that mindset, and you'll be better off for it.
Furthermore, I would like to note that the project is designed not to have unnecessary dependencies like Qt floating around everywhere just for the sake of convenience. The only thing in our project that uses Qt is the user interface, and that's actually an optional part of the repository; other user interfaces will probably be out there that use the back-end that won't use or won't want to use Qt, thus depending on Qt in other places unnecessarily puts extra burden upon them. This is what I call Qt-creep. People go "oh, but you're already using Qt over there, why not use it for this or that over here and over there as well?" without realizing the consequences of such a statement. This is one of the biggest dependency traps I've seen good programmers fall in to, and one of the reasons I dislike Qt as a whole despite it being a pretty decent UI toolkit. Avoid that mindset, and you'll be better off for it.
Last edited: