Re: [Webwork-devel] refactor

[<Jim...@do...>]

As most people voiced, the refactor makes sense structurally and for 
deployment. If the refactor is going to happen, I believe it should happen 
now, *before* 1.0.

It will be many times more painful to introduce this type of refactor (no 
features, just reorg) after 1.0 than it would right now. I am also 
speaking as someone developing a huge, mission-critical system on WebWork. 
I recognize that the product is still RC and changes such as these can and 
will occur. I have prepared myself mentally for this type of change, 
especially in a beta product.

So suck it up guys and complete it. Most of the "fixing" relates to 
package naming, so make sure that the entire codebase rebuilds properly 
and the examples execute correctly. It is very important to get the view 
technology out of the true "core" of WebWork. It has never made much 
sense.

jim





ma...@sm...
Sent by: web...@li...
03/01/2002 03:56 PM

 
        To:     web...@li...
        cc: 
        Subject:        [Webwork-devel] refactor


Well, I guess there is sufficient resistence and rightly so to any 
refactoring at this time. Unless Rickard or someone directs differently, I 
would be more than happy to restore cvs tomorrow to its previous state. I 
saved off a snap shot. We can save these concerns and issues for a later 
time.

-Matt



_______________________________________________
Webwork-devel mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/webwork-devel