Re: Large Java classes wanted

I agree, it is difficult.  I had one class that was 1100 lines.  No wait,
that was a method.

Needless to say I got rid of the class, but it was a long and painful
process.

Basic idea: chop it into main groups.  I.e., 8 groups of 150 line methods.
Then unit tests (I didn't do that), and refactoring more, and chopping it up
further.  The refactoring helped a lot as there was tons of duplication.

My $0.02.  But it was not open source, so I can't give you any code...

Mike

On Mon, Feb 22, 2010 at 3:44 PM, K <[email protected]> wrote:

>
>
> But there's a catch...
>
> I'm doing some research on how to split large, difficult-to-maintain
> classes into smaller ones. Obviously, there is no shortage of open source
> Java projects that contain large classes. What I'm hoping to find is
> somebody who
> (1) works on a Java open source project with large classes
> (2) is willing to give feedback on my suggestions on how to split those
> classes.
>
> What's in it for you? I assert that it is difficult to figure out how to
> divide larger classes into smaller ones. If all goes well, I'll be doing
> this for you.
>
> I'm not sure if this is the best forum to float this idea. If anybody can
> suggest a better one, I'd be happy to hear it.
>
> Regards,
> Keith Cassell
>
>  
>



-- 
----------------------_/ /\/\ /\/ -----------------------


[Non-text portions of this message have been removed]



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/