bishop335 / subtext

Automatically exported from code.google.com/p/subtext
0 stars 0 forks source link

Preview function is requested #250

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Doesn't matter what type of editor I choose, I want to see a preview of my 
content before actual post. Preview should give the same result as I would see 
blog post in my blog.

On edit page, there should be link button "Preview". By clicking on link, new 
window is opened, showing a previeved content.

ps. sure, if it is approved I could work on that :)

Original issue reported on code.google.com by alexande...@gmail.com on 1 Aug 2010 at 8:31

GoogleCodeExporter commented 9 years ago
Even without going to a full preview feature (which could be complicate), a 
possible approach could be to allow logged in users to see "draft" and "future" 
posts.
And the "preview" would simply be saving in draft and redirecting to the post 
page.

Original comment by simone.chiaretta on 1 Aug 2010 at 8:52

GoogleCodeExporter commented 9 years ago
Simone,

I've got several solution in my mind:

1. Subtext style (just like you describe). Near "post" button, we have "draft" 
button. On "draft" button pressed, post saved as draft. On post page logged 
user sees his post marked as draft.
2. Blogger style. We have "preview" button. By pressing on this button new 
frame opened (page is not reloaded) showing the content. It is not 100% exact, 
because not all styles applied, but could show how rendred html looks like.
3. Stackoverflow style. At the bottom of edit post control, we have another 
control, that showes rendred content of post. As user types something in edit 
post, it immediatelly showed in preview control.

I like stackoverflow variant, but it could be usefull for QnA small post, but 
not very much for blogging. So, variant 2 could be one to pickup. But seems 
variant 1 more easy to implement (don't know yet :)).

What do you thing on that ? 

Original comment by alexande...@gmail.com on 2 Aug 2010 at 5:59

GoogleCodeExporter commented 9 years ago
I don't really see the need to do a live preview on the post page:
1 - CKEditor is WYSIWYG so you already preview the formatting
2 - CKEditor has the preview button, which could be configured to use the css 
from the skin.

Of course if you use the plain text editor than a preview might be needed, but 
I think that adding the feature to allow logged in admins to see unpublished 
and future posts is enough for most of the things.

Additionally we could also look at finding a way to inject the css from the 
current skin in the preview page in CKEditor.

Original comment by simone.chiaretta on 2 Aug 2010 at 2:03

GoogleCodeExporter commented 9 years ago
OK, I'll  try "draft" approach then :)

Original comment by alexande...@gmail.com on 2 Aug 2010 at 7:51