Permalink
Browse files

Removed old files which will not be used (100% certain that they are …

…useless)
  • Loading branch information...
1 parent e8c7e0a commit 1f68a029c3ed54062a3e22951259fba0642a23f7 Mihai Maruseac committed Feb 10, 2011
Showing with 0 additions and 114 deletions.
  1. +0 −19 old/LICENSE.txt
  2. +0 −9 old/Makefile
  3. +0 −86 old/tests/01/test
View
@@ -1,19 +0,0 @@
-Copyright (c) 2010 Mihai Maruseac (mihai.maruseac@gmail.com)
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
-of the Software, and to permit persons to whom the Software is furnished to do
-so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
View
@@ -1,9 +0,0 @@
-.PHONY: all clean
-
-all:
- cd src && make
- mv src/hacoteb .
-
-clean:
- cd src && make clean
- rm -f *.hi *.o Main hacoteb
View
@@ -1,86 +0,0 @@
-END
-I am dissatisfied with the Wordpress.com code posting capabilities. All of the
-possible solutions (using the included <code> tag or the included [code]
-plug-in or posting the entire html generated from the code via vim's TOhtml or
-via highlight) were incomplete.
-END
-I wanted something which will allow me to write the post in a text file using
-some syntax (Creole, Markdown, my own) for markup and with the ability to
-introduce source code with a simple paste or some other markups. Afterward,
-the tool will convert the entire file to an HTML which will be used to enter
-the blog post into Wordpress blogs (right now, I don't care about other
-platforms).
-END
-For this purpose, I created HaCoTeB. Even if it is in his infancy, the project
-can be used to make simple posts like this one.
-END
-For example, the following code section lists the Main.hs file (yes, Ha from
-the name means Haskell) of the project.
-END
-[c]
-module Main where
-
-import HaCoTeB
-
-main = do
- s <- readFile "test"
- writeFile "test.html" $ representFileContent s
-END
-[t]
-Because this post is short, I intend to give below the entire source file used
-to generate it.
-END
-[co]
- END
- I am dissatisfied with the Wordpress.com code posting capabilities. All of the
- possible solutions (using the included <code> tag or the included [code]
- plug-in or posting the entire html generated from the code via vim's TOhtml or
- via highlight) were incomplete.
- END
- I wanted something which will allow me to write the post in a text file using
- some syntax (Creole, Markdown, my own) for markup and with the ability to
- introduce source code with a simple paste or some other markups. Afterward,
- the tool will convert the entire file to an HTML which will be used to enter
- the blog post into Wordpress blogs (right now, I don't care about other
- platforms).
- END
- For this purpose, I created HaCoTeB. Even if it is in his infancy, the project
- can be used to make simple posts like this one.
- END
- For example, the following code section lists the Main.hs file (yes, Ha from
- the name means Haskell) of the project.
- END
- [c]
- module Main where
-
- import HaCoTeB
-
- main = do
- s <- readFile "test"
- writeFile "test.html" $ representFileContent s
- END
- [t]
- Because this post is short, I intend to give below the entire source file used
- to generate it.
- END
- [co]
- END
- [tex]
- As you can see, the sections are divided by a separator (think multipart HTTP
- responses) and their type is given by the first line of the section (if of the
- form [..]) or is implicit. What is written in the brackets is any prefix of the
- proper type, allowing for lazy typing :).
- END
- That's all. I will come up with a new version in a few more days, one which
- will have the basic text parsing capabilities (including proper highlighting
- of links and text formatting like bold or alignment).
-END
-[tex]
-As you can see, the sections are divided by a separator (think multipart HTTP
-responses) and their type is given by the first line of the section (if of the
-form [..]) or is implicit. What is written in the brackets is any prefix of the
-proper type, allowing for lazy typing :).
-END
-That's all. I will come up with a new version in a few more days, one which
-will have the basic text parsing capabilities (including proper highlighting
-of links and text formatting like bold or alignment).

0 comments on commit 1f68a02

Please sign in to comment.