On Wed, Feb 25, 2009 at 3:16 PM, Richard D. Worth <rdwo...@gmail.com> wrote: > > On Wed, Feb 25, 2009 at 3:06 PM, brian <bally.z...@gmail.com> wrote: >> >> In my use, at least, I'm not including UI components in all views. >> And, when I do, there may be just one widget or whatever out of >> several that I might use. I could create several "personalized" >> files--one for each use case--but then I can't rely on the core file >> being cached because it's bundled up with several different widgets. >> And I'd require a personalized bundle for every combination I might >> want in future. Better, I think, to just include what I need, as I >> need it. > > We're looking at a hybrid approach. Say if you select 3 plugins, it would > include those 3 individual files, as well as a combined file that contain > those 3 in 1. What do you think? >
Yeah, I'd like something like that. Don't get me wrong, though--I think the personalized bundles are a good idea for some situations. But, in my case, at least, I've only got a few places where I need UI stuff, and then only one thing or so at a time. I did consider creating bundles for each instance with a separate core file (so it'd be better cached) but ran into problems similar to webspeeder's. It seemed as if the bundle wasn't quite correct. And I'm pretty sure it was tabs also, as with webspeeder.
