I have been following with interest the discussions about developing an online server version of PlecoDict (usually in the context of a hoped for iPhone or Blackberry version of the software).
I recognize the tremendous advantages a server version would have in terms of updates and supporting multiple platforms/OS via a lighweight client. And for these reasons, I think a server version would be a great idea.
However, I think a non-networked, fully capable version of PlecoDict (i.e. what we have now) will remain essential for a significant subset of users for a number of reasons:
1). data plans are not ubiquitous around the world, and roaming fees can be exorbitant (as some iPhone users are now discovering) as one moves from country to country.
2). internet network access is also spotty or non-existent in many locales where a handheld dictionary is most useful.
The technology may not be available in a given area, or signal strength may be weak (rural areas, inside buildings, subway tunnels, airplanes). In principle, technological advancements may mitigate these problems, but they will always exist.
Then there are the technological problems that may never go away: breakdowns in network infrastructure (e.g. the damaged undersea cable which seriously degraded internet access for much of mainland China for several weeks earlier this year), or censorship (i.e. Great Firewall), which may block access to particular sites or ranges of IP addresses based on one's web hosting company (which may or may not host a site offensive to a particular government, but unrelated to your site). There is also intentional signal suppression. For example, I rely on PlecoDict on a daily basis for research in Chinese archives which intentionally jam cellphone signals for security reasons.
A server-client model sounds great provided all the pieces are in place and functioning smoothly. But this is a very big IF. Another way to look at it is that there are multiple reasons why relying solely on a server-client model is a bad idea - reasons which, while completely outside of Pleco Software's control, could create a customer support or relations nightmare.
I would urge PlecoDict to make every effort to retain the current software model, and extend it to new platforms intact.
I recognize the tremendous advantages a server version would have in terms of updates and supporting multiple platforms/OS via a lighweight client. And for these reasons, I think a server version would be a great idea.
However, I think a non-networked, fully capable version of PlecoDict (i.e. what we have now) will remain essential for a significant subset of users for a number of reasons:
1). data plans are not ubiquitous around the world, and roaming fees can be exorbitant (as some iPhone users are now discovering) as one moves from country to country.
2). internet network access is also spotty or non-existent in many locales where a handheld dictionary is most useful.
The technology may not be available in a given area, or signal strength may be weak (rural areas, inside buildings, subway tunnels, airplanes). In principle, technological advancements may mitigate these problems, but they will always exist.
Then there are the technological problems that may never go away: breakdowns in network infrastructure (e.g. the damaged undersea cable which seriously degraded internet access for much of mainland China for several weeks earlier this year), or censorship (i.e. Great Firewall), which may block access to particular sites or ranges of IP addresses based on one's web hosting company (which may or may not host a site offensive to a particular government, but unrelated to your site). There is also intentional signal suppression. For example, I rely on PlecoDict on a daily basis for research in Chinese archives which intentionally jam cellphone signals for security reasons.
A server-client model sounds great provided all the pieces are in place and functioning smoothly. But this is a very big IF. Another way to look at it is that there are multiple reasons why relying solely on a server-client model is a bad idea - reasons which, while completely outside of Pleco Software's control, could create a customer support or relations nightmare.
I would urge PlecoDict to make every effort to retain the current software model, and extend it to new platforms intact.
