There is no huge facelift for version 7. It will only happen when we move to dot net. In version 7, all references, notes, tasks, charts, categories (new module) will be organized under one folder tree. Each record can be displayed in separate window. Records can be organized with categories. There are many other improvements as well.
Can live without the facelift, but will the move to .net after version 7 involve a replacement of the embedded database engine? The limitations in the DBISAM implementation are clear, and more robust embeddable engines are available at no cost - you could even use MS SQL server express as the default engine.
And I say the "default engine" because Biblioscape was a more attractive product when the buyer had a choice of database backend, which allowed a tight integration of Biblioscape into the wider information systems in the organization (no, the DBISAM ODBC driver doesn't cut it).
This, like many other features, has been asked before. Many users have also asked for a detailed roadmap for Biblioscape, so that we can make informed purchasing decisions. It may help to have a look at the feature list of Synapsen - it reads like a wish list for many Biblioscape users: cross-platform support, choice of backend engine, unicode support...
And while on cross-platform support - it would in principle be possible to compile Biblioscape for Linux and Mac OS using the Free Pascal compiler - but only if you get rid of DBISAM as the backend engine.
After version 7, we will ask user's input about the next release. If we go to dot net, users will get unicode. But lots of users can't run dot net application. For example, I still use Win2000. Actually only a small percentage of users need unicode. It is not possible to use free pascal to make Biblioscape run under Linux and MacOS. Biblioscape does run under WINE for Linux. http://www.codeweavers.com/ will provide a solution for MacOS soon.
The thrust of the question was: any chance that the database engine will change to something more reliable after version 7 or, better still, that the user will be given the choice of what backend to use?
Not that I'm a fan of .net, but you can actually run it on W2K.
Well, how about posting a permanently running poll where every site user would be able to vote for potential future features? E.g. each user could get a limited number of points, say 100, distributed between several features suggestions. This way they would have to prioritise. Also, each user should be able to submit a new feature into the poll unless it is already there (simple moderation will sort that out). Otherwise, it is unclear how the future features are selected and if the selections indeed reflect the needs of the users.
Still this would say little about the needs of potential users who currently stay away from Biblioscape.
I for one do need Unicode and do find a switch to a program that supports it tempting especially if it is strong on other features. I also know many people who like Biblioscape when they see it in operation but would not consider it for themselves before multiple language support is implemented.
Online poll is a good idea. We have not made this available because we need to get version 7 out. It is already way behind schedule because the amount of changes involved. Once version 7 is out, we will add polling feature. Then we can quickly add new features based on the polling result.
There is no huge facelift
There is no huge facelift for version 7. It will only happen when we move to dot net. In version 7, all references, notes, tasks, charts, categories (new module) will be organized under one folder tree. Each record can be displayed in separate window. Records can be organized with categories. There are many other improvements as well.
No facelift OK, but what about a heart transplant?
Can live without the facelift, but will the move to .net after version 7 involve a replacement of the embedded database engine? The limitations in the DBISAM implementation are clear, and more robust embeddable engines are available at no cost - you could even use MS SQL server express as the default engine.
And I say the "default engine" because Biblioscape was a more attractive product when the buyer had a choice of database backend, which allowed a tight integration of Biblioscape into the wider information systems in the organization (no, the DBISAM ODBC driver doesn't cut it).
This, like many other features, has been asked before. Many users have also asked for a detailed roadmap for Biblioscape, so that we can make informed purchasing decisions. It may help to have a look at the feature list of Synapsen - it reads like a wish list for many Biblioscape users: cross-platform support, choice of backend engine, unicode support...
And while on cross-platform support - it would in principle be possible to compile Biblioscape for Linux and Mac OS using the Free Pascal compiler - but only if you get rid of DBISAM as the backend engine.
Julian
After version 7, we will ask
After version 7, we will ask user's input about the next release. If we go to dot net, users will get unicode. But lots of users can't run dot net application. For example, I still use Win2000. Actually only a small percentage of users need unicode. It is not possible to use free pascal to make Biblioscape run under Linux and MacOS. Biblioscape does run under WINE for Linux. http://www.codeweavers.com/ will provide a solution for MacOS soon.
Thanks, but what about the engine?
The thrust of the question was: any chance that the database engine will change to something more reliable after version 7 or, better still, that the user will be given the choice of what backend to use?
Not that I'm a fan of .net, but you can actually run it on W2K.
We have no plan to replace
We have no plan to replace the database engine. Supporting multiple backends is a headache. We used to do that.
Feature Poll
Well, how about posting a permanently running poll where every site user would be able to vote for potential future features? E.g. each user could get a limited number of points, say 100, distributed between several features suggestions. This way they would have to prioritise. Also, each user should be able to submit a new feature into the poll unless it is already there (simple moderation will sort that out). Otherwise, it is unclear how the future features are selected and if the selections indeed reflect the needs of the users.
Still this would say little about the needs of potential users who currently stay away from Biblioscape.
I for one do need Unicode and do find a switch to a program that supports it tempting especially if it is strong on other features. I also know many people who like Biblioscape when they see it in operation but would not consider it for themselves before multiple language support is implemented.
Online poll is a good idea.
Online poll is a good idea. We have not made this available because we need to get version 7 out. It is already way behind schedule because the amount of changes involved. Once version 7 is out, we will add polling feature. Then we can quickly add new features based on the polling result.