Hi Russ,
I wrote my first inventory/accounting system in Basic in 1977 on a
64K CompuColor... and have written several since. =)
I am writing a Rev app using a remote MySQL server that uses PHP
middleware on the server, it is fast and solid and a great
development environment even for a Rev noob like me, I would highly
recommend it.
My only obstacles are that I am just learning Rev, so things are
going slowly, and don't have much time to put into it... but
everything I finish works fast, reliably, and is easily configurable.
I can do in 20 minutes what it takes a Ruby on Rails expert an hour
or two to accomplish.
I would recommend Rev over RealBasic because you can instantly test
without compiling.
(I chose not to rely on the Rev built-in database commands, but
instead just use the LibURL command to pass values back and forth to
PHP scripts...)
Anyway, IMO Rev makes a wonderful front end for a MySQL system.
Better than a browser based system.
For your content control system, check out WebMerge http://
www.fourthworld.com/products/webmerge/index.html it will save you
some coding!
Cheers,
Josh
On Apr 3, 2006, at 3:18 PM, Russ McBride wrote:
Hi,
It's been a few years since I've used Revolution.
We've got a messy set of systems here that keep the front end and
back end of our store running and I'm exploring ideas for
inexpensively consolidating and streamlining them to reduce
complexity and redundancy. One possibility is rebuilding
everything from the ground up in RR. I'm not sure that it can do
it though. Basically, we need to rebuild nothing less than a
"junior-SAP" system, a set of the following:
--a point-of-sale system
--an inventory management system
--some custom apps that access remote web services
--a content control system for web site data (simpler than
Hemingway, e.g.)
--some custom bookkeeping apps
The goal would be to reduce our 4 overlapping databases down to one
so it means that these apps would be heavily database-centric,
probably built on FrontBase, PostgreSQL, or MySQL. And I would
need to easily tie in some Objective-C code and Java code (and
ideally some Ruby code) when necessary. The web content system
would have to feed into some flat files for the WebDNA web app
system we're using until we get around to rebuilding our WebDNA/
WebObjects composite system.
At one point Geoff Canyon made it sound like RealBasic might be
better for database-intensive applications.
Unfortunately our environment at the University here requires
custom applications, but we don't have the $$ for an actual SAP-
style setup. Having used RR for some apps quite awhile ago my
first impression is that it might be perfect, er--the only possible
candidate--for rapidly building an inexpensive, but comprehensive
set of apps. My other choices would be RealBasic (more code, but
maybe a more desirable language), Cocoa (but this wouldn't be truly
rapid--at least not for me), Ruby on Rails (but I don't want web
interfaces), WebObjects (ditto), or Cocoa-Ruby (interesting, but
limited to Mac), or Ruby + TK (unstable GUI system).
What do you think? Any tips, anecdotes, or suggestions appreciated.
Thanks very much,
Russ McBride
Programmer/Analyst, PhD Cadidate
The Scholar's Workstation
University of California at Berkeley
510-643-6853
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
