From bernhard at intevation.de Mon Dec 4 05:42:26 2006 From: bernhard at intevation.de (Bernhard Reiter) Date: Mon, 4 Dec 2006 11:42:26 +0100 Subject: [Weft QDA users] export does not work (1.0.1 on GNU/Linux Mandriva) In-Reply-To: <20061118103441.GA32283@intevation.de> References: <20061118103441.GA32283@intevation.de> Message-ID: <200612041142.31099.bernhard@intevation.de> On Saturday 18 November 2006 11:34, Bernhard Reiter wrote: > here is the next technical difficulty with weft-qda: > Export to HTML (or txt) does not work. This probably is [#4293] Export doesn't work with UTF-8 text on Linux http://rubyforge.org/tracker/index.php?func=detail&aid=4293&group_id=665&atid=2625 Does export work for somebody on GNU/Linux? With which version of PageTemplate? Locale setting? Encoding of work texts? > I have identified and fixed > one problem of the code when using PageTemplate 2.2.3. > Still it does not work. Should I submit my patch? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://rubyforge.org/pipermail/weft-qda-users/attachments/20061204/5d224b9c/attachment-0001.bin From Roberta_Goldman at mhri.org Mon Dec 4 14:45:05 2006 From: Roberta_Goldman at mhri.org (Roberta_Goldman) Date: Mon, 04 Dec 2006 14:45:05 -0500 Subject: [Weft QDA users] Merging two halves of a project using identical category codebook In-Reply-To: References: Message-ID: <45747AC1.1040804@mhri.org> Alex, thanks for your response. We're both using the identical codebook - she's coding half the transcripts on one side of the country, and I'm coding the other half on the other side of the country. We can send each other a CD of each half of the project (each half is too big to email), but we'd still have to run the reports twice (once for each half), though I see what you mean about cutting and pasting. I was just wondering if there was a merge component - like is available from some of the commercial software programs. Weft is wonderful for what it does do; I just wanted to be sure I was getting the greatest potential out of it. Merging ability would be a fantastic feature for large projects. Roberta weft-qda-users-request at rubyforge.org wrote: >Send weft-qda-users mailing list submissions to > weft-qda-users at rubyforge.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://rubyforge.org/mailman/listinfo/weft-qda-users >or, via email, send a message with subject or body 'help' to > weft-qda-users-request at rubyforge.org > >You can reach the person managing the list at > weft-qda-users-owner at rubyforge.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of weft-qda-users digest..." > > >Today's Topics: > > 1. merging two halves of a project (Roberta_Goldman) > 2. Re: merging two halves of a project (Alex Fenton) > 3. Re: merging two halves of a project (???) > 4. Re: Weft-QDA under Linux (Maurizio Teli) > 5. export does not work (1.0.1 on GNU/Linux Mandriva) > (Bernhard Reiter) > 6. Re: Weft-QDA under Linux (Bernhard Reiter) > 7. Re: poll on an intermediate release (Alex Fenton) > 8. Re: merging two halves of a project (Alex Fenton) > 9. Re: export does not work (1.0.1 on GNU/Linux Mandriva) > (Bernhard Reiter) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Tue, 14 Nov 2006 09:44:20 -0500 >From: Roberta_Goldman >Subject: [Weft QDA users] merging two halves of a project >To: weft-qda-users at rubyforge.org >Message-ID: <4559D644.4040004 at mhri.org> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >Dear Alex and users of Weft - I have used other ethnographic software >programs previously and was delighted to use Weft in my current project >as its simplicity to learn was important for the people working with >me. One feature that would be helpful for my current and other large >projects is the ability to merge two halves of a project after two >individuals have each completed coding a different half of the >transcripts. That would allow running reports on the entire project >rather than separately for each half. Is this a feature that is >possible and I missed that information in the manual? If not, is there >some way around this problem that I could use? > >I apologize if this question is redundent - I posted it previously but >am new to using list serves and did not see a response in the digest. > >Thank you for your help, >Roberta > > > -- Roberta E. Goldman, Ph.D. Cl. Associate Professor of Family Medicine Brown University Center for Primary Care and Prevention Memorial Hospital of Rhode Island 111 Brewster Street Pawtucket, RI 02860 Tel: 401-729-2924 Fax: 401-729-2494 roberta_goldman at mhri.org From alex at pressure.to Tue Dec 12 15:39:48 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 12 Dec 2006 20:39:48 +0000 Subject: [Weft QDA users] export does not work (1.0.1 on GNU/Linux Mandriva) In-Reply-To: <200612041142.31099.bernhard@intevation.de> References: <20061118103441.GA32283@intevation.de> <200612041142.31099.bernhard@intevation.de> Message-ID: <457F1394.3000100@pressure.to> Hi Bernhard >> I have identified and fixed >> one problem of the code when using PageTemplate 2.2.3. >> Still it does not work. >> > > Should I submit my patch? > Sorry for the delay in replying. It's very kind of you to offer a patch - I think this is the first ever received for Weft. It would be very helpful to know where the bug arose, so please send it. However, I think it's unlikely I'll make another release of Weft QDA 1. This is mainly because I now don't have a Linux dev environment for this, and don't want to spend time building old wxruby 0.6.0 on a modern Linux. The good news is that I likely won't have to do an intermediate release of Weft QDA - we can go straight to a version 2.0 that properly supports multilingual projects, and will work much better on Linux and also on Mac OS X. thanks alex From bernhard at intevation.de Tue Dec 12 16:55:20 2006 From: bernhard at intevation.de (Bernhard Reiter) Date: Tue, 12 Dec 2006 22:55:20 +0100 Subject: [Weft QDA users] =?iso-8859-1?q?export_does_not_work_=281=2E0=2E1?= =?iso-8859-1?q?_on_GNU/Linux=09Mandriva_=29?= In-Reply-To: <457F1394.3000100@pressure.to> References: <20061118103441.GA32283@intevation.de> <200612041142.31099.bernhard@intevation.de> <457F1394.3000100@pressure.to> Message-ID: <200612122255.25244.bernhard@intevation.de> On Tuesday 12 December 2006 21:39, Alex Fenton wrote: > >> I have identified and fixed > >> one problem of the code when using PageTemplate 2.2.3. > >> Still it does not work. > > > > Should I submit my patch? > > It's very kind of you to offer a patch > - I think this is the first ever received for Weft. Woohoo, first! ;) Actually my first email described the source code change, which was one line in /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/filters/templates.rb:43 tpl = PageTemplate::Parser.new('source' => CommentStrippingFileSource, 'include_paths' => TEMPLATES_DIR, 'preprocessor' => ExtendedPreprocessor ) changing the middle line to: 'include_path' => TEMPLATES_DIR, As I got no reply, I wondered if the right procedure would have been to submit this analysis to a tracker in diff -u format or so to make it easier for you. It should be easy for you to just change this line, test and commit. > It would be very helpful to know where the bug arose, so please send it. As already written: I expect a change in newer versions of PageTemplate with this particular minor problem. Now I have seen [#4293] which is the larger part of the problem. > However, I think it's unlikely I'll make another release of Weft QDA 1. > This is mainly because I now don't have a Linux dev environment for > this, and don't want to spend time building old wxruby 0.6.0 on a modern > Linux. It is fairly easy to build that environment and currently this is the only released version of weft-qda. >:) > The good news is that I likely won't have to do an intermediate release > of Weft QDA - we can go straight to a version 2.0 that properly supports > multilingual projects, and will work much better on Linux and also on > Mac OS X. Sounds good. Any time frame for the release? Bernhard -- Managing Director - Owner, www.intevation.net (Free Software Company) Germany Coordinator, fsfeurope.org (Non-Profit Org for Free Software) www.kolab-konsortium.com (Email/Groupware Solution, Professional Service) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://rubyforge.org/pipermail/weft-qda-users/attachments/20061212/3b53250b/attachment.bin From alex at pressure.to Tue Dec 12 17:45:35 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 12 Dec 2006 22:45:35 +0000 Subject: [Weft QDA users] export does not work (1.0.1 on GNU/Linux Mandriva ) In-Reply-To: <200612122255.25244.bernhard@intevation.de> References: <20061118103441.GA32283@intevation.de> <200612041142.31099.bernhard@intevation.de> <457F1394.3000100@pressure.to> <200612122255.25244.bernhard@intevation.de> Message-ID: <457F310F.2050501@pressure.to> Hi > Actually my first email described the source code change, which was one line > in > > /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/filters/templates.rb:43 > Thanks again; I have now applied your fix. > As I got no reply, I wondered if the right procedure would have been to submit > this analysis to a tracker in diff -u format or so to make it easier for you. > It should be easy for you to just change this line, test and commit. > The subset of people who care about qualitative data analysis AND can fix bugs in ruby code is very small, so I hadn't given it much thought. A description as you gave is just fine, or a diff -u patch on the mailing list. > As already written: I expect a change in newer versions of PageTemplate > with this particular minor problem. I think this is a change in PageTemplate which has broken this, as this definitely works on Windows, where the library versions are frozen. I am not sure I will use PageTemplate for Weft QDA 2. The idea was to make it possible for users to define their own output templates, but I'm not sure now that PageTemplate's syntax is the best way to achieve this. I'd like to get some discussion going on this once there's a software out there people can experiment with. >> This is mainly because I now don't want to spend time building old wxruby 0.6.0 on a modern Linux. >> > > It is fairly easy to build that environment > and currently this is the only released version of weft-qda. >:) > Okay, but I probably still won't, sorry. I try to strike a balance between developing and supporting the existing version. 80% + of users are on Windows, but almost all install problems arise on Linux. There are a variety of reasons for that, and it doesn't necessarily reflect the inherent quality of those platforms - but it does influence me in how I spend my time. > Sounds good. Any time frame for the release? > I would hope to see an initial Weft QDA 2.0 preview release in perhaps one to two months. A stable 2.0 release might be some months beyond that. But it is also dependent on how quickly wxruby2 progresses and how much time I need to spend on that. cheers alex