|
From: Cameron H. <ca...@bi...> - 2000-12-07 09:58:10
|
> If there's going to be any splitting, I think it should only be done in > the core files and maybe some of the heavier extensions. I'd rather not > have to create split versions of a widget; at that point, it stops being > cross-browser, so why bother having an API? It would be difficult enough > just to maintain the core files for all browsers. I agree, if the whole thing gets split into lots of different browser specific files, it will potentially stop being a cross-browser API. Being cross-browser and abstracting site developers from the underlying cross-browser muck to me is one of the best reasons for using the API. I don't know if my Makefile idea is workable, it would be a pain to add a compile stage into the code/test development process. But then again, the API does mimick Java in many ways already ;-) On another note, does IE on Solaris and Mac even support VB? |