[Mindwrapper] Re: issue list

[Donnal W. <don...@ya...>]

--- Toni Brkic <ton...@sw...> wrote:
> > more appropriate, but if others become interested at some
> > point, maybe we should have more of our discussions on the
> > Mindwrapper mailing list or on the forum.
> >
> > https://sourceforge.net/mail/?group_id=64929
> 
> I think this is a good idea. But a requirement for me is that
> I am able to use my own email client. So is there a email
> address for the sourceforge group? Actually I just found
> out that there is and I will cc this email there.
> >
> > Finally, I thought about trying out:
> > http://www.elementool.com
> 
> About the issue trackers I liked roundup best. Elementool seem
> quite good as well. But I think that it is overkill since it is
> only us two that develop right now.

Yes, it may be overkill, but even when I was doing ALL of the
development myself for months, using an issue tracker, as crude as
it may have been, was helpful. We shall see.

> ... So I would suggest that we
> right now use email but do a cc to the sourceforge group. I think
> it is enogh to convince other people that the project is alive
> and kicking. If there is more people joining we could then
> install a issue tracker.
> 
> I also think that we the open issues we have right now is more to
> decide if and what to implement. The implementation in itself
> would be quite quick i think. 

Yes, most of the open issues are fairly straightforward, but for
the moment I would like to do the implementations: (1) so that I
can run all of the regression tests against the changes, and (2) to
add new unittests for the additions (and possibly (3) so I know
what is going on.<grin>).  

> I am probably working with MW this weekend and maybe tonight.
> If you want me to implement any of the issues I would be happy
> to . 
> 
> Otherwise my plan is to wait with the addressbook until the issue
> with 'linking' is solved. Instead I might do a core for the demo,
> that is to do the startup where you traverse all subdirectories
> to find out the samples and create the AL from that and a
> corresponding PL treeview of all the samples.

That sounds like a good plan.

> Or I will maybe start on the AL/PL for my register file
> generator.

Or this too. :-)

Regards,


=====
Donnal Walter
Arkansas Children's Hospital