Eric,
Probably just a local UW-Madison issue, but in case you forgot...
If we continue to use our .../entities/channel/map-cvs-branched-env-files.xml
we need to distinguish that from the actual channel files.
JimT
On Mar 21, 2011, at 4:00 PM, Eric Dalquist wrote:
If we remove it we would
If you're going to rename them, is there a significant reason to even
leave the '.channel' in the middle? To me this always felt like an
unneeded complication when the 'type' was in the XML content to begin
with. And in the case of uPortals own set of entity files it has them
in
If we remove it we would have to do one of two things.
1. Absolutely require the directory structure currently in use be used
ALL the time.
2. Parse all the XML files twice, once to determine the root element and
sort the data files then again to do the import.
The order that the data is
Having information required in the 'middle' of a filename is very
non-standard. So, if we can't remove it at all, then I guess I am not
in favor of renaming them at all.
Seeing foo.channel I'm more inclined to think I have to keep the file
named *.channel. If I see a file named
I can see the benefit of retaining the identifier and adding the .xml extension.
So we'll end up with files like:
foo.channel.xml
foo.channel-type.xml
foo.group_membership.xml
foo.fragment-layout.xml
Sounds good to me. It is non-standard but means there is more clarity around
what type of file
Anyone have any thoughts on renaming the entity files in trunk by adding
.xml to the end? So IdentitySwapper.channel would become
IdentitySwapper.channel.xml I think it might back life a little easier
if editors recognize these files as XML by default.
-Eric
smime.p7s
Description: S/MIME
+1
All those type names as file name extensions is a pain.
Susan
On 3/14/2011 9:26 PM, Carroll, Timothy Dale wrote:
+1
On Mar 14, 2011, at 8:46 PM, Eric Dalquisteric.dalqu...@doit.wisc.edu
wrote:
Anyone have any thoughts on renaming the entity files in trunk by adding
.xml to the end?
