2007/7/10, Uwe Grauer <[EMAIL PROTECTED]>: > > But adding a new feature without the necessary planning and discussion > is constructive?
Necessary? Why? > 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. We know that you disagree. That's OK. > I already asked for examples of other frameworks which have a update > feature. You didn't reply (maybe because there are no examples). You seem to think that Ed needs a justification for putting features into dabo. You're wrong. > Why can't you start a discussion about the addition of a new feature > before adding it? Who says he can't? He's done it before IIRC. In this case it was unnecessary and would have been a waste of time. > 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? That's neither possible nor necessary. (It's just the same with SVN.) And if your application doesn't use the auto update feature, nobody will be asked anything. > I don't think that throwing out a new feature without any planning is > worth the effort. > Please try to do the planning first. I'm sure Ed did some planning. We'll see how it comes out. For new developers coming to dabo this might be a valuable feature. It's easy to stay current, you don't need svn, and you get only suppesedly reasonabe versions. Wolfram _______________________________________________ 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]
