Hi, On Fri, Aug 7, 2009 at 12:00 PM, Vincent Massol <vinc...@massol.net> wrote:
> > On Aug 7, 2009, at 11:52 AM, Guillaume Lerouge wrote: > > > Hi, > > > > On Fri, Aug 7, 2009 at 11:34 AM, Vincent Massol <vinc...@massol.net> > > wrote: > > > >> > >> On Aug 7, 2009, at 11:22 AM, Guillaume Lerouge wrote: > >> > >>> Hi Devs, > >>> right now an user can go to the Office Importer page and try > >>> uploading a > >>> file even when the backend OOo server isn't running. This leads to > >>> usability > >>> issues. Thus I'd like to send a vote on the following 2 items: > >>> > >>> - On the Office Importer page, add the following message: > >>> - > >>> > >>> "You cannot import an Office document since the conversion > >>> server has not been started. Please ask an administrator to get it > >>> started for you." > >>> > >>> - > >>> > >>> If the current user is an admin, the message should read: "You > >>> cannot import an Office document since the OpenOffice server has not > >>> been started yet. You can start the OpenOffice server and manage it > >>> from this page (link to the OOo server administration page)." > >> > >> +1 > >> > >>> - > >>> > >>> In the action bar: add a check to see whether the OOo server is > >>> running and don't display the link if the OOo server is not. > >> > >> -0 > >> > >> I'm not a big fan of magically hiding things. How will a user know > >> there's an office import feature? > >> I prefer that the menu entry stays and the page explains that the > >> office importer is not started. > > > > > > That's basically the issue. If we leave the link, we build an user > > expectation. The expectation isn't fulfilled and the user is left to > > contact > > his/her administrator, which is frustrating. > > No it's good. It's the pb of the admin if he has forgotten to start it. > > > Additionally, under some > > circumstances the OOo server cannot be installed at all (this has > > happened > > at customer sites). The project manager is then left to explain why > > the > > server can't work and has to handle additional questions. > > No: in this case the admin should remove the officeimporter app. The only drawback I see is that until we have an application manager it's a bit harder for the Admin to bring the application back after deleting it (he needs to re-install it instead of simply changing a configuration setting). But indeed, it's not a big drawback. The admin could also simply rename the page. Since the 3rd option (hide the menu if the application isn't installed) is already implemented, I think we can cancel the second part of the vote. Asiri, ping me if you need help for the message's wording. Guillaume Thanks > -Vincent > > > Thus I think the user doesn't have to know that the feature exists > > if the > > administrator has not activated it. The question then becomes: how > > does the > > administrator knows that the feature exists? I can see 2 options: > > > > - Make the check be: "if the user isn't an admin & the server isn't > > running" so that admins know about the feature > > - Keep the check as it is and assume that admins that want to make > > the > > OOo server work will find out how since it's an often requested > > feature > > > > I'd like to add a new behavior though (if it's not already done): > >> - if the office importer app is not installed (we can test for the > >> main office importer page availability) then the menu entry shouldn't > >> appear. > >> > > > > The OOo app comes bundled by default with XE. It's always there by > > default. > > This option doesn't solve the user expectation issue. > > > > Guillaume > _______________________________________________ > devs mailing list > devs@xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Guillaume Lerouge Product Manager - XWiki Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/ _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
