Hi, Kevin
The definition UI controls I mentioned is just about the code orgnization
in VCLAuto Tools.
I want to define VCL controls in the same sequence as that on application
UI, and organize them by applications and dialogs, to make the items can be
found and maintained easily.
It doen't talk about AOO UI presentation.
Sorry for misleading you with my unclear expression. : )
Regards,
Shan Zhu
2012/7/19 Kevin Grignon <kevingrignon...@gmail.com>
> Shan Zhu,
>
> Could you point me to any documentation, or share any thoughts on the
> available styling options for our UI presentation (workspace and forms).
> I'm scoping a UI refresh and want to get a sense of what tailoring or
> customization is possible.
>
> Thoughts?
>
> Regards,
> Kevin
>
>
>
> On Monday, July 9, 2012, Shan Zhu wrote:
>
> > Hi, all
> >
> > In VCLAuto, we define the UI controls used in our script in UIMap.java.
> > Now, there is a long disordered list of UI controls, which will continue
> to
> > grow up.
> > For readability, I propose to group the definition of controls by Editor
> > and dialogs.
> >
> > 1. Put the definition of controls in same editor together, with a comment
> > line at the front to declare the editor name.
> > 2. Put the definition of controls in same dialog together, with a comment
> > line to declare the dialog name.
> > It would be better that if the sequence of the definition for a
> dialog
> > could following the UI arrangement in dialog.
> > For example,
> > // Spreadsheet: "Select Sheets" dialog
> > public static final VclDialog SCSelectSheetsDlg =
> > dialog(".uno:SelectTables");
> > ...
> > // Spreasheet: "Sort" dialog
> > ...
> > Moreover, suggest to add definition for other controls in one dialog,
> even
> > you've used few of them in your script writing.
> > And, a basic rule for variable name definition is needed, if necessary.
> >
> > Regards,
> > Shan Zhu
> >
>
