From alex at pressure.to Fri Dec 7 07:19:10 2007 From: alex at pressure.to (Alex Fenton) Date: Fri, 07 Dec 2007 12:19:10 +0000 Subject: [Weft QDA users] Weft Feature Requests and Bug Report. In-Reply-To: <1196362417.7930.77.camel@ljs-desktop> References: <1196362417.7930.77.camel@ljs-desktop> Message-ID: <47593A3E.5060408@pressure.to> Hi Lindsay Sorry for the delay in replying - I've been away and not on email. Lindsay Stirton (Dr) wrote: > After a day or so having upgraded from NVivo 2 to Nvivo 7 I got fed up > with various things, mainly feature bloat, and the apparent lack of > anything resembling the old speed coder. In a fit of pique, I have > installed Weft QDA and am now quite myself again. Nice package! > Thank you for your kind words. Most of the specific features you mention I think are available in version 1, or are already implemented in the development version. > 1. Make texts editable within the document text window. This would be > nice for a number of reasons, not least of which because the text > importer is not perfect. > This is currently implemented in version 2. In the document window you'll be able to switch between an "editing" and a "coding" view. Existing coding is maintained. > 2. Enable hyperlinking between documents would be nice. This is the one > feature that might compromise a little on the 'back to basics' > philosophy of Weft. > Version 2 currently allows standalone "notes" to be applied to bits of text, but there isn't a hyperlinking facility. I think I'd worry that having "coding", "annotating" and "hyperlinking" all together might make things a bit confusing in their similarity. But I'm open to suggestions - this will be easier when I have a chance to tidy up and release a draft version 2. > 3. Enable auto-save (especially important in light of the bug no. 1 > reported below). > Again, done in version 2 already. > 4. Enable expanding of the area to be marked/coded using Crl and arrow > keys. > Nice idea, will look into this. > 5. Enable cut, copy and paste from documents and from categories. > This should work already (it does on Windows, anyway - but I don't have a version 1 set up on Linux to test). > 6. It would be nice (really nice) if the review coding view could be > exported as a .csv or similar. > Again, this should already be possible. Have the Code Review window active, then choose "Export" and you should get a CSV option. > I see from Alex's website that a version 2 is due real soon now. It may > be that some or all of the issues listed below will be taken care of in > this new release. I also know that Alex doesn't have unlimited time to > devote to this project. I am posting these mainly in the hope that they > will be of some use to Alex and any other developers. > Thanks, it's appreciated. I made a lot of progress and most of the new features I and others want are in there, but it needs some tidying up, and I'm also waiting for the release of Ruby version 2.0 at the end of the month which will make Weft faster and working with multilingual documents much slicker. Unfortunately I've been swamped with other research work over the past month or two and this may not let up for a little while yet. > Now, the following bugs. I installed the latest Weft onto Ubuntu (Gutsy > Gibbon), which I am running as a virtual machine using VMWare Server. > > 1. Re-naming a node caused Weft to crash. > OK, I'm afraid I don't have a version 1.0 set up on Linux to test this. > 2. Importing documents from .pdf produced blank documents! I had > converted the document to .pdf myself, and there was no security > restrictions on them. > Direct PDF importing is going to be dropped in version 2.0 anyway. The reason for its inclusion in v1 was that major PDF apps (eg Acrobat Reader) didn't support export to text, whereas they do now. So it should be easy to use, for example, XPDF on Linux to produce an importable text file. Thanks again for your comments. Alex From alex at pressure.to Fri Dec 7 07:20:44 2007 From: alex at pressure.to (Alex Fenton) Date: Fri, 07 Dec 2007 12:20:44 +0000 Subject: [Weft QDA users] Weft Feature Requests and Bug Report. In-Reply-To: <2c31f7f50711300555t1db401aam32fc9d63ed720f76@mail.gmail.com> References: <1196362417.7930.77.camel@ljs-desktop> <2c31f7f50711300555t1db401aam32fc9d63ed720f76@mail.gmail.com> Message-ID: <47593A9C.90501@pressure.to> grizzou wrote: > I can report an other problem I receive yesterday from a student. We > use Weft to codify interview realised in french (from Qu?bec/Canada) > and she got a problem with the specific accents (?, ?, ?, ?, etc.). I > found a basic solution just by changing the font style in Weft QDA > (Times New Roman seems to do the job). That was a similarly solution I > found when using NVivo 2. Mabe it could be a good idea to identify all > the font a user can choose to view the french caracteres. Thanks for the report; I'll have a look into this. > But this problems give me an idea. Did it can be an idea to develop a > wiki or something like that to propose an active documentation, open > for modifications? That is a nice idea. Rubyforge (a site which supports Weft's development) allows a Wiki, so I will see if it's possible to put an annotatable version of the docs on there. Best Alex