Re: silva-2.2: comments

Sylvain Viollon <[email protected]> Tue, 2 Jun 2009 11:03:31 +0200
Newsgroups gmane.comp.web.zope.silva.devel
Organization Infrae
Message-ID <[email protected]>
Le Mon, 1 Jun 2009 22:15:56 -0500,
Andy Altepeter <[email protected]> a écrit :

> Hi Marc,
> 

  Hello,

> Thanks for your feedback.  I'll address the items I can below:
> 
> On Sunday 31 May 2009 03:55:31 pm Marc Petitmermet wrote:
> > uploading image:
> > why do i have to browse again for the image when i forgot to enter
> > the required title?
> I think this is standard web behavior for file input fields.  The
> path isn't sent to the server (that's a security issue), only the
> contents of the file. So unfortunately it is impossible for Silva to
> re-populate the image path.

  It's an input file. There is no way that the page can remember the
  file, as it's not send to the server, since the browser just send the
  data of the file. After the item is created when the form is
  successfully validated. This prevent to create a temporary item, that
  if the user click somewhere else (like a navigation tab on the top)
  would stay in an inconsistent way.

  To get that feature we would need ajax validation in the SMI (that
  will come one day however, 2.3 or after).

> >
> > smi image:
> > the image assets are represented with the icon "silvafile.png"
> > instead of the icon "silvaimage.gif" (why the mixed image formats?).
> This is now fixed.

  I have to check that as well, but the icon for image has never been
  the same in a listing, when you add and edit. This confused me.

[...]

> > warning message: what is the definition of "valid relative silva
> > references"? what about "valid absolute silva references", won't
> > they be edited? don't you mean local and external references here?
> An ajax call to Silva happens whenever the button is clicked and
> there is text in the input field.  Silva then determines if the text
> is a link to a Silva object, and returns an absolute edit url.  If it
> isn't an editable link, the alert message is displayed.
> 
> This initial implementation needs relative links, which are the
> easiest to resolve to Silva objects.  If it has to deal with absolute
> urls, Silva then needs to know how to translate a server name to the
> root of a vhost within Silva.  A single silva root could support
> multiple virtual hosts, but Silva doesn't necessarily know that.  It
> only knows about the vhost you're accessing from.
> 
> I recall Kit and I chatting about this feature.  I had forgotten
> this, but we decided to try out absolute urls for the host you're
> accessing silva from as well.  Zope does provide a nice method to
> translate this type of absolute url into a zope path.  I'll put this
> on my list.

   A robust implementation for links in document is forcasted as well.
   That would use zc.relationship, so you could move document around
   without breaking links, and you will know as well if you delete a
   document which is linked in one other (maybe 2.3 since we would
   like to have 2.2 out).


> >
> > lookup users.../groups admin...:
> > i think since silva-2.1 (i don't know about 2.0) the "lookup
> > users..."/"groups admin..." buttons have been moved away from their
> > boxes on the right side to the top left side of the smi. i miss them
> > at their old locations, it was much more convenient.
> I didn't make this change, so I can't really comment other than to
> say I agree with Marc.  My muscle memory is stronger than the
> standardization of actions into the middleground.

   It's only for the standardization. And I think it's less confusing
   for user to find actions always at the same place. And now, you can
   add actions without having to replace all the code SMI of the page:
   you can write extensions which add actions to a SMI screen, and have
   more than one living peacefully on your instance (without anything
   (dirty) to do).

> >
> > export to open document (odt):
> > nice that this feature is now built in. i had quite good experience
> > with https://viewvc.infrae.com/svn/silva2odt/ by dave kuhlmann. this
> > built in export has still a few issues like missing images, list
> > styling, export of complete branches.
> Is there a launchpad bug to tracking these issues?  I can only hope
> Dave will come out with version 2 of silva2odt which includes these
> features...

   It's in 2.1 as well. I did it from scratch actually, since it was
   difficult to integrate silva2odt in Silva. It's working with XSLT. I
   didn't spend a week on the stylesheet, so if there is a sponsor for
   a better *style* it will be welcome. The idea as well is to be able
   to select alternate 'templates' (made in OpenOffice) so you can
   style your documents to the style of your university/company.

> 
> Thanks again for your valuable feedback.  I know your contributions
> are much appreciated in this community.
> 

   Thanks for feedback as well,

   Sylvain,

-- 
Sylvain Viollon -- Infrae
t +31 10 243 7051 -- http://infrae.com
Hoevestraat 10 3033GC Rotterdam -- The Netherlands

_______________________________________________
silva-dev mailing list
silva-dev-IAPFreCvJWM6s/[email protected]
https://lists.infrae.com/mailman/listinfo/silva-dev
signature.asc (application/pgp-signature, 188 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)

iD8DBQFKJOrmdgb223auxaoRAhhUAJ9oXYtBo//yt+ne8HZLGd4VvwPzvACfQw72
+W18FHExVPo5OPGaTTymP14=
=QqDq
-----END PGP SIGNATURE-----