On 7/10/07, Uwe Grauer <[EMAIL PROTECTED]> wrote: > Ed Leafe wrote: > > No bickering. I welcome constructive criticism, but summarily > > dismissing something without even looking at it is hardly constructive. > > But adding a new feature without the necessary planning and discussion > is constructive?
This is Ed and Paul's brainchild and while many of us have contributed code they still have written 95% of the framework and as far as I am concerned they have the right to make changes like this. I don't see what the big deal is here. > > I only wanted to make you aware that i do not agree with putting it into > the framework. And i don't have to look at it before i know that i think > that it's wrong. That's all. > > I already asked for examples of other frameworks which have a update > feature. You didn't reply (maybe because there are no examples). I am not sure of frameworks, but there are plenty of end user programs that I can think of that check for and install updates regularly (virus scanning software, firefox, media players, etc.) > > What are the reasons for putting it into the framework instead of > providing a tool function? If it is put into the tools directory, it is still technically a part of the framework, even if it doesn't get imported when put there. I would say that this is probably a good idea. > > Why can't you start a discussion about the addition of a new feature > before adding it? > > How do you want to make sure it works for every platform and install > method? Do you want to ask for a root password just because a user runs > a dabo app? I really think that you are miss understanding the point. If you wrote an App and then deployed it to a customer, you would not want to turn auto update on because new framework versions might break old functionality. What I see this being used for is by developers to update their frameworks during development. Sure, we have SVN, but as was pointed out earlier most VFPers are used to and prefer auto Update features. This feature is not something to be used be the end user, but rather by the developer using the framework. > > I don't think that throwing out a new feature without any planning is > worth the effort. > Please try to do the planning first. >From what I could tell there was planning. > > Uwe > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
