Sinatra: A CRUD-E Web Based Interaction!

 At the early start of my project with the Command Line Interface(CLI),  I thought I was always going to use the interface to communicate with the user. It was then interesting to realize that that was not always the case. During my stint with the Sinatra application, The interesting aspect was the way the ruby gems interacted with the web application vis a vis the controller application. It felt kind of magical to see the entire code come to life. the ability to Create, Read, Update, and Delete files or stored data within the application was such a tremendous part of the project.

Gardening was what I grew up learning as a kid while growing up. I was always around various plant types for the early part of my youth. Sometimes I was doing it as a hobby or sometimes as a chore. My mus would always drag me out in the wee hours to either water the plants, move some of the plats from the nurseries to the bigger pots, or I would be involved in grafting different plants especially roses. 

When the opportunity came for me to demonstrate in my Sinatra project the ability to use its tools to create an app, I gravitated towards plants. I must say it took a while for me to narrow it down to roses. At first, I thought of different plants to add to my database using their botanical names alongside their known names, but then I thought that would've been too cumbersome for the project. So roses it was! It was not bad a pick because I could easily narrow it down to its three district types namely: Modern Roses, Old Garden Roses, and Wild Roses. with these three choices, it was going to be easier for the user to update the database with just any of these species.

The app in itself gave the user the ability to create the data, read the contents of the data, also update the data, and lastly delete or destroy the data when created. These functions were performed via the tools created within the Sinatra type that made the work organized and somewhat seamless. There was within the app, the MVC model that was adhered to, the acronym MVC stood for Model, View, and Controller. theses were built-in actions tailored to interact with the backend and frontend of the project. the model parts were used as a sort of plate where the developer will test some form of the code, the controller was the interface between the views which was the interactive part of the application the user worked with.. this entire working of the app made the whole experience all the more worth it.

As I slowly and meticulously tried to piece my project together one thing I can say is, I did learn how valuable, and versatile the ruby app is. hopefully, it gets better as I explore rails and other applications going forward!


Comments

Post a Comment

Popular posts from this blog

Blogging!

 The journey in this extraordinary Programing career has been an interesting one albeit quite challenging. When I started this I never thought I'd reach this far in the game. Well, I'm still here! This is about my Javascript project. The javascript was the front end, while for the backend, rails were utilized.  My project choice was a blogging page in which Comments are left depending on the topic, of my choosing or a new topic by a registered user. so, to access the site, one has to register(authentication). Afterwhich, the user(here either to me or any other logged-in person), will be able to leave a comment on a post or comment on a post as the case may be. There are also options for liking the comments, updating comments, or deleting comments. Once logged in on the platform, the user can only update his/her comments but not the initiators' own comments. I must say when I started to tweak with the API it was at first alien( I gotta taste of this in my first project which...
Read more
When i finished my associates in Electrical Engineering Technology, It was an exiting time for me. the idea of solving complex problems was, or so I thought, would come naturally. messing with simple circuits to breaking down hardware just to figure out how things generally worked. Gradually  I drifted to hardware computer maintenance and i discovered the "nitty gritty".  Interesting mother board that had processors, Random Access Memory cards(RAM), To Read Only Memory cards embedded unto it. It was an interesting experience and something I did for  while. Deep inside I had always wanted to find out how computers, worked! I mean other than the hardware what else. I started to get fascinated about software when while in college, i got the privilege to program a robot to move on a track using simple code. When it worked it got me excited so I decided to try more of coding. C++ was one of the earlier languages I attempted to use.It was hard at first to understand what all ...
Read more

Rode the RAILS hard!!!

Image
 This has been the most challenging journey I have had to work on so far. I had earlier at the beginning of the rails class taken some of the concepts for granted. for instance, my previous experience in the SINATRA project was supposed to have actually given me an insight into what I was to expect. well, somewhat. The rails project in itself proved a little bit of a monster I had to tame. There were new concepts I had to learn. In the course of doing my project, I did have a little issue as to what project I was going to come up with. I had sort of a freeze. I came up with a model of a library and its readers. the readers will have comments after reading each book. but I jettisoned the idea. I then came up with the idea of a garden of roses; Roses, garden, and comments of the user with regards to the garden. the problem I ran into was the implementation of the has_many through relationship within the application. I finally made a project with a doctor and a patient, with appointme...
Read more