Hi Harm,

Obviously it will take time to write documentation, I personally wouldn't mind a big bump update on that for next release though

Quote Originally Posted by Harm Wibier View Post
What I get from here is you guys would like to have a more formalized public API that is documented a bit like the class ref? We could work on that, but it would need some time, and maybe you can help by letting us know the type of stuff you’d like to see in there?
Been thinking a bit about this.

For wrapping new controls you wouldn't have to document the javascript side of the normal controls like cWebForm, cWebGrid, cWebImage, cWebHtmlBox (and the long list of other controls).
But.... having said that, developers that want to extend on those controls, might want some basic documentation there anyways.

For developers working on wrapping new controls I suggest documenting things like (from the top of my head in no particular order):
- the core functionality in df.sys, df.dom, df.BaseApp
- documenting of the base controls df WebBaseUIObject, df.WebBaseControl, df.WebBaseDEO, dfWebBaseForm
- a basic example of how-to wrap a single entry item control and make it database enabled (eg. a rudimentary cWebBaseForm control)
- a basic example of how-to wrap a multiple entry item control and make it database enabled (eg. a rudimentary cWebBaseGrid control)
- document the internationalisation options and add examples, if you have customers using a different notation style for example for decimals, how to switch to what the user expects to see in their browser?
- the translation of the various data type(s) to javascript level (eg. client side / server side translations)
- document how-to send / receive larger data chunks between client & server

and no doubt, stuff I forgot about.
--
Wil