databaseformalizer 0.3.0

data/.project

@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>databaseformalizer</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+		<buildCommand>
+			<name>com.aptana.ide.core.unifiedBuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+	</buildSpec>
+	<natures>
+		<nature>org.radrails.rails.core.railsnature</nature>
+		<nature>com.aptana.ruby.core.rubynature</nature>
+	</natures>
+</projectDescription>

data/README

@@ -0,0 +1,256 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(:all)
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.com/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |   |-- images
+  |   |-- javascripts
+  |   `-- stylesheets
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Contains subdirectories for
+  images, stylesheets, and javascripts. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.

data/README.md

@@ -0,0 +1,2 @@
+databaseFormalizer
+==================

data/Rakefile

@@ -0,0 +1,21 @@
+require 'rake/testtask'
+
+Rake::TestTask.new do |test|
+  test.pattern = 'test/**/*_test.rb'
+  test.libs << 'test'
+end
+
+
+begin
+  require "jeweler"
+  Jeweler::Tasks.new do |gem|
+    gem.name = "databaseFormalizer"
+    gem.summary = "Description of your gem"
+    gem.email = "you@email.com"
+    gem.authors = ["Your Name"]
+    gem.files = Dir["{lib}/**/*", "{app}/**/*", "{public}/**/*", "{config}/**/*"]
+  end
+  Jeweler::GemcutterTasks.new
+rescue
+  puts "Jeweler or dependency not available."
+end

data/app/controllers/databaseformalizer/attr_defs_controller.rb

@@ -0,0 +1,98 @@
+module Databaseformalizer
+  class AttrDefsController < ApplicationController
+    # GET /attr_defs
+    # GET /attr_defs.json
+    def index
+      @attr_defs = AttrDef.all
+  
+      respond_to do |format|
+        format.html # index.html.erb
+        format.json { render json: @attr_defs }
+      end
+    end
+  
+    # GET /attr_defs/1
+    # GET /attr_defs/1.json
+    def show
+      @attr_def = AttrDef.find(params[:id])
+  
+      respond_to do |format|
+        format.html # show.html.erb
+        format.json { render json: @attr_def }
+      end
+    end
+  
+    # GET /attr_defs/new
+    # GET /attr_defs/new.json
+    def new
+      @attr_def = AttrDef.new
+  
+      respond_to do |format|
+        format.html # new.html.erb
+        format.json { render json: @attr_def }
+      end
+    end
+  
+    # GET /attr_defs/1/edit
+    def edit
+      @attr_def = AttrDef.find(params[:id])
+    end
+  
+    # POST /attr_defs
+    # POST /attr_defs.json
+    def create
+      @attr_def = AttrDef.new(params[:databaseformalizer_attr_def])
+      if @attr_def.label == ""
+        @attr_def.label = @attr_def.attr_def_name
+      end
+      
+      if params[:databaseformalizer_attr_def]['dataType'] == "entityDef"
+        @attr_def.child_entity_def_name=params[:databaseformalizer_attr_def]['child_entity_def_name']
+      else
+        @attr_def.child_entity_def_name=nil
+      end
+  
+      respond_to do |format|
+        if @attr_def.save
+          format.html { redirect_to @attr_def, notice: 'Attr def was successfully created.' }
+          format.json { render json: @attr_def, status: :created, location: @attr_def }
+        else
+          format.html { render action: "new" }
+          format.json { render json: @attr_def.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # PUT /attr_defs/1
+    # PUT /attr_defs/1.json
+    def update
+      @attr_def = AttrDef.find(params[:id])
+      if params[:databaseformalizer_attr_def]['dataType'] == "entityDef"
+        @attr_def.child_entity_def_name=params[:databaseformalizer_attr_def]['child_entity_def_name']
+      else
+        @attr_def.child_entity_def_name=nil
+      end
+      respond_to do |format|
+        if @attr_def.update_attributes(params[:databaseformalizer_attr_def])
+          format.html { redirect_to @attr_def, notice: 'Attr def was successfully updated.'}
+          format.json { head :no_content }
+        else
+          format.html { render action: "edit" }
+          format.json { render json: @attr_def.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # DELETE /attr_defs/1
+    # DELETE /attr_defs/1.json
+    def destroy
+      @attr_def = AttrDef.find(params[:id])
+      @attr_def.destroy
+  
+      respond_to do |format|
+        format.html { redirect_to databaseformalizer_attr_defs_url }
+        format.json { head :no_content }
+      end
+    end
+  end
+end

data/app/controllers/databaseformalizer/attr_vals_controller.rb

@@ -0,0 +1,85 @@
+module Databaseformalizer
+  class AttrValsController < ApplicationController
+    # GET /attr_vals
+    # GET /attr_vals.json
+    def index
+      @attr_vals = AttrVal.all
+  
+      respond_to do |format|
+        format.html # index.html.erb
+        format.json { render json: @attr_vals }
+      end
+    end
+  
+    # GET /attr_vals/1
+    # GET /attr_vals/1.json
+    def show
+      @attr_val = AttrVal.find(params[:id])
+  
+      respond_to do |format|
+        format.html # show.html.erb
+        format.json { render json: @attr_val }
+      end
+    end
+  
+    # GET /attr_vals/new
+    # GET /attr_vals/new.json
+    def new
+      @attr_val = AttrVal.new
+  
+      respond_to do |format|
+        format.html # new.html.erb
+        format.json { render json: @attr_val }
+      end
+    end
+  
+    # GET /attr_vals/1/edit
+    def edit
+      @attr_val = AttrVal.find(params[:id])
+    end
+  
+    # POST /attr_vals
+    # POST /attr_vals.json
+    def create
+      @attr_val = AttrVal.new(params[:databaseformalizer_attr_val])
+  
+      respond_to do |format|
+        if @attr_val.save
+          format.html { redirect_to @attr_val, notice: 'Attr val was successfully created.' }
+          format.json { render json: @attr_val, status: :created, location: @attr_val }
+        else
+          format.html { render action: "new" }
+          format.json { render json: @attr_val.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # PUT /attr_vals/1
+    # PUT /attr_vals/1.json
+    def update
+      @attr_val = AttrVal.find(params[:id])
+  
+      respond_to do |format|
+        if @attr_val.update_attributes(params[:databaseformalizer_attr_val])
+          format.html { redirect_to @attr_val, notice: 'Attr val was successfully updated.' }
+          format.json { head :no_content }
+        else
+          format.html { render action: "edit" }
+          format.json { render json: @attr_val.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # DELETE /attr_vals/1
+    # DELETE /attr_vals/1.json
+    def destroy
+      @attr_val = AttrVal.find(params[:id])
+      @attr_val.destroy
+  
+      respond_to do |format|
+        format.html { redirect_to databaseformalizer_attr_vals_url }
+        format.json { head :no_content }
+      end
+    end
+  end
+end

data/app/controllers/databaseformalizer/dbformahome_controller.rb

@@ -0,0 +1,7 @@
+module Databaseformalizer
+  class DbformahomeController < ApplicationController
+    
+    def index
+    end
+  end
+end

data/app/controllers/databaseformalizer/entities_controller.rb

@@ -0,0 +1,105 @@
+module Databaseformalizer
+  class EntitiesController < ApplicationController
+    include Databaseformalizer
+
+    # GET /entities
+    # GET /entities.json
+    def index
+      @entities = Entity.find(:all, :limit=>100)
+      EntitiesHelper.setModelGraph("public/images/UMLmodel.png")
+      
+      respond_to do |format|
+        format.html # index.html.erb
+        format.json { render json: @entities }
+      end
+    end
+  
+    # GET /entities/1
+    # GET /entities/1.json
+    def show
+      @entity = Entity.find(params[:id])
+  
+      respond_to do |format|
+        format.html # show.html.erb
+        format.json { render json: @entity }
+      end
+    end
+  
+    # GET /entities/new
+    # GET /entities/new.json
+    def new
+      @entity = Entity.new
+      
+      if params[:entity_def] != nil
+        @all_entityDefs = EntityDef.find_all_by_entity_def_name(params[:entity_def])
+        @entity.entity_def = @all_entityDefs.first
+        @type = params[:entity_def]
+      else
+        @all_entityDefs = EntityDef.all
+        @type = "Entity"
+      end
+      respond_to do |format|
+        format.html # new.html.erbe
+        format.json { render json: @entity }
+        format.js { @entity }
+      end
+    end
+  
+    # GET /entities/1/edit
+    def edit
+      @entity = Entity.find(params[:id])
+      @all_entityDefs = EntityDef.all
+    end
+  
+    # POST /entities
+    # POST /entities.json
+    def create
+      @entity = Entity.new(params[:databaseformalizer_entity])
+      @entity.attr_vals.clear
+      EntitiesHelper.setAttrVals(params[:attr_vals], @entity)
+      
+      respond_to do |format|
+        if @entity.save
+          format.html { redirect_to @entity, notice: 'Entity was successfully created.' }
+          format.json { render json: @entity, status: :created, location: @entity }
+        else
+          format.html { render action: "new" }
+          format.json { render json: @entity.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # PUT /entities/1
+    # PUT /entities/1.json
+    def update
+      @entity = Entity.find(params[:id])
+      @entity.attr_vals.clear
+      EntitiesHelper.setAttrVals(params[:attr_vals], @entity)
+      @entity.attributes = params[:databaseformalizer_entity]
+      
+      respond_to do |format|
+        if @entity.save
+          format.html { redirect_to @entity, notice: 'Entity was successfully updated.'}
+          format.json { head :no_content }
+        else
+          format.html { render action: "edit" }
+          format.json { render json: @entity.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # DELETE /entities/1
+    # DELETE /entities/1.json
+    def destroy
+      
+      @entity = Entity.find(params[:id])
+      @entity.destroy
+  
+      respond_to do |format|
+        format.html { redirect_to databaseformalizer_entities_url }
+        format.json { head :no_content }
+      end
+    end
+  
+  end
+end

data/app/controllers/databaseformalizer/entity_defs_controller.rb

@@ -0,0 +1,90 @@
+module Databaseformalizer
+  class EntityDefsController < ApplicationController
+    # GET /entity_defs
+    # GET /entity_defs.json
+    def index
+      @entity_defs = EntityDef.all
+      EntityDefsHelper.setMetaModelGraph("public/images/UMLmetaModel.png")
+      
+      respond_to do |format|
+        format.html # index.html.erb
+        format.json { render json: @entity_defs }
+      end
+    end
+  
+    # GET /entity_defs/1
+    # GET /entity_defs/1.json
+    def show
+      @entity_def = EntityDef.find(params[:id])
+  
+      respond_to do |format|
+        format.html # show.html.erb
+        format.json { render json: @entity_def }
+      end
+    end
+  
+    # GET /entity_defs/new
+    # GET /entity_defs/new.json
+    def new
+      @entity_def = EntityDef.new
+  
+      respond_to do |format|
+        format.html # new.html.erb
+        format.json { render json: @entity_def }
+      end
+    end
+  
+    # GET /entity_defs/1/edit
+    def edit
+      @entity_def = EntityDef.find(params[:id])
+    end
+  
+    # POST /entity_defs
+    # POST /entity_defs.json
+    def create
+      @entity_def = EntityDef.new(params[:databaseformalizer_entity_def])
+      if @entity_def.label == ""
+        @entity_def.label = @entity_def.entity_def_name
+      end
+      respond_to do |format|
+        if @entity_def.save
+          format.html { redirect_to @entity_def, notice: 'Entity def was successfully created.'}
+          format.json { render json: @entity_def, status: :created, location: @entity_def }
+        else
+          format.html { render action: "new" }
+          format.json { render json: @entity_def.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # PUT /entity_defs/1
+    # PUT /entity_defs/1.json
+    def update
+      @entity_def = EntityDef.find(params[:id])
+      if params[:databaseformalizer_entity_def][:attrDef_ids] == nil
+        @entity_def.attrDefs.clear
+      end
+      respond_to do |format|
+        if @entity_def.update_attributes(params[:databaseformalizer_entity_def])
+          format.html { redirect_to @entity_def, notice: 'Entity def was successfully updated.'  }
+          format.json { head :no_content }
+        else
+          format.html { render action: "edit" }
+          format.json { render json: @entity_def.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # DELETE /entity_defs/1
+    # DELETE /entity_defs/1.json
+    def destroy
+      @entity_def = EntityDef.find(params[:id])
+      @entity_def.destroy
+  
+      respond_to do |format|
+        format.html { redirect_to databaseformalizer_entity_defs_url }
+        format.json { head :no_content }
+      end
+    end
+  end
+end

data/app/helpers/application_helper.rb

@@ -0,0 +1,2 @@
+## Look in lib/application_helper.rb
+## I can't figure out how to get it included unless I put it that directory

data/app/helpers/databaseformalizer/application_helper.rb

@@ -0,0 +1,4 @@
+module Databaseformalizer
+  module ApplicationHelper
+  end
+end