Hi guys - Ryan, I wanted to say thanks for all your detective work - I’ve got at test install of playa and teh going now so I’ll see if I can get a fix going - probably later tonight. Sorry to have ignored this thread lately… have been swamped with client work.
Also, I like markitup, but not being able to do multi-line lists is a deal-breaker for me, otherwise I’d be much happier with a jQuery solution too. I don’t think the Slate guys are really using prototype for anything other than attaching the domready event and instantiating the class - if I can’t resolve the conflict cleanly I might try porting it. That was my plan for EE 2.0 anyway, unless something better comes along of course…
This TEH alternative is shaping up nice (see attached screenshots). Per field settings, most importantly. I think it’s ugly as heck under the hood, but it seems to be working, at least.
I really should be working on client work right now…
Also, I like markitup, but not being able to do multi-line lists is a deal-breaker for me
I didn’t understand what you meant by this at first, but now I think I get it: this thing doesn’t do lists well at all. In Textile mode, the last item always breaks off into another list, no matter what. I tried everything, short of resorting to full-on html. Is that what you were talking about?
Otherwise, this thing is crazy, and it loads extremely fast, even on my test page where I have three Markitup fields, each set to a different setting.
Are we going to get to see the finished extension soon Ryan?
Oh go on! Please, pretty please!
Looks great what you have done so far. Would love to see how it is all done though, I mean integrating something external into an extension. There’s quite a few things I’d like to do like that and give out to the EE community if only I had the knowledge of how to do it and this would be a great leap-board to learning all of that I reckon.
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!
I didn’t understand what you meant by this at first, but now I think I get it: this thing doesn’t do lists well at all. In Textile mode, the last item always breaks off into another list, no matter what.
I believe you may be referring to a Textile bug, for which there is a fix: see here and here.
@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…
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.
I’m not yet using the Markitup extension myself, though I’m going to have to start real soon, because I’m finding the “Playa” extension to be invaluable, and TEH and Playa just do not play nice together.
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.
