Mailing List Archive

On Jan 5, 2011, at 11:22 PM, Zdravko Balorda wrote:

> Let me change the subject of this thread finally.
>
>> Both should be reflected, actually.
>
> Yes, both. The issue here is how to avoid duplicating perl code; once in ckeditor.html
> and than again in container.html.
> Much like the editor itself is handled.
> First suggestion would be:
> - adding a new file comp/widgets/wysiwyg/ckeditor.mc that returns the java arrays;
> which is called from either via mason component call.

I assume you mean "javascript." And that sounds fine, though please don't call it ckeditor.html if other WYSIWYG editors will end up using it.

> If you have some preferred approach (subroutine perhaps?), give me a hint.

You're a lot closer to this than I am. Go for it.

Best,

David

Hi,
one last remaining issue:
For this bricolage-wysiwyg interface the related media/stories needs to
be mapped to concerned html tags: <img>, <a> and <object>.
Relevant to <img> tag are all related media of mime type image/*
Relevant to <a> tag are all non-image related media plus related stories
Relevant to <object> are related media of mime type audio/*, video/*,
and application/x-shockwave-flash

This way, the editor plugins for image, link and object will access relevant
documents only.

Any complaints to this list are wellcome. :)

Regards, Zdravko

Sorry for top-post:

Flash has a number of different MIME types historically, though I'm not sure how this impacts your code.

Are you planning on support for HTML5 tags of Video and Audio?

...Ross...

--
-- I'm sorry if this e-mail is very short or seems terse. It is coming from my cell phone.

On Jan 9, 2011, at 11:54 PM, "Zdravko Balorda" <zdravko.balorda@siix.com> wrote:

> For this bricolage-wysiwyg interface the related media/stories needs to
> be mapped to concerned html tags: <img>, <a> and <object>.
> Relevant to <img> tag are all related media of mime type image/*
> Relevant to <a> tag are all non-image related media plus related stories Relevant to <object> are related media of mime type audio/*, video/*,
> and application/x-shockwave-flash
>
> This way, the editor plugins for image, link and object will access relevant documents

____________________________________________________________________
This e-mail, and any attachments, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information belonging to Planar Systems, Inc. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, any attachments thereto, and use of the information contained, is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the original and any copy thereof.
______________________________________________________________________

On Jan 9, 2011, at 11:53 PM, Zdravko Balorda wrote:

>
>
> Hi,
> one last remaining issue:
> For this bricolage-wysiwyg interface the related media/stories needs to
> be mapped to concerned html tags: <img>, <a> and <object>.
> Relevant to <img> tag are all related media of mime type image/*
> Relevant to <a> tag are all non-image related media plus related stories
> Relevant to <object> are related media of mime type audio/*, video/*,
> and application/x-shockwave-flash
>
> This way, the editor plugins for image, link and object will access relevant
> documents only.

I suggest looking at the Bric::Biz::Asset::Business::Media subclass of each object:

<a> = B::B::A::B::M
<img> = B::B::A::B::M::Image
<video> = B::B::A::B::M::Video
<audio> = B::B::A::B::M::Audio
<object> = [probably some awful special-case for flash]

Best,

David

> I suggest looking at the Bric::Biz::Asset::Business::Media subclass of each object:
>
> <a> = B::B::A::B::M
> <img> = B::B::A::B::M::Image
> <video> = B::B::A::B::M::Video
> <audio> = B::B::A::B::M::Audio
> <object> = [probably some awful special-case for flash]

<a> should deliver related_story, too. Right? But perhaps, no images. To make things
simpler.

Regarding the <video>,<audio> I'm not aware that wysiwyg editors support HTML 5, yet?!
The closest thing to insert video,audio is using flash plugin.

Zdravko

On Jan 10, 2011, at 11:56 PM, Zdravko Balorda wrote:

>>
>> I suggest looking at the Bric::Biz::Asset::Business::Media subclass of each object:
>> <a> = B::B::A::B::M
>> <img> = B::B::A::B::M::Image
>> <video> = B::B::A::B::M::Video
>> <audio> = B::B::A::B::M::Audio
>> <object> = [probably some awful special-case for flash]
>
> <a> should deliver related_story, too. Right?

Yes.

> But perhaps, no images. To make things
> simpler.

Huh?

> Regarding the <video>,<audio> I'm not aware that wysiwyg editors support HTML 5, yet?!
> The closest thing to insert video,audio is using flash plugin.

*BARF*.

I've gone Flash-free:

http://daringfireball.net/2010/11/flash_free_and_cheating_with_google_chrome

Best,

David

>> But perhaps, no images. To make things
>> simpler.
>
> Huh?

Well, a href pointing to an image? I don't see much use of this in
a wysiwyg editor.


> I've gone Flash-free:
>
> http://daringfireball.net/2010/11/flash_free_and_cheating_with_google_chrome

But this cancels out audio and video, too, because editors don't do HTML5?!

Zdravko

On Jan 11, 2011, at 10:07 PM, Zdravko Balorda wrote:

>
>>> But perhaps, no images. To make things
>>> simpler.
>> Huh?
>
> Well, a href pointing to an image? I don't see much use of this in
> a wysiwyg editor.

Okay, your call. I dub you the wysiwyg expert. I hate them. More even than Debian “stable.”

>> I've gone Flash-free:
>> http://daringfireball.net/2010/11/flash_free_and_cheating_with_google_chrome
>
> But this cancels out audio and video, too, because editors don't do HTML5?!

Yeah, slackers. Yet another reason for my well-directed and, of course, entirely rational hate. ;-P

Best,

David

>> Well, a href pointing to an image? I don't see much use of this in
>> a wysiwyg editor.
>
> Okay, your call. I dub you the wysiwyg expert. I hate them. More even than Debian “stable.”

There is still a text field one can type in any url. :) The interface will provide a
shortcut to linking releated stories while filling in "title" attribute, too.

I almost forget to ask: Could both, media and story have equal UUIDs?

Regards, Zdravko

On Jan 12, 2011, at 10:12 PM, Zdravko Balorda wrote:

> There is still a text field one can type in any url. :) The interface will provide a
> shortcut to linking releated stories while filling in "title" attribute, too.
>
> I almost forget to ask: Could both, media and story have equal UUIDs?

No.

David