|
|
Home » U++ Library support » LineEdit, EditFields, DocEdit » TextCtrl (aka LineEdit,DocEdit) dont use global Style
|
|
|
|
Re: TextCtrl (aka LineEdit,DocEdit) dont use global Style [message #30365 is a reply to message #30362] |
Sun, 26 December 2010 11:33 |
|
mirek
Messages: 13980 Registered: November 2005
|
Ultimate Member |
|
|
kohait00 wrote on Sun, 26 December 2010 04:38 | yes, there is one case in the highlighting as far as i know. a came across it when compiling the ide, but after having the things changed. OTOH, i dont know how i could have made the style change different in order to supprt ide compiling here. since the style *has* made some things obsolete.
IMHO, there is not a big problem in theide not compiling. ofcorse it involves changes to it, but we cant ensure that always, i try to, but some changes are 'drastical'..
the point is another..do we need/want all Ctrl's to be chameleon aware?
|
Of course not.
Also, LineEdit in fact IS chameleon aware, in broader sense of meaning. Chameleon is not only about Style. LineEdit is using (as default) colors that are supplied from host platform and also host platform specific frame (ViewFrame). And all can be changed by user code for any individual widget.
We are using Style only when basic parameters are not enough.
|
|
|
|
|
|
|
|
Re: TextCtrl (aka LineEdit,DocEdit) dont use global Style [message #32060 is a reply to message #32049] |
Tue, 19 April 2011 19:06 |
|
mirek
Messages: 13980 Registered: November 2005
|
Ultimate Member |
|
|
kohait00 wrote on Tue, 19 April 2011 04:28 | yes i know that the stuff is manipulatable as well. but...
it's got to do with code consistency..user comes the way to use an arbitrary Ctrl and knows, 'i want to customize appearance -> i look for the Style', instead of skimming the code to find appropriate methods.
upp code is very user friendly, but there are still things that can be 'standardized' to be more predictable. which is a feature of good design concepts as well.
like i said, i dont want upp to go 'my way'. i simply emphasize what could be changed to improve user experience. (of corse i came across this issues while coding my self, so it's my user experience).
|
Well, my take on chameleon is that widgets should derive as much of their appearance from existing information in the system. Only if this is not possible, it is time to use Style.
I believe that ArrayCtrl or LineEdit are examples of widgets where the full information about appearance can be derived from such public information.
(But keep poking me, I still might reconsider this - but breaking existing code is a big no-no here...)
|
|
|
Re: TextCtrl (aka LineEdit,DocEdit) dont use global Style [message #32064 is a reply to message #32060] |
Tue, 19 April 2011 20:22 |
|
kohait00
Messages: 939 Registered: July 2009 Location: Germany
|
Experienced Contributor |
|
|
Quote: |
breaking existing code is a big no-no here
|
fully understand you..
maybe there can be a way to leave the methods and have a
One<Style> which is then set up correctly and registered as Style. user wouldn't notice any difference. but maybe theres better ways.
just to emphasize another point about attractivenesses of upp and its Ctrl's:
they not only can look like native controls, if one as coder whishes so, but they can also be customized to a maximum degree to make totally *OS-unrelated* GUI's, to reflect some personal style, if desired. depending how much effort one is willing to spend.
thats another *big* advantage of upp to keep in mind and is actually what keeps me using upp (besides the Core goodies).
i'm programming gui's for enterprises, that clearly want to set their visual style apart from the 'common' and 'boring' OS gui experience. here, the customization is lovely welcome and i dont need to recode the wheel again just to fit the appearance.
but, again, thank you veeery much for your patience with me.
[Updated on: Tue, 19 April 2011 20:25] Report message to a moderator
|
|
|
Re: TextCtrl (aka LineEdit,DocEdit) dont use global Style [message #32205 is a reply to message #32064] |
Sat, 30 April 2011 19:12 |
|
mirek
Messages: 13980 Registered: November 2005
|
Ultimate Member |
|
|
kohait00 wrote on Tue, 19 April 2011 14:22 |
Quote: |
breaking existing code is a big no-no here
|
fully understand you..
maybe there can be a way to leave the methods and have a
One<Style> which is then set up correctly and registered as Style. user wouldn't notice any difference. but maybe theres better ways.
just to emphasize another point about attractivenesses of upp and its Ctrl's:
they not only can look like native controls, if one as coder whishes so, but they can also be customized to a maximum degree to make totally *OS-unrelated* GUI's, to reflect some personal style, if desired. depending how much effort one is willing to spend.
thats another *big* advantage of upp to keep in mind and is actually what keeps me using upp (besides the Core goodies).
i'm programming gui's for enterprises, that clearly want to set their visual style apart from the 'common' and 'boring' OS gui experience.
|
Definitely:
http://www.ederedv.at/solutions/gks.html
Anyway, if it was possible to do that with U++ 4 years ago, I guess Chameleon is not missing much...
|
|
|
Goto Forum:
Current Time: Thu May 30 14:20:31 CEST 2024
Total time taken to generate the page: 0.01694 seconds
|
|
|