MSEide+MSEgui/es: what changed

Revision 2 to 3. Removed lines have a minus sign; added lines have a plus sign.

Old	New		Line
1	1		# Introducción
2	2
3	3		MSEide es un sistema de desarrollo gráfico (GUI) de plataforma cruzada orientado a programadores de Pascal. Está completamente escrito en Pascal. MSEgui no aporta compatibilidad con la librería de componentes visuales (VCL). La librería de gráficos aporta un interface con win32 y X11. Hay que tener en cuenta que es un proyecto fruto del esfuerzo en casi su totalidad de una persona (Martin Schreiber),
4	4
5	5		El IDE y GUI tienen un listado de muy buenas características:
6	6
7	7		- La codificación de caracteres es UCS2.
8	8		- Incluye utilidades de internalización.
9	9		- Docking forms.
10	10		- Embedded forms (similar to TFrame).
11	11		- Visual form inheritance.
12	12		- Enlaces a xlib y gdi32, no necesita de librerias de widgets externas.
13	13		- Componentes de acceso a bases de datos y widgets de edición de datos.
14	14		- Depuración integrada.
15	15		- Integrated report designer.
16	16		- Flexible and handy build system with switchable macros.
17	17		- y más...
18	18
19	19		## Pero, ¿que acerca de Lazarus?
20	20
21	21		[Lazarus](http://www.lazarus.freepascal.org) es un IDE que trata de aportar un alto grado de compatibilidad con código VCL, al tiemo que aporta un aspecto nativo en bastantes plataformas. La visualización nativa es muy importante para bastantes desarrolladores, pero combinada con la compatibilidad VCL hace necesarias interfaces complejas a los diferentes conjuntos de widgets nativos (GTK, Win32, Carbon, QT...). La continua evolución de este conjunto de widgets nativos (GTK1 -\> GTK2, Win32 -\> ?, , QT) conlleva un interminable conjunto de mantenimientos.
22	22
23	23		[MSEide+MSEgui](http://sourceforge.net/projects/mseide-msegui/) neither features (or suffers :-) de compatibilidad VCL, no provee un aspecto nativo en las plataformas objetivo. La librería de gráficos provee un interface a Win32 y X11. La ventaja de la capa X11 es la inmediata disponibilidad de un largo y estable conjnto de plataformas a lo largo del tiempo.
24	24
25	25		Estas diferentes finalidades de ambos proyecto hace que se adapten a las distintas necesidades de los programadores.
26	26
27	27		## ¿Porqué esta wiki?
28	28
29	29		El diseño de MSE GUI es una fresca aproximación a los patrones de diseño GUI. Aporta bastantes características innovadoras para tareas típicas de un inteface gráfico de usuario (GUI). Siendo innovador, la librería MSE GUI difiere sustancialmente de VCL/LCL/CLX. Pasar de VCL a MSE puede suponer mucho más cambio que cambiar desde [[Code Conversion Guide\|VCL o LCL]]. Estas páginas de la wiki tratan de mostrar facilmente los primeros pasos con esta prometedora (IDE & GUI) librería alternativa.
30	30
31	31		# Instalación
32	32
33	33		- Versión actual: 4.6.2 (03/11/2108).
34	34		- Referencia autoritativa: [MSEide+MSEgui homepage](http://mseide-msegui.sourceforge.net/) con instrucciones de instalación.
35	35		- Página principal cooperativa homepage: [MSEide+MSEgui](http://www.msegui.com/)
36	36		- Descargas: [Sourceforge](http://sourceforge.net/projects/mseide-msegui/files/)
37	37		- Trabajo en progreso: [git](https://gitlab.com/mseide-msegui/mseide-msegui)
38	38
39	39		# Quick start
40	40
41	41		## Abriendo un proyecto
42	42
43	43		Lanza el IDE y utiliza Project-\>Open para abrir la demo de msegui/apps/demo/demo.prj. El título del IDE refleja el proyecto que hemos abierto. Pulsa F9 y (si has seguido las instrucciones de instalación correctamente :-), disfruta de la velocidad de FPC+MSE.
44	44
45	45		## First RAD steps
46	46
47	47		Close the running project. Use Project-\>Source to open the project source demo.pas. Ctrl-click on the parameter mainfo in the line
48	48
49		-	~~`application.createform(tmainfo,mainfo);`~~
	49	+	```text
	50	+	application.createform(tmainfo,mainfo);
	51	+	```
50	52
51	53		to navigate to main.pas. Click on F12 to toggle between unit and form. Not everything will feel that familiar, because of that, these pages are written. Click on the button, this will auto raise the property editor (unusual but usefull). Let us add another button. Make the component palette visible if necessary (View-\>Toolbar-\>Component Palette). Select the tbutton on the widget page. Click on the form to create the button. Give it a caption in the usual way. Creating an event handler does not work with the usual double clicking on the onexecute property. Instead, you must select the onexecute property in the property editor, type the name of an event handler and press enter. The MSE RAD will create the handler and position the pointer on the definition. Use ctrl-shift-down arrow (or up) to navigate between implementation and definition. Just add some code like writeln('Hello world'); Hit F9. The writeln will end up in the target console window of MSE (not the console in which you started MSE).
52	54
53	55		## Adding a Main Menu
54	56
55	57		### Add Main Menu
56	58
57	59		Add a tmainmenu component from the Gui component tab to your main form. Click on your mainform (mainfo), so that Object Inspector shows the properties of the mainform. Use the arrow next to the mainmenu property of the mainform, to select tmainmenu1 as the mainmenu of mainfo.
58	60
59	61		### Add Menu Items
60	62
61	63		In the Object Inspector, expand the mainmenu branch. In this branch, open the menu property of mainmenu. Change the submenu.count of menu to 1 (or higher). Now expand the submenu.count property, which will show "Item 0". Expand "Item 0" and set the caption, for instance to "&File". Now you can repeat the same procedure one level deeper... Change the submenu.count property of "Item 0" to 1. Expand this last submenu.count property and set the caption of the new "Item 0", for instance to "E&xit". Hit F9 and your program should have a menu File with the entry Exit in it.
62	64
63	65		Alternatively, in Object Inspector you may right click a submenu.count property, or an "Item n" property, which will reveal a context sensitive pop up menu. Use this pop up menu to insert, append or delete menu items.
64	66
65	67		Once you have more than one submenu, you can use drag and drop to move the menu items ("Item n"). Start the drag mouse move on the "Item n" line.
66	68
67	69		## Crear un nuevo proyecto
68	70
69	71		Para crear un nuevo projecto basado en una plantilla utilizar Project -\> New \> From Template. Para un nuevo proyecto GUI seleccionar "default.prj", y para un proyecto de consola seleccionar "console.prj".
70	72
71	73		# El concepto
72	74
73	75		MSEgui es una librería de programa escrita en Pascal, aporta los bloques de construcción para el desarrollo de programas con interface gráfico de usuario.<sup>1</sup>
74	76
75	77		MSEide es el correspondiente entorno de desarrollo integrado (IDE) para la producción efectiva con Free Pascal y MSEgui. MSEide es también apropiado para el desarrollo de aplicaciones con gcc y microcontroladores.
76	78
77	79		Actualmente MSEide+MSEgui corre bajo i386-linux, x86-64-linux, arm-linux, x86-64-freebsd, i386-win32 y x86-64-win64 mientras que los microprocesadores soportados son CPU32, ARM and AVR32. MSEgui es predominantemente una plataforma independiente. Se pueden añadir plataformas adicionales implementando los elementos dependientes del sistema. Los módulos dependientes del sistema de MSEgui se encuentran ubicados en subdirectorios dentro de lib/common/kernel.
78	80
79	81		## Principales finalidades del desarrollo
80	82
81	83		- Una relevante incremento en la productividad. comparado con otros sistemas de desarrollo.
82	84		- Idéntica apariencia y funcionalidad en todas las plataformas, sin adimentos medibles en el código de usuario.
83	85		- La dependencia de librerias adicionales de mantiene al mínimo posible.
84	86		- Ortogonalidad - debería haber la mínima interferencia posible entre los diferentes elementos de programa y tan pocos como sea posible a nivel de escepciones y casos especiales.
85	87		- Elementos del interface gráfico de usuario (GUI) altamente parametrizados.
86	88		- Trabajando con MSEide+MSEgui debería ser agradable.
87	89
88	90		## Architecture overview
89	91
90	92		MSEgui no requiere de librerias de componentes externas - , se comunica directamente con el interface gráfico del sistema operativo. Con X11 a través de Xlib en Linux y con gdi32 bajo Windows.
91	93
92	94		Para los elementos individuales del GUI no se necesitan recursos adicionales del sistema operativo - únicamente las ventanas principales son conocidas pore el sistema operativo. El procesado completo de los eventos externos (teclado, ratón, control del foco, ...) tiene lugar dentro de MSEgui a nivel de Pascal.
93	95
94	96		La clase base para los elementos del GUI es un `twidget`. No hay distinción entre elementos gráficos simples y los que puedan recibir el foco, como es el caso en Delphi. Todos los widgets de MSEgui tienen a su disposición la funcionalidad completa de un `twidget`.
95	97
96	98		Importantes característica de un `twidget` son: `twidget.frame` y `twidget.face`. Cuando no se utilizan frame o face se representan mediante un puntero NIL, de forma que no consuma recursos.
97	99
98	100		`twidget.frame` es responsable del frame around del área de trabajo del elemento. La apariencia del frame es altamente ajustable - puede ser simle y rápidamente ser dibujable mediante un frame 3D, al tiempo que una compleja y lenta estructura basada en imágenes. Hay además otros elementos del frame que pueden construir barras de desplazamiento, pulsadores y etiquetas.
99	101
100	102		`twidget.face` dibuja el fondo del área de trabajo de un elemento del escritorio del GUI - de forma que se pueden mostrar gradientes de color e imágenes de maneras diferentes, mientras que se permite también una transparecia parcial.
101	103
102	104		Setting the properties of frame and face can be centralised by using `tframecomp` and `tfacecomp`, which can be selected into `tframe` and `tface` as templates.
103	105
104	106		The next level of centralization is `tskincontroller`, through which program-wide settings can be made. In order to achieve that, `tskinkontroller` assigns to the GUI elements the appropriate `tframcomp` and `tfacecomp` templates.
105	107
106	108		The control of the widget functions (focusin, focusout, ...) is done by virtual procedures and functions and not through messages. The MSEgui message function has other tasks. Also a Corba-style interface is used - for the safe connection between the various components and the automatic disconnection through destroy, a `tobjectlinker` is used.
107	109
108	110		The type `msestring` is used in MSEgui for storing text. At the moment, msestring equals WideString. However, the reference counted FPC WideString (UnicodeString) is planned to be used under Windows, as soon as it becomes available in one of the future FPC releases.
109	111
110	112		In text files the utf-8, ASCII or the local encoding is used - MSEide+MSEgui does not use utf-16 files.
111	113
112	114		The MSEgui database components provide the conversion from the local encoding or the utf-8 (adjustable) to WideString for the data buffering. For file operations, a set of MSEgui's own functions with WideString interface exists. An MSEgui application can therefore work consistently with WideStrings, which is a significant relief for some tasks.
113	115
114	116		Specialized data edit widgets for the basic data types (integer, real, tdatetime, ...) are available in MSEgui (`tintegeredit`, `trealedit`, `tdatetimeedit`, ...). The main event property of these widgets is `onsetvalue`, which can be used for reacting upon user input.
115	117
116	118		The `t*edit` widgets can be inserted into a `twidgetgrid` and in that way form a column of the appropriate data format.
117	119
118	120		For viewing and editing of data fields a `tdbwidgetgrid` togeather with a set of `tdb*editwidget`s can be used. Worth mentioning are also different lookup components and a `tlookupbuffer`, a fast associative data memory.
119	121
120	122		The basic component of the MSEgui's database environment is `tmsebufdataset`, from which `tmsesqlquery` is derived. MSEgui DB is a fork of the FPC SQLDB system, where TBufDataset and large parts of TSQLQuery and the connection components have been completely rewritten.
121	123
122	124		`tmsebufdataset` offers local indices, calculated and internalcalc-fields, a mode with an interrupted database connection, an in-memory mode where no database connectivity is necessary and can keep a local journal, in order to later reconect a previously disconnected database connection. `tmsebufdataset` stores texts as WideStrings of variable length.
123	125
124	126		Further, there are SQL script components and `tsqlresult` for quick queries without the TDataset overhead. Persistent TField instances are either kept within `tmsesqlquery`, where they can be edited in the object inspector via `tmsesqlquery.controller.fields`, or they can be inserted into forms or modules as as individual components from the 'DBf' component palette.
125	127
126	128		MSEide supports 'visual form inheritance', Submodule (Delphi TFrame equivalent) and allows the assignment of components of other forms or modules to component properties at design time.
127	129
128	130		Internationalization is done via resource modules that are loadable at runtime. The MSEi18n, a tool that supports the import and export of texts in spreadsheet programs is available for editing - therefore facilitating a translation by nonprogrammers.
129	131
130	132		<sup>1</sup>) This chapter is based on a translation of a German text provided by Martin Schreiber.
131	133
132	134		# Tips: MSEide
133	135
134	136		## Larger fonts
135	137
136	138		Some may find the standard menu font a bit small. The standard font for the main menu of an MSEgui application is the font defined by the stf_menu stock font. You can change a stock font value with a startup parameter, \<fontheight\> is given in pixels.
137	139
138		-	~~`--FONTALIAS=<alias>,<fontname>[,<fontheight>[,<fontwidth>[,<options>]]]`~~
	140	+	```text
	141	+	--FONTALIAS=<alias>,<fontname>[,<fontheight>[,<fontwidth>[,<options>]]]
	142	+	```
139	143
140	144		So if you start the mseide like this, you can get a larger menu font:
141	145
142		-	~~` mseide --FONTALIAS=stf_menu,sans,16`~~
	146	+	```text
	147	+	mseide --FONTALIAS=stf_menu,sans,16
	148	+	```
143	149
144	150		In order to increase the base font size for all stock fonts use
145	151
146		-	~~` mseide --FONTALIAS=stf_default,,16`~~
	152	+	```text
	153	+	mseide --FONTALIAS=stf_default,,16
	154	+	```
147	155
148	156		## Shortcuts
149	157
150	158		Common
151	159
152	160		- Ctrl+F4 - Close
153	161		- Ctrl+S - Save
154	162		- Ctrl+E - Select page
155	163		- F11 - Toggle Form/Inspector
156	164		- F12 - Toggle Form/Unit
157	165		- Shift+Ctrl+\[0..9\] - Bookmark 0..9
158	166		- Ctrl+\[0..9\] - Go to bookmark 0..9
159	167		- Ctrl+LeftClick - Go to var(class, method, unit) declaration
160	168		- Shift+Ctrl+Up - Go to method declaration
161	169		- Shift+Ctrl+Down - Go to method implementation
162	170		- Shift+Ctrl+Space - Show procedure header
163	171
164	172		Debug
165	173
166	174		- F7 - Step
167	175		- F8 - Next
168	176		- F9 - Continue
169	177		- Shift+F7 - Finish
170	178		- Shift+Ctrl+F8 - Next instruction
171	179		- Shift+Ctrl+F7 - Step instruction
172	180		- F5 - Toggle breakpoint
173	181		- Shift+F5 - Toggle breakpoint enabled/disabled
174	182		- Ctrl+B - Breakpoints on/off
175	183		- Ctrl+W - Watches on/off
176	184
177	185		Editor
178	186
179	187		- Ctrl+Z - Undo
180	188		- Ctrl+X - Cut
181	189		- Ctrl+C - Copy
182	190		- Ctrl+V - Paste
183	191		- Ctrl+F - Find
184	192		- F3 - Search again
185	193		- Ctrl+L - Go to line.
186	194		- Ctrl+I - Indent block
187	195		- Ctrl+U - Unindent
188	196
189	197		## Print from IDE
190	198
191	199		You need the [ghostscript](http://ghostscript.com/awki)
192	200
193	201		## Recent opened files or projects
194	202
195	203		The last opened projects are in the dropdown list of 'Project'-'Open'-'Name'. The last opened files are in the dropdown list of 'File'-'Open'-'Name'.
196	204
197	205		## Menu Editing
198	206
199	207		- Use submenu.count to set the wanted menu items count.
200	208		- Right click on submenu.count or on a menu item "Item X" to display a context-sensitive menu that allows to insert,append or delete a submenu entry
201	209		- Use drag and drop on a submenu entry to move the the item in the array.
202	210
203	211		## New Panels in the IDE
204	212
205	213		Example, you want to have the watch, stack and cpu window in a window:
206	214
207	215		- select the menu item View-Panels-New Panel.
208	216		- select the menu item View-Watches.
209	217		- drag the Watches window by the grip (not the window title!) in the new panel.
210	218		- same with Stack and CPU window.
211	219		- to split horizontal drag one of the grip of the inserted widgets to the left border of the panel.
212	220		- to split vertical drag one of the grip of the inserted widgets to the bottom border of the panel.
213	221		- to use tabs drag one of the grip of the inserted widgets to the centre of the panel.
214	222
215	223		## Design Tab-Order
216	224
217	225		Main way in MSEide is set the tab order after all widgets are placed in the form with the popup menu function "Set Tab Order". Select a widget in the container where you wish to set the tab oder, click right, click "Set Tab Order", click row 0, click "Start", click the widget in the container which should get tab order 0, click the widget which should get tab order 1..
218	226
219	227		An alternative is to drag and drop the rows to the desired position. The first row corresponds to the tab order 0 the second to the 1 and so on.
220	228
221	229		### Creating a new event handler
222	230
223	231		Select the event you want in the Object Inspector, then type name of the new event handler. IDE create a new procedure(declaration and implementation) in the source code. If you double-click the name of the event handler in the Object Inspector, source editor opens with the cursor at begin of your handler implementation.
224	232
225	233		# Tips: MSEgui
226	234
227	235		## Tabbed control
228	236
229	237		- Put ttabwidget control on the form. Now you have container (ttabwidget1) for pages.
230	238		- Put as many ttabpage controls on the ttabwidget1 as tabs you want.
231	239
232	240		## Splitter
233	241
234	242		We have two widgets (widgetLeft, widgetRight) and we need horizontal splitter between them.
235	243
236	244		- Add TSplitter to form and resize it as you want.
237	245		- Change the linkleft of tsplitter1 to widgetLeft and linkright to widgetRight. At this step our widgets stick to splitter.
238	246		- Change the spo_hmove to True. That's all.
239	247		- If you want to save a proportion between width of widgetLeft and width of widgetRight when the main form is resized then change the so_hprop to True.
240	248		- If you need the vertical splitter then use other properties linktop, linkbottom, spo_vmove, spo_vprop.
241	249
242	250		## Switch-off auto-scrolling of the form(widget)
243	251
244	252		Change the container - frame - sbhorz - options - sbo_showauto property of the form to False.
245	253
246	254		## Read/write data in the twidgetgrid
247	255
248	256		- editwidget.value -\> value of the actual row
249	257		- editwidget\[rowindex\] or editwidget.gridvalue\[rowindex\] -\> value of the addressed row
250	258		- editwidget.gridvalues the whole column as a dynamic array.
251	259
252	260		## First events
253	261
254	262		OnCreate is called before loaded procedures of the components of the form are called, OnLoaded is called after loaded procedures of the components of the form are called. Many components do initializations in loaded procedures, event properties are inactive before procedure loaded of the component is called.
255	263
256	264		## MDI
257	265
258	266		MDI - application can be created using TDockFormWidget or TDockPanel (as MDI-area) and TDockForm (as ancestor for you MDI-child window). There are examples:
259	267
260	268		- How to use TDockForm with custom MDI-buttons <http://brefi.narod.ru/mdi_example2.tar.gz> or in \$MSESOURCES/contributed/ivankob/examples
261	269		- Simple MDI-controller (create, switch, ... the child windows) <http://mihafpc.narod.ru/MDISample.tar.gz> or in \$MSESOURCES/contributed/miha
262	270
263	271		## Drawing
264	272
265	273		### Redraw form the additional thread
266	274
267	275		Use a tthreadcomp (tab Gui) to do the long time procedure. If you need to access widgets and other gui variables from the additional thread, call application.lock before and aplication.unlock after accessing the main event thread elements.
268	276
269	277		### Force repaint
270	278
271	279		- twidget.invalidate to invalidate an individual widget
272	280		- twidget.rootwidget.invalidate to invalidate the window
273	281		- application.invalidate to invalidate all windows (=forms) in the application
274	282
275	283		### Draw text
276	284
277	285		There are two methods to draw texts in MSEgui:
278	286
279	287		- Simple text positioning by baseline position of start of the first character with tcanvas.drawstring.
280	288		- With the drawtext procedures of msedrawstring.pas.
281	289
282	290		### Widgets canvas
283	291
284	292		No twidget has a canvas. The canvas used for painting is normally one of the canvas of twindow, it can also be an canvas of a tbitmap or a tprinter or... MSEgui uses one canvas to paint a whole window with all widgets. tcanvas.font is initialized by twidget.getfont, canvas.color by twidget.actualcolor before calling twidget.dopaint, see twidget.paint procedure in msegui.pas.
285	293
286	294		### Theming (Frames & Faces)
287	295
288	296		Every twidget has a property frame and face. If they are deactivated (\<disabled\> in object inspector) they are only an nil pointer and need no more resources. Activate them by clicking on the ellipse button in the right object inspector column in the row face respective frame.
289	297
290	298		The face property defines the background of the client area of the widget.
291	299
292	300		It is a combination of a fade and a bitmap. Both of them can be semitransparent. The bitmap can be stretched and/or tiled. Example: you want to create a button with a fade as face.
293	301
294	302		- place a tbutton on the form.
295	303		- in object inspector activate property face.
296	304		- set face.fade.color.count to 2.
297	305		- click on the + at color.count.
298	306		- in item 0 select cl_gray.
299	307		- in item 1 select cl_ltgray, now you have a left to write fade from gray to light gray.
300	308		- change face.fade.direction to gd_up or gd_down, you get a convex resp. concave fade.
301	309
302	310		If you want, you can blend an additional structure over the fade:
303	311
304	312		- select the wanted pattern image in face.image.
305	313		- activate face.image.alignment al_tiled.
306	314		- adjust face.image.transparency to your needs, \$000000 = opaque, \$ffffff = fully transparent. The number defines the transparency of the three color channels (\$RRGGBB).
307	315
308	316		To centralise the face look use an tfacecomp (tab Gui) and select the facecomp in template of the face properties.
309	317
310	318		The frame property defines the look of an additional frame around the component and shows a possible caption at the widget. Example: you want an lowered frame around and a caption right of the button.
311	319
312	320		- activate property frame.
313	321		- set frame.levelo to -1.
314	322		- set frame.leveli to 1.
315	323		- enter the caption text in frame.caption.
316	324		- set frame.captionpos to cp_right.
317	325
318	326		To centralise the frame look use an tframecomp (tab Gui) and select the framecomp in template of the frame properties.
319	327
320	328		### Desktop colors in the MSE application
321	329
322	330		Default values of the mapped colors stored in the array msegraphics.defaultmapped. For change it's values you can use function msegraphics.setcolormapvalue [Win32 and KDE example](http://www.freepascal.org/wiki/index.php/User:Miha) (\$MSESOURCES/contributed/miha/GuiStyle.pas)
323	331
324	332		# Aplicaciones de ejemplo y pantallazos
325	333
326	334		## Una aplicación utilizando Firebird
327	335
328	336		Los siguientes pantallazos se han tomado desde una aplicación de bases de datos con Firebird que utiliza MSEgui. El programador indica que ha personalizado el aspecto y comportamiento de su aplicación en unos 30 minutos utilizando un tfacecomp y dos tframecomp y ha constatado que el aspecto y comportamiento es idéntico tanto en Linux como en Windows.
329	337
330	338		![](/wiki-images/e/ea/Mse_dbwidgetgrid2.jpg)
331	339
332	340		Versión utilizando Linux: ![](/wiki-images/c/c0/Mse_form1.jpg)
333	341
334	342		Versión utilizando Windows: ![](/wiki-images/8/8a/Mse_form1w.jpg)
335	343
336	344		Versión utilizando Linux: ![](/wiki-images/a/ab/Mse_button1.jpg)
337	345
338	346		Versión utilizando Windows: ![](/wiki-images/6/65/Mse_button1w.jpg)
339	347
340	348		El reporte ha sido diseñado y renderizado con el diseñador y generador de reportes del MSEide+MSEgui embebido.
341	349
342	350		![](/wiki-images/2/2e/Mse_report1.jpg)
343	351
344	352		Dos forumularios MDI con frame fade y flat.
345	353
346	354		![](/wiki-images/1/18/Mse_gripfade1.png)
347	355
348	356		## Un sistema embebido
349	357
350	358		Un sistema embebido para aplicaciones médicas, en este caso esterilizadores steam, fue realizado con MSE-IDE & MSE-GUI con la unidad de conrol, nowadays además comunmente llamado "human machine interface", HMI.
351	359
352	360		![](/wiki-images/d/d4/MainScreen.png)
353	361
354	362		La unidad de control utiliza un panel táctil como display, por lo que todos los controles activos necesitan ser suficientemente largos para que el personal pueda manejarlos a mano facilmente. La pantalla principal consiste de unos pocos campos informativos que permiten seleccionar los procesos de esterilizado por meido de un menú consistente en varios componentes pulsadores con sus correspondientes nombres descriptivos junto con una breve descripción de su funcionalidad en un panel separado. La visibilidad de los pulsadores y sus captions se definen durante la carga del programa mediante un fichero de configuración. Los campos informativos muestran los valores de operación de los dispositivos en tiempo real utilizando un timer de sistema MSE para recolectar la información desde un PLC.
355	363
356	364		![Process Display](/wiki-images/2/2b/ProcessDisplay.png)
357	365
358	366		After processing has been started, the display is switched to a different format showing the operating values in large digits on some numeric display field components on the left and a graphical representation of the process history on the right, again both as real time "live displays". If the diagram curves would reach the right panel border, the diagram would change to a scrolling mode, always showing the current state at the extreme right.\
359	367
360	368		![State Display](/wiki-images/b/b2/StateDisplay.png)
361	369
362	370		For diagnostic purposes, also a schematic state display is available. This shows a simplified schematic of the apparatus, along with real time animated symbols of the control elements, as there are valves and pumps, each displayed in a derived version of a timage component, created and placed dynamically on program load. Also shown are the most important process values as numerical displays, also dynamically placed. The schematic field really is the output of a separate program, running in parallel to the process display which provides the upper and lower parts of the screen display.\
363	371
364	372		![Control Screen](/wiki-images/e/ec/ControlScreen.png)
365	373
366	374		There is also a mode for setting several control and function parameters and to recall previous operational and diagnostic data. It is organised as a tabbed screen containing several run time parametrized menu pages and a couple of display field pages. Some of the pages allow access only after entering a pass code to prevent missuse of critical functions.\
367	375
368	376		![Protocol Review](/wiki-images/a/aa/ProtocolReview.png)
369	377
370	378		This is a screen displaying a graphical protocol of a previous process. The protocol is usually printed out immediately after termination, as required by the regulations. The printer output is generated as a postscript file, processed by ghostscript both for print out and for the on screen display shown, which uses the png format for loading into the display field.\
371	379
372	380		![Attribution](/wiki-images/e/e0/Attribution.png)
373	381
374	382		Of course, there is also an attribution display, showing program version, creator information and the tools used for the creation of the system, Free Pascal and MSE-IDE & MSE-GUI. As background, it uses a photography of one such apparatus as it is used in clinics displayed in an image component carrying several label fields used for the text. Above all of that sits a transparent button to close the picture.
375	383
376	384		# Reference: MSEide
377	385
378	386		- To move and resize components without gridsnap use shift+cursorkeys and ctrl+cursorkeys.
379	387		- There are many possibilities with properties twidget.frame and twidget.face, for instance tiled semitransparent bitmaps and color fades (all twidget descendants have these properties!).
380	388
381	389		For client area of forms use tmseform.container.frame and tmseform.container.face, tmseform has additionally onpaint to do custom drawing.
382	390
383	391		You can write your own widgets and override procedure dopaint or use teventwidget with onpaint,onresize,onmouseevent,onkeydown,onkeyup...
384	392
385		-	~~`How to convert filenames to windows format? `\~~
386		-	~~`Unit msefileutils: `\~~
387		-	~~`function tosysfilepath(const path: filenamety): filenamety; `\~~
388		-	~~`procedure tosysfilepath1(var path: filenamety); `\~~
389		-	~~`Converts to filename format of actual OS. `\~~
390		-	~~`function tomsefilepath(const path: filenamety): filenamety; `\~~
391		-	~~`procedure tomsefilepath1(var path: filenamety); `\~~
392		-	~~`Converts from filename format of actual OS.`~~
	393	+	``` pascal
	394	+	How to convert filenames to windows format?
	395	+	Unit msefileutils:
	396	+	function tosysfilepath(const path: filenamety): filenamety;
	397	+	procedure tosysfilepath1(var path: filenamety);
	398	+	Converts to filename format of actual OS.
	399	+	function tomsefilepath(const path: filenamety): filenamety;
	400	+	procedure tomsefilepath1(var path: filenamety);
	401	+	Converts from filename format of actual OS.
	402	+	```
393	403
394		-	~~`Where is the MDI ??? `\~~
395		-	~~`In MSEgui we have tdockform and tdockpanel for that purpose. `\~~
396		-	~~`Have a look at property dragdock.`~~
	404	+	```text
	405	+	Where is the MDI ???
	406	+	In MSEgui we have tdockform and tdockpanel for that purpose.
	407	+	Have a look at property dragdock.
	408	+	```
397	409
398	410		## MSEi18n
399	411
400	412		# [[Reference: MSEgui]]
401	413
402	414		[[Reference: MSEgui\|On this page you can find a working in progress for documenting MSEGUI.]]
403	415
404	416		# External links
405	417
406	418		Website: <http://mseide-msegui.sourceforge.net/>
407	419
408	420		Community website: <http://www.msegui.com>
409	421
410	422		Unofficial incomplete help pages started from Z505 at: <http://z505.com/cgi-bin/mse/idx.cgi?file=generalindex>
411	423
412	424		Read the beginner's tutorial (in Russian) at: <http://freepascal.ru/article/mse/20060108181639/>
413	425
414	426		Also: "MSEide+MSEgui. Draw lesson." (in Russian) <http://freepascal.ru/article/mse/20060205191314/>
415	427
416	428		You can also find an English translation here: <http://www.geocities.com/yetanothergeek/mseide-tutorial-en/>
417	429
418	430		This page in Russian: <http://freepascal.ru/wiki/index.php/MSEide%26MSEgui>
419	431
420	432		MSElang, the future compiler for the MSEide+MSEgui project <https://gitlab.com/mseide-msegui/mselang/wikis/home>
421	433
422	434		------------------------------------------------------------------------
423	435
424	436		---
425	437		From the Free Pascal wiki, page "MSEide+MSEgui/es", as it stood on 2020-04-20 after a change by FTurtle, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).

Back to history