HI Jonathan -
Funny thing - I (for various reasons) have been using Google Chrome browser,
and the editor simply does not work with that (I don't get _anything_ but an
editable text area).

If I _really_ want to edit thru browser, I go to my Firefox.   While the
editor is _interesting_ there, I (personally) don't find it to be enough for
"real work" - so with Firefox I simply install the "Its all text" plugin and
configure it to use my favorite editor (gvim in my case, but it can be
anything).

Now - all issues of session, font size, etc.  are ... irrelevant and
decoupled.

I like it this way - I don't care what web2py editors do;  for me it's just
for an occaisional convenience, not main use.

Of course everyone will not approach it this way - but for serious work, I
use other channels (its-all-text is only small level;  I really prefer
parallel work in WingIDE).

Just to show another perspective on this topic.

Regards,
Yarko

On Tue, Mar 3, 2009 at 6:45 AM, Jonathan Benn <[email protected]>wrote:

>
> Hi all,
>
>
> A long-standing issue I've had with the EditArea in web2py's Admin
> interface is the default font size. I don't have the best eyes, and so
> in Firefox I set the minimum font size to be 12. The default font size
> for EditArea is 10. As a result, Firefox ends up garbling the code in
> EditArea. This required me to manually change the font size every time
> I reloaded an editing page.
>
> I'm not the only one with a similar problem. Here's an old discussion
> on the issue from the Gluon days:
>
> http://groups.google.com/group/web2py/browse_thread/thread/8bb6718600ad886/db2f0c855daba4aa?hl=en&lnk=gst&q=font#
>
> Today I figured out how to fix the issue. The fix for this is to edit
> the following file:
> web2py/applications/admin/views/default/edit.html
>
> Find these lines of code:
> editAreaLoader.init({id: "body",start_highlight: true,allow_resize:
> "both",allow_toggle: true,language: "en",syntax:
> "{{=filetype}}",replace_tab_by_spaces: 4});
>
> And just add a few extra settings:
> editAreaLoader.init({id: "body",start_highlight: true,allow_resize:
> "both",allow_toggle: true,language: "en",syntax:
> "{{=filetype}}",replace_tab_by_spaces: 4, font_size: 12, fullscreen:
> false});
>
> The full list of parameters is available here:
> http://www.cdolivet.net/editarea/editarea/docs/configuration.html
>
>
> What I'd like to do is for users to be able to set the defaults in
> some kind of initialization file for the Admin interface. This kind of
> init file could be generally useful for things other than EditArea
> too. There doesn't seem to be any init file at the moment though.
>
> Does anyone else think this is a good idea?  Are there any other
> default settings that should be moved into a user-editable init file?
> Are there any objections to adding an init file to the Admin
> interface?
>
>
> Sincerely,
>
> --Jonathan
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to