RE: [nant-dev] Re: [Nant-users] 0.8.3 final

2003-09-10 Thread Brar Piening
 Ian MacLean wrote:

 I'm still fleshing out the details but basically infer the locale based
 on the resx file name ( or allow it to be specified ) and then use

... or infer it if not specified?

 assemblylinker to build the satellite assemblies.

So you plan a comfort feature of implicitly resgening *.resx files to
*.resources files (as seen in the csc task) for the al task too?
I'd appreciate that.

 
 I'm asking because I'm doing a localized build (use of fallback *.resx-
 files
 compiled into the main assembly and localized satellite assemblies) of
 current Npgsql CVS
 (http://gborg.postgresql.org/project/npgsql/projdisplay.php) using NAnt
 and
 mostly all of my problems are outside of NAnt ([Linux] lack of Mono
 assembly
 linker; [Mono Windows] monoresgen failure (at least for default
 installation)).
 
 So does that mean you can't use localised resources on mono if there is
 no assembly linker ?

It means you can't use satellite assemblies on mono as there's no way to
compile them (actually I never tried to run mcs without *.cs files and only
-resource:my.resource specified but I don't expect it to work ;-).

You still can compile the whole set of resources into the main assembly
using mcs and -resource:my.resource, or directly use the *.resources files
from the application (see:
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconretrievingresource
sinresourcesfiles.asp?frame=true)
(I never tried this too, I don't even know if the necessary classes are
implemented - but in this case I expect it to work.)
I personally expect the windows guys to use MS .Net (except developers who
should speak English) and the linux guys to speak some English until mono
provides an al.

 
 In Fact the only Nant-Problem (in my case) is the lack of a Prefix
 Attribute for the resgen-task (to prefix the namespace to the *.resources
 files) which I usually patch out for my own NAnt installation and fix by
 a
 script-task (ugly) for the public.
 
 
 
 OK - I'm going to fix that as well in the next day or so. Its a simple
 enough change.

Thanks in advance.

Brar




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Re: [Nant-users] 0.8.3 final

2003-09-07 Thread Ian MacLean
Gert Driesen wrote:

and for the solution task)
- datatype documentation
 

Have you made any progress on the type docs ?

 

nope. Got the 0.83 release out first. Its on the list for this week.

Ian



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Re: [Nant-users] 0.8.3 final

2003-09-07 Thread Gert Driesen

- Original Message - 
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Sunday, September 07, 2003 9:04 AM
Subject: [nant-dev] Re: [Nant-users] 0.8.3 final


 Jaroslaw Kowalski wrote:

 Is there any updated roadmap to 1.0 ? I've checked the
 
 
 
 http://nant.sourceforge.net/todo.html
 
 and looks like we've silently got a lot of features planned for
 0.8, 0.9, 1.0 and 1.1 into the current version.
 
 
 
 yeah - thats well out of date. Now is definately a good time to revisit
 it and decide on the list of features/bug fixes for a 1.0 release.

In my opinion, high on the list of things to do are :

- support for building locazized applications (for both the compiler tasks
and for the solution task)
- datatype documentation
- packaging (one distribution for all supported frameworks, or separate
distributions)

Note: I'm not saying these are all on MY to-do list :-)


  adding a nice GUI installer (I can make one using
 NSIS if you want),
 
 that would be great if you could. Its on my todo list but with quite a
 few other things in front of it. :)

 integrating some external GUI tools (like NAntMenu
 shell extension, script editor - is the idea still alive?) and it's ready
to go.
 
 
 
 I contacted the author of NAntMenu to see if its ok to package. Waiting
 for his response. Another one is the NUnit2Report task which is a
 seperate project right now.

I'm not sure if we should add external tools to the NAnt distribution.  I
think we should focus on the core build system itself and on supplying
generally useful tasks (which NUnit2Report is indeed).  We should,
however, include a list of third party extensions to NAnt.  That way more
users will discover these tools, and as public interest grows, more people
will be likely to join the authors in improving these tools.

I think most active committers are busy enough without adding even more to
their to-do list ...  thank god we're getting payed good money for all of
this :-) lol


 Maybe the GUI installer can also be one of the products of a daily build?
 
 
 
 good idea. I don't see why not. Add the NSIS build process to the
 nightly build script. NSISTask anyone ?

I agree that it's a good idea, but it wouldn't be cross-platform 

Gert



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Re: [Nant-users] 0.8.3 final

2003-09-07 Thread Ian MacLean
Gert Driesen wrote:

In my opinion, high on the list of things to do are :

- support for building locazized applications (for both the compiler tasks
and for the solution task)
- datatype documentation
 

- packaging (one distribution for all supported frameworks, or separate
distributions)
Note: I'm not saying these are all on MY to-do list :-)

 

hmmm - actually the first two are on *my* TODO list. I've started 
looking at the localisation stuff for the compiler tasks anyway.

adding a nice GUI installer (I can make one using
NSIS if you want),
 

good idea. I don't see why not. Add the NSIS build process to the
nightly build script. NSISTask anyone ?
   

I agree that it's a good idea, but it wouldn't be cross-platform 

 

so is that a problem. Is there a decent cross-platform installer ? I 
don't think so. Mono's windows installer uses NSIS btw.

Ian

Gert
 





---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Re: [Nant-users] 0.8.3 final

2003-09-07 Thread Ian MacLean
Brar Piening wrote:

what you plan to do in case of
building locazized applications?
 

I'm still fleshing out the details but basically infer the locale based 
on the resx file name ( or allow it to be specified ) and then use 
assemblylinker to build the satellite assemblies.

I'm asking because I'm doing a localized build (use of fallback *.resx-files
compiled into the main assembly and localized satellite assemblies) of
current Npgsql CVS
(http://gborg.postgresql.org/project/npgsql/projdisplay.php) using NAnt and
mostly all of my problems are outside of NAnt ([Linux] lack of Mono assembly
linker; [Mono Windows] monoresgen failure (at least for default
installation)).
So does that mean you can't use localised resources on mono if there is 
no assembly linker ?

In Fact the only Nant-Problem (in my case) is the lack of a Prefix
Attribute for the resgen-task (to prefix the namespace to the *.resources
files) which I usually patch out for my own NAnt installation and fix by a
script-task (ugly) for the public.
 

OK - I'm going to fix that as well in the next day or so. Its a simple 
enough change.
Ian



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Re: [Nant-users] 0.8.3 final

2003-09-07 Thread Ian MacLean
Sascha Andres wrote:

* a version system task for cvs - a SourceSafe one would be
  nice too, cause I know many using this.
 

both of these tasks exist right now. Sourcesafe tasks are in 
NAntcontrib. And I've started on perforce tasks.

* ensure documentation ist complete, the way it's now is
  ok, but if there are leaks, they should be filled.
 

great - feel free to submit patches for areas that are lacking.

* sql would really enhance NAnt and would make the
  possibilities outstanding.
 

there is already a sql task in nantcontrib - check it out and see if it 
meets your needs.

The features I think that should come in 1.1 are:

* a tight integration with the different IDEs - VS.NET
  being the highest priority.
 

There is an addin in NAntContrib - I can't vouch for the state of it as 
its been without a maintainer for a while. There is a nant addin for C# 
builder - the only other .net IDE I'm aware of - apart from sharp develop.
Ian



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers