Hi @all!
Additionally to the localisation thread I want to “extend” your thoughts a bit, before the project starts. Maybe you can consider the following stuff for the admin resource bundles in order to clean up the project.
Within the admin there are several duplicated files that just differ with some text and some ids.
Example:
\modules\contentbox-admin\views\pages\editorSelector.cfm
\modules\contentbox-admin\views\entries\editorSelector.cfm
\modules\contentbox-admin\views\contentStore\editorSelector.cfm
All files contains the following code
`
Insert From ContentStore
#html.endForm()#
The marked text parts are the only differences in the files. Green are the ids and red the text changes.
So when adding localisation to the project I would recommend to have a resource bundle per module. Additionally to that it would be cool to have a chance to add optional resource files to views, layouts and handlers.
With them you could overwrite the default text.
eg: admin.editorSelector.title= "Content insert" (Defined in the global resource file a default title..``)
For the page view you would now like to have another title. So you need to define a new resource bundle for that view or handler. The key would be the same: admin.editorSelector.title= “Link To A ContentBox Page”
This would give you the change to reduce duplicated templates to a widget for example. The IDs (green marked) for html elements could be passed in…
The optional resource bundles would have a priority. So the last defined key would count. So it goes from “Module resource bundle”-> handler -> layout -> view
Within the admin it could be used to have predefined button values for creating, deleting and so on in the global resource file. This would be enough for most pages, but if some button values should be “friendlier” you could define a new resource set for the handler or view to overwrite these keys and return something like “Save this page” instead of just “save”.
Let me know what you think…
Cheers Andy
