introducing dynFields™

In the making now for almost a year, dynFields™ has fast paced itself in the content management industry allowing dynamic web sites to go that one step further with their database interaction.

dynFields™ allows the developer to create dynamic links between tables and across multiple databases to link, sort, filter and build information with a click of a button and display it seamlessly to the end user.

dynamic fields

dynFields™ is comprised of 'pre-built' fields that allows the user to select and add into the database as they see fit. dynFields™ then takes the field information and applies dynamic information, formatting the field from a basic text box or text area into a interactive text box or a full WYSIWYG (what you see if what you get) editor. With the use of ajax and mooTools, dynFields™ opens up the possibilities on how you want your fields to be pre-formatted before displayed to the end user.

Some of the pre-built fields within the dynFields™ API are:

• Text Box
• Password Field
• Dynamic Select Box
• Dynamic Multiple Select Box
• Textarea
• Checkbox
• Radio Button
• File Upload Field
• Date/Time Field
• Hidden Field

All available fields to the end user allow them to set their own tool-tips, custom error messages, select if the field is required on add or edit, select if the field is shown on add or edit plus much much more... Infact so much more functionality we possibly couldn't type it all on one (1) A4 sheet of paper at 6px (really really small). We can supply more indepth information about dynFields™ on request.

developers & dynFields™ ?

When developing dynFields™ we had developers in mind, becasue, we are developers too. There are two different levels of dynFields™ available within fooBar CMS. The developer, with a valid developer license, is granted access to the dynFields™ developer console where alot more functionality is opened up and pretty much allows developer to add field widgets, edit javascript files, load custom ajax scripts, write programming hooks, set xml output fetching to load external information from another database tables based off field data stored in mySQL and load custom php functions on $_POST for add, edit or delete actions sent to dynFields™.

dynFields™ opens up the playground for developers and we guarentee they won't be able to use all it's functionality in just one day! In a nut shell you can create small to medium size web applications for fooBar CMS using dynFields™.

You said field widgets?

Yes, let us explain...

Not only does dynFields™ allow you to add pre-built fields, with the developer console you are able to add Status, Display Order or Non-Removable Entry widgets into the system.

Status Widget:

The Status Widget is a basic (int) field used to display if the record is currently active or not, mainly used for accounts, products, groups or email templates. With a click of a button you can change the status from On to Off or vice-versa.

Display Order Widget:

Want to have your records sorted in a list and only in the order you want them? We have the solution, the Display Order Widget allows you to move entries up or down within the list, also turning off any other field sorting functionality so your entries display in the order you set them.

Non-Removable Entry Widget:

Got some information you don't want removed by limited Administrators or Moderators? Using the Non-Removable Entry Widget you can 'lock' entries from being deleted, since the Widget is permission based you can select what users are allow to remove the entries or change the entry back to a normal entry that can be removed.

clustering & synchronization

Want to run more than one fooBar CMS with dynFields? We've got you covered...

Using xml-rpc we have built into the dynFields API a means to 'synchronize' two or more systems based off a 'master' CMS. What this means in a nutshell is; the ability to have secondary CMS's to update on the fly when the 'master' CMS is updated.

A command is sent via an encrypted and authenticated connection to all secondary server(s) accessing the information that was just updated; giving fooBar CMS the ability to 'cluster' or 'synchronize' itself with other fooBar systems. Each secondary server has an authentication key it uses to talk to the master server and vice-versa; also the secondary systems can be installed on sub-domain(s) or other domain(s) on seperate servers giving you optimal performance for your web sites and the reassurance your data will be kept up-tpo-date!

How do you restrict what secondary servers are allowed to be sent commands?

With your license key for fooBar CMS you have a ability to purchase secondary domain licenses (prices may vary per reseller), that will allow you to install your CMS onto another domain(s) or sub-domain(s). Each secondary license key allows you to install one (1) CMS per domain/sub-domain.

What if a connection cannot be established at the time upon update?

The system knows when it cannot create a connection to the secondary server(s) and, via cron will check every minute (by default, this option can be set in the dynFields settings within the fooBar CMS console) untill it has created a successfull connection.

How does the parent or main CMS know what secondary server(s) to update?

When an authenticated connection has been made for the first time from a secondary server that information is stored within the parent or main CMS database. When an update occurs, the parent or main CMS knows what secondary server(s) require updating. A command is sent to all secondary server(s) to request the updated information.

So when an update occurs from the parent or main server it only tells the secondary server(s) to request the information, it doesn't just send it?

That's correct. A command is sent to the secondary server(s) telling them to request the updated information.

step by step forms

Got a registration form that just massive? Then we've got your answer!

An extension to the dynFields API is the stepByStep feature. You can setup multiple stages or steps as we like to call it, tell each step what fields are to be requested, then just let dynFields build it for you.

It's really that simple.

Want tabs?

No worries, a command can be sent telling dynFields stepByStep what layout to use.

What about AJAX?

Too easy, again we just tell dynFields stepByStep we're using AJAX to handle the form and special commands are used via AJAX to tell dynFields stepByStep where to go and what to load.

How about loading fields from multiple databases?

Now that's tricky, but we already thought of that.

When setting up your stepByStep form you can simply tell it what fields to load and from what table. You can also have your fields mixed around, so load 4 fields from table 1 then 2 fields from table 2 and so on and so forth, then arrange them in the order you specify.

How do you manage the ordering of the fields per step?

We have built a full GUI (Graphical User Interface) for the stepByStep system so you can manage your form with ease.

did somebody say mocha?

Even though we drank alot of it developing this system we managed to add it in, well sort of.

Mocha is our window based popup system without the popup. Confused yet? Maybe we drank too much. No seriously, it's a <div> based window that overlays ontop of the fooBar CMS console allowing you to load content via XHR (the traditional XMLHttpRequest), AJAX (the soon to be standardized XMLHttpRequest) or just in a simple iFrame.

Originally created by Greg Houston we intergrated it into the fooBar CMS.

So what does this have to do with dynFields?

Well, we added in commands so that any option icon, <tr> or <td> tag, link, text, pretty much anything you can click has the ability to load a Mocha window or Modal window (A dialog that must be closed before the user can take further action).

Want to see it in action?

Then check it out in our code examples section or check out the fully featured Mocha Desktop system (not used in fooBar CMS currently) at Greg's web site.

ajax, oh how we love it

AJAX is used heavily in our system but not in the tradition of most content management systems. We still refresh a lot of pages instead of loading it dynamically with AJAX, but in good reason because we make up for it in other areas.

With a lot of features in fooBar CMS and dynFields the client or administrator has the option to change the settings allowing more customisation to his or her preferred environment. One of those is performance! We use AJAX to load our <select> tags, multi <select> tags, drop down content, Mocha window content, PM (private message) Notification windows and alerts and most importantly our AJAX Extension system.

Now the AJAX Extension system is pretty big so we're just going to cover the basics for you.

The AJAX Extension or AJAX Ext is the portal to allowing Javascript to talk to the dynFields and fooBar API. Using the dynFields hook system a developer can write AJAX Applications using these API's and their own! It allows full interaction with any installed module within the fooBar CMS. Posting information to the dynFields API for either custom front-end systems or loading templates via the fooBar API.

With this sort of functionality you're not limited to static page refreshes to $_POST information to dynFields or retrieve it. Special commands are available for dynFields to return errors for $_POST or return XHTML for dynamic forms built on the fly.

This is just a tip of the iceberg, but we're going to leave it at that. The possibilites are endless, it's just up to how you want to utilize the functionality available at your finger tips!

want to know more...

We would love to have everything listed on what dynFields™ can do for you and your clients however we'll gladly send you a full information kit on request. Check out the contentManagement page for more information on fooBar CMS and the modules available.

To request more information on dynFields™ just use our contact form and we'll have one of our sales staff get in contact with you.