On 1/23/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> 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?
I've been working off and on for several months getting FCKeditor to
work with Lenya 1.2.4 (per
http://wiki.apache.org/lenya/HowToIntegrateFCKEditor) and am very
happy to hear that people are interested in making it run in 1.4 as
well. It is truly worth the trouble.
Simon & Doug: I do recommend keeping all your changes outside the
directory you dump FCKeditor into (that is, don't modify the
fckconfig.js file at all), as recommended at
http://wiki.fckeditor.net/Developer%27s_Guide/Configuration/Configurations_File,
, so you can easily upgrade FCKeditor itself later. The trick is to
set your FCKeditor configuration values using the
oFCKeditor.Config["foo"] = "bar" syntax in a separate javascript file
that you invoke from the page that first invokes the editor.
As you have probably seen, you can set FCKConfig.LinkBrowserURL and
other FCKConfig.*BrowserURL settings in your configuration file, but
FCKeditor expects those URL's to have a certain pattern and
manipulates that URL in ways that require such a pattern. In other
words, if you set:
oFCKeditor.Config["LinkBrowserURL"] = FCKConfig.BasePath +
'editor/filemanager/browser/default/browser.html?Connector=connectors/lenya/connector.lenya';
then when FCKeditor makes requests back to the server FCKeditor
liberally changes what comes after the ? in that string. In order to
enforce a ?lenya.module={modulenname} argument I believe you will have
to modify FCKeditor.
The good news is that FCKeditor is designed so that you can replace
the "file browser" portion with your own. It is the file browser code
that formulates these URL's that interact with the server. You can
copy FCKeditor's "default" file browser, in the
editor/filemanager/browser/default/ directory, to a new directory
entirely outside of FCKeditor's directory and then modify it to behave
how you want it to. I have done some of that for Lenya 1.2.4 and will
be posting that code to the Wiki in the next day or two.
How did you implement the "GetFoldersAndFiles" request, by the way?
My approach was to first handle GetFolders and GetFiles requests
(which use DirectoryGenerator to list the contents of the separate
content and resources directory for the publication) separately, then
I aggregate the GetFolders and GetFiles requests for the
GetFoldersAndFiles requests.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
