Closed Bug 446072 Opened 13 years ago Closed 11 years ago

[Editor] Make the content area in the editor much bigger

Categories

(support.mozilla.org :: Knowledge Base Software, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Future

People

(Reporter: cilias, Assigned: paulc)

Details

(Whiteboard: tiki_fixed)

Attachments

(2 files)

The area where the article source is edited in the page editor should be a lot bigger (wider and taller).
Can you mockup how you want it to look like and attach it here?
There is a button on the left under "Edit" to make the edit field taller...is this not sufficient?
Assignee: nobody → paul.craciunoiu
Target Milestone: --- → 0.8
I don't think it can be wider, or it would conflict with the format of the page. But I made the default 10 rows taller in textareasize.php. That should help, unless a default is set somewhere else for $defaultRows
20 rows would have been taller than my 800px screen, which I think most people still have.
Comments?

svn r19309 (trunk)
svn r19311 (prod)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: 0.8 → 0.7.2
They look the same to me as well.
Reopening until we know what's going on.  I see the patch, clearly, I'm just scratching my head as to why this isn't evident on support-stage; Smarty cache, perhaps?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
So, since the line is:
$rows = isset($_REQUEST['rows'])? $_REQUEST['rows']: (isset($defaultRows)?$defaultRows: 30);

... maybe $defaultRows is set. If that is so, then it could have been set by an admin. I haven't used tiki wiki to know, but it seems that $defaultRows can be a variable stored in the db.
Ding! Got it! I set up a local copy of SUMO and logged in as admin.

Nelson: My SUMO db dump shows you were the admin user. Could you log in and change the textarea default size?

The link should be 
/tiki-admin.php?page=textarea

I see these as textfields:
-------
Default number of rows (wiki):  	
Default number of rows (comments): 	
Default number of rows (forum): 	
Default number of rows (forum replies):
-------

If anyone in this bug wants specific sizes or increase in comments or replies, say so please. So far the (wiki) and (forum) should be increased to ~30.
Done. No code committed, used admin rights to change prefs.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Re-opening.
This shouldn't be part of 0.7.2. Sorry for not making this clearer earlier. This is about making the content area wider as well as taller, and is part of the editor redesign.
<http://blog.mozilla.com/sumo/2008/11/05/article-editor-mockups/>
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 0.7.2 → ---
So now it is both taller and wider, right? Why is it reopened?
AFAICT, it is not wider. If this were to be applied to the current editor, that would constitute getting rid of the "Edit" button to the left of the content area. Again, I'm sorry for not clarifying this earlier. My fault. :-(
Chris, can you submit a screenshot of how it looks like today and how you want it to look like?
Attached image current editor
Attached image wider content area
Sounds good, when would we like to have this?
Suggest Future since this hasn't been requested by other article editors (that I'm aware of, at least). If there are no lower priority bugs in your todo list, Paul, feel free to submit a patch. :)
Target Milestone: --- → Future
We can get this done when we get to an editor-redesign milestone.
Summary: Make the content area in the editor much bigger → [Editor] Make the content area in the editor much bigger
There is a full screen mode in recent versions of Tiki:
http://doc.tikiwiki.org/Fullscreen

You can swap from normal to fullscreen when in edit mode.
Whiteboard: tiki_fixed
Status: REOPENED → RESOLVED
Closed: 13 years ago11 years ago
Resolution: --- → INCOMPLETE
fixed in kitsune 
https://master.support.mozilla.com/en-US/kb/How%20to%20set%20the%20home%20page/edit
Resolution: INCOMPLETE → FIXED
You need to log in before you can comment on or make changes to this bug.