Managing flowcharts
in [Slackware]
|
From: E. Hoffmann on 4 May 2010 02:37 Hello all. Some months ago under Slackware 12.2 I wrote +-30 complicated flowcharts which I *really* need at my job (btw. I openly confessed there my conviction that linux is much more reliable and efficient than windows) - and my choice was kivio in koffice. Now kivio does not seem to exist since some time, they are looking for volunteers; I myself cannot share the effort because I don't know Qt neither python. But I have to modify those flowcharts. Working under Slackware 13.0 I tried to install koffice 1.6.3 of the 12.2 distribution, but kivio did not start because of the wrong libpython version. I then tried to compile koffice 1.6.3 from the sources with the slackbuild script (12.2) and failed because of the wrong Qt version. Luckly I still have a running Slackware 12.2 and can the necessary work there. What can I do? * Keep Slackware 12.2 and wait until a new release of kivio appears (with the risk of kivio disappearing again)? * downgrade libpython or do a parallel install of the older version? * downgrade Qt or do a parallel install of the older version? * modify the slackbuild script, but how? - this is why I post that problem here, I don't know whether I ruin the 13.0 installation by one of these possibilities. * migrate to another flowchart program and rewrite everything? Wich: dia? OOo? I'm not using the kde gui. It's only this flowchart problem. Thanks for any help, erch
From: Glyn Millington on 4 May 2010 03:18 "E. Hoffmann" <erichhoffmann(a)gmx.de> writes: > What can I do? I would suggest a combination of > * Keep Slackware 12.2 and wait until a new release of kivio appears (with > the risk of kivio disappearing again)? If this is a job-threatening and urgent situation I would install Slack 12.2 as a virtual machine under VirtualBox (avalaible as a Slackbuild). It will take up a few gigabytes, but a slack install is a smooth and swift procedure and you will end up with a usable version of kivio. Set up shared folders so you can move the finished product into your main OS for printing and emailing etc etc and > * migrate to another flowchart program and rewrite everything? > Wich: dia? OOo? This has to happen eventually I guess - can't comment on which of these might be better, but you know you can produce flowcharts in LaTeX, via PStricks? http://tug.org/PSTricks/main.cgi?file=pst-node/psmatrix/psmatrix#flowchart atb Glyn -- RTFM http://www.tldp.org/index.html GAFC http://slackbook.org/ The Official Source :-) STFW http://groups.google.com/groups?hl=en&group=alt.os.linux.slackware JFGI http://jfgi.us/
From: E. Hoffmann on 4 May 2010 04:42 Glyn Millington schrieb: > "E. Hoffmann" <erichhoffmann(a)gmx.de> writes: > >> What can I do? > > I would suggest a combination of > >> * Keep Slackware 12.2 and wait until a new release of kivio appears (with >> the risk of kivio disappearing again)? > > If this is a job-threatening and urgent situation I would install Slack > 12.2 as a virtual machine under VirtualBox (avalaible as a Slackbuild). > It will take up a few gigabytes, but a slack install is a smooth and > swift procedure and you will end up with a usable version of kivio. Set > up shared folders so you can move the finished product into your main OS > for printing and emailing etc etc > Luckily I can do this work at home on my own linux box, so this goes with no problem. > and > >> * migrate to another flowchart program and rewrite everything? >> Wich: dia? OOo? > > This has to happen eventually I guess - can't comment on which of these > might be better, but you know you can produce flowcharts in LaTeX, via > PStricks? No, i didn't! > http://tug.org/PSTricks/main.cgi?file=pst-node/psmatrix/psmatrix#flowchart This is a *really* good idea. I'll check that out. Latex is perfect. thanks. Erich > > atb > > > Glyn
From: jr4412 on 4 May 2010 10:25 > This is a *really* good idea. I'll check that out. Latex is perfect.. as is Xfig (IMO).
|
Pages: 1 Prev: How does one update Flash under Slack? Next: HOW2 change root ? |