chuckr at telenix.org
Sat Mar 14 14:06:19 PDT 2009
-----BEGIN PGP SIGNED MESSAGE-----
soralx at cydem.org wrote:
>> question: if the "browser_products" of other entities are --so--
>> problematic, just --how-- difficult would it be to "roll our own" ?
>> note that this question is --not-- the same as asking
>> how long it would take to code all of the whiz_bangs
>> that the marketing_department_dweebs want to advertise.
>> it doesn't have to do everything,
>> but, what it does do must be done well; reliably, predictably.
>> i would want it to do things "the bsd way", e. g., search by reg_ex.
>> it would be totally divorced from anything "gnu".
>> i don't care about animation [ images hog bandwidth, big_time ].
>> i have been researching how to write a "browser".
>> it is my understanding that,
>> once i can recursively render tables, the rest is comparitively easy.
>> i have not, just yet, figured_out how to do the secure_http thing
>> [ this is where i am stalled ].
>> i want a program
>> that, either, is or, to the outside_world, appears to be a
>> "browser"_like thingy and which is --programmable--,
>> so that it may, in co_ordination with my book_keeping app,
>> log in to any account,
>> >----> to which i am already authorized access, <----<
>> such as my bank or my electric_utility,
>> in the middle_of_the_night, while i am asleep,
>> to down_load transaction_events or other postings,
>> to up_load bill_payment schedulings or other instructions,
>> so that i don't have to use my waking moments to
>> do these routine, but, necessary, time_consuming chores.
I might be misreading you, but you're talking about doing what is basically a
way to do your bookkeeping app remotely, and make it adaptable to your targets
(which I'm thinking you're not talking about supplying yourself). It seems to
me that making your interface, and making it adaptable to your app's targets, is
the main thing, and NOT the browser. A browser needs to be capable of hitting a
wide array of standards, but far, far more general in scope than what's required
by your app.
So, it seems to me that what you really want is a program that interfaces your
targets to an html protocol, and really, then make use of any of the existing
browsers, the better ones. You *could* then at a later date (if you still find
it interesting) write a browser, but concentrate on getting your app to play
nice with html, and leverage all of the existing high quality work presently
existing (stuff like firefox). Trying to do a general purpose browser now would
require you to do tons of software that would be far afield of your actual main
I'm not saying that doing a thing like a browser isn't a worthy goal, merely
that it seems to be a very separate target than a browser, so I'd consider each
item as a separate goal, making use of existing standards to link the two. If
you start writing a browser now, you're going to find yourself either doing a
very limited browser, or doing a ton of software that's only slightly connected
to your bookkeeping goal.
> isn't "links" or "lynx", with some modifications, exactly what you
> want? or are they too complex to modify?
>> rob spellberg
> [SorAlx] ridin' VN2000 Classic LT
> freebsd-chat at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-chat-unsubscribe at freebsd.org"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the freebsd-chat