Reminder: Zikula Meeting 2009-08-05 @ 15:00 UTC (11 AM EDT)
satya.komaragiri at gmail.com
Fri Aug 14 10:07:38 UTC 2009
2009/8/13 Toshio Kuratomi <a.badger at gmail.com>:
> When hitting the login screen:
> "Error: This browser maybe incompatible with Beacon. Please use Firefox
> 3.0+ only."
> That's not a very nice message. If Beacon uses standards compliant
> browsers as well. Maybe downgrade to a warning? Or having a blacklist
> instead of a whitelist? (Note that it already seems to be a warning --
> I'm able to login and use Beacon using arora (webkit based) despite the
The problem with other browsers is that contentEditable (or
designMode) implementation varies a lot and Firefox has the most
consistent behaviour (I have not checked *all* the browsers but tried
on most of the widely used browsers). Other than that Beacon uses
standards compliant JS.
Beacon does not prevent you from using any other browser but it cannot
guarantee that the document will be sane in any other browser. Which
is why it let you log in through arora. Its known to run in Safari,
Opera and even IE to some extent.
I'll change it to a warning and tone the color to yellow or orange.
The only reason I called it an error was because warnings are most of
the times ignored. :)
> I took a brief look. Creating a new document was intuitive. Saving it
> a few times generated new revisions which is a nice feature. I was able
> to change titles in the sample docbook document and highlight some
> paragraph text and change what type it was and edit the paragraph. Some
> * How do I enter a new paragraph or section?
You need to add a new node in the document tree. Right click on the
node after or before which you want to add the new node. It will give
option for adding a sibling before the selected node, adding it after
the selected node or deleting the selected node. Once you choose the
add at appropriate location, you will get a drop down for the type of
node you want to add. (The list only contains those tags that are
allowed in order to maintain the sanity of the document.) I'll add an
"Add Child Node" function soon as well.
> * The Source tab lets me edit the content but the changes don't seem to
> be persisted. Should they or should I not be able to make changes there?
Could you please try it again? I checked to confirm and it was
persistent. It is supposed to be persistent so we can have a way of
inserting tags that are not yet supported by Design view at least.
(More like a 'for experts only' feature)
> * The list of types in "Insert inline Elements" is not alphabetical.
> Sorting them would make it easier to find the type of element we want to
> apply to the text we're editing.
Yeah sure will do. Will be a small change. :)
>> The login page requires the user's FAS account details.
>> It would be really nice if you could take some time to test it out and
>> give some feedback.
> As long as this is running on publictest we should hit the publictest3
> fas server instead of the real fas server. publictest doesn't have SSL
> which makes it insecure to type your real username and password in.
> I've changed the server being pointed to on publictest1 by editing
> So if you want to try this out, create an account on
> Then use that test account to log into beacon on publictest1.
Thanks a lot :)
More information about the logistics