[AHK & AHK_L] Forms Framework 0.8
Started by
majkinetor
, Jan 13 2010 04:41 PM
205 replies to this topic
F o r m s
Forms framework is a group of modules used together to create rich AHK and AHK_L applications and graphical user interfaces. It contains the list of optional module includes with each module designed to work with or without the framework in place. It includes number of custom controls, extensions and useful libraries.
Download          Documentation         ProjectÂ
Unlicensed
Notes:
[*:1gse30tb] All 3thd party dll controls are not Unicode and will be removed from the framework in the future (HiEdit, RaGrid, SpredSheet (Property)). Those controls will be kept on their respective pages outside the framework.
[*:1gse30tb] Latest source code is always here.[/list]
#1
-
Posted 13 January 2010 - 04:41 PM
Majkinetor this is fantastic! :shock:
Thank you so much. Bravo!
It looks that I have new homework - to study all that modules :lol:
Croatian/Serbian:
Bravo majstore! Tako to rade najbolji!
Thank you so much. Bravo!
It looks that I have new homework - to study all that modules :lol:
Croatian/Serbian:
Bravo majstore! Tako to rade najbolji!
#2
-
Posted 13 January 2010 - 04:57 PM
really nice and usefull
#5
-
Posted 14 January 2010 - 05:31 PM
Thx.
Any suggestions, comments and/or reports are welcome.
Any suggestions, comments and/or reports are welcome.
#6
-
Posted 15 January 2010 - 09:08 AM
How about adding the RMChart.dll as a third-party GUI element?
8)
8)
#7
-
Posted 15 January 2010 - 11:05 AM
The framework is extensible. Anybody can make RMChart module and if it conforms to other principles I used (described in docs under Features) I will be more then happy to include it. This is more or less how freakkk's RichEdit entered the framework. Some extensions are also produced by forum members (like CColor or ILButton) and are included in framework with some modifications to follow mentioned principles.
Some non-mandatory principles are also described in project wiki about code styling and some mechanism used cross module, like message chains that are mostly used for WM_NOTIFY message used by many different controls at the same time or methods of hiding globals inside "storage" functions.
Other then that, if I ever need charting in AHK Ill probably do it myself.
Some non-mandatory principles are also described in project wiki about code styling and some mechanism used cross module, like message chains that are mostly used for WM_NOTIFY message used by many different controls at the same time or methods of hiding globals inside "storage" functions.
Other then that, if I ever need charting in AHK Ill probably do it myself.
#8
-
Posted 15 January 2010 - 11:49 AM
If you need any help designing API, PM me.
Cheers.
Cheers.
#10
-
Posted 15 January 2010 - 11:56 AM
It has nothing to do with Lil Builder.
The purpose of Lil Builder was to generate "standard" AHK script from drag & drop GUI editor.
This is GUI framework which is used instead Gui, Add and several other function (or in parallel) , not all to be AHK internal (like Attach or Anchor for example). It is also implementation of some wishes, for example this one.
LiL Builder could be updated to generate Forms code out and it would be much easier to do so as Forms standardize Gui creation among custom or internal AHK controls.
In essence, Forms editor is not that much needed because its follows very simple idea consistently across modules.
It also allows for custom control creation using Panel control. I call such high level controls widgets and one example is given as Writter control that uses Toolbar, RichEdit, Dlg, Align & Attach to implement. it. The code then may look like the one bellow without the need to know details of implementation of Writer (i.e. black box)
The purpose of Lil Builder was to generate "standard" AHK script from drag & drop GUI editor.
This is GUI framework which is used instead Gui, Add and several other function (or in parallel) , not all to be AHK internal (like Attach or Anchor for example). It is also implementation of some wishes, for example this one.
LiL Builder could be updated to generate Forms code out and it would be much easier to do so as Forms standardize Gui creation among custom or internal AHK controls.
In essence, Forms editor is not that much needed because its follows very simple idea consistently across modules.
It also allows for custom control creation using Panel control. I call such high level controls widgets and one example is given as Writter control that uses Toolbar, RichEdit, Dlg, Align & Attach to implement. it. The code then may look like the one bellow without the need to know details of implementation of Writer (i.e. black box)
hForm1 := Form_New("w400 e1 h500 +Resize +ToolWindow") hWriter := Form_Add(hForm1, "Writer", "", "w100 h100", "Align T,200")
#13
-
Posted 19 January 2010 - 12:41 PM
2automaticman
No, it doesn't make sense
*** version 0.61 ***
+ Demo.ahk script added that can be used to launch and view other test scripts.
* Attach: changed reset without any arguments so that it uses first window created instead the last one.
! Toolbar: doc fixes
+ Toolbar: New sample Dynamic.ahk - shows how you can reposition controls bellow the toolbar when main window resizes and new toolbar rows are added.
+ Scroller: New sample added that shows how to scroll everything except the toolbar (thx HotKeyIt)
* Some small changes in various tests
* Doc fixes.
No, it doesn't make sense
*** version 0.61 ***
+ Demo.ahk script added that can be used to launch and view other test scripts.
* Attach: changed reset without any arguments so that it uses first window created instead the last one.
! Toolbar: doc fixes
+ Toolbar: New sample Dynamic.ahk - shows how you can reposition controls bellow the toolbar when main window resizes and new toolbar rows are added.
+ Scroller: New sample added that shows how to scroll everything except the toolbar (thx HotKeyIt)
* Some small changes in various tests
* Doc fixes.
#15
-
Posted 21 January 2010 - 12:20 PM