On Thu, Feb 26, 2004 at 02:58:11PM -0500, Clayton Carter wrote: | Hi all. I'm going to play curmudgeon again and say that, | while this is all well and good, I don't use evo and I have no plans | to. In fact, I don't want my GC SXs showing up in my email client at | all.
Well, it depends on how you view evo. As an email client: probably not. As a PIM: maybe. | starts and kills the daemon itself when I open and close it, that's | cool by me, but I think we have to keep home users in mind here as | well, esp. since this is still in planning. That's an excellent perspective to keep in mind. Thanks. | PS - as for the question of how to make evo act on a SX, what's wrong | w/ 'PUT /scheduled?SXid=00000?action=enter' ? PUT is already the verb in there. If you're going to have the "action" part, then "PUT" just becomes "DO", which isn't really useful. The gnucash/scheduled-transaction typed data would have to contain enough information for Evo to be in a position to do a GET,PUT,POST or DELETE something... Don't quite know what that is, yet. Probably the only real thing to do is open GnuCash, or get the next-level of detail for display. | Also, I said I don't | use evo, but that doesn't mean that it wouldn't be cool for me to | have, say, a GNOME panel applet that could periodically do a | 'GET /acct_info?acct_name=HUECU:Checking&value=balance' and display | it. That's the idea. Constrained functional interfaces with generic, shared data types can lead to useful and novel combinations. Small pieces loosely joined. :) ...jsled -- http://www.asynchronous.org - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
