Still, what happens with plugins? Do we then have to write our plugin 3 times as well.? Just some more stuff to think about.
(Although you'd then still have to manually rewrite the GUI calls.) Unless Mono+C#+GTK# was going to be the new single cross-platform solution? (Although I don't think GTK is going to be any more satisfying in that role than Swing.) If you really do still want to do a C# version, I'd say convert it automatically with something like Sharpen the way NGit did. Je to preto, e na rozdiel od inch prehliadaov nemme iadny finann zujem na tom, aby sme. Prehliada Firefox o vs zhromauje tak mlo dajov, e na stiahnutie nepotrebujeme ani vau e-mailov adresu. Zskajte vetku rchlos a nstroje bez naruenia skromia.
#TOMIGHTY FIREFOX WINDOWS#
I'm not sure what the advantage of a C# port would be, since the Java version seems to work just fine on Windows (7 at least). Ak je Firefox v porovnan s inmi prehliadami.
Especially since it seems like 90% of the problems are related to the System Tray, and that those are more the fault of the Swing GUI rather than the Java language itself. But it sure is a shame to write the same thing 3 times (at least).
Personally, I lean heavily in favor of the former at the expense of the latter, but I understand many would feel the exact opposite. There are more than 50 alternatives to Tomighty for a variety of platforms, including Windows, Mac, Linux, Online / Web-based and iPhone. Hmm, I can appreciate the tension and trade-off between cross-platform portability vs native feel. Tomighty is described as 'convenient, easy to use, eye candy desktop application that helps you organize and execute your tasks in the Pomodoro way' and is a Pomodoro Timer in the office & productivity category.
0 kommentar(er)
