/*
 * ECatalog is a database front-end, with two main features:
 * 1. Use of preferences
 *  A preference-based approach, where the user is allowed to define the importance of each criterion.
 *  Then the items are ranked accordingly to his criteria.
 * 2. Trade-off analysis
 *  A cooperative database approach, where the system "argues" with the user about his criteria.
 *  When there are no matching items, the system explains the minimal conflicting set and
 *  give some possible strong and weak relaxations about his criteria.
 * This package also containts the software and the set-up details used for our User Study,
 * comparing the use or not of the two previous features mentioned above.
 *
 * Copyright (C) 2006 David Portabella Clotet, Artificial Intelligence Laboratory, EPFL
 * 
 * This file is part of ecatalog-1.0.zip
 * 
 * ECatalog is free software and a free user study set-up;
 * you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation; either version 2 of the License, or
 * (at your option) any later version.
 * 
 * ECatalog is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with ECatalog; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 * 
 * @version 1.0
 * @author David Portabella
 * To contact the author:
 * email: david@portabella.name and david.portabella@epfl.ch
 * 
 * More information about ECatalog:
 *  http://sourceforge.net/projects/ecatalog/
 *  http://icwww.epfl.ch/~portabel/ecatalogs/
 */

package ecatalog.db;

import ecatalog.ECatalog;

/* Each constraint has a weight associated (the importance of the constraint).
 * The database uses the constraints with "MUST" weights to filter the database,
 * and the VisualizationGui uses these weights to rank the items
 */
public class Weight {
    /* the weightvalue, from 0.0 to 1.0.   0.0 = not important. 1.0 = very important
     * -1 indicates that the constraint/prefenrece is a MUST ("more" than very important).
     */
    double weightValue; 

    /* the weightvalue, from 0.0 to 1.0.   0.0 = not important. 1.0 = very important
     * -1 indicates that the constraint/prefenrece is a MUST ("more" than very important).
     */
    public Weight(double weightValue) {
        this.weightValue = weightValue;
    }


    /* the weightvalue, from 0.0 to 1.0.   0.0 = not important. 1.0 = very important
     * -1 indicates that the constraint/prefenrece is a MUST ("more" than very important).
     */
    public double getWeightValue() {
        return weightValue;
    }
}




/* Each constraint has a weight associated (the importance of the constraint).
 * The database uses the constraints with "MUST" weights to filter the database,
 * and the VisualizationGui uses these weights to rank the items
 */
/*
public class WeightType {
    int weightValue; // the weightvalue, from 0 to 4. -1 indicates that the constraint/prefenrece is a MUST.
    PREFER(0.33, "prefer"), IMPORTANT(0.66, "important"), VERY_IMPORTANT(1.0, "very important"), MUST();

    double weightValue;
    String description;
    WeightType(double weightValue, String description) {
        this.weightValue = weightValue;
	this.description = description;
    }

    WeightType() {}

    public double getWeightValue() {
	if (this == MUST) {
	    ECatalog.error(new Error("MUST does not have a weight value!"));
	    throw new Error(); //it is already done, but to avoid the java compiling error
	}
        return weightValue;
    }

    public String toString() {
	return description;
    }
}
*/