Okay, enough “database theory 101”.ĭisplay a page where the user could select their “Location” from a drop-down combo field… Since each Signature relates back to a Location, if the Company changes their logo or web site, no change to the Signature record is needed, you need only regenerate the HTML signature for Outlook.
The “Locations” table is a lookup table containing information that will be related to multiple “Signatures” (usually one Signature per person). Of course, what I could have finished in VFP in about 60 seconds took me many frustrating hours with more than one Rails/Ajax book thrown across the room.įor this application, I only have 2 tables (told you it was simple) Locations and Signatures.
#OUTLOOK FOR MAC EMAIL SIGNATURE DOUBLE SPACED HOW TO#
Of course, now that I know how to do it, it seems simple (and Rails is great again, the web makes sense, and all is right with the world). I understand the whole “disconnected” “stateless” model of web development, but I never dreamed it would be this dang hard to put a drop-down box and a couple of text fields inside form tags on a page and get them to interact with my database and with each other. I used the Scaffolding classes built into Rails 2.1x to initially generate the pages (see, I wanted to call them screens or forms) to do the CRUD work, then I set about understanding how they worked and editing them to look a little better. Well, most of my software development background has focused primarily on creating data-based applications with heavy data-entry and reporting, so I was eager to see if Rails was up to the task. This small application was my first chance to do true data-based entry using form fields (most of my prior RoR projects just tapped into existing databases for searching and presentation in a browser). Recently, I wrote about creating a Ruby on Rails app that would create HTML formatted signatures for Outlook and web-based e-mail systems (see: Outlook and the Double-Spaced Signature ).
0 kommentar(er)
