CushionTheBlow (구 BluemoonSoft)

VMware에서 빠져나오기 위해서는 Ctrl + Alt 키를 눌러주면 된다.

다음 사이트가 공식 사이트이다.

http://m2eclipse.codehaus.org/

이 사이트에서 다음 링크를 사용해서 설치하면,

필자와 같은 곤란한 상황에 직면할 수 있다.

http://m2eclipse.sonatype.org/update/

설치 에러는 다음과 같다.

Cannot complete the request.  See the details.
Unsatisfied dependency: [org.maven.ide.eclipse.editor.feature.feature.group 0.9.6.20080905-0917] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.draw2d/[3.4.0.v20080529,3.4.0.v20080529]
Cannot find a solution where both Match[requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.jdt.feature.jar/[3.4.0.v20080603-2000-7o7tEAXEFpPqqoXxgaBhhhq,3.4.0.v20080603-2000-7o7tEAXEFpPqqoXxgaBhhhq]] and Match[requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.jdt.feature.jar/[3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97,3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97]] can be satisfied.
Cannot find a solution where both Match[requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.0.v3448f,3.4.0.v3448f]] and Match[requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.1.v3449c,3.4.1.v3449c]] can be satisfied.
.....

이 장황하고도 긴 메시지에 당황하기 쉽다.

링크를 바꾸어서 다음 링크를 사용하여 설치를 시도하였더니 문제없이 설치할 수 있었다.

http://m2eclipse.sonatype.org/update-dev/

이유는??

모르겠다.. 알면 커멘트 부탁 :-)

Maven is a software tool for Java project management and build automation created by Sonatype's Jason van Zyl in 2002. It is similar in functionality to the Apache Ant tool (and to a lesser extent, PHP's PEAR and Perl's CPAN), but has a simpler build configuration model, based on an XML format. Maven is hosted by the Apache Software Foundation, where it was formerly part of the Jakarta Project.

Maven uses a construct known as a Project Object Model (POM) to describe the software project being built, its dependencies on other external modules and components, and the build order. It comes with pre-defined targets for performing certain well defined tasks such as compilation of code and its packaging.

A key feature of Maven is that it is network-ready. The core engine can dynamically download plug-ins from a repository, the same repository that provides access to many versions of different Open Source Java projects, from Apache and other organisations and developers. This repository and its reorganized successor, the Maven 2 repository, strives to be the de facto distribution mechanism for Java applications, but its adoption has been slow. Maven provides built in support not just for retrieving files from this repository, but to upload artifacts at the end of the build. A local cache of downloaded artifacts acts as the primary means of synchronizing the output of projects on a local system.

Maven is built using a plugin-based architecture that allows it to make use of any application controllable through standard input. Theoretically, this would allow anyone to write plugins to interface with build tools (compilers, unit test tools, etc.) for any other language. In reality, support and use for languages other than Java has been minimal. Currently a plugin for the .Net framework exists and is maintained [1], and a C/C++ native plugin was at one time maintained for Maven 1.[

Reference:
http://en.wikipedia.org/wiki/Apache_Maven

The Graphical Editing Framework (GEF) allows developers to create a rich graphical editor from an existing application model. GEF consists of 2 plug-ins. The org.eclipse.draw2d plug-in provides a layout and rendering toolkit for displaying graphics. The developer can then take advantage of the many common operations provided in GEF and/or extend them for the specific domain. GEF employs an MVC (model-view-controller) architecture which enables simple changes to be applied to the model from the view.

GEF is completely application neutral and provides the groundwork to build almost any application, including but not limited to: activity diagrams, GUI builders, class diagram editors, state machines, and even WYSIWYG text editors.

Reference:
http://www.eclipse.org/gef/overview.html

The Project Object Model (POM) is the central construct of the Apache Maven build management system. In Maven, it is represented by an XML file which contains general information about the project and configuration details, which are used by Maven to build the project. Some of the configuration that can be specified in the POM-file are project dependencies, plugins or goals that can be executed, the build profiles, and so on.

Reference:
http://en.wikipedia.org/wiki/Project_Object_Model

jkl을 입력하니 123이라는 숫자가 나온다.

Fn 키를 눌러줘야 나왔던 녀석들이 갑자기 튀어나오니

Fn 키에 뭘 올려놓고 쓸 수도 없고 당황스러웠다.

문제는 Num Lk에 있었다.

습관 상 데스크탑에서도 Num Lk을 쓰지 않았는데

나도 모르게 활성화되어 당혹스런 상황이 연출되었던 것.

필자가 사용하는 LG XNOTE의 경우에는

Fn + Scr Lk으로 Num Lk을 해제하거나 활성화시킬 수 있다.

무식하면 결국 몸이 고생.

The Revision Control System (RCS) is a software implementation of revision control that automates the storing, retrieval, logging, identification, and merging of revisions. RCS is useful for text that is revised frequently, for example programs, documentation, procedural graphics, papers, and form letters. RCS is also capable of handling binary files, though with reduced efficiency and efficacy. Revisions are stored with the aid of the diff utility.

RCS was initially developed in the 1980s by Walter F. Tichy while he was at Purdue University as a free and more evolved alternative to the then-popular Source Code Control System (SCCS). It is now part of the GNU Project but is still maintained by Purdue University.

RCS operates only on single files, has no way of working with an entire project. Although it provides branching for individual files, the version syntax is cumbersome. Instead of using branches, many teams just use the built-in locking mechanism and work on a single head branch.

A simple system called CVS was developed capable of dealing with RCS files en masse, and this was the next natural step of evolution of this concept, as it “transcends but includes” elements of its predecessor. CVS was originally a set of scripts which used RCS programs to manage the files. It no longer does that, rather it operates directly on the files itself.

A later higher-level system PRCS uses RCS-like files but was never simply a wrapper. In contrast to CVS, PRCS improves the delta compression of the RCS files using Xdelta.

In single-user scenarios, such as server configuration files or automation scripts, RCS may still be the preferred revision control tool as it is simple and no central repository needs to be accessible for it to save revisions. This makes it a more reliable tool when the system is in dire maintenance conditions. Additionally, the saved backup files are easily visible to the administration so the operation is straightforward. However, there are no built-in tamper protection mechanisms (that is, users who can use the RCS tools to version a file also, by design, are able to directly manipulate the corresponding version control file) and this is leading some security conscious administrators to consider client/server version control systems that restrict users' ability to alter the version control files.

Some wiki engines, including TWiki, use RCS for storing page revisions.

Reference:
http://en.wikipedia.org/wiki/Revision_Control_System

http://staruml.sourceforge.net/ko/
이 유명하댄다. 한글 페이지도 있네.

nsclass 도 좋다던데,
nsclass는 c#, java만 지원한다고 한 거 같다.

A first-generation programming language is a machine-level programming language.

Originally, no translator was used to compile or assemble the first-generation language. The first-generation programming instructions were entered through the front panel switches of the computer system.

The main benefit of programming in a first-generation programming language is that the code a user writes can run very fast and efficiently, since it is directly executed by the CPU. However, machine language is somewhat more difficult to learn than higher generational programming languages, and it is far more difficult to edit if errors occur. In addition, if instructions need to be added into memory at some location, then all the instructions after the insertion point need to be moved down to make room in memory to accommodate the new instructions. Doing so on a front panel with switches can be very difficult. Furthermore, portability is significantly reduced - in order to transfer code to a different computer it needs to be completely rewritten since the machine language for one computer could be significantly different from another computer. Architectural considerations make portability difficult too. For example, the number of registers on one CPU architecture could differ from those of another.

Reference:
http://en.wikipedia.org/wiki/First-generation_programming_language

Second-generation programming language is a generational way to categorize assembly languages.

- The term was coined to provide a distinction from higher level third-generation programming languages (3GL) such as COBOL and earlier machine code languages.
- The code can be read and written by a programmer. To run on a computer it must be converted into a machine readable form, a process called assembly.
- The language is specific to a particular processor family and environment. Second-generation languages are sometimes used in kernels and device drivers (though C is generally employed for this in modern kernels), but more often find use in extremely intensive processing such as games, video editing, graphic manipulation/rendering.
- One method for creating such code is by allowing a compiler to generate a machine-optimized assembly language version of a particular function. This code is then hand-tuned, gaining both the brute-force insight of the machine optimizing algorithm and the intuitive abilities of the human optimizer.

Reference:
http://en.wikipedia.org/wiki/Second-generation_programming_language