Bertrand Dunogier a écrit :
>
> Well, what you're describing here looks very much like a module/view 
> extension [1].
Thanks, I'm reading it, didn't find this one surfing on ez.no this morning.
> Integrating it in eZ Publish shouldn't be too complex. Each view has 
> to return a result, mainly HTML + Path information. This HTML can 
> perfectly be generated by what you currently use, maybe even with an 
> output buffer.
Do you mean each class will have its own method "public function View{"?
> The most important part will be to map your application to the 
> module/views API, and change the way results are handled.
What you call results is HTML, right? Like said above.
> You'll probably have to make a few changes to your DB Handling. The 
> best option would probably be to use the DB API eZ Publish already 
> features.
Ouch, you mean Ezpublish doesn't handle database like ezc does? all my 
classes are persistent objects, that's the point of using ezc, with 
graphs too.
>
> Depending on your application's complexity, configuring the 
> permissions can require some thinking, but you probably won't have to 
> change much.
That sounds cool.
>
> Now if you want to provide a better integration , a few options are 
> available:
>  - modify your app so that it uses view parameters instead of GET 
> parameters;
I don't understand this yet but I guess explanation is in the link. Most 
GET parameters are Json sent by jquery.
>  - add fetch functions that will allow you to fetch data from your 
> application from any eZ Publish template;
>  - change your settings system so that it uses eZINI. That way, you 
> will benefit from overrides
>  - and probably many more ;)
>
> Do you plan on releasing this to the eZ Publish community, or is it 
> too private ?
No, it has to be totally free and public :-) I was thinking of making it 
GPL, but I don't even know if ezc allows it. I plan to make it work with 
moodle (not inside, beside).
Thanks a lot for you reply.


-- 
Components mailing list
Components@lists.ez.no
http://lists.ez.no/mailman/listinfo/components

Reply via email to