On 09/23/2010 03:33 PM, Stefan Andersson wrote: > No, we are not trying to keep you away from "real", whatever it is, work.
"We"?! > > Instead, we are trying to get a structured view of the status of the > framework and its tools. It didn't sound like that. You might want to re-consider your writing style. > Now we have a good table, which also can be > used in the documentation of qooxdoo! :-) (I make an enhancement bug for > the documentation) We also understand where optimizations can be done > and we fairly can realise how much optimization there can be achieved in > the future. This is really important as we do want to see our > application run faster! Don't you? Of course, if the optimizations are general enough and can be sustained over time. > > Answering if we use our time to pop questions on you. The answer is NO, > cause we have better things to do. If it all had been documented before, > we wouldn't have to ask you. > > What should I think for a second? What should I know? Every serious and sensible improvement that is not already implemented is so because of lack of time. I thought that was obvious. > > FYI > 1. we have read through the bugzilla database > - can you find the answers there? we couldn't! Interacting with bugzilla is one of the primary skills to interact with the whole project. I suggest you acquaint yourself with it if you plan to use qooxdoo on a regular basis. Searching bugzilla for keyword "performance", component "tool-generator" and status "NEW" would e.g. show you outstanding optimization enhancements that are filed for the generator, and you could check which of those match the items you have in mind. > 2. we have inspected the code > - the questions is a result of that As there are various types of code to inspect, as I indicated, it is unclear what exactly you are referring to. But that aside, if you had inspected the code as you say you would already know that we e.g. don't do loop optimizations. So why ask? > 3. to be able to through results at you we need to finish our scanning "to throw results"?! > process and one part included is to get answers from you to synchronize > point by point > > Does it bother you answering the questions? I'm not bothered answering questions in general. But like any other open forum or mailing list, this list relies on a certain netiquette, a form of well-behaved information exchange. This includes doing own research upfront and before posting a question. Primary sources for such research are the manual, the wiki, the blog and the mailing list archive, but may include also code for specific interests like yours. If those don't provide sufficient answers, you should post your question stating which information you have found so far and why it was not sufficient. Taking part in the mailing list is an *activity* (not a "passivity"), you cannot just throw questions at it and let others work out the answers. The aim to is put as much effort as is reasonable on the side of questioner. And questions should not be demands in disguise. There are no servants on this list. HTH, T. ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
