You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There has been a few requests for custom functionality. (e.g. #39, #70, #86). So I'm considering three possible scenarios (open to more).
1. Stick to the Basics
The intention of alertify from the beginning was simply to be able to replace native dialogs with customizable ones. The plan all along was to mimic the behaviour and stop. Currently, it's very close and with a few tweaks and optimization, version 1.0 could be just around the corner.
2. Core Library + Extensions
Still sticking with the basics of what alertify was meant for but adding extension that could be added as dependencies to provide additional and more customized options. This would solve the problem about whether a certain feature is useful and generic enough to fit in the core and allow anyone to write extensions without touching the core. This would give greater flexibility and could be extremely useful for advanced users and allow personalization to the library.
3. Custom Build
This would be very similar to option 2, where the code would be split into stand alone features that could be hand picked and then used to generate a custom build.
I'm leaning heavily towards #2 or #3. This would need to be properly scoped out but would love to get feedback on whether this would be useful...
The text was updated successfully, but these errors were encountered:
I like proposal 2, but only if it doesn't add too much complexity to the core. In my earlier request (#70), I proposed leaving the API more open, so it would be easy to subclass. Then it's a simple matter of overloading the pieces that should be custom. Alternatively, if Alertify were more modular, new instances could be be composed out of stock and custom components, mixin style (e.g. A renderer, various callbacks, etc.). The latter is not really a custom build, since every distribution would be the same, it's just how the pieces are assembled during object construction.
I'm still looking for the ideal build to make it easy for users to use and for developers to extend/customize. I've started modularizing it for 0.4.0. You can check it out at http://fabien-d.github.com/alertify.js/0.4.0rc1 and the source code is the master branch.
Still not perfect, but much more structured and a step in the right direction. I'm hoping by the release of 0.4.0 to have an extendable library but also one that can be added to the site in no time.
There has been a few requests for custom functionality. (e.g. #39, #70, #86). So I'm considering three possible scenarios (open to more).
1. Stick to the Basics
The intention of alertify from the beginning was simply to be able to replace native dialogs with customizable ones. The plan all along was to mimic the behaviour and stop. Currently, it's very close and with a few tweaks and optimization, version 1.0 could be just around the corner.
2. Core Library + Extensions
Still sticking with the basics of what alertify was meant for but adding extension that could be added as dependencies to provide additional and more customized options. This would solve the problem about whether a certain feature is useful and generic enough to fit in the core and allow anyone to write extensions without touching the core. This would give greater flexibility and could be extremely useful for advanced users and allow personalization to the library.
3. Custom Build
This would be very similar to option 2, where the code would be split into stand alone features that could be hand picked and then used to generate a custom build.
I'm leaning heavily towards #2 or #3. This would need to be properly scoped out but would love to get feedback on whether this would be useful...
The text was updated successfully, but these errors were encountered: