So does this mean that your gonna end up with something that already exist in my code? You forgetting that the advanced widgets use a combination of simple widgets to work. This means that you are still relying on the user knowing which files are required and what order they must be included in.
If simplicity is your main reason for doing this redesign, then your heaqding in the wrong track. My code already allows for automatic inclusion of requird files and this works for ALL widgets and not just the core code. If you wanted to automatically include the core files, then the process just requires a cut-and-paste to make the DynAPI.js file include the core files as I do in my distro. As for as creating code that can be used by "M$ Frontpage coders", you are again looking in the wrong place for a solution. You should be looking at getting involved in the WYSIWYG project that Henrik started. >From: "Eytan Heidingsfeld" <[EMAIL PROTECTED]> >I know you guys hate this but basically what this means for ppl who DON'T >want to get their hands dirty they'll include one merged DynAPI file of >hopefully around 20k and then just call include their widgets and in a few >simple lines create a form or DHTML app. These people won't want to get in >to the core. The users of this pack won't only be web designers who don't >really no JS but can also be active core developers who see the need for >separation between core technology and application design. >Flame Away, >8an _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
