| View previous topic :: View next topic |
| Author |
Message |
Shapierian
Tux's lil' helper
Joined: 15 Sep 2003
Posts: 88
|
 Posted: Wed Oct 08, 2003 2:21 am Post subject: gnome-spell, gtk-spell, and enchant |
 |
|
| As of now there are enchant backends for gnome-spell and gtk-spell availible at the enchant site: http://www.abisource.com/enchant/, is there any chance of getting enchant as a USE flag on those ebuilds |
|
| Back to top |
|
 |
Shapierian
Tux's lil' helper
Joined: 15 Sep 2003
Posts: 88
|
| Posted: Mon Oct 27, 2003 6:25 am Post subject: |
|
|
| If anyone else was curious enchanted ebuilds are now in portage. |
|
| Back to top |
|
|
cpdsaorg
Guru
Joined: 16 Oct 2003
Posts: 359
|
| Posted: Tue Feb 24, 2004 4:11 pm Post subject: |
|
|
why is enchant now a requirement for the new spelling library?
I would like to keep my installation small but more and more new apps and libraries are squeezing there way in on every update.
I read the http://www.abisource.com/enchant/ site and found that this is a wrapper for libraries that already exist on my system. Does this now meen that programmers are breaking with the base library compatibility and going with the enchant API? Why doesn't the underlying library get extended/fixed why add another layer?
What am i missing here? |
|
| Back to top |
|
|
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9608
Location: beyond the rim
|
| Posted: Wed Mar 17, 2004 2:42 pm Post subject: |
|
|
Maybe this ?
| Quote: | | Enchant wraps a common set of functionality present in a variety of existing products/libraries, and exposes a stable API/ABI for doing so. |
|
|
| Back to top |
|
|
cpdsaorg
Guru
Joined: 16 Oct 2003
Posts: 359
|
| Posted: Wed Mar 17, 2004 9:15 pm Post subject: |
|
|
so what you are saying here is that developers ARE going with the enchant api instead of recommending extensions/fixes to existing package api's.
It makes me sad to see how complicated things get. (my .02) |
|
| Back to top |
|
|
Kabuto
l33t
Joined: 01 Aug 2002
Posts: 701
|
| Posted: Thu Mar 18, 2004 3:52 pm Post subject: |
|
|
| No. Instead of having to custom code for each spell checker they can use one API and not have to worry/spend time custom coding. By your line of reasoning we should get rid of KDE API, GNOME API, ALSA API, OSS API, etc. Then it would takes years to write a single app or you would be locked into only one thing. No choice of sound card, desktop, or spell checker. No thanks. I would rather load a few more apps. |
|
| Back to top |
|
|
cpdsaorg
Guru
Joined: 16 Oct 2003
Posts: 359
|
| Posted: Fri Mar 19, 2004 7:51 am Post subject: |
|
|
How many spell checking programs are there out there?
And I aready know there is an api for each big application.
Wait are you saying that spell checkers don't have an api or are you saying that they don't aggree on a common syntax? Because I assumed that there is an api for each spell checker and that each one was different. |
|
| Back to top |
|
|
Kabuto
l33t
Joined: 01 Aug 2002
Posts: 701
|
| Posted: Fri Mar 19, 2004 4:34 pm Post subject: |
|
|
| Enchant hooks in 3 spell checkers. ASpell, ISpell, and MYSpell. You would need code to handle each one or pick one and make the user use that one. |
|
| Back to top |
|
|
|
Desktop Environments
