If filesize is to be TB biggest advantage, personally in fact i rarely need to be able to launch a TB with iframe, ajax and images on the same page, or even Application.
I guess i'm not the only one to choose before hand at design time how my app will use TB (ajax/iframe) to display interfaces. I would therefore love to have 3 different thickbox plugins, so 3 different files. If i need to mix, just adding the script source link to the related TB version would enable me to. <script src="plugin.thickbox.images.js" type="text/javascript"></script> <script src="plugin.thickbox.ajax.js" type="text/javascript"></script> <script src="plugin.thickbox.iframe.js" type="text/javascript"></script> this would also enable to build more functionalities for specific uses (gallery, zoom, prev/next only apply to images). as for feature, proportional dimensions is a must IMO. There is no sense fixing width and height of thickbox in today's multitude of screen sizes... thank you! alex [-Stash-] wrote: > > I agree with this. Keep it tight and let it do the core things extremely > well. Is there any reason you can't have an extension for a plugin? > Perhaps all you need is a section in the core file where you can add as > many lines as yuo like that say "enable this extension -> path"? > > -- View this message in context: http://www.nabble.com/ANNOUNCE%3A-Thickbox-Reloaded-alpha-tf3293077.html#a9203349 Sent from the JQuery mailing list archive at Nabble.com. _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
