Some general propositions...

Hello,

1. Create the possibility to put alone for each table the "Output Code Page" (some in UTF8; some in Europe occidental (Windows); some in Europe Central (Windows); etc. ?
   
2. Create one special interface -for each template- in the "Editor" for admin all the CSS style from the interface ?
   
   or some special module for admin the CSS for all the tables at the same time dynamically ?
   
   For example: For each PHPRunner template, make a special table in the database including all the Styles concerning all objects included in the files ADD; EDIT; VIEW; LIST; SEARCH; etc; and include in one PHP file all this CSS for admin later in the Super Admin, colors, fonts, sizes, paddings, borders, margins, text options, line options, shadows, backgrounds, images, round corners, fill, position, etc. ?
   
   This can make (maybe also) possible to create "themes" for the users and to make quickly very reach interfaces in short time.
   
3. Make a preview for the different pages (like we can see later in the browser) before to do all the compilation -inside PHPRunner-.
   
4. Save all the compiled pages -with no change- for accelerate the next compilation and to expense less time in the next compilation with only for the changed pages .
   
5. Create one external file (or one table in the data base) for each language. This make very much quick the do the translations. By the way, maybe is possible to group in only one place, all the words appear more than one time in the application, for translate them only one time. (Actually I work in one big application in 3 languages at the same time, and one customer want to add 3 new languages (Chinese, Arabian and one cyrillic language) as you imagine, this represent a very big time today. If you consider to include one external file for the languages in the future this became very possible to do this in a short time.
   
6. Create one external file (or table for the admin) automatically if we add in the EDITOR, properties "List values" from the "Lookup wizard" with this values. If we need later to drop or add new values here, with one external edition possibility, we don't need to recompile the application, just add or drop this values, in the database or external file.
   
7. Make possible to modify the look for the "import" page. Today, each time I do a very little change here, the Import button don't work. The only way for use them today is : (don't change nothing in the look interface for this page) ...
   Thank you for consider to include some or all this propositions in the next future.
   Mario