Sign in   or   Create free account

• Getting started
  • How Bildy works
  • Requirements
  • Licences
  • Installing Bildy
  • Hello world
    • Creating a data model
    • Creating a template
    • Creating content
• Using Bildy
• Template development
  • B:tags
    • b:page.field
    • b:page.metadata
      • b:page.metadata.path
      • b:page.metadata.url
      • b:page.metadata.name
      • b:page.metadata.parent
      • b:page.metadata.datamodel
      • b:page.metadata.id
      • b:page.metadata.template
      • b:page.metadata.created
      • b:page.metadata.modified
    • b:get
      • b:get.field
      • b:get.metadata
        • b:get.metadata.path
        • b:get.metadata.url
        • b:get.metadata.name
        • b:get.metadata.parent
        • b:get.metadata.position
        • b:get.metadata.datamodel
        • b:get.metadata.id
        • b:get.metadata.template
        • b:get.metadata.published
        • b:get.metadata.created
        • b:get.metadata.modified
      • b:get.recursion
      • b:get.resultdata
      • b:before
      • b:after
      • b:data
      • b:nodata
    • b:get.field
    • b:id.datamodel.field
    • b:structure
      • b:structure.recursion
      • b:structure.resultdata
        • b:structure.resultdata.count
      • b:before
      • b:after
      • b:data
      • b:nodata
      • b:structure.path
      • b:structure.url
      • b:structure.name
      • b:structure.parent
      • b:structure.position
      • b:structure.datamodel
      • b:structure.id
      • b:structure.template
      • b:structure.published
      • b:structure.created
      • b:structure.modified
    • b:structure.field
    • b:getcount
    • b:include
    • b:value.name
    • b:cookie.name
    • b:format
      • b:format.trim
      • b:format.condense
      • b:format.substring
      • b:format.date
      • b:format.removehtml
      • b:format.makehtml
      • b:format.lowercase
      • b:format.uppercase
      • b:format.capitalize
      • b:format.urldecode
      • b:format.urlencode
      • b:format.replace
      • b:format.sqlsafe
    • b:env
      • b:env.domain
      • b:env.root
      • b:env.request
      • b:env.get
        • b:env.get.field
      • b:env.post.field
      • b:env.extension
    • b:if
      • b:else
    • b:form
      • b:form.field
      • b:rule
    • b:validate
      • b:validate
      • b:before
      • b:data
      • b:after
    • b:sent
    • b:notsent
  • PHP API
    • B
    • API_GetStructure
    • API_GetData
    • API_CreateData
    • API_UpdateData
    • B_Content
  • Caching
  • Customizing 404 Error page
• Control development
• Bildy engine development

Control development

In Bildy a control is a single content field type that can be added to a data model. The way Bildy is structured makes it fairly simple and convenient to create new types of controls. It is not a task for beginners, but for experienced JS and PHP programmers it is very flexible and powerful way to create different types of content management fields. Imagination is the biggest limit.

We are working on control development documentation and will publish it as soon as possible.

A brief explanation of how Bildy controls are structured:

The Bildy editor portion

• control.xml describes the control and provides documentation
• control.js contains a MooTools style class with information needed to create the control in database table and the behavior of the control in Bildy editor. The sqlfields property in the class is also required by Bildy Engine, so this file is required when running a Bildy site.
• icon.png is the icon that's shown next to the control in data model view of Bildy editor
• input_settings.html contains the settings of the control that are accessible through the Bildy editor in data model view
• input.html contains the markup that represents the control in content editor in Bildy

The Bildy Engine portion

• control.php gives additional control to the control when it's used on the web site, such as formatting input from Bildy forms and Bildy editor, formatting output to web site and form validation
• output.php is optional and formats the output of control on the web site. Without output.php the data is output to the web site as it is in the database table
• webinput.php contains what's needed by Bildy to render the control in a Bildy form on the web site

A control may also contain any number of other files, but these files have a defined special function in Bildy.

To create a control properly you will have to wait for the documentation, but feel free to check out and experiment with the controls made by us. You can create a new control by just copying a control folder and renaming it. Don't forget to modify control.xml, control.js and conrol.php to avoid conflicts between controls.