Gert Driesen wrote:
----- Original Message -----
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: "Nant-Developers (E-Mail)" <[EMAIL PROTECTED]>
Sent: Saturday, July 24, 2004 7:08 AM
Subject: Re: [nant-dev] ResourceFileSet
First off sorry for top-posting but this thread is getting too long to
reply inline. I agree that having a profusion of resource related
elements isn't a good thing so lets go with the augmented fileset rather
than a dedicated <namedresources> element.
We might have one more option : add an <embeddedresources> element, which
supports a nested fileset and a nested array of <resource> element, meaning
something like this :
<csc>
<embeddedresources>
<files basedir="..."> (not sure about the <files> name though)
<include name="..." />
<include name="..." />
</files>
<resource file=".." name=" " /> (files name would be relative to
project base directory)
<resource file=".." name=" " />
</embeddedresources>
</csc>
I do think its less confusing, but it is ofcourse (a lot) more verbose ...
Not sure I really like it myself ...
yeah - its a bit too verbose for my liking and not necessarily any less
confusing.
What will we do with the accessibility modifier that can be specified for
resources files in .NET 2.0 ? Should we add a "accessibility" (any better
name for this ?) attribute to the (Resource/ResX/Whatever)FileSet (we can't
have one on the individual include elements, that's for sure) and to the
<resource> element ? Guess so, right ?
I guess so. I don't know what the accessibility modifier does. I should
go check it I suppose.
Now just to be clear on what
we are going to need in terms of fileset types:
an augmented resourcefileset that supports explicit names ( will be used
by compiler tasks )
a new type extending fileset that supports explicit names ( will be used
by the al task )
I'd like to hear you opinion on <embeddedresources> element first (although
I know what you'll be saying, and I can't say I don't agree),
see above.
but if we
still to the "old" plan then we could just rename the current
ResourceFileSet to ResXFileSet (although it handles more than just resx
files) and use that for the compiler tasks, and add a new ResourceFileSet
for the al task, right ?
Yeah that sounds fine.
resgen will change to using a regular fileset instead of a
ResourceFileSet. Incidentally why does it use ResourceFileSet now ? Is
it just for easier assignment from the compiler tasks ?
Its not easier at all, so I really have no clue ...
hmm - pretty sure I wrote at least some of that code and I have no idea
either. Well - if we don't need the ResourceFileset there then lets
change it to FileSet.
Ian
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
