Hello Shaun, Martin.
Sorry for the late reply.
As you know, the structure of our RadControls
folder is pretty simple - it holds a r.a.d.control
folder, a folder with the product's version (for upgrading capabilities and to NOT overwrite any used/modified files), and a folder named Scripts which in turn has the file(s) which are needed by the control to function:
The only product (r.a.d.designer
excluded) that has more files and folders is r.a.d.editor
as it needs much more resources, such as popup dialogs, a spellchecker, etc.
Shaun, I am not sure that we will change this structure and will put all scripts in a single RadControlsScript
folder instead. The idea behind the structure above is proper upgrading - if you update/upgrade your application to a new t
elerik control or version, the old files will remain and you could easily revert back, if something breaks! If we include all scripts in a single RadControlsScript
folder, we will be back where we were 2 years ago, i.e. many upgrading problems, broken live applications, etc. We do not want this to happen again :)
What I suggested (our Developers should think over this suggestion, of course) is to have an extra RadControlsConfig
folder, which will hold:
- all telerik skins used in your app (there is no need to update those with every new release)
- a telerik.config file to keep common settings of all telerik controls (paths to skin folders, image directories, etc.)
- CSS files
- editor's ConfigFiles
- editor's ToolsFiles
- XML and other configuration files.
So, the final structure would be something, like:PROJECT ROOT
This way your project will say intact during the update process (as far as properties, skins and code goes). And you will update only the needed files (assemblies and JS files). What do you think of this setup?