| EGL's handling of target files [message #572667] |
Fri, 07 August 2009 08:52 |
 Steffen Zschaler
Messages: 266
Registered: July 2009 |
Senior Member |
|
|
Hi all,
I'm currently fiddling with EGL a bit, trying to adjust it a bit for my
purposes. In this context, I have noticed what seems to be an
unnecessary redundancy in the EGL code. In particular, this has to do
with how EGL stores the results of generating code from a template,
especially when this code needs to go to a file.
At the moment, this is implemented doubly: Once in EglTask and once in
FileGeneratingTemplate.store. In fact, whenever I need to modify the way
generated code is stored (e.g., because I am using EGL in a different
environment that has its own ideas of how to manage texts), I need to
effectively touch two places: EglTask and an appropriate template
(including its template factory etc.).
I was wondering if it wouldn't be better to change this, so that
EglModule instead of fixedly coding what to do with generated code
(i.e., store it in a string attribute of the module's context) could be
asked to leave this decision to a template instance? This way, there
would only have to be one place where to implement storing of generated
texts. Obviously, every template would have to have a store method (and
we would have to come up with a suitably general parameter set for this
or use a configuration pattern instead), but this would be the only
place affected by any changes to storing generated code.
Do you feel this is a useful enhancement to EGL? Should I file an
enhancement request for it? I might even be able to provide some patches.
Best regards,
Steffen
|
|
|
Powered by
FUDForum. Page generated in 0.02945 seconds
] 
Search
Help
Register
Login
Home
