Re: [Mailsomething-devl] In general

[Kevin P. <kr...@ya...>]

Okay, I am a bit confused now :)

Correct me if I am wrong, but I believe this is what need
to be done:

- Keep the MAPI code as how it is. No coding on it.
- Work in the mailsomething project.
- Write JUnit tests using the mailsomething code
- Stig will make the MAPI code work

______
As for the CVS structure: is it okay if I structure it just
like I did the MAPI project? So that the complete structure
will look like this:

HEAD/
  mailsomething/
    src/
    lib/
    .../
  src/
    net/
      sf/
       .../
    ../

Kevin

--- stig <st...@eu...> wrote:
> Hey
> 
> I have been looking some more at it. I realized why I
> stopped with the
> seperation - the mailcode in mailsomething is on some
> points very tight
> integrated with code which isnt considered mailcode. So I
> started
> restructuring it and removed some of that code, and my
> idea was then, that
> in order to use the mapi project in mailsomething, the
> mailsomething project
> had to add some extra functionality, like extending some
> classes and
> similar.
> 
> What it comes to is - It doesnt make a very big
> difference if we take the
> code from mailsomething and put into the mapi, it still
> requires a lot of
> work to seperate it. Best thing I think now is to keep
> the current mapi
> code.
> 
> Next progress is to make it to work. So my thought is -
> write a huge number
> of junit
> tests, starting with the simple things and then go up.
> And use the
> mailsomething code to write the tests - the mailsomething
> code has the
> current use of the mailcode.
> 
> I will stick around in the mapi project until the code is
> working. And start
> doing some tests.
> 
> Stig
> 
> ----- Original Message ----- 
> From: "Kevin Pors" <kr...@ya...>
> To: "stig" <st...@eu...>
> Sent: Thursday, April 01, 2004 3:25 PM
> Subject: Re: [Mailsomething-devl] In general
> 
> 
> > > 1. ignore the mapi project so far.
> >
> > Nah, I liked the idea of seperation :D
> >
> > > 2. ignore all existing code in mapi project, ie,
> remove
> > > all code which you (kevin) have moved to /mapi/src
> and
> > > import the packages  from mailsomething. Since u have
> no
> > > idea probably of what packages is  necessary to do a
> > > reasonable seperation of the mailcode, I can do this.
> I
> > > will not do it until I got ur opinion though. This is
> the
> >
> > > option I like the most.
> >
> > I agree on this. If you want you can remove the remove
> > everything from the /mapi/src folder. The /mapi/test
> folder
> > can remain. It only contains one JUnit test,
> > AddressListTest.java
> >
> > > 3. Work hard to understand the code and continue the
> > > restructuring from the
> > > point I was at. This is a VERY bad idea I think,
> since
> > > the restructered code
> > > is not functional as far as I remember.
> >
> > Yeah forget this one.
> >
> > > As mentioned, I think the best, for new people
> starting
> > > on this, to use the mailcode in the mailsomething
> > > project, ignore all the structure changes I
> > > made in mapi, and then start with this.
> >
> > If we want to do this and prevent conflicts with MAPI
> code
> > and mailsomething core-code, I think it would not be
> wise
> > to add changes to the mailsomething core-code, if you
> catch
> > my drift.
> >
> > Kevin
> >
>