[ImageJ-devel] ImageJ2 development
ctrueden at wisc.edu
Tue May 6 16:17:10 CDT 2014
> I am really glad you are open to collaboration. Like you said, there
> is definitely a learning curve, so I will try to get acquainted with
> the current codebase and drop in on #imagejdev for questions.
> I am happy to work on documentation while I am getting up to speed
> with the code.
Great, that would be really helpful.
> Most of my itches are actually GUI-related, but from what I've
> gathered you are not planning to initially change the GUI much from
> what it was in 1.x for compatibility reasons. Maybe once I understand
> the code structure a little better, I can help with work on the Swing,
> AWT, or RCP GUIs for the later releases. I'll be keeping in touch.
Right, there are two very different modes: the ImageJ 1.x user interface,
and the ImageJ 2.x Swing UI. The latter is (at the moment) designed to
function much like the former, although we will probably diverge more from
ImageJ 1.x's design in the future.
To facilitate total backwards compatibility, as well as to accommodate
Wayne Rasband's continued development of ImageJ 1.x, we are now opting to
release ImageJ 2.0.0 running with the 1.x UI by default. You can still
switch to the ImageJ2 UI using Help > Switch to Modern Mode, but it has
more limitations compatibility-wise.
I would encourage you to discuss your UI ideas and requirements on
imagej-devel or in the #imagejdev IRC channel (i.e., somewhere public).
That way we can stay on the same page about what things are possible and
warranted within each user interface.
I look forward to hearing more from you!
On Tue, May 6, 2014 at 3:35 PM, Pawel Niewiadomski <
pawelthebiologist at gmail.com> wrote:
> Hi Curtis,
> I am really glad you are open to collaboration. Like you said, there is
> definitely a learning curve, so I will try to get acquainted with the
> current codebase and drop in on #imagejdev for questions. I am happy to
> work on documentation while I am getting up to speed with the code. Most of
> my itches are actually GUI-related, but from what I've gathered you are not
> planning to initially change the GUI much from what it was in 1.x for
> compatibility reasons. Maybe once I understand the code structure a little
> better, I can help with work on the Swing, AWT, or RCP GUIs for the later
> releases. I'll be keeping in touch.
> On 2014-05-06 6:29 PM, Curtis Rueden wrote:
>> Hi Pawel,
>> Thanks very much for your interest in the ImageJ project! I'm CCing the
>> imagej-devel mailing list, since that is the best place to discuss
>> ImageJ2 core development.
>> > ImageJ is one of my all-time favorite pieces of software and I would
>> > like to contribute to its development. I have a decent knowledge of
>> > Java, but I haven't really worked on an open source project before. I
>> > saw that the list of contributors on the ImageJ github page is pretty
>> > limited and so I am wondering if you generally like outside people
>> > contributing to the codebase or whether you prefer to keep it within
>> > the core development team.
>> One of the major goals of ImageJ2 is to support a more
>> community-oriented group of developers. Requests like yours are
>> surprisingly rare because most people do not have a lot of free time to
>> contribute to projects like ImageJ. But your help would definitely be
>> most welcome.
>> > If you welcome new devs, what features/bugfixes do you think are most
>> > critical at the moment?
>> I would encourage you to first "scratch your own itches" . You can
>> get started right away: fork the relevant project(s) from
>> https://github.com/imagej and https://github.com/scijava, push changes
>> to topic branches, and file pull requests . (And if you need an
>> introduction to Git: https://try.github.io/).
>> If you really don't have any itches and just want to fix bugs, that's a
>> bit trickier at the moment, since you would need to become more
>> acquainted with the ImageJ2 project structure -- and it is still in beta
>> and documentation is scarce in many places.
>> It might make the most sense for you to jump into the ImageJ chat room
>> (#imagejdev) on IRC freenode during U.S. business hours and chat with us
>> at more length. One way you could start helping the project right away
>> would be transform any information you learn there into wiki pages on
>> the ImageJ wiki (http://wiki.imagej.net/).
>> We are gearing up for an initial release of ImageJ 2.0.0 (finally
>> leaving beta!) on June 1, so your timing is hectic, but also really
>> fantastic to help improve the project documentation and learn the
>> system, so that you can embark on more involved coding endeavors.
>>  https://gettingreal.37signals.com/ch02_Whats_Your_Problem.php
>>  https://help.github.com/articles/using-pull-requests
>> On Wed, Apr 30, 2014 at 12:36 PM, Pawel Niewiadomski
>> <pawelthebiologist at gmail.com <mailto:pawelthebiologist at gmail.com>> wrote:
>> Hi Curtis,
>> I am a postdoc in molecular biology, who has recently started to
>> seriously work on improving my coding skills. ImageJ is one of my
>> all-time favorite pieces of software and I would like to contribute
>> to its development. I have a decent knowledge of Java, but I haven't
>> really worked on an open source project before. I saw that the list
>> of contributors on the ImageJ github page is pretty limited and so I
>> am wondering if you generally like outside people contributing to
>> the codebase or whether you prefer to keep it within the core
>> development team. If you welcome new devs, what features/bugfixes do
>> you think are most critical at the moment?
>> Paweł Niewiadomski
>> e-mail: pawelthebiologist at gmail.com <mailto:pawelthebiologist@
>> website: www.pawelthebiologist.com <http://www.pawelthebiologist.com>
> Paweł Niewiadomski
> e-mail: pawelthebiologist at gmail.com
> website: www.pawelthebiologist.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ImageJ-devel