Hi all. Not a bad idea keeping the file types in the server, always allowing a user override the type when adding a file, though then perhaps the data transfer between client and server ought to be changed.
I've also had problems with text files being added as binary (my fault, of course, but that's the problem with such a nice tool as SJ, you get used to getting everything done and you don't mind verifying the type when you add a new file). I know it's not a priority and it could be quite a big deal of work, but having the ability to swap a file type once it's been added would be nice. You can delete it and add it again, but you lose all the history. Anyway, summing up, one vote for James proposal of storing the default file type in the server. Albert. ----- Original Message ----- From: "James Saffery" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 14, 2004 6:11 AM Subject: [SourceJammer-users] FW: Changing File Types from Binary to Text I spoke too soon. Although the 'fix' I described below did lead to the client showing the files as text, and allow them to be checked out, upon checking them back in we got the following "Error: Only Binary files can store history as compressed (zipped) files". So we've decided to delete this archives and add them back in with file type text. James -----Original Message----- From: James Saffery [mailto:[EMAIL PROTECTED] Sent: Wednesday 14 April 2004 12:08 To: '[EMAIL PROTECTED]' Subject: Changing File Types from Binary to Text Hi Rob, We've been happily using SJ now since early Feb since you resolved the initial "no name" folder problem. Thank you again for your support then and for an excellent tool. Recently we had some text files (with .spec and .body extensions) which were first checked in by a user who unfortunately had not configured his client (account?) preferences for these extensions to be text. So then according to SJ these files are binary, meaning we cannot do diffs / view them, and presumably cannot do keyword expansion either. I think I have worked out how to reform the situation by editing the appropriate 'file' XML file for each archive as shown by the ID under File Info in the Properties dialog and changing the FileType to "2". The change then takes effect after a restart of the server. This email then is just a suggestion for what I think would be an improvement so the above does not happen to me or others in the future: make the extension / file type associations attributes of the archive in question rather than the user/client. Then the file types can be set up once for the archive by the administrator and that will be it. No need to remember to repeat this configuration across all users/clients, and no potential for the above situation. Many thanks. Cheers, James ____________________________________________________________ This message may contain legally privileged or confidential information and is therefore addressed to the named persons only. The recipient should inform the sender and delete this message, if he/she is not named as addressee. The sender disclaims any and all liability for the integrity and punctuality of this message. The sender has activated an automatic virus scanning by Messagelabs, but does not guarantee the virus free transmission of this message. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=ick _______________________________________________ SourceJammer-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sourcejammer-users ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ SourceJammer-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sourcejammer-users
