Projects

obsessivecomp

ObsessiveCompulsive is a tool intended to combine multi-step task documentation with an onscreen visual prompting aid. As a programmer, I try to automate as much as possible via scripts, but some things simply have to be done by hand. For example, issuing a release for me is currently a 23-step ... [More] process, combining many automated subtasks with other manual steps and verifications. I previously used a paper printout of the release procedure as my reference. The problem was that I tended to skip steps, due to running releases (on several concurrent projects) as often as every few days, and of course being in a hurry. ObsessiveCompulsive solves that problem in a rather unobtrusive way. Here are the features that keep me using it regularly: - Uses ASCII source file format - Create a *.steps file and double-click it to start the process; a steps file is basically a sequence of text lines with optional whitespace between them. - The step prompting window is small, shown semi-transparently on the edge of the screen, and is easily moved. - Steps files are intended to also function as documentation; since they are actually used by the programmer, they remain 'in your face' and will likely be kept up to date. - Encourages creating lots of documentation in steps format, which other programmers can follow. - Text can wrap and contain additional lines of explanations and notes (which are tab or space indented), and the prompting window expands as necessary to show all of it. - Links embedded in the text are clickable, e.g. http://localhost/test or file://c|/dev/whatever.bat . I use this to launch automated scripts, reference documents, source files, etc. Try it out! Hopefully you will like it as much as I do, and/or offer a suggestion to improve it. To install, you can just download the latest source and run the setup program in the Output folder, which is built with InnoSetup and automatically creates the *.steps file association. Then create some *.steps files and double-click on one to try it out. Currently if you just run the executable by itself, the program crashes. Sorry, it's just not meant to be run that way! ... OK, I'll fix it one of these days. [Less]

sap-mrp-simulator

Custom SAP MRP Simulator that allows running MRP simulation for different demands and inventory levels without changing them in SAP

publisheddoclet

PublishedDoclet is a Javadoc Doclet/Taglet pair that allows hiding and publishing of selected parts of a Javadoc API. It is useful to hide non-public parts of an API. This is actually pretty stable right now, though still missing a number of features that I want to implement. Also docs are ... [More] missing... :-) Take a look at the Readme to get an idea where this is headed. I am planning a release RSN, until then, just pull the source from SVN. [Less]

vim-ko

Vim의 구성요소들을 한글로 번역하고 유지보수하기 위한 공간입니다. 사용설명서 및 상세설명서 Vim 프로그램 메시지 및 GUI 메뉴 항목 Vim을 따라다니는 명령들의 manpage들 Vim 자습서인 vimtutor We create & maintain Korean translations ... [More] of the following parts of Vim: User & Reference Manual Program messages & labels of the GUI menu Manpages of commands distributed along with Vim The Vim tutorial file: vimtutor [Less]

mydbdoc

A command line tool to create professional documentation from MySQL schema.

jsigner

JsignerJsigner provides an easy way to automatically draw classes diagram, based on annotations on the source code. Features: Divide your domain in multiple diagrams You can decide which class will be in which diagram. Configure the diagram generation omitting unwanted methods/attributes ... [More] Diagrams can be generated by Jsigner maven plugin. PurposeThe main purpose of this project is to provide an easy tool for drawing and keeping the class diagrams of your projects up to date. The reason for that is simple...when starting the development of a task, Its common to have a high level vision of the classes... and then... Hands on! The development evolves the model, and at the end of a task, the model is not the same, so we spend time updating the diagrams by doing reverse engineering or manually. I don't want to do this anymore! But How?Its quite simple, you just use the @Domain annotation on the classes that you want to be in a the diagram, specifying the diagram name (or names, if the class will appear in multiple diagrams). See the User Guide and examples wiki pages. What it looks likeHere is an example of an image generated by jsigner. Thanks toJsigner is based on MODSL, so thanks to the project and its team. [Less]

xcode-tokens-from-qtdocs

Qt API Documentation in XCodexcode-tokens-from-qtdocs Qt Documentation -> AppleRef Tokens.xml generatora python script to parse Trolltech's Qt HTML Documentation for tokens to be used in Xcode ContextFor developing Qt (Nokia's / Trolltech's cross platform C++ application ... [More] framework) on a Mac, there are some useful tools, like qmake, which can help you to generate an Xcode project through this command:% qmake -spec macx-xcode Also the Qt Frameworks installs itself nicely in the system, so Xcode can easily compile your Qt project and can even do the code-completion for you. However, the integrated documentation services in Xcode are not so easily supported right out of the box. And as a avid Mac developer and Xcode user, I missed those features severely, trying to develop Qt on my machine. Why the Tokens.xmlI searched the web and found this nice How To integrated the Qt documentation in Xcode 3.0. One thing was still missing though: API search. With the help of Yan Shapochnik's explanation you get a full text search to the Qt docs from within Xcode. But even more useful is Xcode's API documentation service. E.g. API search allows you option-click on a term in the code editor and directly open the documentation about that class or method in the Documentation window. To get the API search integrated in Xcode, it needs a Tokens.xml file. Basically this file lists all the API terms (tokens), that can be looked up, and describes some context about the token: whether it's a class or a function; what's its scope etc etc. Such a Tokens.xml file doesn't exits for Qt's Documentation, so we'll have to make one. I found parsing every Qt html doc page for classes, methods, functions and other terms much to difficult and too much work. So I whipped together a very simple python script which just does some of it. So the resulting Tokens.xml file is not perfect and all-containing, but at least it gets us somewhere halfway. And I think it will cover for 80% of all the terms you want to look up in your code. How to use thisIf you are using Qt 4.4.1, as I am, you can just copy my Tokens.xml file from the svn into the same location as the Nodes.xml file from Yan's tutorial and run docsetutil. If you have an other version of Qt, you'll need to make the python script run on your own machine. For this you'll have to: copy the functions.html and the classes.html file from the documentation into your working folder clean them up quit a bit until treeElement can parse them correctly (remove the headers and footers, make a clear root node, remove the  s from the html ...). E.g. my functions.html looks like this: DTDHandler: QXmlReader ... run the python script until there are not too many errors and unprocessable stuff left copy the resulting Tokens.xml to the ~/Library/Developer/Shared/Documentation/DocSets/com.trolltech.qt.4.4.1.docset/Contents/Resources folder. and run /Developer/usr/bin/docsetutil index com.trolltech.qt.4.4.1.docset ConclusionThis docsetutil tool finds 13467 tokens (and ignores 114), on my version. I found this enough for my needs. I know this python code is one big hack. And the code is very ugly indeed. But I found it useful enough to not only put the resulting Tokens.xml file here, but also the python script to generate that file yourself. [Less]

fidoip

Fidoip contain shell scripts, sources and binaries which automatically compile, install FIDO software(Binkd, Hisky HPT and Golded), create directories, setup configuration files and script on FreeBSD, Linux, Windows and DragonFly BSD.

rapidoc

RAPIDocRAPIDoc is a controller generator for your Rails Restful API. It generates a API controller, by simply invoking... ./generate It parses the controllers you specify, and generates a ApiController with appropriate views for it. This makes it very easy to document your Rest API. For methods you ... [More] use, and according to ERB templates it generates the view for you. EXAMPLE Class documentation=begin apidoc name:: /projects json:: xml:: This resource can be used to show edit and list projects. A project is a one floorplanner. A project has multiple floors, which can contain multiple designs. =endEXAMPLE Method documentation=begin apidoc url:: /projects method:: GET access:: FREE return:: [JSON|XML] - some project param:: page:int - the page param:: per_page:int - max items per page Get a list of projects. This method uses pagination. If you want to retreive project 1-10 for example: /projects?page=1&per_page=10. =endFor more information: http://www.suite75.net/blog/dev/rapidoc-rails-rest-api-documentation-generation-well-just-rapidoc.html [Less]

my-first-attempt

The project's summaryThis is my first project, which I hope will help me use Google Code SVN. --Jar I've posted my dummy text file here to help Jar make some deal with RCS systems. --Oleg Useful SVN resourceshttp://subversion.tigris.org/ http://svnbook.red-bean.com/ Basic SVN ... [More] commandsMost commonly used SVN commands are: svn help svn checkout svn commit svn status svn info svn diff svn log svn ls svn import svn copy svn merge svn revert Our Wiki linkshttp://code.google.com/p/my-first-attempt/wiki/BasicWorkCycle http://code.google.com/p/my-first-attempt/wiki/ExaminingHistory [Less]