summaryrefslogtreecommitdiff
path: root/examples/apps/uidesigner/readme.txt
diff options
context:
space:
mode:
authorgraemeg <graemeg@ae50a9b5-8222-0410-bf8d-8a13f76226bf>2007-09-08 11:17:20 +0000
committergraemeg <graemeg@ae50a9b5-8222-0410-bf8d-8a13f76226bf>2007-09-08 11:17:20 +0000
commit8c2cd0a27d852f4b02ca07850a2fbaf9cec05368 (patch)
treeb46694481fff1a719d8f6323aa02c78605d1c363 /examples/apps/uidesigner/readme.txt
parent1e7af73a67cff669d2b5801f5097e71b30673adc (diff)
downloadfpGUI-8c2cd0a27d852f4b02ca07850a2fbaf9cec05368.tar.xz
* GUI Designer: Some code formating changes in generated code.
* GUI: minor amendments in basegrid and listbox to work correctly in the GUI Designer.
Diffstat (limited to 'examples/apps/uidesigner/readme.txt')
-rw-r--r--examples/apps/uidesigner/readme.txt50
1 files changed, 50 insertions, 0 deletions
diff --git a/examples/apps/uidesigner/readme.txt b/examples/apps/uidesigner/readme.txt
new file mode 100644
index 00000000..b0ffd0eb
--- /dev/null
+++ b/examples/apps/uidesigner/readme.txt
@@ -0,0 +1,50 @@
+
+ fpGUI's Visual User Interface Designer
+ ======================================
+
+
+Introduction
+============
+
+fpGUI Designer is a port of a product called VFD written by Nagy Viktor in 2003.
+I ported VFD to fpGUI because I thought it would add a lot to the framework as
+a whole. I could see it has lots of potential and could easily be extended to
+become a great tool. What I immediately liked about VFD is that it used the
+same source unit and writes actual code describing the UI like I would have
+done manually. This departs from the GUI designers used in Lazarus or Delphi
+where they save the UI code to external files (*.lfm or *.dfm respectively).
+
+
+Features
+========
+
+* It uses the same source unit where your normal code lives. No external GUI
+ files.
+
+* It can handle "unknown" or "custom" components and properties. Whenever the
+ designer finds a component it doesn't natively know it paints a green
+ rectangle in it's place. Whenever it finds properties it doesn't know it
+ adds them "as is" to the Unknown section memo in the Properties window. Any
+ code in the Unknown memo will be written back to the source unit "as is".
+
+* The designer can handle more that one form in a unit.
+
+* When creating a new form, that form can be merged into an existing unit or
+ the designer will create a new unit for it.
+
+* The designer uses comment markers in the code to define what parts it will
+ maintain. Existing code (Forms) can be easily amended (manually by the
+ programmer) so that the designer can start managing it. No need to redesign
+ Forms from scratch.
+
+
+
+Graeme Geldenhuys - September 2007
+
+ ============================================
+
+
+
+
+
+