Lisp HUG Maillist Archive

URL in a rich-text-pane

Hi,

I am trying to programmatically turn a URL in a rich-text-pane into a  
highlighted, clickable link.  If I manually select the text in the  
pane and right click, OS X gives me an option "Make Link", but I  
would like to do this automatically when the pane is created or  
displayed.  Any suggestions?

Thanks,
-Chris

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________


XMLS:parse very slow

I am using XMLS:parse on a 500KB file and it takes four minutes.  Is this 
normal?  Is there a faster alternative?  Thank you.

Mitch 


Re: XMLS:parse very slow

On Thu, 14 Sep 2006 16:10:02 -0400, "Mitch Berkson" <mitch@bermita.com> wrote:

> I am using XMLS:parse on a 500KB file and it takes four minutes.  Is
> this normal?

I think if that's fast or not depends very much on the contents of the
file and on your machine.

> Is there a faster alternative?

There are several other Lisp XML parsers out there:

  http://www.cl-user.net/asp/tags/XML
  http://www.cliki.net/XML

I've found CXML to be pretty nice.


Text/editor pane vs list pane, design decision

Hi,

I've noticed that text-input-panes differ from things like list panes,
in that they don't hold arbitrary objects; only text. Wouldn't it be an
improvement to let them contain arbitrary objects, and have them use a
print function to find a textual representation?

I understand that text panes are modifiable in ways that list panes
aren't. However, the underlying objects within list panes are also
modifiable. And it'd be convenient to get the underlying textpane object
in addition to the (user-modifiable) textpane text.



MfG,
Tayssir


Re: Text/editor pane vs list pane, design decision

On Sat, 16 Sep 2006 11:09:47 +0200, Tayssir John Gabbour <tjg@pentaside.org> wrote:

> I've noticed that text-input-panes differ from things like list
> panes, in that they don't hold arbitrary objects; only
> text. Wouldn't it be an improvement to let them contain arbitrary
> objects, and have them use a print function to find a textual
> representation?
>
> I understand that text panes are modifiable in ways that list panes
> aren't. However, the underlying objects within list panes are also
> modifiable. And it'd be convenient to get the underlying textpane
> object in addition to the (user-modifiable) textpane text.

Note that text input panes have a change callback, so you can subclass
them and implement the behaviour you want.  I've done something
similar for a project I'm working on, but I'm afraid I can't show you
the code as it's proprietary.

Cheers,
Edi.


Updated at: 2020-12-10 08:47 UTC