[Phoenix] Dialog messages
Michael Wechner
michael.wechner at wyona.com
Wed Sep 6 23:46:49 CEST 2006
Andreas Wuest wrote:
> Hi
>
> On 6.9.2006 16:15 Uhr, Michael Wechner wrote:
>
>> Andreas Wuest wrote:
>>
>>> Hi Michi
>>>
>>> On 6.9.2006 15:37 Uhr, Michael Wechner wrote:
>>>
>>>> Hi
>>>>
>>>> I have tried to use "Ulysses/Yulup" to edit Atom entries within the
>>>> WordPress example but received messages such as
>>>> "Could not be saved". Andi told me that the actuallly it is probably
>>>> an authorization error (401).
>>>>
>>>> I think it would be nice if the dialogs could show this, e.g.
>>>> "Authorization denied! Document could not be saved/opened"
>>>
>>>
>>>
>>> I am currently refactoring the Neutron-Auth implementation. After
>>> this is completed, I can easily enable Neutron-Auth for APP/Atom, and
>>> I can also improve error handling while I'm at it.
>>>
>>> So, ETA of all of this would be tonight.
>>
>>
>> sounds cool :-)
>
>
> Well, all three things are done.
very cool
>
> Unfortunately, the message display is not optimal. If we have to display
> something to the user, it MUST be localised. Of course, we should not go
> around and localise exceptions (and even worse, in components which are
> not actually connected to any UI stuff).
>
> So, for the moment, it's hardcoded in english. A viable path would be to
> create exception classes for all the possible things we want to report
> to the user, and then localise them at display time.
well, I guess standard stuff like 401 could be localized within "Yulup"
itself, but server specific exception messages cannot except if these
would follow a standard or would check on the browser language.
Michi
>
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://cocoon.apache.org/lenya/
michael.wechner at wyona.com michi at apache.org
More information about the Phoenix
mailing list