Skip to main content

ColdFusion Builder - A few tweaks

ColdFusion Builder sometimes might take a lot of time during startup or when a large project is imported into workspace. This post explains how one can change Builder settings to improve the startup experience.

Server settings:

If you have added a server to CFB, then you can see at the bottom right corner of the IDE that the CFCs are getting indexed. CFB uses the server settings to provide code assist for datasources, CFCs. This might take a lot of time since it indexes all the files in the webroot. This setting can be disabled in the preferences section. Navigate to Window -> Preferences -> ColdFusion -> Server Settings. Mac users can find Preferences under Adobe ColdFusion Builder (standalone) or under Eclipse (plugin installation).


CFB indexes all the CFCs located under webroot and mappings directory for the servers defined. By default these options are checked. One can uncheck 'Build server settings' and can observe that the build is not initiated when the CFB is started or when the server is started/added/refreshed. 

If the webroot or mappings path contain a few files then I would recommend users to keep the default settings  as it is since it would not take much time for the CFCs to get indexed.

Startup settings: 

ColdFusion Builder also provides an option of indexing files only in workspace and not the entire server webroot and mappings directory. This can be achieved by unchecking the options available under Server settings page (as explained in the previous section) and enabling 'Build CFCs in project on startup' under Preferences -> ColdFusion -> Startup. By default this is enabled.

If you are importing a very large project then I would recommend that you disable this option since it might take long time to index these project files. Once the project is imported successfully then enable this option and restart Builder. Indexing large project is always an expensive operation, however if one disables this then the code assist for the CFCs will not be shown.




Labels:

Comments

Post a Comment

Popular posts from this blog

File upload and Progress events with HTML5 XmlHttpRequest Level 2

The XmlHttpRequest Level 2 specification adds several enhancements to the XmlHttpRequest object. Last week I had blogged about cross-origin-requests and how it is different from Flash\Silverlight's approach .  With Level 2 specification one can upload the file to the server by passing the file object to the send method. In this post I'll try to explore uploading file using XmlHttpRequest 2 in conjunction with the progress events. I'll also provide a description on the new HTML5 tag -  progress which can be updated while the file is being uploaded to the server. And of course, some ColdFusion code that will show how the file is accepted and stored on the server directory.
18 comments
Read more

Server sent events with HTML5 and ColdFusion

There are several ways to interact with the server apart from the traditional request\response and refresh all protocol. They are polling, long polling, Ajax and Websockets ( pusherapp ). Of all these Ajax and Websockets have been very popular. There is another way to interact with the server such that the server can send notifications to the client using Server Sent Events (SSE) . SSE is a part of HTML5 spec:  http://dev.w3.org/html5/eventsource/
19 comments
Read more

Adding beforeRender and afterRender functions to a Backbone View

I was working on a Backbone application that updated the DOM when a response was received from the server. In a Backbone View, the initialize method would perform some operations and then call the render method to update the view. This worked fine, however there was scenario where in I wanted to perform some tasks before and after rendering the view. This can be considered as firing an event before and after the function had completed its execution. I found a very simple way to do this with Underscore's wrap method.
Post a Comment
Read more