What Features Should A GUI toolkit have?
ketmar via Digitalmars-d
digitalmars-d at puremagic.com
Thu Mar 5 23:49:51 PST 2015
On Fri, 06 Mar 2015 19:30:40 +1300, Rikki Cattermole wrote:
> Stop trying to make GUI toolkits! Seriously just stop.
it should be turned inside out: to be productive we need component
framework a-la BlackBox Component Builder. sadly, most people were never
worked with *real* component framework, so they keep thinking that "ide +
gui builder + compiler is like component framework". no, no, and no. not
even close. that loses the main property of component frameworks: you
aren't writing program using CF, you are simply extending CF until it can
do what you want.
D is one small step away from the goal: all it need is dynamic module
loader. i.e. a module that can load other compiled modules with all their
dependences, and can unload modules (again removing all unused
dependencies). with dynamic loader the way to component framework is open.
but alas: dynamic loader means that D should stop producing that "object
files" for linkers. it has to produce something like delphi .dcus (a
compiled code, plus all the interface -- it can be titled "rich object
writing "gui toolkits" is like randomly throwing bricks, windows, doors
and floor panes onto buildint site and hoping that they somehow will
arrange themselves into the real house.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: not available
More information about the Digitalmars-d