El lun, 23-01-2006 a las 14:49 -0500, Doug Chestnut escribió:
> In this case we are loading a js file, which can be done as you show
> below. The js file then loads more js files, images, html, etc to
> present you with an fckeditor.
>
> In the fckeditor conf, which can be in the invoking javascript on the
> webpage, you have to specify the root path that the fckeditor resources
> can be reached at. I am sure that one could tweak the fckeditor js to
> get it to append ?lenya.module=fckeditor to each resource request, but
> it is just something else to have to maintain.
>
Agree, with keeping maintenance low, but does reserving url space will
help with this?
Actually I thought a while ago about the same problem and came to the
conclusion that it would be best if resources could have a unique id.
Then re-using this resources would be piece of cake in multi-publication
but that leads us straight to asset management.
We need a central interface that is responsible to look up and manage
assets. The storage of this assets would be ideally a combination of
decentralized, so modules can easily register resources in this asset
storage, and centralized for publications.
I think the sitemap usage in lenya pubs/modules/... is too excessive
already (including all the parameter magic we are doing) and would love
to see something more generic like a true assets management (the only
thing IMO which will keep maintenance low in the future).
salu2
> Thorsten Scherler wrote:
> > El lun, 23-01-2006 a las 19:22 +0100, simon escribió:
> >
> >>hi devs
> >>
> >>i played a bit in lenya 1.4 and i tried to implement the FCKeditor as
> >>module.
> >>i would like to propose a change in the lenya-core.
> >>it would be very nice to have acces to /module/{modulenname}/resources/
> >>where you can reach different files that the modules using inernaly
> >>internally. like images or javascripts who are used in the module.
> >>
> >>the simples i see so far would be to add
> >>
> >> <!-- Enter a module -->
> >> <map:match pattern="**/modules/*/**">
> >> <map:mount uri-prefix="" src="lenya/modules/{2}/sitemap.xmap"
> >>check-reload="true" reload-method="synchron"/>
> >> </map:match>
> >>
> >>to the lenya sitemap.
> >>but in this case *modules* would be a reserved word.
> >>but maybe there are some other ways avoiding this problem.
> >>
> >
> >
> > You can already reach all module resources like pics.
> >
> > uri?lenya.module={modulenname}
> >
> > e.g. path/someCss.css?lenya.module=myModule
> >
> > This would mount the sitemap of {modulenname} and looking for the uri.
> >
> > ...or did I miss something?
> >
> > salu2
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
