|
I was
mistaken about it not being supported. I hashed this out with the other TMM
members yesterday. Bastian is correct, it is easy, my blog app is fully
supported cross-platform, the only changes that I needed to make where those
that Bastian mentions.
I
still prefer to use \ on windows and / on linux, just in case Windows doesn't
want to do /. I don't trust windows. And I deffinately would not want to use the
MXNA example because I don't think there is a need to invoke java just to get
the path seperator. You can make it an option in the config, automatically
configure it with by the server.os.name variable, etc. No need to go through all
that other stuff just for the path seperator.
My
0.2
Bryan
Why not only use "/" at fileoperations? it's
default linux seperator and even supported by windows.
i code all my <cffile>'s with "/" as
seperator - work's fine.
an for linux you have to mode="xxx" the files ->
add this to cffile would only effect linux systems, windows ignores
this...
so i think cross-platform compatibility is easy
-> no additional functions or so on needed.
greets
Bastian Konetzny
----- Original Message -----
Sent: Tuesday, August 12, 2003 9:14
PM
Subject: RE: [CFXML_Blog] Linux/Windows
source tree (was RE: CFXML_blog on SourceForge)
Bryan: Integrating Java into your CFML in this manner is
perfectly supported by Macromedia (I work in Macromedia ColdFusion Product
Support). Your mechanism is simple and requires less code, and it works
well. I believe Geoff Bowers wrote the other function (MXNA has a
copyright notice with his name on it.), so he may just prefer the
object/method approach.
Cornel(1): Again, you may want to ping
Geoff Bowers ([EMAIL PROTECTED])
before using that exact code... but of course if you modified from the
original, then ???...
Cornel(2): >>"The reason
why I said there should be a
>> separate folder
for css and one for
>> Language files is that in
the current setup
>> the latest are kept with the
latest version only
>> and we are working
still with 2 versions, soon
>> to be 3
(Linux)versions"
I think that there should only be one latest
version. Trying maintain more than one source tree will become very
complicated very quickly. I have not yet joined the CFXML_Blog team on
SourceForge, but would like to. At this time I haven't seen how the
project is organized up there.
Giampaolo: I would like to
participate in the project development on SF. Please tell me how.
Thanks!
-Steven Erat
-----Original Message-----
From:
Bryan F. Hogan [mailto:[EMAIL PROTECTED]
Sent: Tuesday,
August 12, 2003 2:00 PM
To: [EMAIL PROTECTED]
Subject:
RE: [CFXML_Blog] Linux/Windows source tree (was RE: CFXML_blog on
SourceForge)
What I meant was that the docs AFAIK do not contain
documentation of things that you can do with java.io. I'm sure that MXNA is
supported but, if it's not documented, I very much doubt that you will be able
to get support for it.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Steven Erat
Sent: Tuesday,
August 12, 2003 2:00 PM
To: '[EMAIL PROTECTED]'
Subject:
RE: [CFXML_Blog] Linux/Windows source tree (was RE: CFXML_blog on
SourceForge)
>> "On top of that it's a supported
technique."
In what sense? One implementation in CFML isn't
necessarily 'supported' more than the other, at least not by Macromedia
Product Support standards.
-----Original Message-----
From:
Bryan F. Hogan [mailto:[EMAIL PROTECTED]
Sent: Tuesday,
August 12, 2003 1:19 PM
To: [EMAIL PROTECTED]
Subject:
RE: [CFXML_Blog] Linux/Windows source tree (was RE: CFXML_blog
on
SourceForge)
On top of that it's a supported
technique.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Steven Erat
Sent: Tuesday,
August 12, 2003 1:21 PM
To: '[EMAIL PROTECTED]'
Subject:
RE: [CFXML_Blog] Linux/Windows source tree (was RE: CFXML_blog
on
SourceForge)
Agreed. The old
stand-by...
-----Original Message-----
From: Bryan F. Hogan
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003
1:16 PM
To: [EMAIL PROTECTED]
Subject:
RE: [CFXML_Blog] Linux/Windows source tree (was RE: CFXML_blog
on
SourceForge)
Well I don't know about Macromedia, but 7 lines
is better than 16 for me.
<cfscript>
if(Server.OS.Name
contains 'Windows') {
localVars.pathSep='\';
} else
{
localVars.pathSep='/';
}
</cfscript>
|