+2005-02-21 Marcus Mueller <znek@mulle-kybernetik.com>
+
+ * README: updated with a detailed NOTE to prevent confusion
+
+ * Project Templates/SOPE/Web Application/GNUmakefile: slightly improved
+
2004-12-19 Marcus Mueller <znek@mulle-kybernetik.com>
* Project Templates/SOPE/Web Application/*: fixed various replacement
WOAPP_NAME = ÇPROJECTNAMEÈ
-ÇPROJECTNAMEÈ_OBJC_FILES = \
-ÇPROJECTNAMEÈ_main.m Application.m Session.m DirectAction.m \
-Main.m
+ÇPROJECTNAMEÈ_OBJC_FILES = \
+ Application.m \
+ Session.m \
+ DirectAction.m \
-ÇPROJECTNAMEÈ_COMPONENTS = \
+ÇPROJECTNAMEÈ_OBJC_FILES += \
+ Main.m \
+
+ÇPROJECTNAMEÈ_OBJC_FILES += \
+ ÇPROJECTNAMEÈ_main.m
+
+
+ÇPROJECTNAMEÈ_COMPONENTS = \
+
+
+ÇPROJECTNAMEÈ_RESOURCE_FILES = \
+
+
+ÇPROJECTNAMEÈ_LANGUAGES = \
+ English \
+
+
+ÇPROJECTNAMEÈ_LOCALIZED_RESOURCE_FILES = \
-ÇPROJECTNAMEÈ_RESOURCE_FILES = \
ÇPROJECTNAMEÈ_WEBSERVER_RESOURCE_FILES := $(shell find WebServerResources -type f -print)
Templates installed in 1) are available for all developers working
on this machine. Templates installed in 2) are available for you,
only.
+
+NOTE: installing templates means to copy them - there's no other magic
+involved, no need to compile anything etc. Simply copy them to one of the two
+destinations above. I usually do a
+find . -type d -name .svn -exec rm -rf {} \;
+afterwards in order to remove the Subversion metadata. This metadata would
+get copied to the new projects destination otherwise, probably causing
+confusion if you plan on using Subversion in your projects.
+
+Whether you copy the templates with 'cp' or 'gnutar' is up to you, there are
+no special files involved.
+