Thread

Looking at the video I notice that it’s possible to create new pages which update the menu links. That’s one of those things you can’t do with pagelime. Also surprised to see WYSIGWYG editing. Maybe also a standard option for EE 2.x? When upgrading to EE clients might otherwise be surprised when they suddenly are looking at html code?

EDIT: nevsie’s comment crossed mine. I agree that switching to a different editing flow is a showstopper for clients, especially when it’s more challenging.  So when switching, ideally clients should be able to keep working the way they are used to.

Completely agree. WYSIWYG, and even the more broad work-flow around MojoMotor won’t be for everyone, in the same way that EE isn’t for everyone. Mojo is our attempt to build the opposite of “one size fits all”. For projects where it will work, I’m hopeful it will work well - but that might not be everything.

@nevsie: sorry communication hasn’t been what you want. We kept the price off the main site since it isn’t actually available for sale until we finish the final private beta. That should happen quickly, and then we’ll have it in your hands. What other questions can I answer for you?

Hi Derek - and thanks for the response.
In reference to MM - i can see roles where this will work well, and have clients which will suit it. I was just curious to know how you guys anticipated the move from MM to EE seeing as that is a feature as such.

In reference to communication - it is not so much what is being said but how it is being said (from where and how often). In my opinion if you state quite big revelations (EE2.1’s soon release) at public meetings then logically a full public statement would be made in a timely fashion to prevent speculation and to be honest keep traffic on your site. But getting dribs and drabs from other sites that you have to search out to keep in the know on a product that matters to our businesses - that then might not be factual as we have no idea how official it is…..... etc, etc.

I understand EE has grown quickly, and work flows that worked in the past may not be suitable now and that we as customers have a lot to learn, and you as a company have to learn how to handle us awkward customers too! But in short - we are businesses that have to make correct decisions (on our clients behalves) based on what we know - therefore we have to remain regularly informed and not make decisions based on unofficial speculation.

This situation kind of arose when EE2 was in development and we received updates roughly every two weeks (as a reaction to customer pressure). But since the BETA was released I can think of two updates (in 6ish months) with no real information on “yes this is going to be ready soon” or “no this is still a buggy beta” etc.

Perhaps I am off note here with my communication is key approach - other might agree/disagree? Perhaps I am trying to have a say in something that is not my business (but the community feel we have here makes me feel differently)...

AND, Finally… Sorry very off topic for this post… We can drop it here if people prefer!!!! 😊
It is not a rant or whinge - just open thoughts and discussion of my current opinion - which might be the odd one out i know.

Thanks, and good points. I assure you’ve they’ve been heard and taken to heart. Appreciate that you’d take the time to make them.

Thanks. And now on topic. CKEditor has been used in this (i am guessing from the video).
is it possible this integration will be heading EE’s way too to ease the upgrade integration as mentioned above? Or is this seen as treading on Brandon’s toes a little too much?

Hey, I thought you wanted to talk about Mojo! 😊

The editor in Mojo and that in EE are separate, and there is no current plan to port it over.

The first thing I thought when I seen Mojo, is that clients who have their site upgraded from Mojo to EE are going to straight away ask for the editor back. I can see this being a stumbling block.

The first think I thought when I seen Mojo, is that clients who have their site upgraded from Mojo to EE are going to straight away ask for the editor back. I can se this being a stumbling block.

Yeah, because it’s practically impossible for a seasoned EE developer to install one. If it doesn’t come out of the box it might as well not exist.

i think he was pointing out that the upgrade from a system with a editor to one without (or of equal strength by default) would be a bit irritating for many. Yes it is easy to go buy and install a third party extension to do this - but that also adds to the fee of the software. However, i suspect a free CK editor field will be released soon.

MojoMotor looks perfect for a current project. How soon will it be available, PLEASE?!

No official ETA yet, I am afraid. There will be a short Beta phase before the release. Pressed for a date I’d say a couple of weeks, perhaps? End of summer at the latest? Please don’t consider this an official estimate, though.

OK, thanks, Ingmar. That gives me something to hope for 😉

It’s not flash… it’s HTML 5 video, which hasn’t been included in FF 3.6 yet. I believe that’s coming with FF 3.7.

Greetz,
Wouter

Hm, its supposed to fall back to flash if HTML 5 video can’t be played, but I’m having troubles also. Sorry! Here’s a direct link to the video, and we’ll look into it more (I can’t play it in FF on mac either).

Sorry to bring this up, but Firefox 3.6 does support <video> tag (even 3.5 supports it), and the fallback to Flash only applies to browsers that do not recognise the <video>, not for other issues like the one here present (Firefox does support <video>, hence it doesn’t fallback to Flash [although I personally think it should]).

The reason the video doesn’t play in Firefox could be because the server hasn’t got the correct MIME type added. Or you could just change the extension to .ogg instead of .ogv.

Also, the type parameter is missing from the <source> tag. You need to add the video and audio codecs for the browser to know what source to play.

<source src="video.ogv" type='video/ogg; codecs="theora, vorbis"' >

/offtopic