On Thu, 15 Aug 2013 14:38:44 +0300
"Ville M. Vainio" <[email protected]> wrote:
> I would speculate this causes huge performance regression when moving
> through the tree with cursor keys (and e.g. across set of siblings where
> every other node is @rich, every other is not). Am I wrong?
I don't think there's any regression... regression would be noticeable
slow down of movement through non-rich nodes because of the scanning
for @[no]rich directives, which is
for nd in p.self_and_parents():
if '@norich' in nd.h or '@norich' in nd.b[:1000]:
do = 'close'
break
if '@rich' in nd.h or '@rich' in nd.b[:1000]:
do = 'open'
break
I don't see an impact from this - there must be some impact, but if
those operations are cheap enough, it won't be perceptible. And of
course only applies if you enable the plugin.
Alternating rich non-rich nodes, if someone insists on setting up such
a case :-) will be slower than moving through non-rich nodes, but I
think the real issue is the speed of moving through a series of rich
nodes, i.e. it's page load time rather than widget swap / setup time.
This is slow, because of the web page load / layout times. Which is why
it would be better to use a native (Py)Qt rich editing GUI, instead of
running a browser in a window to use a javascript app. But there isn't
one.
Cheers -Terry
> On Wed, Aug 14, 2013 at 6:14 PM, Terry Brown <[email protected]>wrote:
>
> > On Wed, 14 Aug 2013 09:21:34 -0500
> > Terry Brown <[email protected]> wrote:
> >
> > > On Wed, 14 Aug 2013 09:32:45 -0400
> > > Jacob Peck <[email protected]> wrote:
> > >
> > > > Terry, any chance of supporting a '@rich' node type, such that when an
> > > > @rich node is selected, it automatically switches to the CKEditor, and
> > > > perhaps autosaves without user intervention? I suppose that could be
> > an
> > > > add-on plugin, but it seems like it would make sense in the core of
> > this
> > > > plugin as well.
> > >
> > > Excellent idea. So the rule would be:
> > >
> > > cke-text-open is called whenever a node is selected that includes
> > > "@rich" in its headline, or is the descendant of a node which includes
> > > "@rich" in its headline.
> >
> > This is pushed:
> >
> > @rich in the headline or first few lines (1000 characters) of a node or
> > its ancestors will automatically open the rich text editor. @norich cancels
> > this action. Manually opened editors are not affected.
> >
> > Cheers -Terry
> >
> > > And when rich text is opened by the above mechanism, it will be
> > > automatically closed when a node not matching the above criteria is
> > > selected.
> > >
> > > I don't know if you need any way of disabling the behavior, I suppose a
> > > toggle wouldn't hurt, but you can access the Body pane when the rich
> > > text pane is showing using the free_layout right click on the divider
> > > functionality.
> > >
> > > Cheers -Terry
> > >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "leo-editor" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [email protected].
> > To post to this group, send email to [email protected].
> > Visit this group at http://groups.google.com/group/leo-editor.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
> >
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
