Hello,

Thanks..I'm gonna try it today. WHat I find a bit naught is that js file are
set as attachments to snippet and it is quite hard to edit them as you have
to replace athhachments. Couldn't it be stored whithin some
/midcom/whatever/_js ?

This is exactly what Bergius suggested me to investigate. Since it'll be upgrade hell when new version of HTMLArea comes around and they've changed editor config API (like they did in HTMLArea-3.0-beta).

Basically what I've done so far is to patch all HTMLArea
files (.js, .html) to use attachments from the widget_html
snippet. But that'll be pain to update...

So, what I'm about to do is copy-paste all HTMLArea files
into snippets and try to get AIS to understand how it
can fetch snippets instead of real files in filesystem.
(NOTE: All relations in HTMLArea files are relative by default.)

Any MidCOM developers available to give me pointer
where to start looking at?  Bergie explained the reasoning
twice and I still had problems on getting it... ;)

Second, what is the login of URLs like /midcom-serverattachment-{guid} and
is it possible to write your own hadler for such URL to launch given
component? I am thinking of using sitemap for HTMLArea link insertion. I've
already rewrote sitemap "linkmap" component to produce JS awared sitemap but
have no idea how to lauch linkmap as a standalone outside of RootTopic.

Logic is to have those attachments served by MidCOM. If you want to write your own JS you should do it in HTMLArea's configuration. You'll need to create a button of your own and function for that.

I replaced the image functionality with the Aegir's
image pop-up window as I find it quite easy to use
compared to "give-me-the-URL-of-your-image".

You should download htmlarea-3.0-beta and look for
references.html file in the package. There's a bunch
of examples how to build your own extensions.

Solt


Cheers


//Henkka


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to