Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
I was perusing the SVN repository and see a couple updates since the 0.9 version, so I was wondering if there's a planned .9x version any time soon. Having the latest release in 2006 and with so many good patches for XSS, finding duplicates (and hopefully Google Scholar shortly) that should be out there, and it would help with internal deployment questions that come up as to the update timeliness, especially with PubMed and other NSF updates lately.
we plan to issue a 0.9.x release in the foreseeable future, but, unfortunately, I cannot promise any release date, sorry. I'm very busy working on this ATM, but there are still some open frontiers that need to be finished or polished before we can issue a release.
I realize that we could (and should have) released the version that's currently in the SVN trunk a long time ago. Sorry for the inconvenience.
However, making a proper release takes me a lot of time due to thorough testing, announcement preparations, etc. I simply did not have the time to do so. Thanks for your understanding.
Also, by referring to Google Scholar, what exact feature or enhancement did you have in mind?
I'm not sure that I understood exactly what you meant w.r.t. to PubMed and NSF updates, can you elaborate?
As a general note: while one can post anonymously on SourceForge it helps us and avoids confusion if you mention your name in the posts. Thanks!
Thanks to all, for the new features in the newest Version.
feature is great ... maybe I will find some more new features ;-)
> Thanks to all, for the new features in the newest Version.
Glad you like it! Please note that this new version (currently only in the bleeding-edge branch of our SVN repository) has still a few rough edges, and some more features & fixes are yet to be done (and to be checked in). We will make this new version also available in the SVN trunk when it's considered to be ready for production use. And, finally, a proper release should follow in due course.
I note that you've already updated one of your refbase databases:
Please make sure that:
- you have the very latest script versions (note that there will be some more checkins today)
- you're using the latest version of 'initialize/ini.inc.php'
- you've executed 'update.php' after updating any of your scripts
The update script ('update.php') can be run repeatedly without doing any harm, and it will tell you when your refbase installation is up-to-date.
Let us know if you run into any trouble.
> Please note that this new version (currently only in the bleeding-edge branch of our SVN repository) has still a few rough edges,
I always hope that the "edges" are round and small ;-)
>Please make sure that:
>you have the very latest script versions (note that there will be some more checkins today)
How do I know that all changed scripts are in the bleeding edge branch. I thougt you released all of them because there was a break.
But it seems that there are some more new files in the bleeding edge now.
>- you're using the latest version of 'initialize/ini.inc.php'
It wold be fine if you could mark the changed entries with any kind of revision number.
I have always to decied to use the new one and put in my personal settings, or use the old one and put in the new or changed items.
In both cases it would be easy to search f.e rev.9.03 to find the changed entries quick and save.
> How do I know that all changed scripts are in the bleeding edge branch.
> I thougt you released all of them because there was a break.
Yes, normally I try to commit all my changes in one go, but this time this just wasn't feasible for me. Also I wanted to (finally) make these commits available at the SF repository as quick as possible, so I decided to commit my changes when they were ready for checkin. Sorry for the trouble!
When deploying refbase from SVN, we generally advise to stick with the refbase version that's available in the SVN trunk. The trunk should always contain a working refbase version. The SVN bleeding-edge branch really is for development and might contain incomplete or nonfunctional modifications.
> But it seems that there are some more new files in the bleeding edge now.
That's correct. You can follow the refbase checkins in real time at:
The cia.vc site also allows you to subscribe to an RSS feed that always lists the most recent refbase commits.
>>- you're using the latest version of 'initialize/ini.inc.php'
> It wold be fine if you could mark the changed entries with any kind of revision
> number. I have always to decied to use the new one and put in my personal
> settings, or use the old one and put in the new or changed items
A good text editor (or file comparison tool) is able to compare two versions of the same file and can solve this issue nicely.
A capable text editor can usually highlight differences among two file versions on character level, and let's you apply changes individually from one version to the other. On Mac OS X, there are quite a few good text editors (such as BBEdit, TextMate or the free TextWrangler). See Wikipedia for a comprehensive cross-platform comparison of text editors and file comparison tools. And, of course, on *nix systems there's always the 'diff' command line tool.
Hope this helps, Matthias