Aiksaurus and Its Needed Libraries

[jakfish]

I would like to build this thesaurus (I've used it in Puppy Linux and it's great).  From this page, which libraries do I need to make Aiksaurus run on LLL:

http://packages.debian.org/search?keywords=gaiksaurus

The page listed above appears to have the GUI for stand-alone use.  Will that work on LLL?  If not, there is this:

http://packages.debian.org/etch/aiksaurus

But obviously, users would probably prefer a GUI-based thesaurus.  If for some reason, I can't use Gaiksaurus, which libraries would I need for Aiksaurus?

Thanks for any assistance/pointers,
Jake

[wicknix]

Uploaded gaiksaurus to the '3MX-Ultra' folder on 3mx.taita.co.uk

Cheers.

[jakfish]

Thank you, thank you--it works perfectly.  I compiled it last night myself and made the HUGE mistake of inserting libraries from libatk1.0-0 (I thought the gui needed this).  Even though I uninstalled my attempt before rebooting, my compiling must've left that library in /lib anyway.

Blew out my desktop and all gui apps save Midnight Commander and other text-based programs.  Even after hand-deleting the lib, I couldn't get the desktop back and had to reinstall everything.

The Deb Etch repository is so confusing to the amateur like me.  I get the concept of it (and ultimately was able to compile gaiksaurus), I see how mkxap works, but the list of supposedly "depends" is huge and as I've learned the hard way, very few are necessary and many are dangerous.

At any rate, thanks for a much-needed app and for such fast work,
Jake

[wicknix]

Yeah it's tricky. 95% of most 'required deps' on most programs are already in Ultra. If you were to include one of those (such as atk as you found out) and then remove the program you made it could possibly remove needed libraries resulting in broken software. It's easy for me because i already know what i included, but for anyone else it's not as easy.

It's tedious, but look through /lib to see whats already installed before making .xap's to ensure you arent overwriting any preexisting files.

Cheers.

[jakfish]

And since the usr, lib and other directories remain after xap compilation, you can always go back and add more libs if the app screams for on in console.  I think I'll err on the side of leaving things out rather than putting them in.

Further good news on Gaiksaurus.  If a user extracts the Abiword "old-etch" plugins (I did it w/o compiling an xap file; I just extracted in XP with LZArc and dropped the directory into its proper slot), lo and behold, there's Thesaurus under Tools.  It's very cool.  The plugins give lots of nifty Save-As options as well.

In Tools, the plugins also gives Google search and other on-line services, but they all call for Lynx.

Oh, I've downloaded/extracted the Abiword help files, put them in their proper directories, but I can't call them from inside Abiword/Help button.  There doesn't seem to be any kind of needed lib, so am I missing something else, or is this the way 2.4 is?

Jake

[wicknix]

Cool info about the plugins. As for the help files you can easily call them through a web browser.
skipstone file:///path/to/abiword-help-files (or index.html depending on how the help files are packaged)

Cheers.

[jakfish]

I found that I had to install "Links" from your site (I'm using 3mx-Ultra) and once I did that, abiword can call up babelfish, google and others in the Tools drop-down.  Several things the plugins won't do: grammar check (it calls for libs not compiled for etch), gdict (which also calls for libs not etch-ready), and wordperfect and other save-as functions need libs not-yet-ready.  If one looks in the abiword profile file, one can see the errors.

What I did with the abiword help files was drop its directory into /documents, then go to etc/jmw and open its file and insert under Office a command calling for:

xterm -e elinks ~/documents/Abiword_Help/index.html

That brings up the initial abiword help page and one can go from there.

With your gaiksaurus and an installation of links (why did they change it from "lynx"--I got so confused, considering how picky Linux is about syntax), abiword in LLL truly moves into real word processing.  A user can find a synonym, do a translation, or a google search, all on the fly.  Grammar check would be cool, but there it is.

Jake

[wicknix]

Actually elinks was already included in Ultra and those are 3 different text based browsers (elinks, links and lynx) with elinks being the best IMO. You could symlink elinks to lynx for apps that call upon lynx.

cd /usr/bin
ln -s elinks lynx

Cheers.

[jakfish]

You're right: I should've figured that out.  There's already a symlink in 3mx-Ultra for lynx to links; I didn't connect the dots.  Back when I was playing with lynx, there was just one flavor, in Terminal with the old Sharp Zaurus Classic/Compuserve Classic.

Another cool thing about elinks is that if a user drags his bon echo bookmark.html to the desktop, elinks will open it by default--great for quick browsing of text news sites, where I mostly go.

Jake

[wicknix]

Packaged up the 'abiword-plugins' with all the required files i could find. Also packed up lynx. Installing both make abiword much nicer. Thanks for the tips/idea. Both packages are in the 3mx-ultra folder on 3mx.taita.co.uk.

Cheers.

[jakfish]

What fun.  I don't know where you found the needed libs for grammar check.  I looked and looked in the debian etch stuff and found only Lenny libs and others.

With your package, the Word Perfect plugin now works.

Gdict shows no error loading in abiword profile (as it did before, when I was playing w/ my package), and it shows itself as an active plugin, but I can't get it to work.  I highlight a word, click on Tools/Gdict and the word flashes (so something's happening) but nothing else.  I've never used Gdict, so I'm not certain what's supposed to occur.

Tools/Summarize can crash Abiword.  The plugin shows up as active, but upon clicking, abiword complains of a missing glade file: */glade/ots.glade.  I've brought down the program by using this, so best to avoid it or disable the plugin.  Unless there's a workaround I don't know about.

Grammar is there, but it's pretty basic.  There's no actual check; abiword just underlines suspicious sentences in green. but offers no choice of correction or even tells why the sentence is in trouble.  I would enable the plugin when the document is completed just to see what warning signs show up.

Everything else works the way it's supposed to in Tools: google search, translations, wikipedia, url dictionary, thesaurus (but your gaiksaurus must be installed first).  Many, many thanks; it really improves the program.  Jake