I have somewhat described the underlying features/flaws of each project. The rest is pretty much just visible things.
Pretty much all of the buttons (sans flood fill, for the moment) in JEIE are also reproduced in jimn's. Jimn's has a few more buttons that are implemented. He also has several buttons that are not implemented (text, selection), and icons for them (he used an icon set that is license compatible with JEIE and LGM, so JEIE could just as easily steal them). jimn's project also provides some tools with a widget to modify the behavior of the tool (e.g. brush width), which JEIE currently hasn't defined any widgets yet (although the framework supports them, and in a more modular fashion). jimn's also has alpha support and alpha blending support - something which JEIE still has some catching up to do with.
So basically, jimn's has more features - and those would need to be ported to JEIE. JEIE has a framework, which isn't really something you can port. He said he'd work on the memory thing (which is part of the framework).
The only other things that really stand out for the projects are the developers and the IDE. JEIE being developed in Eclipse by myself, with an extensive background in algorithms, but I hardly have the time to develop JEIE, so JEIE is inactive and will start falling behind. jimn appears to be actively developing his in Netbeans with the WYSIWYG, but he's doing a lot of learning as he goes, so you'll see some inefficient algorithms and the whole everything-in-1-class thing that I mentioned before. A Netbeans project can be ported to Eclipse, but not vice versa if you plan to keep using the WYSIWYG. However, JEIE's framework makes adding components trivial, meaning you don't need a WYSIWYG at all.
|