unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: rvmolen@bambecksystems.com (Richard V. Molen)
Subject: Re: (Slightly Off-Topic) Emacs-like Office App
Date: 31 Oct 2002 14:16:24 -0800	[thread overview]
Message-ID: <usmym6ypz.fsf@bambecksystems.com> (raw)
In-Reply-To: mailman.1036030537.11556.help-gnu-emacs@gnu.org

bobstopper@australispro.com.au writes:

> This isn't really a request for help with Emacs but a request for knowledge
> on Applications inspired by Emacs, specifically office type Applications.
> 
> I love how Emacs is so extensible and provides so many features due to its
> use of modes and elisp. So what I'm (very idly at this stage) considering
> is the idea of an office kinda suite (yeah, like M$) all within the one
> program through the use of emacs style modes and retaining a lot of
> extensibility through a lisp dialect (probably guile).

Sounds great, when can I get one.
 :-)

> Emacs can probably do something similar to what I'm thinking already if 
> support was written for it, but I'm thinking Emacs would probably remain,
> well, ugly in the eyes of typical office workers and it would thus
> be unappealing.

Wait, who are the target users, software developers or typical office
workers?  :-|

> Instead I'm envisioning something that looks a lot like current gnome
> office products... only it's capable of doing all of them simply by loading
> the appropriate modes (perhaps after first writing them ;).

If the target users are typical office workers then why not help
improve the OpenOffice offering.  It would probably be much less work.
:-\

> Gnome office is a great idea and I think it's a great alternative to M$
> office but I think the idea of having separate programs attempting to 
> integrate through some additional system like bonobo or OLE will still
> remain somewhat unintegrated and perhaps not as consistent in its interface
> as what I'm suggesting would be. I imagine typical office users would be
> much more satisfied if they only needed the one app that could do everything
> and I imagine advanced office users and programmers would be much more
> satisfied if they can extend that app to do almost anything they please.

So the target users would be _advanced_ office users and programmers?
Certainly programmers using Emacs would benefit.  What incentive would
advanced office users have to make the switch and undergo a learning
curve? :-?

> So if something *better* (rather than just equivalent) than M$ office is
> written as part of the GNU/Linux project then we have much more clout for
> winning the average user over. I imagine for this sort of goal the app
> would almost certainly have to have a fully featured M$ Windows port so
> it can first appeal to all these M$ windows users, and once they're won
> over it's a small step to realising that if everything they need for
> office work is in that app, and that app is available on GNU why not just
> use GNU?

Yow! Sounds ambitious.  But wait, who is the target user?  Uncle
Bill's M$ success was by appealing to the lowest common comuter-user
demoninator and releasing not-so-thoroughly tested software early in
order to beat others to market.  What features will this project
provide that will attract these folks in herds and send them
stampeding to GNU/Linux boxes? Answering that question, what would be
the quickest route to providing these features and advertising that
fact? :-/

> 
> So, with that description of my infant idea in mind, I have a couple of
> questions:
> 
> Does anyone know if something like what I'm describing already exists
> or is in the process of being written etc?
> 
> and of course:
> 
> Is my idea stupid, infeasible, lacking in some major consideration, too
> damned hard etc or is it actually a good idea?

I like the idea, but it sounds like a lot of work.  Would it be worth
it?  Eventually, of course, the best features of Emacs will creep into
other applications and visa versa.

> I'm looking forward to any kinds of comments/suggestions. Thanks!

-- 
Richard V. Molen

Warning!!
Signature under construction, safety glasses required.

  parent reply	other threads:[~2002-10-31 22:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1036030537.11556.help-gnu-emacs@gnu.org>
2002-10-31 16:42 ` (Slightly Off-Topic) Emacs-like Office App Todd Wylie
2002-10-31 21:00   ` Paul Thompson
2002-11-01 18:15     ` Todd Wylie
2002-11-01 19:35       ` Paul Thompson
2002-10-31 16:48 ` Artist
2002-10-31 19:40 ` Alex Schroeder
2002-10-31 20:09   ` bc
2002-11-01 13:24     ` Alex Schroeder
2002-11-01 14:33       ` bc
2002-10-31 22:16 ` Richard V. Molen [this message]
2002-11-03  8:56 ` Carlos Betancourt
     [not found] <mailman.1036125295.14204.help-gnu-emacs@gnu.org>
2002-11-01 17:43 ` Richard V. Molen
2002-11-01 19:23   ` Alan Shutko
2002-11-02  0:21   ` Vilhelm Bergman
2002-11-03 19:42 ` Chris L
2002-11-03 23:16   ` Matthias Rempe
     [not found] <mailman.1036160096.13152.help-gnu-emacs@gnu.org>
2002-11-01 18:14 ` Joshua Goldberg
     [not found]   ` <joshgold@thresher.cs.indiana.edu>
2002-11-01 18:48     ` Peter S Galbraith
2002-11-01  4:59 bobstopper
  -- strict thread matches above, loose matches on Subject: below --
2002-11-01  4:20 bobstopper
2002-11-01 14:13 ` Kevin Dziulko
2002-10-31  2:14 bobstopper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=usmym6ypz.fsf@bambecksystems.com \
    --to=rvmolen@bambecksystems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).