Hopefully this wont go beyond the scope of this discussion, but maybe
something to think about - what if it's not so much the toolkit, but
"what really makes a user interface"?
buttons, textbox, graphics, etc - they all do that
rules, limits, alarms, what not - software does that
Could there be a reasonably (good) standard to define user interfaces?
can it be modeled? formally (xsd like) defined?
Would that bring cross compatible DMs (qt/eclipse/etc), open new paths
to extensions? Could new ideas be modeled rather than specific
implementation?
I must be thinking too simplistic for it to work.
Matthieu
- References:
- Re: QT-based tools: Expressions of interest requested Claude Saunders
- RE: QT-based tools: Expressions of interest requested Elder Matias
- Navigate by Date:
- Prev:
RE: QT-based tools: Expressions of interest requested Elder Matias
- Next:
RE: QT-based tools: Expressions of interest requested james.rowland
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: QT-based tools: Expressions of interest requested Elder Matias
- Next:
RE: QT-based tools: Expressions of interest requested james.rowland
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|