Blocks by AJAX comprises a number of complementary components:
First, use of the remote control block is entirely optional. By default, any Blocks by AJAX template will load a block when its DOM becomes visible. If that is the behaviour you require, you don't need to use a Remote Control block.
Before v2.0 of Blocks by AJAX, you could customise the AJAX loading behaviour by creating new templates with your own Blocks by AJAX settings.
The Remote Control block now provides an easy alternative enabling AJAX settings to be edited directly in the page. Each Remote Control block provides settings for one or more subsequent Blocks By Ajax templates.
Initial AJAX load
Repeat AJAX load
Magic Data integration
Magic Data integration is entirely optional and is not required for AJAX loading.
Also introduced with v2.0 of Blocks by AJAX is a simple Trigger block to show a link or button that, when clicked, will trigger the 'blocks_by_ajax' DOM event. The AJAX setting should be 'on_event', set either through a custom block template or through a Remote Control block.
Many blocks already have a Blocks by AJAX template. So check the Blocks by AJAX forum and/or ask the block develoepr see if a Blocks by AJAX template is already available.
Next, try the block in a Universal Content Puller block, Stack Randomizer block or Global Areas block with a with a Blocks by AJAX template. This will confirm that the block is actually loadable by AJAX and you are not wasting your time developing a custom template.
Full details on creating a custom template for other block types are given in the support pages.
Available separately through the marketplace is the Universal Content Puller block which includes pulling content from stacks, other page areas and anywhere on the web using a Blocks by AJAX template.
Universal Content Puller is also the best way of testing out a block for AJAX compatibility before creating a custom template.