RFC Name : ...

Editor(s): ...

<<TableOfContents: execution failed [Argument "maxdepth" must be an integer value, not "[2]"] (see also the log)>>

About this document

This is an official Request for Comment (RFC) for Fixing the loading and saving of the vizmap.props file.

For details on RFCs in general, check out the Wikipedia Entry: Request for Comments (RFCs)

Status

Open for public comment

How to Comment

To view/add comments, click on any of 'Comment' links below. By adding your ideas to the Wiki directly, we can more easily organize everyone's ideas, and keep clear records. Be sure to include today's date and your name for each comment. Here is an example to get things started: /Comment.

Try to keep your comments as concrete and constructive as possible. For example, if you find a part of the RFC makes no sense, please say so, but don't stop there. Take the extra step and propose alternatives.

Introduction

The vizmap.props file is currently loaded from at least 2 different default locations. One is the cytoscape installation directory and the other is the users .cytoscape directory in their home directory. Figuring out these locations, learning when files get saved to certain locations, and when files get loaded from certain locations is difficult for users.

This document is an attempt to develop a new scheme for loading and saving vizmap.props files.

Biological Questions / Use Cases

Proposal

Loading

The current scheme for loading vizmap.props at startup is as follows. This is also the order of precedence, so the most recently loaded vizmap.props file will be the current one.

Either of the following actions will overwrite (in memory) the current vizmap.props:

Saving


No Longer Under Consideration or On Hold

Requirements

Backward Compatibility

In the proposal above, backwards compatibility is achieved by the user importing his or her favorite vizmap.props file.

Implementation Plan

VizMapPropsRFC (last edited 2009-02-12 01:03:34 by localhost)

MoinMoin Appliance - Powered by TurnKey Linux