Well, I fixed the last call conflict (my bad with the TEH extension), but looks like even just including Prototype and disabling all other javascript causes errors with Playa, so no quick fix here from me unfortunately.
I think I’ll still look at getting rid of the Prototype dependency, since that’s silly anyway, but I’m not sure how quickly I can get that done unfortunately.
One question: do you guys think going the full custom field type is the way to go? My only issue there is how to handle flipping formatting back to “none” or “xhtml” to hide the editor. edit-add: duh, just took a closer look at the markitup fields, pretty slick!
I know jQuery has a no conflict mode, but I’m not as familiar with Prototype. Does that have something similar? How exactly are you using it - to append the buttons to the fields?
If you did a “full” custom field, you could easily loop through those field types and look for those whose formatting is textile (actually that second step might even be redundant then). Then (with jQuery it would be pretty easy) to find the select box below the textarea and toggle the Textile editor buttons on/off based on whether it reads textile or not.
I’d love to take a stab at that but I’ve wasted enough time this week…I really have to get to the client work!
@Dan - think we might mean 2 different things here - Ryan might be experiencing the list bug, good call - I forgot about that since I fixed that in the EE textile plugin long ago. But above I actually was referring the fact that with TEH you can select a multi-line list and click the list button, and it formats each line with the asterisk for you (and even cleans up bad bullet characters on Mac), but with Markitup you have to select each list line individually and click the bullet button (unless I’m missing something)…that’s all I was referring to. It’s amazing how many lists I seem to always be pasting in and formatting so it’s the little things…
I’ve run into both things.
1) In markitup, you do have select each list item individually to make a list…yuk. I’m not finding a fix for that. lavalamp - do you think it would be possible to alter markitup’s code with however you’re doing yours for lists?
2) Also, I’m using the Textile plugin under the hood for my markitup custom field - I guess you’d say as the parser. Is there something I’m supposed to to to that to help markitup render lists correctly? (actually that was due to the Textile bug Dan mentioned - I just tweaked the textile plugin and lists are working fine now).
I guess there’s really no reason I can’t release a down and dirty markitup Extension at this point. Although I totally agree with lavalamp - why the heck can’t you select multiple lines and convert that into a list all at once?
Ignite, I started a thread about the Markitup extension, just so you know. I think it’s good enough to start out as a version 0.9, and I would really appreciate feedback. I’ll see if I can package it up tonight, and offer it for download with a few (friendly) warnings and instructions.
Sorry for the delay…been enormously busy with client work lately.
OK, this extension is now available at my Markitup Extension page. Give it a try and let me know what you think. I’m sure there will be suggestions, but hey, at least it’s out there.
There is also a thread about it here.
In Textile mode, the last item always breaks off into another list, no matter what.
I think this is a Textile bug, see here: http://ellislab.com/forums/viewthread/68575/
Yep, you’re right Nathan. I made sure to put the “proper” Textile plugin in with the other files in the Markitup extension.
I really would like a “Middle Ground” extension though…basically TEH, but TEH running on jQuery. I like Markitup (otherwise I wouldn’t have spent time making an Extension) but sometimes I want to be able to switch formatting type right there on the publish page (can’t do that with the Markitup Ext) and I don’t necessarily need the super-fancy skin, either.
Ugh, I wish TEH played nicer with the other kids in the schoolyard. Figured out how to get it to work alongside Playa by changing Playa’s priority to 11, but now I’m finding that TEH conflicts with my extension Dulee Noted. Maybe I have to put Dulee Noted into non-conflict mode.
There’s always something!
UPDATE: Putting Dulee Noted’s jQuery in no-conflict mode didn’t solve the issue, nor did changing the priority. If I can figure out how to put TEH on jQuery, believe me, I’m going to do it!
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.