Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Re: [propel-dev] Propel event handler

propel
Discussion topic

Back to topic list

Re: [propel-dev] Propel event handler

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-11-16 07:22:12 PST
Message Another thing we could consider is an approach similar to phpAspect's
where source is transformed using XSLT via the parse tree... that
would, actually, be the nicest solution, if it can be done in a simple
fashion and without (any|too many) external dependencies.

David



Am 16.11.2007 um 15:44 schrieb Hans Lellelid:

> David Z├╝lke wrote:
>> How bout something wicked such as having method bodies in an array,
>> with
>> each line having a unique ID ;) That would be hax0r.
>>
>> But seriously - yes, we need something like that. The more modular it
>> is, the better. But as you pointed out, it could be a bitch to
>> design -
>> maybe we need alien technology from outer space to do that. Not quite
>> sure... :>
>>
>>
>> David
>>
>>
>>
>> Am 16.11.2007 um 14:58 schrieb Ron Rademaker:
>>
>>> Hans Lellelid wrote:
>>>> It becomes a little less clear to me when I think about a builder
>>>> advertising that it wants to override / customize other methods. I
>>>> guess the question is what happens when several builders want to
>>>> all add
>>>> custom behavior into the save method?
>>>>
>>> I guess we could reevaluate the way classes are generated
>>> completely.
>>> Instead of passing along some string by reference and appending code
>>> in a function we could model the classes that are being generated
>>> and
>>> let the builders fill the model. Finally, some toString function on
>>> the model class creates the actual code. That way you don't have to
>>> create an entire function in one sweep but you can add, remove and
>>> change stuff later. Obviously, the model is gonna be a challenge to
>>> design :)
>>>
>
> Yeah, that's a possibility. I looked into that a bit when considering
> the initial design. In the end, I opted for the current system,
> because
> I think it's a lot easier for people (including myself) to understand.
> I worry about completely abstracted code generation being really
> difficult to get in there and change :)
>
> Maybe the initial pass continues to use a template-based approach
> and we
> look at revamping this based on usage / needs.
>
> Hans
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

« Previous message in topic | 11 of 19 | Next message in topic »

Messages

Show all messages in topic

Propel event handler Ron Rademaker <r dot rademaker at virtualbuilding dot nl> Ron Rademaker <r dot rademaker at virtualbuilding dot nl> 2007-11-15 02:45:32 PST
     Re: [propel-dev] Propel event handler hlellelid Hans Lellelid 2007-11-15 15:28:03 PST
         Re: [propel-dev] Propel event handler Ron Rademaker <r dot rademaker at virtualbuilding dot nl> Ron Rademaker <r dot rademaker at virtualbuilding dot nl> 2007-11-16 00:28:50 PST
             Re: [propel-dev] Propel event handler Bert-Jan <info at bert-jan dot com> Bert-Jan <info at bert-jan dot com> 2007-11-16 02:34:57 PST
             Re: [propel-dev] Propel event handler hlellelid Hans Lellelid 2007-11-16 04:02:10 PST
                 Re: [propel-dev] Propel event handler Ron Rademaker <r dot rademaker at virtualbuilding dot nl> Ron Rademaker <r dot rademaker at virtualbuilding dot nl> 2007-11-16 04:15:58 PST
                     Re: [propel-dev] Propel event handler hlellelid Hans Lellelid 2007-11-16 05:21:35 PST
                         Re: [propel-dev] Propel event handler Ron Rademaker <r dot rademaker at virtualbuilding dot nl> Ron Rademaker <r dot rademaker at virtualbuilding dot nl> 2007-11-16 05:58:30 PST
                             Re: [propel-dev] Propel event handler =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com> =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com> 2007-11-16 06:36:22 PST
                                 Re: [propel-dev] Propel event handler hlellelid Hans Lellelid 2007-11-16 06:44:57 PST
                                     Re: [propel-dev] Propel event handler =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com> =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com> 2007-11-16 07:22:12 PST
     Re: [propel-dev] Propel event handler Ron Rademaker <r dot rademaker at virtualbuilding dot nl> Ron Rademaker <r dot rademaker at virtualbuilding dot nl> 2008-05-05 07:16:33 PDT
         Re: [propel-dev] Propel event handler hlellelid Hans Lellelid 2008-05-05 09:53:00 PDT
             Re: [propel-dev] Propel event handler Ron Rademaker <r dot rademaker at virtualbuilding dot nl> Ron Rademaker <r dot rademaker at virtualbuilding dot nl> 2008-05-06 00:15:41 PDT
                 Re: [propel-dev] Propel event handler hlellelid Hans Lellelid 2008-05-06 06:39:12 PDT
                     Re: [propel-dev] Propel event handler Ron Rademaker <r dot rademaker at virtualbuilding dot nl> Ron Rademaker <r dot rademaker at virtualbuilding dot nl> 2008-05-06 06:47:08 PDT
                         Re: [propel-dev] Propel event handler hlellelid Hans Lellelid 2008-05-06 06:49:51 PDT
                             Re: [propel-dev] Propel event handler Ron Rademaker <r dot rademaker at virtualbuilding dot nl> Ron Rademaker <r dot rademaker at virtualbuilding dot nl> 2008-05-06 08:51:25 PDT
                                 Re: [propel-dev] Propel event handler hlellelid Hans Lellelid 2008-05-06 09:48:07 PDT
Messages per page: