Adobe Community: Message List - Mobile

Illustrator Draw app mobile

forums_noreply@adobe.com — Wed, 05 Nov 2014 13:11:01 GMT

Hy,

Anybody here, use Illustrator Draw on iPad?

I have a question about share my projects. I know that is exist the option to share for Illustrator on Desktop, but and my app this don't appears.

I need help, please!

Tks,

Jey Castro

Are you a PhoneGap expert?

forums_noreply@adobe.com — Mon, 08 Sep 2014 12:28:37 GMT

I am looking for a community expert who would be willing to demonstrate their PhoneGap products to my online graduate class. Show off your work. Talk about the roadblocks you have encountered.

flash player on our ipad and iphone

forums_noreply@adobe.com — Thu, 21 Aug 2014 20:54:57 GMT

we need flash player on our ipad and iphone

Re: ColdFusion 11: ... how does normal CFML code and code interact?

forums_noreply@adobe.com — Mon, 07 Jul 2014 10:31:55 GMT

There is something else about cfclient that I find even more worrying. Consider the following code snippet:

<cfclient>

<cfset document.getElementById("result").innerHTML = "Hello">

</cfclient>

This code, found in almost all the demonstrations Adobe has published on the new cfclient tag, mixes the syntax of the two languages, Coldfusion and Javascript. That can only mean one thing: confusion.

In fact, I wonder why it works, as it is invalid CFML. Do you get my 日本語? Then you get my drift.

Reference: Adobe cfclient documentation

Gossip

forums_noreply@adobe.com — Sat, 21 Jun 2014 17:28:17 GMT

Why do people rather to attend to others business than their own? E. g. installation remove redeye

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

forums_noreply@adobe.com — Wed, 07 May 2014 09:48:42 GMT

The functions defined in the cffunctions.js are not namespaced. If it is namespaced, you would have to add the namespace while using a function inside cfclient.

These functions are not namespaced, so that you can use the same syntax for using a function inside and outside the cfclient block.

This is indicative of everyone's concern that you guys would just implement / encourage poor practice in your <cfclient> implementation.

How is it - given you're "compiling" the CFML anyway - you cannot translate source code that says "listlen()" into "compiled" JS that is CF.listLen() or something? Thus good CFML can be translated into good JS.

You seem to think that there's a one-to-one mapping between what the CFML says and what the resultant JS needs to be.

You've basically written a mechanism for a CFML developer to write bad JavaScript.

Well done.

Adam

Re: ColdFusion 11: ... how does normal CFML code and code interact?

forums_noreply@adobe.com — Wed, 07 May 2014 09:29:37 GMT

PaulNibin wrote:

Hi Adam,

When you write code inside <cfclient>, it is translated to java script. It cannot access server side variables(defined outside cfclient).

<script> message = "G'day World"; </script> <cfclient> <cfoutput>#message#</cfoutput> </cfclient>

The above code works because, message is defined in a script block and client side CFML is interoprable with javascript. So client side CFML can use variables, functions defined in javascript blocks.

Thanks,

Paul

So you're saying you did not provide a mechanism for transferring the variables from the server-side part of a file's code to the client side part? Is this not a bit of an oversight?

And what - in your mind - is the point of having a file with blocks of both normal CFML, and then a <cfclient> block, then more CFML, then another <cfclient> block (for example) if the code cannot interact?

Adam

Re: ColdFusion 11: ... how does normal CFML code and code interact?

forums_noreply@adobe.com — Wed, 07 May 2014 08:48:11 GMT

Thanks Akhila

Adam

Re: ColdFusion 11: ... how does normal CFML code and code interact?

forums_noreply@adobe.com — Tue, 06 May 2014 09:21:24 GMT

A bug(#3755482) is logged to get proper error message when <cfclient> tag is used with invalid attributes.

Thanks,

Akhila.

Adobe ColdFusion Engineering Team.

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

forums_noreply@adobe.com — Tue, 06 May 2014 09:09:28 GMT

An ER logged for this - #3755497.

Thanks,

Akhila.

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

forums_noreply@adobe.com — Tue, 06 May 2014 08:26:11 GMT

An ER is logged to load cffunctions.js only when its required/used by application.

Ooh. Are we playing "guess the E/R number?"

1? 23? 8874012?

Oh, I give up. Perhaps you're just gonna have to tell me :-|

--
Adam

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

forums_noreply@adobe.com — Tue, 06 May 2014 08:17:51 GMT

Hello Adam,

An ER is logged to load cffunctions.js only when its required/used by application.

Thanks,

Akhila.

Adobe ColdFusion Engineering Team.

Re: ColdFusion 11: ... how does normal CFML code and code interact?

forums_noreply@adobe.com — Mon, 05 May 2014 14:26:40 GMT

Hi Adam,

When you write code inside <cfclient>, it is translated to java script. It cannot access server side variables(defined outside cfclient).

<script> message = "G'day World"; </script> <cfclient> <cfoutput>#message#</cfoutput> </cfclient>

The above code works because, message is defined in a script block and client side CFML is interoprable with javascript. So client side CFML can use variables, functions defined in javascript blocks.

Thanks,

Paul

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

forums_noreply@adobe.com — Mon, 05 May 2014 14:21:11 GMT

Hi Adam,

cffunctions.js contains all the supported inbuilt CFFunctions in the javascript form.

This file is added as a script source in the pages where cfclient is used. This is included, so that you can use the supported CF functions in the cfclient.

Right now, coldfusion does not check whether the built in functions are used to add the script source.

This is done only for the phonegap device plugins and device detection plugins. i.e., the device API plugins and device detection plugins are included only when they are used in your code. But cffunctions.js is always included. But this is definitely an enhancement that we are looking to implement later.

The functions defined in the cffunctions.js are not namespaced. If it is namespaced, you would have to add the namespace while using a function inside cfclient.

These functions are not namespaced, so that you can use the same syntax for using a function inside and outside the cfclient block.

Thanks,

Paul

ColdFusion 11: cfclient ports a lot of CFML functions to JS

forums_noreply@adobe.com — Sat, 03 May 2014 15:51:52 GMT

G'day:

I am reposting this from my blog ("ColdFusion 11: cfclient ports a lot of CFML functions to JS") at the suggestion of Adobe support:

@dacCfml @ColdFusion Can you post your queries at http://t.co/8UF4uCajTC for all cfclient and mobile queries.
— Anit Kumar Panda (@anitkumar85) April 29, 2014

I have edited this in places to remove language that will be deemed inappropriate by the censors here. Changes I have made are in [square brackets]. The forums software here has broken some of the styling, but so be it. There are comments back against the original article - linked to above - which are worth reading too.

G'day:
I will start this article - which won't be a long one - by stating I am an adequate JavaScript developer, but I am by no means an expert. I'm at that stage wherein I'm au fait with the syntax and the nuts and bolts of writing OO-esque JS, but I don't spend enough time doing it to know the minutiae of "best practice" and don't automatically know the differences between the "best" way of doing something, and just "a way of doing something". Hence this article asks a question, rather than making any concrete statements.

A few days ago I wrote my first <cfclient> hello world (or in my case "G'day World") example. I'm not compiling it to a mobile app as I'm not really testing the ColdFusion Builder app packagings stuff (I simply don't care about that), I'm only interested in how <cfclient> performs / works in the context of a tag in the CFML language. See this article for more on that: "ColdFusion 11: <cfclient> in the context of the CFML language, not the tooling".

One thing I noticed in my "G'day World" code, is that to output those 11 bytes on the screen, <cfclient> loads around 128kB of data, in the form of various tracts of line code and external libraries. Describing this as "egregious" is an understatement.

One of the libraries particularly caught my interest, as it's called "cffunctions.js", and - as the name suggests - contains a port of alla lot of CFML's built-in functions to JS.

My first observation is its inclusion is completely unnecessary as I'm not using any functions in my code, and it would be reasonable to think that the <cfclient> CFML to JS compiler might notice that and save people a download. Secondly... it's a single, monolithic 106kB file. Let's have a look at it:

Well actually when I suggest we should have a look at it, I am actually inviting the JavaScript aficionados amongst us to offer their input. I'm not going to be able to lend much expert analysis to it.

Observations I will make:

as I said above: including this file when it's not necessary seems wrong.
Every single function is just slapped into one huge file. This to me seems equivalent to having a CFC called AllMyCode.cfc, containing... everything, including kitchen sinks and family pets.
Connected to that: the functions are all declared straight in the global scope, which seems a bit "pollute-y" to me. I can't help but think they ought to be grouped together in a CF namespace, within that some sort of type-centric namespace like CF.List.listAppend(), CF.Math.abs() etc?
A lot of the code seems rather "longhand", eg: someVar = SomeVar+1 instead of perhaps someVar++; using an indexed for() loop to loop over arrays etc.
The file's not minified: this would almost halve its size. I dunno if this is such a consideration these days with responses being GZipped?

Is there anything else you've spotted?

I might sound a bit nit-picky here (hey: it would not be the first time, and someone needs to ask these questions), but equally if I want someone writing a wizard to write my JS for me, then I want to know that person actually knows what they're doing. And if I can raise code-quality questions... I suspect the answer is I don't want this person writing my JS for me.

But I completely accept that perhaps there's not an issue to answer here... this article is more soliciting other - more expert - people's opinions.

What do you think?

--
Adam

ColdFusion 11: ... how does normal CFML code and code interact?

forums_noreply@adobe.com — Sat, 03 May 2014 15:48:56 GMT

G'day:

I am reposting this from my blog ("ColdFusion 11: ... how does normal CFML code and code interact?") at the suggestion of Adobe support:

@dacCfml @ColdFusion Can you post your queries at http://t.co/8UF4uCajTC for all cfclient and mobile queries.
— Anit Kumar Panda (@anitkumar85) April 29, 2014

G'day:
Another quick one. I'm raising these quick-fire questions here because Adobe have declined to suggest a better place to raise them, other than as comments on one of their blog entries. Well that was Ram's suggestion (which I don't think is terribly-well thought out). He declined to react to my suggestion that the Adobe ColdFusion forums might be a good place. Anit suggested Twitter or just emailing him, but I think there'd be public interest in this stuff, so don't want to resort to email.

As I'm the master of what goes on on this blog: I'll clutter this thing up.

Say I want to have a mix of "normal" CFML and <cfclient>-based CFML in the same file. I can only presume the intent is to allow this, otherwise having <cfclient> as a tag rather than just a file extension seems like a poor approach. Obviously if one can have a start tag and an end tag, then code can come before (and I guess after) the <cfclient> tags themselves.

So I'd expect this to work:

<cfset message = "G'day World"> <cfclient> <cfoutput>#message#</cfoutput> </cfclient>

However all I get is an error in JS:

Uncaught ReferenceError: message is not defined variablesScopeVariable.cfm:4

And, indeed, the only mention of message in the JS source is the one that's erroring (as it's on the right-hand side of an assignment).

So I thought perhaps <cfclient> worked like <cfthread> and I needed to pass attributes into it:

<cfset message = "G'day World"> <cfclient message="#message#"> <cfoutput>#message#</cfoutput> </cfclient>

This doesn't compile:

Attribute validation error for the client tag.
The tag does not have an attribute called message. The valid attribute(s) are ''.

*ColdFusion cannot determine the line of the template that caused this error.*This is often caused by an error in the exception handling subsystem.

Note also there's an error in the error message itself. It's not the <client> tag, it's the <cfclient> tag.

Rightio then, so I tried just using the request scope instead (the code's the same as the variables-scoped example, except using the request scope). No dice: same JS error.

As a last ditch effort, I just tried to see if <cfclient> was aware of anything going on around it, by passing a value on the URL, and seeing if <cfclient> saw that, eg:

<cfclient> <cfoutput>#URL.message#</cfoutput> </cfclient>

This behaved differently from the variables- / request- scoped examples, in that I didn't get a JS error, I just got this on the screen:

undefined

And no JS error. It pains me to have to do this, but let's look at the generated JS to see why the behaviour is different:

Variables scope example:

<script type="text/javascript" src="/CFIDE/cfclient/cfclient_main.js"></script> <script type="text/javascript" src="/CFIDE/cfclient/cffunctions.js"></script> <meta name="viewport" content="width=device-width"> <script type='text/javascript'> globalDivStruct=null; var _$variablesScopeVariable_func=function(){     var self=this;     var variables={};     self.__init=function(){         var localdivstruct=globalDivStruct;         var __output_var="";         var tmpVarArray={};         localdivstruct.outputvar+=message;        return""     } }; function __startPage__$variablesScopeVariable(){     document.write("\x3cdiv id\x3d'__cfclient_0'\x3e\x3c/div\x3e");     window.ispgbuild=false;     var clientDivStruct={         divId        : "__cfclient_0",         outputvar    :""     };     globalDivStruct=clientDivStruct;     try{         _$variablesScopeVariable=new _$variablesScopeVariable_func;         _$variablesScopeVariable.__init()     }     catch(__eArg){         if(__eArg!=="$$$cfclient_abort$$$")             throw __eArg;     }     __$cf.__flush(clientDivStruct) } __startPage__$variablesScopeVariable(); </script>

The only significant difference (other than function names, based on the file names) between this and the URL-scoped example is the indicated line above is replaced by this in the URL example:

localdivstruct.outputvar+=__$cf.__arrayGet(URL,"message",true);

So it's like it's trying to do the right thing, but just failing. I thought it might be because CF does stupid thinks with scope-key casing, and changed the <cfclient> code to expect URL.MESSAGE not URL.message, but this didn't work either.

So I'm flummoxed. I can't find anything in any documentation which might point me in the right direction, so anyone know what the story is here?

Update:

At Joel's suggestion I tried this:

<script> message = "G'day World"; </script> <cfclient> <cfoutput>#message#</cfoutput> </cfclient>

Thisworked. Which elicits from me a mixture of "heh: cute" and "this is an abomination".

--
Adam

ColdFusion 11: seems to require /CFIDE to be available

forums_noreply@adobe.com — Sat, 03 May 2014 15:43:54 GMT

G'day:

I am reposting this from my blog ("ColdFusion 11: <cfclient> seems to require /CFIDE to be available") at the suggestion of Adobe support:

@dacCfml @ColdFusion Can you post your queries at http://t.co/8UF4uCajTC for all cfclient and mobile queries.
— Anit Kumar Panda (@anitkumar85) April 29, 2014

G'day:
This will be a short one... I just want to trot out various observations I make about <cfclient> as I make them. I don't want to waste too much effort on it.

I also feel a bit dirty round about now... I'm about to use a <cfform> tag.

As should everyone, I do not expose /CFIDE to the outside world. This is a terrible vector for security vulnerabilities. One that Adobe seems to be dragging its heels about resolving once and for all ("Isolate the /CFIDE/scripts directory from the rest of /CFIDE" (3732913)).

So when I'm using <cfform> (which is only ever when I am writing example code like this), I need to redirect ColdFusion to look in my isolated directory which just has the script stuff in it:

<cfajaximport scriptsrc="/lib/js/CF/scripts"> <cfform method="post" action="#CGI.script_name#">     <cfinput type="dateField" name="date">     <input type="submit" name="submitButton" value="Go"> </cfform> <cfdump var="#form#">

Note: do not use <cfform> or any of ColdFusion's other UI wizard tags. Just don't. See here: "ColdFusion UI the Right Way", here: "I'm not going to tell you to stop using ColdFusion UI tags anymore...", and here: "Oi! You [naughty] [people]! Stop using ColdFusion UI controls".

Anyway, back to the code. The poorly-named <cfajaximport> tag allows one to point ColdFusion at a different, isolated directory. That's quite handy.

Now I try it with my <cfclient> code:

<cfajaximport scriptsrc="/lib/js/CF/scripts"> <cfclient> <cfset message = "G'day World"> <cfoutput>#message#</cfoutput> </cfclient>

and I get this:

14:46:11.292	GET	http://localhost:8511 /shared/scratch/blogExamples/coldfusion /CF11/cfclient/moveScriptDir.cfm	[HTTP/1.1 200 OK 284ms]
14:46:11.655	GET	http://localhost:8511 /lib/js/CF/scripts/ajax/messages/cfmessage.js	[HTTP/1.1 200 OK 5ms]
14:46:11.655	GET	http://localhost:8511 /lib/js/CF/scripts/ajax/package/cfajax.js	[HTTP/1.1 200 OK 10ms]
14:46:11.656	GET	http://localhost:8511/CFIDE/cfclient/cfclient_main.js	[HTTP/1.1 404 /CFIDE/cfclient/cfclient_main.js 3ms]
14:46:11.656	GET	http://localhost:8511/CFIDE/cfclient/cffunctions.js	[HTTP/1.1 404 /CFIDE/cfclient/cffunctions.js 3ms]
14:46:11.657	GET	http://localhost:8511/CFIDE/cfclient/cfclient_main.js	[HTTP/1.1 404 /CFIDE/cfclient/cfclient_main.js 1ms]
14:46:11.657	GET	http://localhost:8511/CFIDE/cfclient/cffunctions.js	[HTTP/1.1 404 /CFIDE/cfclient/cffunctions.js 0ms]

Groan. Because <cfclient> doesn't put its script files in the scripts dir, does it? No. Of course it doesn't. Muppets.

But this could still be solved if one could specify some other way of pointing it to a different location for its resources, but... no. There's not a way of doing this that I can find. Short of [messing] around on the web server and setting up virtual directories pointing to /CFIDE/cfclient. This isn't really a hardship, but still, it just shouldn't be necessary, and I can't help but think this is a bit sloppy on the part of Adobe.

It also demonstrates that for their internal testing they don't test this sort of thing. Which is odd, as it's the second thing I tested: you know, that it even works on a secured server.

That's it. I've nothing else to say on this topic. I'll raise a bug for this shortly, once I have the article published so I can refer back to it: 3750729.

--
Adam

ColdFusion 11: in the context of the CFML language, not the tooling

forums_noreply@adobe.com — Sat, 03 May 2014 15:39:40 GMT

G'day:

I am reposting this from my blog ("ColdFusion 11: <cfclient> in the context of the CFML language, not the tooling") at the suggestion of Adobe support:

@dacCfml @ColdFusion Can you post your queries at http://t.co/8UF4uCajTC for all cfclient and mobile queries.
— Anit Kumar Panda (@anitkumar85) April 29, 2014

I have edited this in places to remove language that will be deemed inappropriate by the censors here. Changes I have made are in [square brackets]. The forums software here has broken some of the styling, but so be it. There is worthwhile discussion in the comments of the article on my blog: perhaps go have a read.

G'day:
This article could end up being a complete waste of space, as I am operating under more real-world re-interpretation of the raison d'être of <cfclient>, as described by Ram:

ColdFusion [11] has added support for client side CFML (<cfclient>) and this code is translated to JavaScript

Mike Henke has pointed out that the first part of this "CF11 has added support for client-side CFML" is actually ******** (my wording, not his):

"ColdFusion Splendor has added support for client side CFML" is probably phrased wrong and gave me flash backs to VBScript or CFML running in the client browser.
Maybe this is better verbiage. "ColdFusion Splendor has added support for CFML to generate JS".

Because... there's not such thing as "client-side CFML". That would imply CFML actually running on the client (ie: the browser, or the mobile device, as is the target of <cfclient> as a concept). This is absolutely not true. I know Ram went on to qualify what he meant there, but the messaging from Adobe on <cfclient> has been inaccurate. Possibly I think to the point of actual misrepresentation (in the legal sense, I mean).

What <cfclient> does is... convert CFML code to JavaScript. So let's look at that idea.

Why I say this article could be a complete waste of space is that I dunno if this is the intent of <cfclient>; because, really, the messaging from Adobe as to what <cfclient> is for is very muddied. In general the narrative about it is bundled-in with various features of ColdFusion Builder 3.0, in regards to mobile application creation and packaging (and debugging, and all sort of stuff that sounds quite nice but I don't care about as I don't use CFB).

However <cfclient> has to stand on its own merit in the CFML language, completely decoupled from CFB features. And as far as I can tell, Mike is right: as far as CFML goes, <cfclient> is a tag which tells ColdFusion to - instead of compiling to byte code - compiles the enclosed CFML code to JavaScript instead.

This of course just sets my alarm klaxons going. Because Adobe are (I choose my words carefully) [not very good] at converting CFML to client-side code. This has been borne out by <cfform>, <cflayout>, <cfpod> etc. Back in the days of CFMX7 the "CFML-to-client-side" wizards had some merit, because the client-side arena was still immature, and the team at Macromedia actually had some exposure to the idea of "website development", so they knew where the pain points were that they could possible ameliorate. Times have changed, and the client-side of things is probably now more mature an environment than CFML is - Javascript is probably are more coherent language than CFML is, now - and it is very very very clear that the current Adobe ColdFusion Team don't know the first thing about web development (they can't even write decent CFML for their own documentation, before we get onto how they'd be doing web work!), so they are completely out of their depth when it comes to addressing pain points that web devs might have these days. Not only have they not walked a mile in a web dev's shoes, they don't even - as far as I can tell - know what shoes are, or why someone would be wearing them.

And <cfclient> is a far more "meta" solution than <cfform> or <cfpod> were... at least the CFML-to-client-side solution there had a tangible target in mind. <cfclient> has removed the targets, and is just a tag designed for converting general CFML to general JS. Yikes.

600-odd words in, here's some code. This is the first-ever code I have written using <cfclient>:

<cfclient> <cfset msg = "G'day World"> <cfoutput>#message#</cfoutput> </cfclient>

So I'm off to a false start: I admit I'm sitting in the pub and I've had a few pints (probably four, I guess; this is "having some drinks before deciding to actually drink this evening" sort of level for me), and I inadvertently [messed-up] my variable names here. And this did not yield a compile error. The error just fell through to JS, where it did error

Uncaught ReferenceError: message is not defined gdayWorld.cfm:4

If, in contrast, I tried this in CoffeeScript, I'd get this:

coffee> msg = "G'day world"
'G\'day world'
coffee> alert msg
undefined
coffee>
alert message
ReferenceError: message is not defined
at eval (eval at (http://larryng.github.io/coffeescript-repl/js/main.js:96:26), :1:9)

Important note: I know nothing about CoffeeScript - it seems like a solution to a non-existent problem to me - so I just googled "hello world coffeescript" and REPLed the code on http://larryng.github.io/coffeescript-repl/.

The point is here is that ColdFusion, during the "compile" process should actually notice I am referencing a variable that doesn't exist. I'm OK with this being a runtime error in the normal CFML-compile process, because there could be many moving parts (and other files) involved in the runtime environment, but I don't think this is a valid notion with <cfclient>? Or maybe it is?

Update:

As Ray points out and Aaron agrees with below: I was being unduly harsh here... it's entirely reasonable for variables to be declared in other JS code elsewhere in the response.

Anyway, once I actually write my code properly, I get this:

G'day World

On the screen. What CF actually sends back in the response is this:

<script type="text/javascript" src="/CFIDE/cfclient/cfclient_main.js"></script> <script type="text/javascript" src="/CFIDE/cfclient/cffunctions.js"></script> <meta name="viewport" content="width=device-width"> <script type='text/javascript'>globalDivStruct=null;var _$gdayWorld_func=function(){var self=this;var variables={};self.__init=function(){var localdivstruct=globalDivStruct;var __output_var="";var tmpVarArray={};message="G'day World";localdivstruct.outputvar+=message;return""}}; function __startPage__$gdayWorld(){document.write("\x3cdiv id\x3d'__cfclient_0'\x3e\x3c/div\x3e");window.ispgbuild=false;var clientDivStruct={divId:"__cfclient_0",outputvar:""};globalDivStruct=clientDivStruct;try{_$gdayWorld=new _$gdayWorld_func;_$gdayWorld.__init()}catch(__eArg){if(__eArg!=="$$$cfclient_abort$$$")throw __eArg;}__$cf.__flush(clientDivStruct)}__startPage__$gdayWorld(); </script>

[Blimey]. To output a string variable? Really? That's what you compile my CFML down to?

Gobsmacked.

And [forget] emotive things like "gobsmacked"... if one looks at the size of the response, it's 128kB to represent "G'day World" on the screen. 128kB might not be a great deal these days when it comes to a web page, but when it comes to rendering "G'day world", it's lunacy. And on a mobile phone - which intrinsically might be in an area in which one is paying a premium for data - it's just irresponsible. This is before we get to the point that it seriously should not take 128kB of data to render 11 bytes.

Blimey. To be honest I was gonna try some more tricky CFML and see how it compiled, but I've run out of will to live (and I have to concede the beer is getting the better of me, and my laptop battery is almost dead). I'll continue this, but I will let this article stand or fall on its own merit; something <cfclient> certainly seems to be unable to do, thusfar.

I'll be back on the case with this tomorrow.

--
Adam

Adobe Community: Message List - Mobile

Illustrator Draw app mobile

Are you a PhoneGap expert?

flash player on our ipad and iphone

we need flash player on our ipad and iphone

Re: ColdFusion 11: ... how does normal CFML code and code interact?

Gossip

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

Re: ColdFusion 11: ... how does normal CFML code and code interact?

Re: ColdFusion 11: ... how does normal CFML code and code interact?

Re: ColdFusion 11: ... how does normal CFML code and code interact?

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

Re: ColdFusion 11: ... how does normal CFML code and code interact?

Re: ColdFusion 11: cfclient ports a lot of CFML functions to JS

ColdFusion 11: cfclient ports a lot of CFML functions to JS

ColdFusion 11: ... how does normal CFML code and code interact?

Attribute validation error for the client tag.

Update:

ColdFusion 11: seems to require /CFIDE to be available

ColdFusion 11: in the context of the CFML language, not the tooling

Update: