Closed xiphos-bug-inhaler closed 8 years ago
Logged In: YES user_id=34539 Originator: NO
From http://www.nongnu.org/bibledit/ -> Download -> Installation -> Fedora -> 3.2 on F7 -> Install Bibledit from source, the download link offered is: http://code.google.com/p/bibledit/
This gives me: Forbidden Your client does not have permission to get URL /p/bibledit/ from this server.
Original comment by: karlkleinpaste
Logged In: YES user_id=890881 Originator: YES
There is a mistake in the documentation on the site. The correct download location is:
http://download.savannah.nongnu.org/releases/bibledit/source/
Thanks for spotting the mistake. I've corrected it, to be available soon.
Teus.
Original comment by: teus
In BibleTime it works the following (see https://sourceforge.net/tracker/?func=detail&atid=350954&aid=2799852&group_id=954):
Comment By: Martin Gruner (mgruner) Date: 2009-06-02 17:44
Message: We changed the communications protocol from DCOP to DBUS, but the interface is still the same and should be working. DCOP will not come back, external apps need to switch to DBUS (freedesktop.org standard) to talk to BibleTime.
Original comment by: ewst
I have got a question on this one. Is it true that this will probably be implemented using the DBus system? And another question: Has this been implemented? And the last question: If it has been implemented, are there samples of how to communicate with Xiphos? Thanks, Teus.
Original comment by: teus
Thanks for implementing this. It works well!
Original comment by: teus
It seems to be desirable to have a way that bibledit and gnomesword can communicate. This comes in particularly useful when scrolling within bibledit. If there is communication between the two, then gnomesword could scroll to the same verse as bibledit, and vice versa. For example somebody works in bibledit on Matthew 1:5. This person than would be helped if gnomesword automatically would show the same verse also. It was suggested that gnomesword could be running on one machine and bibledit on another. In that case the communication path could be going though the network.
Reported by: teus
Original Ticket: "gnomesword/bugs/71":https://sourceforge.net/p/gnomesword/bugs/71