brisk-bills 0.6.0

data/COPYING.LESSER

@@ -0,0 +1,165 @@
+		   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

data/INSTALL

@@ -0,0 +1,5 @@
+
+To install BriskBills, simply run :
+	gem install brisk-bills
+	
+And refer to the README for organizational setup instructions  

data/README

@@ -0,0 +1,22 @@
+== Welcome to BriskBills
+
+BriskBills is an extensible Rails App designed to provide a billing and basic accounting features for small businesses. BriskBills currently provides:
+- Automatic PDF-based invoicing, via email, to clients
+- An extensive interface for managing time, materials, and proposals for multiple employees in an organization
+- Tax collection and tracking
+- Payment and Account Balance tracking
+- Basic Client Roster Management
+- Comprehensive unit tests
+- Excellent stubs for fleshing out your own organization's specific models & controllers
+
+== Getting started
+
+BriskBills is a traditional Ruby on Rails application, meaning that you can
+configure and run it the way you would a normal Rails application.
+
+1. Once the brisk-bills gem has been instakled, start a new brisk-bills deployment using the brisk-bills command
+   and your site name. Ex: brisk-bills myorganization
+2. Change directory into myorganization and run "rake brisk_bills:first_time_setup" to create your administrative account and get started.
+3. Start the web server: <tt>script/server</tt>
+3. Go to http://localhost:3000/ and login with your administrative account to begin creating employees and get started
+4. Visit www.briskbills.com to read more 

data/Rakefile

@@ -0,0 +1,11 @@
+require File.join(File.dirname(__FILE__), 'config', 'boot')
+
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+
+require 'tasks/rails'
+
+unless Rake::Task.task_defined? "package:release"
+  Dir["#{BRISKBILLS_ROOT}/lib/tasks/**/*.rake"].sort.each { |ext| load ext }
+end

data/TODO.txt

@@ -0,0 +1,112 @@
+*I want to delete that old ashbritt invoice ... I should be able to !
+	* THen figure out if perhaps we can disable the auto-assign on create  	
+  	* Remove create_invoice_payments from create/destory
+  	
+  	* We need to go through and see where client balances are being handled, and make sure its using invoiced_amount - payment_amount
+  	* let's start by adding a detail that shows what payments are currently allocated..
+  	* Don't forget to Add the right show fields too (in the payments controller)
+  	* THen we can add an edit...
+  	* And then we need to add a complemntary field in the invoices view? Nah - but show which payments are currently assigned as a read-only...
+  	* Then we can allow multiple invoices to be unpublished...
+
+	* I guess I unpublish and delete it?
+	* We should put proper transactions in place here too while we're in here...
+	* No - let's get the damn payments applying with the interface quickbooks uses
+	* We should probably allow payment updates, just do a destroy_invoice_payments and create_invoice_payments when that happens. if its the newest payment for a client.
+		* Make sure the payments_test adds a test for this...
+
+* Add Existing Client Representatives should show them in alaphabetical order
+
+* We should add an unpublished Open Invoices controller ...
+
+* We should put tax before cost in the activities with prices controller...
+
+* I want to delete that old ashbritt invoice ... I should be able to !
+  * Here's what I'm thinking:
+  	* We remove create_invoice_payments from create/destory
+  	* We add an unallocated_amount to the payments controller / view
+  	* We need to go through and see where client balances are being handled, and make sure its using invoiced_amount - payment_amount
+  	* let's start by adding a detail that shows what payments are currently allocated..
+  	* THen we can add an edit...
+  	* And then we need to add a complemntary field in the invoices view? Nah - but show which payments are currently assigned as a read-only...
+  	* Then we can allow multiple invoices to be unpublished...
+
+	* I guess I unpublish and delete it?
+	* We should put proper transactions in place here too while we're in here...
+	* No - let's get the damn payments applying with the interface quickbooks uses
+	* We should probably allow payment updates, just do a destroy_invoice_payments and create_invoice_payments when that happens. if its the newest payment for a client.
+		* Make sure the payments_test adds a test for this...
+
+* Add better transactions throughout!
+
+* Translate the time into the local zone for the user, probably each user/client should have a zone associtation in their account.
+	*  Its already stored in UTC everywhere...
+	* We need to factor this into invoices too, I think
+
+* Public interface
+	* Showing the Client eventlogs as an unedutable nested list  might be nice... Hell, employee eventlogs too....
+   * CC payments handling - not a plugin
+
+---------------
+Plugin interface using engines?
+---------------
+LONGER-TERM: (Needs re-prioritization...)
+
+Feature:
+
+* I'd like some tests cases written for the view objects, make sure they work just like the non-views... ...
+	* Boy this is getting hard, I think it has something to do wioth the transactions... Oddly, the tests work on their own, outside of the rake test	
+
+* Better searches by using the search sql fields...
+
+* See what we decide to do long-term with our model_view hack, maybe we can run tests on both models, as well as their view_models. Just one by one... I think thats smart...
+
+Feature: Make the Search actually work the way we'd expect. Perhaps even make something mroe useful still that would let us filter records...
+
+BUG: We should probably write a plugin that better displays delete errors in the flash[:error] , invoices is a good place for that
+	* BTW - why does it show delete as an option here when we clearly can't delete some of these
+	* Also- it'd be nice to show a pretty record error in the invoices update, if you try to update the activities on a published invoice
+	* Create two invoices - both unpublished, try to delete the oldest one
+
+* Use polymorphic relationship for sub activities
+	* Maybe ..
+
+* all delete confirms should go through the modal box - make this a plugin
+
+* The ability to create an activity from the activities & invoices/activities list would be sweet
+	* With a little pop-up that asks for the activity type?
+
+* Emailer: 
+	* <p>Please note that your current account balance, including this invoice, is: $XXX.XXX . Invoices 1,2, & 3 are outstanding. <red>Invoices 1 & 2 are past their 30 day </red> </p>
+	* And change the if line to only send when there's been a change in the invoice status (See the invoice TODO...)
+	* This gets a little complicated though - we have to decide if we're going to generate these warnings based on the date of the invoice, or the current situation
+	
+* The invoice issued_on date I think is rounding off to the end of the day on assignment. It should really be time sensitive.
+	
+* Better unit tests for Activity::* model. (too , make sure negative values work on whatever..)
+
+Plugins for 
+   * Reimbursable scanning
+	* phone calls
+		* The :phone_extension field, *might* be something we put into the asterisk plugin 
+
+* An employee_rate_changed_last changed plugin would be super-useful at some point...
+
+Nice Features:
+	* Todo list.. maybe just a block? Call it an outstanding issues/projects
+	* Client Notes? Probably just a google docs link
+-------------------
+dd if=/dev/urandom bs=200 count=1 | tr -cd 'A-Za-z0-9!@#$%^&*()_+'; echo
+
+CREATE DATABASE `briskbills_development`;
+GRANT ALL PRIVILEGES ON briskbills_development.* TO briskbills@localhost IDENTIFIED BY 'cut1ckle';
+
+CREATE DATABASE `cusis_test`;
+GRANT ALL PRIVILEGES ON cusis_test.* TO cusis@localhost IDENTIFIED BY 'cut1ckle';
+-------------------
+required gems:
+ * extensions
+ * pdf-writer
+ * slimtimer4r
+ * money
+

data/app/controllers/admin/activities_controller.rb

@@ -0,0 +1,151 @@
+class Admin::ActivitiesController < ApplicationController
+  include AdminLayoutHelper
+  include ExtensibleObjectHelper
+ 
+  def self.activities_scaffold_config(&block)
+    @activities_scaffold_configs ||= []
+    @activities_scaffold_configs << block.to_proc  
+  end
+  
+  def self.activities_scaffold_init
+    # I dont love this mechanism of scaffold_init - but I think its going to work quite well...
+    configs = @activities_scaffold_configs
+
+    active_scaffold(:activity){|c| configs.each{|ac| ac.call c if ac.respond_to? :call} }
+  end
+  
+  activities_scaffold_config do |config|
+    config.label = "Activity Quick-Review"
+    
+    config.show.link = nil
+    config.search.link = nil
+    config.create.link = nil
+    
+    config.list.per_page = 6
+    
+    config.list.sorting = { :occurred_on => :asc }
+    
+    config.columns = [:activity,:invoice, :occurred_on]
+    
+    config.columns[:occurred_on].form_ui = :calendar
+    
+    config.list.columns = [:activity, :occurred_on]
+    
+    config.create.columns = config.update.columns =  [:occurred_on]
+    
+    config.full_list_refresh_on = [:update, :create, :destroy]
+    
+    # This allows us to use the for_activity_type parameter to selectively constriain fields to the appropriate record types.
+    config.columns.instance_eval do    
+
+      # Column selective inclusion, based on activity_type:
+      alias :add_without_activities :add
+      
+      def extend_activity_column(col)     
+        def col.for_activity_type?(type); (for_activities.length == 0 or for_activities.include? type) ? true : false; end
+        def col.for_activities; @for_activities ||= []; end
+      end
+      
+      # Extend the existing columns:
+      @set.each{|col| extend_activity_column col}
+      
+      # And ensure that we continue to do the same for new ones here on:
+      def add(*args)
+        add_without_activities *args
+  
+        args.flatten.collect { |a| extend_activity_column find_by_name(a.to_sym) }
+      end
+      
+      alias :<< :add
+    end
+
+  end
+
+  private
+  
+  def do_activity_type_for_method?(method_name)
+    self.respond_to? "#{@record.activity_type}_#{method_name}".to_sym
+  end
+  
+  def do_activity_type_for_method(*args)
+    method_name = args.shift
+    
+    unless @record.nil?
+      activity_action = "#{@record.activity_type}_#{method_name}".to_sym
+      self.send( *([activity_action] + args) ) if self.respond_to? activity_action
+    end
+  end
+
+  def conditions_for_collection
+    ['activities.is_published = ?', 0] if params[:parent_model].nil?
+  end
+  
+  def list_row_class(record)
+    record.activity_type
+  end
+
+  def do_edit
+    super
+    do_activity_type_for_method :do_edit
+  end
+
+  def do_update
+    super
+    do_activity_type_for_method :do_update
+  end
+    
+  def before_update_save(record)
+    super(record)
+    record.is_published = true
+    
+    do_activity_type_for_method :before_update_save, record
+  end
+
+  def update_record_from_params(activity_record, columns, attributes)
+    activity_params = HashWithIndifferentAccess.new
+    subactivity_params = HashWithIndifferentAccess.new
+    
+    attributes.delete 'apply_tax'
+    
+    attributes.each_pair { |k,v| ((/^(occurred_on|is_published|cost|tax|client_id)/.match k) ? activity_params : subactivity_params )[k] = v }
+
+    activity_record = super(activity_record, columns, activity_params)
+    activity_record.sub_activity.attributes = subactivity_params if subactivity_params.length > 0        
+    
+    activity_record
+  end
+  
+  def do_list 
+    super
+
+    records_by_type = {}
+
+    @records.each do |r|
+      records_by_type[r.activity_type] ||= []
+      records_by_type[r.activity_type] << r
+    end
+
+    records_by_type.each_pair do |activity_type, records|
+      do_list_action = "#{activity_type}_do_list".to_sym
+
+       self.send( do_list_action, records) if self.respond_to? do_list_action
+    end
+  end
+  
+  public
+  
+  def row        
+    # I think they should have had a do_row in active scaffold ....
+    record = find_if_allowed(params[:id], :read)
+    
+    do_list_action = "#{record.activity_type}_do_list".to_sym
+
+    self.send( do_list_action, [record]) if self.respond_to? do_list_action
+    
+    render :partial => 'list_record', :locals => {:record => record}
+  end
+
+  handle_extensions
+
+  activities_scaffold_init
+end