Browse files

document new directory structure and bump version

  • Loading branch information...
1 parent 1a39937 commit 8be63558ddcd4c6acdff9c3f3f9b48948df81fce @chazmcgarvey committed Apr 9, 2013
Showing with 17 additions and 2 deletions.
  1. +1 −1 Makefile
  2. +15 −0
  3. +1 −1 src/com/dogcows/
@@ -3,7 +3,7 @@
# Supported targets: all clean distclean dist fetch jar
project = VimCoder
-version = 0.3.4
+version = 0.3.5
sources = $(wildcard src/com/dogcows/*.java)
classes = $(sources:src/
@@ -87,6 +87,21 @@ use. If you have already saved some problems to the previous storage
directory, you may also want to actually move the directory to the new
location so that VimCoder can find the work you've already done.
+Beginning with VimCoder 1.3.5, there is a new option for an alternative
+directory structure. It is not enabled by default, but it may be in the
+future. Rather than having directories named after problem identifiers, the
+new structure uses two levels of directories. On the first level, directories
+are named after the contest associated with the problem (e.g. SRM-144-DIV-1),
+and on the second level, directories are named after the problem's point value
+(e.g. 300). This directory structure may be preferable if you ever want to
+browse your repository since the contest name and point values are more easily
+identifiable than the problem identifier.
+If this new directory structure is enabled, it will only apply to new
+problems. VimCoder will not try to reorganize your current repository, though
+you are welcome to do it manually yourself if you would like to switch to the
+new directory structure.
##### Vim Command
By default, VimCoder tries to invoke Vim using the `gvim` command (or
@@ -27,7 +27,7 @@
* The name and version of this plugin.
- public final static String version = "VimCoder 0.3.4";
+ public final static String version = "VimCoder 0.3.5";
* The website of the plugin project.

0 comments on commit 8be6355

Please sign in to comment.