At 05:45 PM 9/1/2006 +0100, Nick wrote:
Tracy Pearson wrote:
>
> VFP's MD will create the whole level from one command.
> IF NOT DIRECTORY(targetDirectory)
> MD (targetDirectory)
> ENDIF
>
Almost there! Only problem with MD is that it creates all the directories
in _lower_ case rather than the mixed case that they were in. Can't think
of a way around this at the moment, any ideas?
Yes. DROP the concept of case-sensitivity in regards to file/directory
names. This is one of the dumbest concepts around, IMO (and as much as I
like Linux I think it's still dumb). I can NEVER imagine that I would want
a file named Myimporantdoc.odt to be separate from myimportantdoc.odt or
MyImportantDoc.odt. In fact, I think it's downright 'dangerous' to
non-technical users.
If you want 'pretty' things for your users, implement a naming convention
that you can parse in your user interface (you don't let them directly use
Windows Explorer do you? uh-oh). E.g. separate words with underscores
(spaces - Ack - another stupid idea for file names). So then you'd do
something like
Method MakePrettyFN(cRealFN)
RETURN STRTRAN(PROPER(STRTRAN(crealfn,'_',' ')), ' ', '_')
So my_important_doc.odt, My_important_DOC.odt, and MY_IMPORTANT_DOC.ODT
would all come out as My_Important_Doc.odt.
You could parse the pieces of the path the same way and you could add a
bunch more stuff in there to handle other filename stuff (like, ugh, in
case they used spaces).
Yes, I'm having a rough day..... :-)
-Charlie
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
