Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
wx_cfg custom variable
thomas:
--- Quote from: Takeshi Miya on December 21, 2005, 05:12:29 pm ---Because now, it assumes everything is a C++ project (predefining the /lib, /include).
It should be more flexible.
--- End quote ---
That, however, will certainly stay the way it is. First, it makes sense, and second, I cannot change the semantics of these without being burned on the stake, because existing projects rely on this functionality.
takeshimiya:
I'm not sure about that, this needs to be discussed now that RC3 isn't released yet, so anything can be broken/unbroken in SVN.
I'm not even sure a different syntax for global and non global variables is good.
It would be perhaps better (and more intuitive for new users) to have $(PROJ_VAR), $(GLOBAL_VAR), $(COMPILER_VAR) syntax.
The current solution only saves you to type the /include and /lib only, but it appears to me that causes more harm than it does.
I'd rather would like to be prompted with 3 global vars: $(WX_INCLUDE), $(WX_LIB), and $(WX_PREFFIX).
And on the GUI part: Instead of (as is currently), prompt one dialog after another when Global Variables are used for the first time, show all the new global variables to be entered in a single dialog.
This should be taken seriously IMHO.
mandrav:
--- Quote from: Takeshi Miya on December 21, 2005, 10:09:35 pm ---I'm not even sure a different syntax for global and non global variables is good.
--- End quote ---
Really? Can you come up with an implementation that uses the same syntax for all variables then?
It's nice to talk from a theoretical point of view all the time, but the least you could do is elaborate on what you wrote.
How would you differentiate between normal vars and custom vars, if they all share the same syntax?
And how come that it would be more intuitive to the user? At first glance you can tell a variable is global right now. How would you tell if all variables looked the same?
--- Quote from: Takeshi Miya on December 21, 2005, 10:09:35 pm ---The current solution only saves you to type the /include and /lib only, but it appears to me that causes more harm than it does.
I'd rather would like to be prompted with 3 global vars: $(WX_INCLUDE), $(WX_LIB), and $(WX_PREFFIX).
--- End quote ---
Hmm, nice, type in three edit boxes. Do you know of many common libraries that don't use the /lib and /include convention? I don't understand what the gain would be.
And about $(WX_PREFIX) you mentioned, Thomas already posted that some things will be changed in global vars to make them more adaptable.
thomas:
You might want to read the documentation, too. I spent a good hour writing one, you know. Maybe then you don't want three separate variables any more ;)
280Z28:
I am pretty happy with the syntax and abilities right now. However, I think the last update that fixed per-target custom variables actually broke things again. It replaces global variables correctly but replaces all per-project and per-target variables with "" (empty).
rev 1578.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version