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? 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). What are the reasons for putting it into the framework instead of providing a tool function? 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 don't think that throwing out a new feature without any planning is worth the effort. Please try to do the planning first. Uwe _______________________________________________ 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]
