<br><br><div class="gmail_quote">On Tue, Sep 7, 2010 at 2:11 PM, Michael Wild <span dir="ltr"><<a href="mailto:themiwi@gmail.com">themiwi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><br>
On 7. Sep, 2010, at 18:22 , David Cole wrote:<br>
<br>
> On Tue, Sep 7, 2010 at 11:44 AM, Michael Wild <<a href="mailto:themiwi@gmail.com">themiwi@gmail.com</a>> wrote:<br>
><br>
>><br>
>> On 7. Sep, 2010, at 17:30 , David Cole wrote:<br>
>><br>
>>> On Tue, Sep 7, 2010 at 11:23 AM, David Doria <<a href="mailto:daviddoria@gmail.com">daviddoria@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>>> On Mon, Sep 6, 2010 at 9:18 AM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>><br>
>> wrote:<br>
>>>><br>
>>>>> The "Generate" button should be enabled after the first configure.<br>
>>>>><br>
>>>>> It's not enabled because the prevailing theory of the day was that you<br>
>>>>> shouldn't allow generate unless there were *no* *new* cache entries<br>
>> after<br>
>>>>> the most recent configure... -- force users to pay attention to those<br>
>> new<br>
>>>>> red entries -- in other words, it's just history and reluctance to<br>
>> change<br>
>>>>> behavior that's "always been that way"...<br>
>>>>><br>
>>>>> I've always thought that you should be allowed to generate whenever you<br>
>>>>> want to: I'd go so far as to say that "Generate" should be enabled as<br>
>> soon<br>
>>>>> as you open cmake-gui, and that, if there have not been *any* configure<br>
>>>>> steps, it would do the same thing as command line cmake: configure once<br>
>> and<br>
>>>>> generate, all in one click.<br>
>>>>><br>
>>>>> Please reply with more feedback:<br>
>>>>><br>
>>>>> How many of you would:<br>
>>>>> - keep the current behavior exactly as is, it's good<br>
>>>>> - enable "Generate" unconditionally<br>
>>>>> - something in between<br>
>>>>><br>
>>>>><br>
>>>>> Thanks,<br>
>>>>> David<br>
>>>>><br>
>>>><br>
>>>> David C.,<br>
>>>><br>
>>>> I fear all of the votes for "enable generate unconditionally" will never<br>
>> be<br>
>>>> cast because the users that really want/need it are not on the CMake<br>
>> mailing<br>
>>>> list. I'd like to cast 32 votes by proxy in favor of the unconditional<br>
>>>> generate button!<br>
>>>><br>
>>>> Thanks,<br>
>>>><br>
>>>> David D.<br>
>>>><br>
>>><br>
>>><br>
>>> :-)<br>
>>><br>
>>> OK. So far, we have these votes: 32 - 0 - 0<br>
>>><br>
>>> Anybody else?<br>
>><br>
>><br>
>> I'd say CMake should re-configure automatically until it is able to<br>
>> generate, then stop let the user take action (modify the cache and then<br>
>> re-configure, or generate). I could also live with no separate "generate"<br>
>> step, like when using "cmake" from the command line. Perhaps this would be<br>
>> the most transparent for new users, but for large projects it could be a<br>
>> nuisance.<br>
>><br>
>> Not sure in which bin my vote goes :-)<br>
>><br>
>> --<br>
>> There is always a well-known solution to every human problem -- neat,<br>
>> plausible, and wrong.<br>
>> H. L. Mencken<br>
>><br>
>><br>
> "Configure" is always going to make exactly one configure pass.<br>
><br>
> Any "auto-reconfigure until there are no more new options" behavior is iffy<br>
> at best, because you *could* write code (likely accidentally...) that always<br>
> adds a new option on a configure pass... and then the user would wonder why<br>
> it's taking forever... when it literally would take forever.<br>
><br>
> The pause in between configure steps is why we have a gui. It's essential to<br>
> make things red and let people inspect the new things that just popped up in<br>
> case they do want to change the newly introduced options. If they do,<br>
> they're responsible for making the changes and configuring one last time<br>
> again before generate.<br>
><br>
> But...... if they're happy with the values (as most newbies are) then we<br>
> should let them click generate right away.<br>
><br>
> Michael, your vote goes with David's proxy votes as far as I can tell. 33-0<br>
> in favor of enabling generate so far.<br>
><br>
> Any other votes?<br>
<br>
<br>
</div></div>What I meant was that the curses and Qt UI's should behave more like 'cmake'.<br>
<font color="#888888"><br>
Michael<br>
</font><div><div></div><div class="h5"><br>
--<br>
There is always a well-known solution to every human problem -- neat, plausible, and wrong.<br>
H. L. Mencken<br>
<br>
</div></div></blockquote></div><br><div><br></div><div>OK... good. I was just clarifying for the readers of the thread why we will not be "auto-configuring-for-multiple-iterations"... Ever. :-)</div><div><br></div>