Re: Fluid Application Environment 3.0.alpha1 Released!
- Posted by useless_ Oct 14, 2013
- 2319 views
....
I will even say that it is best to give a reasonably complete set of GUI functions and tell him to take it or leave it.
... but the standard is there so people don't need to reinvent the wheel every time they write a program.
I agree. Same thing said differently.
Give the programmer a standard library which is reasonably complete so they do not have to reinvent the wheel.
I believe what i detailed is using FAE as if it is almost Win3.11, asking for ~10 lines of code hooks to allow "user" code to be called and run by each widget. I am not asking to change the gui itself. I am not asking to change anything to Ry's code. I am asking only for two "hooks": to load a .e file, and a target procedure name for the FAE wm_msg'er to send a msg to. I believe a standardised set of hooks, known to interface to FAE properly, is needed, to eliminate the need for the user to hack these into FAE. And i am making the assumption that the .e file can call what widget internals needed to send wm_msgs back to the FAE msg handler, and do it's own widget popups and text input/output box, and interactions to it's own display (which can also be done by sending a wm_msg to itself, i presume).
Consider the windose desktop to be the root gui. Consider each icon on the desktop to be a mouse-able selection in FAE's root gui. I can write an app in Eu and put a shortcut to it on the winxp desktop, i can have a gui window on FAE show a list of programs in a hdd directory. I can click on and launch a winxp desktop shortcut or a FAE list item(?). Each application i launch (either way) "inherits" the characteristics of the parent: the "skin" if you prefer, unless that widget or program changes it. I believe the comparison of FAE to win3.11 is quite appropriate.
Mirc has the same ability: it can write new executeable code, it can include or drop executeable code (Eu can do that to DLLs now), it presents a gui with runtime-programmable popups and programmable backgrounds, it's child windows can be separate and placed anywhere onscreen, so it is like FAE also. Mirc has two huge problems: it runs dreadfully slowly, and has very restrictive lengths to variables.
I think FAE hands us win3.11 on a silver platter, written and therefor 100% compatable with Eu code, very easily understood, with all the options of every other gui lib in the archives plus some, and potentially cross-platform. It literally gives me goosebumps. I am only asking for the two hooks, which you may use or not, as you like.
useless
