- ColdFusion Developers Guide
- Develop ColdFusion applications
- Introducing ColdFusion
- Changes in ColdFusion
- Changes in ColdFusion
- Replacement of JRun with Tomcat
- Security enhancements
- ColdFusion WebSocket
- Enhanced Java integration
- ColdFusion ORM search for indexing and search
- Solr enhancements
- Scheduler enhancements
- Integration with Microsoft Exchange Server 2010
- RESTful Web Services in ColdFusion
- Lazy loading across client and server in ColdFusion
- Web service enhancements
- Displaying geolocation
- Client-side charting
- Caching enhancements
- Server update using ColdFusion Administrator
- Secure Profile for ColdFusion Administrator
- Introduction to application development
- The CFML programming language
- Building blocks of ColdFusion applications
- Develop CFML applications
- Develop CFML applications
- Design and optimize a ColdFusion application
- Handle errors
- Use persistent data and locking
- Use ColdFusion threads
- Secure applications
- Client-side CFML (for mobile development)
- Use the ColdFusion debugger
- Debugging and Troubleshooting Applications
- Develop globalized applications
- REST enhancements in ColdFusion
- Authentication through OAuth
- Social enhancements
- Develop mobile applications
- Access and use data
- ColdFusion ORM
- ColdFusion and HTML5
- Flex and AIR integration in ColdFusion
- Request and present information
- Office file interoperability
- ColdFusion portlets
- Work with documents, charts, and reports
- Use web elements and external objects
- Use external resources
- Send and receive e-mail
- Interact with Microsoft Exchange servers
- Interact with remote servers
- Manage files on the server
- Use event gateways
- Create custom event gateways
- Use the ColdFusion extensions for Eclipse
- Use the data services messaging event gateway
- Use the data management event gateway
- Use the FMS event gateway
- Use the instant messaging event gateways
- Use the SMS event gateway
Adobe ColdFusion Builder is End of Life from Oct 1, 2024
Thank you for being part of the exciting journey of Adobe ColdFusion Builder.
As Adobe continues to focus on ColdFusion Builder extension for Visual Studio Code as the IDE for Adobe ColdFusion, we have decided to End of Life (EOL) Adobe ColdFusion Builder on Oct 1, 2024.
View the End of Life (EOL) announcement for ColdFusion Builder.
ColdFusion Builder allows you to create a mobile application based on pre-defined templates. These templates are basically CFML files that can use third-party web frameworks like Bootstrap or jQuery Mobile. ColdFusion Mobile Templates enhance productivity, allowing few of your developers to focus on the design of your applications, while the other developers can focus on the functionality of the applications.
ColdFusion Builder supports 2 kinds of mobile templates:
- System templates - The bundled mobile templates.
- User templates - The templates created by you.
Structure of mobile templates
Your mobiles templates can be in a custom directory or an archive (.zip) file. User defined templates should be stored in <cfbuilder install>/templates/mobile/user. If you want to create your own mobile template, you need to have the following mandatory items in your template directory:
- config.xml - The configuration file for your template.
- <your_template_dir> - The directory containing the template files.
Note the following requirements:
You can provide a template name in the config.xml file as follows:
<template name="My Template">
If you do not provide a template name, the folder name or the archive (.zip) file name will be used.
Description can be provided in the configuration file:
The template description
</description>- You MUST specify one or more types in your template. Types are logical grouping of your templates. For instance, all jQuery Mobile based templates can be named as 'jQueryTemplates'. In this case, you need to have a corresponding directory, 'jQueryTemplates' at teh same level as config.xml file.
An example configuration file
The following example shows a valid configuration file, config.xml:
<template name="My Template"> <description> The template description </description> <types> <type value="jQuery" > <description> My mobile template containing jQuery Mobile files. </description> </type> <type value="javascript" /> <type value="bootstrap"> <description> My mobile template containing Bootstrap files. </description> </type> </types> </template>
For using the mobile templates, see Building Mobile Applications.