Re: [swig#] Let's start!

[James M. D. <mdu...@ya...>]

Guys,
you need to get www.cygwin.com/setup.exe
from there, intall :  ssh, and cvs
then you need to upload your files to the webserver.
we will use the sf.net server for now, untill we get savannah running-

Also, it would be best to use the savannah server in the long term
so get you savannah server accounts and send them to me.

mike

--- Peter Gloor <pg...@gm...> wrote:
> As suggested by Mike I added the following tasks to the task 
> list :
>  1. Check in the current source code into cvs
We should try and keep the size of the sources needed
to a bare minimum, that means,
if we dont need to change it, then we dont change it.
If we have to change the core swig, we should send a patch to the swig
mailling list. if we are happy with any patches, we should send them to
swig. We should make all the sources in our cvs gpl, and post the
patches to swig without any license.

>  2. Apply the patchs
important!
We need to get all the patches applied

>  3. test with compiler mono C#
important for compatibility, but not important to me.
Do you use this?

>  4. test with compiler pnet / cscc
this is my primary goal

>  5. test with compiler Rotor
for compatibility, but not important to me
Do you use this?

>  6. test with compiler DotNET Csc (standard Microsoft .net)
for compatibility, but not important to me
Do you use this?

>  7. Test with the lib redland
this is my secondary goal

>  8. Test with the other swig libs (name some here)

>  9. Create debian package 
this is my third goal

> 10. Create web page
Any takers?

> 11. Create announcement.
we wait for this.

> 
> However, personally I feel a little uncomfortable with that
> list (but lets see as a starter).  Do we really need all those 
> things (some of them I even don't know what it is)?  
I put my priorities in there.
> 
> I'm a little bit concerned that if we don't concentrate on
> just one goal, we will not get it done in a timely manner.

ok. agreed.

> 
> PROJECT GOALS:
> Before actually starting we should discuss and define the 
> project goals.  
> 
> My personal and primary interest is to see a C# module that
> produces wrapper code to access an existing API (unmanaged
> code) from C#.  To achieve this, all I need is a working 
> csharp.cxx (or whatever you want to call it) module.  

yes. mine too.

> 
> Anything else I need is already there.  Whenever possible I
> will never touch the other existing code.  However, to achive
> my goal I need at least
>   1. access to the latest SWIG release and patches,
>   2. a practical environment that supports a team 
>      to work on the project (the C# module) and

sourceforge is the most tested of such an env.

>   3. a motivated team.
i am here.
> 
> JAVA APPROACH:
> The approach to take the Java module as a "template" makes
> sense to me since both Java and C# have a lot in common.  
> This will make it much easier to maintain it. Additions to 
> the Java module can easily be adopted.
> 
> In addition, from what I have seen, Neil's clr.cxx module 
> provides much more functionality than Feng Songyan's 
> csharp.cxx module.
> 
> One of the most important things I'm missing is support of
> callback routines.

that is interesting, I will ask the dotgnu developers in another mail,
so they can see your questions. Rhys and Gopal are wizards at all this.
email to : dev...@do...

> 
> TIME FRAME:
> Time is limited and important to me.  I would like to get it 
> done within a short time frame.  I need it soon.  If we can 
> get it done within one month or so it is o.k. to me.

I have to evaluate the existing code base, and run some tests. 


> 
> I think there is a lot that can be done within that time.  I
> don't expect a perfect and complete implementation within that 
> time frame, but something that is almost complete and 
> documented.

Ok. I will help test , document and coordinate.

> 
> Since I have to do something anyway I am willing to spend some
> time on this project to get my other work finished faster. I
> could implement callback support within a few days.

And we are sure to get lots of support from the dotgnu community.

> 
> TESTING:
> I'm working on a relatively large project that could provide 
> a ideal test bed.  Except for API's written in C++ there is 
> nothing I can imagine that is not touched by this project 
> (the API has been written in native C).  
> 
> I assume that if it's working for my API it will work for any
> other API written in ANSI C and following standard calling 
> conventions too.
> 
> For legal reasons I cannot provide the API, but I could build
> some examples working the same way.

OK. I am testing this with :
1. redland
2. gcc
3. perl
4. bash
5. gtk
6. vcg

basically, all the components of the introspector will be wrappable,
we can easily run them all through the swig for testing.

> 
> LEGAL STUFF:
> As I said in earlier messages, as long as I don't violate
> anybodys rights I don't care much about the legal things.

lets just stick to gpl and post all our changes. Dont post any code
that
is not yours. 

> 
> HOSTING:
> I'm glad we have got a "home". My thanks goes to Mike! 
no problem.

> However, if we could get CVS access at swig.org and a 
> place to put our things I have nothing against it.

yes, we post all tested patched to swig org

> 
> MOTIVATION:
> First, my personal primary motivation to work on this 
> project is to get my (primary) job done.  

my motivation is to help out, 
my long term goals are to use swig to wrap redland for the dotgnu
project.

> 
> Second, for me it's a new experience. It's the first time 
> I'm trying to do something with others I never met or have
> seen before. 

i am involved in a couple of free software projects, 
and this one looks like an easy win.

> 
> FURTHER PROCEEDINGS:
> Please let me know the current status and how you think we
> should proceed.
> 
> What can you provide at the moment and what are your interests.

1. source safe admin
2. cvs admin
3. testing
4. pnet/dotgnu interface

> 
> What are you interested in doing and how much time can you
> spend.
I can spend about 2 evenings a week for 4-8 weeks.

> 
> Who cares about the CVS and the patches to be applied (I 
> already assigned this task to Neil).
sounds good.

> 
> Who writes the documentation (sorry my English) and other 
> things that will be published.
not me. my docs suck.
> 
> Give me your input so I can setup the task list as acurate
> and detailled as possible.  Don't forget this will be an 
> ongoing process.
> 
> Always let me know if you need any kind of help or assistance.  
> Feel free to ask, I will ask too.
> 
> 
Sounds like a plan Peter! Good start!

Schöne Grüsse aus Frankfurt,
mike

=====
James Michael DuPont
http://introspector.sourceforge.net/

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com