Hi Tino, Like Norbert, I was already using the source-hybrid most of the time, so for me this change is ok. I don't mind it either way. But I think that it's a nice improvement for new users who might not know about the existence of the source-hybrid job.
On 09/26/2011 02:05 PM, Derrell Lipman wrote: > The second big issue I had was that "generate.py source-each" wouldn't > work because my config.json didn't know about it. I had to manually > add "source-each" to the export list before it could be used. This is > a sufficiently "advanced" feature that I don't feel it's appropriate > to put people through it. > > If everyone with an existing project has to add "source-each" to their > export list, I feel that the change should not be made. It may be, > however, that that would not be typically required. I don't know. I think this is more of a "problem" of the current tooling/config system as a whole, not an issue of this job change. The steep learning curve of the generator config is something that has been discussed on the list before, and IMO should be addressed some time. But until then, I don't think that should be a reason to withhold changes like these, as long as users are properly educated about the required changes (or even better, if those could be automated during the migration process). Regards, Marc ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
