>>I find it amazing >>that nobody else seems to consider this even odd, much >>less counterproductive. Or at least very few people...
> I think I just don't have enough discipline to write all > the changes down and remember what I modified. I'd end > up using the same blogware for the next 5 years if I got > too deep. In this case, I'll take the easy path and let > Ray add the features and kill the bugs. > On another note? Any blogCFC'ers play Halo2? I've got > a stats pod just about done. After looking at the NiftyCorners code for a bit it's not terribly complicated... but I actually dislike the antialias feature because it "tightly couples" the code with the style (which was the purpose of css to begin with, to separate the style from the code). I toyed around some today (when I probably shouldn't have because I've got much more important things to work on) with creating my own implementation of NC that would include only the content color and border color and potentially allow for the size of the curve to be set with numbers (instead of "small"). I did manage to get NC working and even managed to get most of my custom implementation working... but then abandoned it (at least for now) because of the potential havoc caused by the way it creates and modifies html elements in the page. Once you've applied the corners, there's a significant possibility of any javascript which might work against the affected html elements going wacko because the script makes dramatic changes to the node structure. I toyed with a few ideas for resolving that issue, but haven't come up with anything I really like, so for now I'm filing it as "an interesting idea to return to later". The question of upgrades is one I'm actively persuing still tho... As I said, much of the purpose of the framework is bound up in the idea of being able to upgrade gracefully, so it eliminates the need to manually record each and every modification you make and then go through the app with a fine-toothed comb when you want to upgrade later. The framework code is so loosely coupled that, asside from being able to alter the style sheets, you can make any number of other subtle changes like for instance adding navigation links, and then when you upgrade you just copy the new files over and you don't have to worry about your navigation because you don't edit any of the original application's templates when you make your changes. Most applications should install through a browser anyway -- using the framework's pluginmanager tool, though I haven't gotten to the point of writing any upgrade installers yet. As of yet there's only one publicly available plugin and it's in the final stages of significant redevelopment -- hopefully future versions will have upgrade installers. s. isaac dealey 954.522.6080 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://www.fusiontap.com http://coldfusion.sys-con.com/author/4806Dealey.htm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:207976 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
