Dear ArenMook,
I am developing rather big projects with dozens of packages imported from various sources, but most of them from the asset store, and NGUI being one of the most important and central ones. Now I have made the experience that for day-to-day development of bigger projects, it is paramount to move as much of the "not daily worked on" code, especially that of externally maintained packages, into "Standard Assets". This keeps Unity's "changing just a few lines of code"-compiletime down to a minimum, by moving most of the workload into the "firstpass"-Projects that only get compiled when necessary. This requires a quite tedious splitting process, as every "Editor"-Directory of every Standard Assets Package needs to be moved to Standard Assets/Editor/ to be recognized as "Editor firstpass".
And of course, whenever there is a package update - which is rather frequent for NGUI, thank you for such an active development! - and files are added or removed (luckily mere changes are recognized by Unity's package importer), this starts over with searching for the "new bits and pieces" and moving them into place. Now my question is, why isn't NGUI's package delivered as "Standard Assets" package by default? This of course applies to almost anything one can buy at the Asset Store, but aside from requiring two directories instead of a single one (which doesn't seem to be a problem with stuff like Gizmos), I don't see a good reason for it. There would even be a clear distinction between Pro Standard Assets (which could and should hold packages requiring Unity Pro) and Standard Assets (which also work on free). Maybe you can enlighten me, especially with your insights of having worked at Unity yourself (if that is legally possible, of course!), thank you
.
