Just uploaded the latest version of the beta. This includes a better Add Shared Decks form and better behaviour in the Deck Settings part of the Options form. The DE gives you a whole load of information about the decks for sharing.
Big thanks to everyone who is sharing decks with the beta. It is starting to look really good now. Amaze your friends - tell them you are not particularly interested in downloading it ;-)
8.4 Beta Updated 20 October 2007
Moderators: Programmer, WebWeaver, WillowsHeart
-
Programmer
- Major Contributor
- Posts: 1725
- Joined: Sat 01 Jan, 2005 12:00 am
- Location: Spain
- Contact:
-
WebWeaver
- Major Contributor
- Posts: 419
- Joined: Sat 01 Jan, 2005 12:00 am
- Location: Chicagoland, IL
- Contact:
Re: 8.4 Beta Updated 20 October 2007
I take it we need to reshare any decks we've shared?
Shari
Shari
-
Programmer
- Major Contributor
- Posts: 1725
- Joined: Sat 01 Jan, 2005 12:00 am
- Location: Spain
- Contact:
Re: 8.4 Beta Updated 20 October 2007
Hi Shari!
You would only need to reshare them if you want to add anything that relies on the new features, like a background file or cursor. Otherwise it shouldn't be necessary.
However, you will need to go into the DE in order for other people to see them. Previously there were a lot of decks showing on the DE which seemed to be ungettable. It occurred to me that this could be because people had shared some decks and then deleted them from their Orphalese folder (perhaps while doing a clean install or whatever), rather than deleting them via the Add Decks form. In that case the server would still think the decks were available, and still keep showing them as such while the user was logged on. Any attempt to request such a deck in that kind of scenario would lead to that ubiquitous message about the other user not responding. This is just a hunch. Anyway, when I started this round of beta testing I cleared out all the data about existing decks, which is why the DE now lists a couple of hundred decks rather than more than a thousand.
I am pretty happy with the way the DE seems to be working during testing, and that the server is managing data about people's shared decks much more efficiently and accurately. Actually I haven't seen that error message for over a month. Nobody has reported any errors with the DE either, but that might be because people who found the DE too buggy before have just given up on it. I might have to wait until the beta goes into production before I get much in the way of feedback - you know, that typical programmer's whinge
Cheers,
Richard
You would only need to reshare them if you want to add anything that relies on the new features, like a background file or cursor. Otherwise it shouldn't be necessary.
However, you will need to go into the DE in order for other people to see them. Previously there were a lot of decks showing on the DE which seemed to be ungettable. It occurred to me that this could be because people had shared some decks and then deleted them from their Orphalese folder (perhaps while doing a clean install or whatever), rather than deleting them via the Add Decks form. In that case the server would still think the decks were available, and still keep showing them as such while the user was logged on. Any attempt to request such a deck in that kind of scenario would lead to that ubiquitous message about the other user not responding. This is just a hunch. Anyway, when I started this round of beta testing I cleared out all the data about existing decks, which is why the DE now lists a couple of hundred decks rather than more than a thousand.
I am pretty happy with the way the DE seems to be working during testing, and that the server is managing data about people's shared decks much more efficiently and accurately. Actually I haven't seen that error message for over a month. Nobody has reported any errors with the DE either, but that might be because people who found the DE too buggy before have just given up on it. I might have to wait until the beta goes into production before I get much in the way of feedback - you know, that typical programmer's whinge
Cheers,
Richard