[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kupu-dev
Subject:    Re: [kupu-dev] kupu 1.4b1 testing report
From:       Duncan Booth <duncan.booth () suttoncourtenay ! org ! uk>
Date:       2006-10-03 16:53:56
Message-ID: Xns9851A00593F5Cduncanrcpcouk () 127 ! 0 ! 0 ! 1
[Download RAW message or body]

"Jon Stahl" <jon@onenw.org> wrote:

> I've put Kupu 1.4b1 through its paces on my Plone 2.5, Zope 2.9.4,
> Python 2.4.3 instance, and here are my notes.  I hope they are
> helpful. This is shaping up to be a huge leap forward for Kupu, and
> I'm extremely excited to start rolling it out across our 70+ sites.
>  
> 1) When kupu loads object icon images in the browse drawer, for a site
> at http://cms.onenw.org:10080/kupu2, it seems to be calling the images
> as <img
> src="http://cms.onenw.org:10080/kupu2/kupu2/document_icon.gif"> rather
> than what I'd expect: <img 
> src="http://cms.onenw.org:10080/kupu2/document_icon.gif">.  This
> doesn't cause problems on a normal Plone install, but it doesn't seem
> right, and it's breaking when I install one of our custom products,
> for reasons I don't fully understand.  I can supply some screenshots
> if what I'm describing isn't clear.

Fixed: I found a bug report for Plone topics which used to have the same 
problem: the catalog stores the icon path relative to the Zope root, not 
relative to the Plone site root. The solution is to ignore the catalog and 
get the icon from the types tool instead.

>  
> 2) There seems to be no way to remove a span style once applied.  That
> is likely to frustrate users.

New '(remove style)' option automatically added to the style pulldown. This 
removes the most obvious style it can find.

> 3) There seems to be no way to set an anchor tag <a name="foo"> on an
> arbitrary chunk of text that is not defined by a div or span style.  I
> think most users would expect to be able to just select a chunk of
> text and hit a button to apply an anchor tag.  (That is how most
> WYSIWYG editors work.)  Then they would expect to use the new anchor
> tag button to link to it.   Instead, Kupu seems to automatically
> create <a name> tags only "on demand."  Which is cool, but confusing. 
> (see next item) 
>  
> 4) The anchor browse drawer, whilst extremely cool once you understand
> it (see above) is a bit opaque at first glance.  I think it would
> greatly benefit from some help text that explains how it works, if
> that's possible.

I've added some help text to the anchor drawer.


[prev in list] [next in list] [prev in thread] [next in thread]