Jason, I'm looking forward to installing your extension. I too like
textile (though what drove me to it was the ability to add styles to the
tags that it creates -- don't think markdown can handle that).
That said, I too would like a markdown toolbar. Personally, I'd start
with what Ryan Joh
Simon Rönnqvist said the following on 11/20/2008 02:48 PM:
> OK, sounds like you did a pretty thorough comparison of the two.
> Personally I just picked Markdown cause it seemed easier to teach my
> clients doing ## than h2. And also a few other things seemed more
> simple to learn, and all o
OK, sounds like you did a pretty thorough comparison of the two.
Personally I just picked Markdown cause it seemed easier to teach my
clients doing ## than h2. And also a few other things seemed more
simple to learn, and all of the tags that I needed to get done were
doable using Markdown,
Jason Garber said the following on 11/20/2008 10:38 AM:
> Anton,
> I wasn't sure what you meant about people your age, so I looked back at
> what I sent. I added 50-ish to quantify "a lot," not to describe the
> age of the technically-challenged users. Sorry for the
> misunderstanding!
Life's l
Perhaps you need to do a rake radiant:extensions:update_all?
This happens automatically when you install extensions via ./script/
extension install extension_name, but if you installed them by just
copying the files in, you may have missed updating the instance with
images, javascripts, and
I have a little different take: I really like Markdown for plain text
documents that are to be read as plain text and might be converted to
HTML, but Textile works better for me when I'm using it as a shortcut
to HTML (and it won't be published plain-text). I tried Markdown
before I'd ever
Hi!
I installed your extension along with the other extensions that you
made + page_attachments. I ran rake migrate:db:extensions and
everything seemed to go fine... I also saw them show up under
Extensions in Radiant. However, no toolbar ever showed up for me, and
below the content fie
Anton,
I wasn't sure what you meant about people your age, so I looked back
at what I sent. I added 50-ish to quantify "a lot," not to describe
the age of the technically-challenged users. Sorry for the
misunderstanding! We have about 50 "curators" who update our web
site. Most of them
Hi!
Personally I feel that Markdown is easier to learn for noobs, and
would really have liked to see your extension done with Markdown.
However, maybe your toolbar makes the reduces the differences in ease
of use between Markdown and Textile.
Maybe even Textile is better in conection to
Jason Garber said the following on 11/20/2008 08:50 AM:
> [...]
>
> [ANN] radiant-textile_editor-extension makes Radiant really easy to
> use for non-technical content editors!
>
> [...]
>
> If you're using Textile, make sure you're using version >= 4.0. A
> lot of the hate on RedCloth was
Hi!
Just a short note about note about how you can make TinyMCE into
something pretty close to WymEditor: As I mentioned earlier I've tried
a "tightly configured" TinyMCE, by that I mean that I made available
only the few things that I felt that my customer needed... and those
pieces of
I'm catching up to this interesting thread a couple days late, but I
can't believe no one's mentioned my textile_editor extension yet!
I'm hurt! (jk!) It would have helped if I'd have announced it to the
list when I released it in September, huh? :-)
[ANN] radiant-textile_editor-extension
I am happy my frustrations resulted in some discussion and good ideas.
The ideas for extensions for a scratch pad, filter toolbars and som
WymEditor + paperclipped would all be highly usable to me, but I don't
have the time to build any of them right now.
I have used TinyMCE filter for some
Hi!
Yes some WymEditor + paperclipped combination could be really cool.
I've never really used WymEditor for any of my clients.. but I've
tried both Markdown and a tightly configured TinyMCE (which would be
pretty close to WymEditor). With Markdown I've seen that the content
remains lar
Steven Southard said the following on 11/18/2008 01:33 PM:
> I think maybe you just need to take another approach with her. Seems
> sometimes web development is more psychology then programming. Does
> she just put her hand over her ears when you say Markdown or Textile?
> I've had a clien
Adam van den Hoven said the following on 11/18/2008 01:42 PM:
> You just hit on an interesting idea for an extension.
>
> Frequently, people are going to reuse the same bits over and over.
> Instead of making them go find it, what if we put a "scratchpad" on
> the right hand side of the parts
A couple of thoughts.
1) In general, isn't it the case that the site developer is going to
want to deal with content. When you're creating content, you're seldom
calling for the the part of some other page (I prefer to do this sort
of work in the the layout myself). I'm not sure exposing co
Alright, since this post is already heading in this direction, I'll
throw out some ideas that I've been working on. These are getting
pretty refined in my mind and I'm looking into creating an extension
around them (possibly waiting for the new UI, we'll see)...
1. I think the textareas nee
On Nov 18, 2008, at 1:42 PM, Adam van den Hoven wrote:
You just hit on an interesting idea for an extension.
Frequently, people are going to reuse the same bits over and over.
Instead of making them go find it, what if we put a "scratchpad" on
the right hand side of the parts (which will co
That's actually something I'd use. I really like that idea. It's
kind of there with the filters and available tags but I really like
the idea of a customizable scratch pad. I'd use it all the time.
Steven
On Nov 18, 2008, at 12:42 PM, Adam van den Hoven wrote:
You just hit on an intere
Casper Fabricius wrote:
However, I have a client whose content editor is very frustrated with
the system. She can only just tolerate using Markup, and she refuses
to write any kind of HTML - Radius tags falls into this category from
her point of view. According to her, a proper CMS would hide a
You just hit on an interesting idea for an extension.
Frequently, people are going to reuse the same bits over and over.
Instead of making them go find it, what if we put a "scratchpad" on
the right hand side of the parts (which will consume some space from
the parts but that should be OK t
I think maybe you just need to take another approach with her. Seems
sometimes web development is more psychology then programming. Does
she just put her hand over her ears when you say Markdown or Textile?
I've had a client like that! She just wants to make headers,
paragraphs, and upl
I'd like to see this too. I use it for exactly this purpose, to give
non-technical people the ability to manage a simple website using a
CMS. To be honest, I think that the mostly technical person doesn't
really need an OS CMS, they can either hand code the HTML just as
easily (maybe run so
24 matches
Mail list logo