From: <Web...@St...> - 2004-07-23 08:39:35
|
On Thu, 22 Jul 2004, Eric B.Ridge wrote: | On Jul 22, 2004, at 2:33 PM, Sebastian Kanthak wrote: | | > Neither of the three seems nice to me, so does anybody have a better | > idea? | > Otherwise, I'd suggest to postpone a change like this after 2.0 is | > released | > and keep it the way it currently is (global macros loaded once at | > WebMacro | > startup). | | I don't have a solution for the problem, but a global #macro library is | totally useless to developers if it can't be reloaded on-the-fly. :) First (the question): postone such changes. Second (the opinion): don't agree. In my case, I'd make these "static macros", and then "my developers" (the folks coding on top of my framework) would be allowed to use them, buf -of course not- change them. They would work more like directives, not macros. Thus, this wouldn't be that big a problem. I was just asking. For my part, the "macro-files-aren't-reload-checked" are a MUCH MUCH worse problem. IM(H)O: I WANT A 2.0 OUT!! NOW!! Fix the bugs (if any) - DO NOT include more features. DROP ANY MORE DEVELOPMENT! STOP!!!! *GET* *IT* *OUT*! (That was just to express my inner thoughts about the state of WebMacro, do not take it to seriously. ;) ) Endre. |