태터데스크 관리자

도움말
닫기
적용하기   첫페이지 만들기

태터데스크 메시지

저장하였습니다.

CVS/Subversion Resources

CVS 안내 (김민식, 박용주)  CVS의 개념, 사용법, 저장소 관리 방법 안내

1. 로그인
export CVSROOT=/home/cvs
cvs -d :pserver:vepcvs@mycvs.net:/backup/vepcvs/project login

2. 프로젝트 만들기
cvs import -m "메시지" 프로젝트이름 vender_tag release_tag
cvs -d :pserver:vepcvs@mycvs.net:/backup/vepcvs/project import -m "VEP Project" VEP vep start

3. 수정
cvs checkout(co) myprj
cvs commit -m "인사말 추가" Hello.java
cvs -d :pserver:vepcvs@mycvs.net:/backup/vepcvs/project commit -m"Framework Update" -R(Recursive Directory)
cvs update

4. 화일 추가와 삭제
cvs add Test.java
cvs commit -m "새 파일" Test.java

rm Test.java
cvs delete Test.java
cvs commmit -m "삭제" Test.java

5. 이력 조회
cvs diff driver.c > driver.c.diff
cvs log Hello.java

7. rsh/ssh로 CVS 접근하기
cvs -d :ext:minskim@mycvs.net:/home/cvs login

Subversion 사용 HOWTO
Subversion does the same thing CVS does (Concurrent Versioning System) but has major enhancements compared to CVS.

CVS와 비교한 Subversion의 장점들

  • 커밋 단위가 파일이 아니라 체인지셋이라는 점입니다. CVS에서라면 여러 개의 파일을 한꺼번에 커밋하더라도 각각의파일마다. 리비전이 따로 붙습니다. 반면 Subversion에서는 파일별 리비전이 없고 한번 커밋할 때마다 변경 사항별로리비전이 하나씩 증가합니다.
  • CVS에 비해 엄청나게 빠른 업데이트/브랜칭/태깅 시간.
  • CVS와 거의 동일한 사용법. CVS 사용자라면 누구나 어려움 없이 금방 배울 수 있습니다.
  • 파일 이름변경, 이동, 디렉토리 버전 관리도 지원.
  • 원자적(atomic) 커밋. CVS에서는 여러 파일을 커밋하다가 어느 한 파일에서 커밋이 실패했을 경우 앞의 파일만커밋이 적용되고 뒤의 파일들은 그대로 남아있게 됩니다. Subversion은 여러개의 파일을 커밋하더라도 커밋이 실패하면 모두이전 상태로 되돌아 갑니다.
  • 양방향 데이터 전송으로 네트워크 소통량(트래픽) 최소화.
  • 트리별, 파일별 접근 제어 리스트. 저장소 쓰기 접근을 가진 개발자라도 아무 소스나 수정하지 못하게 조절할 수 있습니다.
  • 저장소/프로젝트별 환경 설정 가능
  • 확장성을 염두에 둔 구조, 깔끔한 소스
사용예
svn co svn://www.xmlBlaster.org/xmlBlaster/trunk xmlBlaster
svn co http://www.xmlblaster.org/svn/trunk xmlBlaster

설치방법
svnadmin create release
svnserve -d -r /backup/svn -> 3690에 바인딩
vi svnserve.conf
vi passwd
svn mkdir svn://mycvs.net/release/leader
svnadmin create source
cp ../../release/conf/svnserve.conf .
cp ../../release/passwd .

svn import leader svn://mycvs.net/release/leader
cd leader
svn ci -m "Delete some comments" .bashrc

Microsoft Windows에서 사용하기

Microsoft Windows에서도 Subversion을 사용할 수 있습니다. 소스를 컴파일하지 않고 설치 파일을 통해
간단하게 설치해서 사용할 수 있습니다. Windows에서도 리눅스, 유닉스와 똑같은 기능을 사용할 수 있습니다.

GUI 클라이언트 프로그램

Subversion에서 기본적으로 지원하는 커맨드 라인 명령 svn은 사용하기에 불편한 점이 많습니다. 앞으로 소개할 것들은 MS Windows, X Window 등에서 사용 가능한 Subversion 클라이언트 프로그램 입니다.

Subclipse -  Eclipse Plugin

How to use Subversion with Eclipse
Update URL : http://subclipse.tigris.org/update_1.0.x

TortoiseSVN

MS Windows용 GUI 클라이언트 프로그램입니다. CVS GUI 클라이언트 프로그램으로 유명한 TortoiseCVS와 거의 같은 인터페이스를 가지고 있습니다.

http://tortoisesvn.tigris.org
download : http://easynews.dl.sourceforge.net/sourceforge/tortoisesvn/TortoiseSVN-1.4.0.7195-RC1-win32-svn-1.4.0RC1.msi

Ankhsvn

Visual Studio .NET 애드인 형식의 Subversion 클라이언트 프로그램입니다. VS.NET과 통합성이매우 높습니다. VS.NET의 솔루션 뷰에서 커밋, 업데이트 등의 작업이 가능하며 솔류션 뷰의 각 파일에 수정되었거나 수정되지않은 파일의 상태를 표시해줍니다.

http://ankhsvn.tigris.org

RapidSVN

크로스 플랫폼 Subversion 클라이언트 프로그램입니다. Windows, 리눅스, BSD의 X Window에서 사용할 수 있습니다.

http://rapidsvn.tigris.org

웹 인터페이스

저장소를 웹브라우저로 편하게 볼 수 있는 인터페이스들입니다.

ViewCVS

CVS 웹 인터페이스로 유명합니다. 아파치와 mod_python 기반으로 동작하며 Subversion 파이썬 바인딩으로만들어져 있습니다. 최신버전은 Subversion도 지원하고 있습니다. 유닉스, 리눅스, Windows 모두 사용할 수 있습니다.

http://sourceforge.net/projects/viewcvs

WebSVN

Subversion 전용 웹 인터페이스입니다. Subversion svnlook과 연동하여 웹으로 표시합니다. 아파치와 php가 필요합니다.

http://websvn.tigris.org

powered by performancing firefox

Posted by BlogZin


Leave a comment

MOM - xmlBlaster

MOM을 Java로 구현한 xmlBlaster가 감동을 주는군요. http://xmlblaster.org에서 필요한 자료만 추려 보았습니다. 성격이 급하신 분들은 Cool demosReplication Demo를 먼저 보시는 것도 좋은 접근이 되겠군요. XMLParser로 Xerces를 사용하기 때문에, C++ Client를 빌드하기 위해서는 xerces-c-src_2_7_0.tar.gz가 필요합니다.

XmlBlaster is MOM (Message oriented Middleware) with a lot of features.

XmlBlaster is a publish/subscribe and point to point 100% Java based MOM server (message-oriented middleware) which exchanges messages between publishers and subscribers. The message is described with XML-encoded meta information. Messages may contain everything, GIF images, Java objects, Python scripts, XML data, a word document, plain text - just anything.

Communication with the server is based on socket, CORBA (using JacORB), RMI, XmlRpc, HTTP or email, clients are free to choose their preferred protocol. Other protocols like SOAP may be plugged in.

Subscribers can use XPath expressions to filter the messages they wish to receive.

This is the publish/subscribe middleware server you have needed many times before, now available for free to glue together your distributed client/server application.

The xmlBlaster server is pure Java and under LGPL.
PHP, Perl, Python, C, C++, C#, Visual Basic.net, Flash, J2ME, Java (applications, servlets, applets) client samples are delivered in the xmlBlaster distribution.

You should be ready to go with your preferred development language.

XmlBlaster provides a browser callback framework, allowing browsers (Mozilla, MSIE, Netscape) to receive instant callbacks over a persistent http connection.

Features:

  • Free for private,commercial,education use (LGPL - License)
  • Message Orientated Middleware (MOM) with Publish/Subscribe and PointToPoint (PtP) support
  • Multi platform support (server is pure Java)
  • Multi protocol support (CORBA, RMI, XmlRpc, raw socket, EMAIL, native access)
  • Language neutral (clients for C++/C, Java, Python, PHP, Javascript, Perl, C#, Visual Basic.net ...)
  • Client side persistent queuing with C/C++/Java/ActiveX/Javascript
  • Extensible (XML based QoS)
  • Queryable Topics (Topic access with XPath)
  • Mime based full text search (currently plugins for regular expressions and XPath)
  • JMS conforming SQL key/value query support (SQL92)
  • Security system independend (currently plugins for LDAP and crypt-passwd), supports authentication, authorization and message interceptors
  • Persistence plugin architecture (currently plugins for Oracle, MS-SQLServer, Postgres, Firebird and others)

Wow! Tell me more!

Every Dad (Distributed application developer) needs a Mom (Message oriented middleware). Architecture
http://www.xmlblaster.org/architecture.jpg
Plugin overview

When a publisher sends a message toxmlBlaster it passes several plugins until it is rejected by a pluginor savely stored in the server.

When a subscriber subscribes on atopic, the message is passed with a callback to the subscriber,traversing several plugins before it is delivered.

The grafic below gives you an overviewof such a message flow. Please click on the plugin symbol to get moreinformation about the plugin and how to code and register a specificplugin yourself.

The grey plugins are mandatory, youneed to registered a plugin, otherwise a default plugin is chosen.

The green plugins are optional, theyare registered on startup. The mime plugins are activated dependingon the message mime type, the dispatch plugin is activated on demandby a client on login.

The brown plugins allow to control theclustering behavior, they are mandatory if clustering is switched on.

Administrative pluginsLogging pluginCluster supportDispatcher pluginCallback queue pluginMIME access filter pluginQueue/MsgStore pluginPublish pluginSecurity (authentication/authorization) pluginSecurity pluginProtocol pluginSecurity pluginProtocol plugin


Administrative pluginsLogging pluginCluster supportDispatcher pluginCallback queue pluginMIME access filter pluginQueue/MsgStore pluginPublish pluginSecurity (authentication/authorization) pluginSecurity pluginProtocol pluginSecurity pluginProtocol plugin
Fig:Message flow in the server (click on plugins for detailedinformation)


Client features

The following table shows on the columns different implementationlanguages for the clients and on the rows the different features aredisplayed. If a certain feature is already implemented, a green tickis written into the corresponding cell. In case the feature is notimplemented yet (or if the language does not allow this kind offeature) a red cross is drawn. For features under implementation agreen arrow is drawn.

Feature

Java

C++

C

Javascript
(Rhino)

Perl

Python

PHP

C#

Visual Basic
.net

Flash

protocol.corba



/

/



/


/

/

none

protocol.socket

/

/

/





/

/

none

protocol.xmlrpc

/


/



/


/

/

yes

protocol.rmi

/







/

/

none

client.browser.xmlrpc


/






/

/

none

failsafe reconnect

/







/

/

none

invocation recorder

/







/

/

none

callback update

/


/




yes

/

/

none

client cache

/



/

/

/

/

/

/

none

burst mode

/







/

/

none

protocol abstraction

/







/

/

none

synchroneous get

/


/





/

/

yes

publish/subscribe

/


/





/

/

yes

PtP / PtX

/


/





/

/

yes

client persistent queue

/



*

/

/

/

/

/

/

none

Performance

Message throughput per second

Publishing ten thousand small messages to xmlBlaster, which updates the messages to one subscribed client. The published and updated messages are acknowledged:

672 messages per second

on a AMD-K7 600 MHz, both client and server on the same machine running Linux 2.4.4 using JRockit 3.1 JVM with JacORB 1.3.30 CORBA lib.

The java virtual machine options are set to -Xms18M -Xmx32M:
   java -server -Xms18M -Xmx32M org.xmlBlaster.Main
   java -Xms18M -Xmx32M org.xmlBlaster.test.stress.LoadTestSub

The socket connections eat up most of the cpuload, thereafter XML parsing is expensive. The xmlBlaster code itself only consumes little of the processing time.

Green threads and native threads have more or less the same performance.

For other java virtual machines see the Volano Report.

When running the above test with different protocols, JacORB seems to beat the others:

Protocol Performance Comparison
Fig: Performance comparison of different protocols used in xmlBlaster, message throughput in percent to the winner.


Current state
Client
Pushing client callbacks on the same socket connection, allows to tunnel firewalls more ....
Client
more ...
Application

e.g. Application Logic

E-Mail
CORBA
RMI
HTTP
XmlRpc
SOCKET
SOAP
Native

Engine
Query
(XQL, SQL not scheduled)
Message Unit
  • Key
  • Content
  • QoS
Persistence (database)
Transaction
  • JINI Transactions
  • XA
  • OTS (Corba Transactions Service)
Cluster
  • Load balancing
  • Failover
  • Logical separation
Read requirement
MIME based plugins
QoS features
Authentication
  • Login
  • Logout
  • Certificate
See org.xmlBlaster.authentication.plugins
Authorization
  • ACL
See org.xmlBlaster.authentication.plugins
Remote Administration

XmlBlaster allows remote administration over a plugin framework.
Current plugins cover:
  1. JMX access
  2. telnet access
  3. An SNMP view on states and messages
  4. Message based remote administration

Mapping
RDBMS
Password plugin
LDAP plugin

 
Download
Full SVN snapshot: all sources, docs, libraries (big).

If you develop with xmlBlaster, checkout from subversion. This is the most current snapshot and usually as stable as the official releases.


http://www.xmlBlaster.org/xmlBlaster_REL_1_2.tgz 27 MB (26782285 Bytes)

http://www.xmlBlaster.org/xmlBlaster_REL_1_2.tar.bz2 26 MB (26003984 Bytes)

http://www.xmlBlaster.org/xmlBlaster_REL_1_2.zip 28 MB (28169871 Bytes)


Posted by BlogZin


Leave a comment

SIP Server from Flextronics Software Sys

SIP Server from Flextronics Software Systems for Next Generation Networks

SIP Server Framework is a powerful framework to build carrier-class reliable, scalable and feature-rich SIP applications. The FSS SSF comprises two components:

  • SIP Core Infrastructure Server
  • SIP Application Server

SIP Server Framework serves as a base for Proxy as well as any other SIP-based server entity. SSF therefore, radically reduces time-to-market by providing a hassle-free infrastructure that:

  • Implements all the core SIP functionality including state information automatically.
  • Provides a carrier class framework that easily allows new components to be added in and out dynamically as well as statically.

The SIP-SF is a powerful yet flexible solution. It provides tested and standards compliant core SIP functionalities like Call State Control Function (CSCF), Proxy, Registrar, Redirect, B2BUA, and Location Server. More importantly the framework allows application developers to build upon these core functionalities and deliver niche applications. The framework isolates the application developer from all SIP specific protocol and behavioral details. The application developer can focus on what services to provide and the framework can take care of how. FSS' carrier class, proven, interoperable solution thus helps the customers in reducing time and development costs. The FSS solution, one of the most proven and mature products in the industry, handles live traffic for the largest Service Providers' network and for one of the largest Internet Telephony Service Provider (ITSP) Network in Japan.

FSS (formerly HSS)has also introduced Centrex functionalities in its SIP-SF. The Centrex feature enables Equipment Manufacturers to build a hosted PBX solution in minimal time. The FSS SIP Server Framework with Centrex functionality is a powerful framework with a sophisticated dial plan, a hunt group, privileged profiling and intranet/extranet calling.

SIP-SF Architecture

FSS' award winning SIP Server Framework (SIP-SF) ("Internet Telephony" Product of the Year 2002 and "Communications Solutions" Product of the Year 2003) is an ideal platform for hosting SIP services. SIP-SF is a ready-to-deploy SIP Proxy, Registrar, Redirect, Presence and Location Server. FSS’ SIP-SF today provides several advanced features, including SIP Centrex (Hosted PBX) and Per-User Call Processing Language, all of which render tremendous value in using it as an underlying platform to build new services while significantly reducing time, risk, and cost to market. The SIP-SF is a ready-to-deploy platform with Virtual IP redundancy, SIP Load Balancing, SNMP Manageability, Congestion Control, Emergency Calling, and other real-life network requirements already addressed.

Targeted at OEMs, SIP-SF has been developed keeping in mind the flexibility and extensibility that OEMs so much need to be able to offer differentiated products to the market.

FSS' SIP server is a dual play architecture, positioned as both Core Infrastructure and Application Development Framework.


Click to enlarge
Click to enlarge
SIP-SF Core Infrastructure Element
OSA Application Server

FSS’ SIP Server can be positioned both as the SIP core infrastructure element to build basic infrastructure needed in a SIP Network or using its B2BUA feature set, as well as an application infrastructure to build applications, such as Collaboration, CTI, and Gaming. The SIP-SF thus enables one to easily integrate multiple call models, be it BCSM-based or RFC 3261, and to use any one of them depending on the kind of service being executed. Further, the SIP-SF can be made to interact with an SCN using a regular BCSM-based model and at the same time, perform forking functionality of proxy using the regular 3261 UAC/UAS model.


SIP-SF Features

Salient Features

  • Ready-to-deploy SIP Proxy, Registrar, and Redirect Server
  • Value-added features including SIP Centrex, Call Processing Language, and Presence Server
  • Integrated load balancing and high availability platform
  • Multi operating system portability
  • Easy management - SNMP, API, XML
  • Multiple database support - ODBC
  • Supports both IPv4 and IPv6.
  • TLS security and digest authentication
  • Support for emergency calls and priority routing
  • Implemented in C++ to offer complete object-oriented interface
  • Configuration through Number Translation Mark up Language (NTML)


Architectural Superiority
The key architectural features of the SIP Server Framework are:

  • High scalability - performance increases with increase in number of CPUs
  • Can support multiple CSMs (service logic) simultaneously
  • Support for user-defined service logic
  • Component-based architecture- can chain components as desired for future enhancements
  • Supports distributed operation across various nodes
  • Centralized configuration of all components
  • Message-based interfaces
  • Threaded model-thread pool management
  • Easy integration with third party modules- all functional modules implemented over APIs
  • Compliant to ISO C++ and EC++ standards to ensure maximum portability


Key Standards Compliance

  • 'SIP: Session Initiation Protocol', RFC 3261
  • 'HTTP Authentication: Basic and Digest Access Authentication', RFC 2617
  • Session Initiation Protocol (SIP): Locating SIP Servers', RFC 3263
  • 'CPL: A Language for User Control of Internet Telephony Services', draft-ietf-iptel-cpl-06
  • 'URLs for Telephone Calls', RFC 2806
  • 'Management Information Base for Session Initiation Protocol', draft-ietf-sip-mib-04.txt

SIP Application Server Features

The SIP Application Server (B2BUA) provides a scalable, reliable, andfeature-rich environment for rapid service creation. FSS' B2BUA Serveris a framework that exposes a set of well-defined APIs to theapplication to develop various services, such as Prepaid, NatTraversal, Call Queuing, Click-to-Dial, and Call Pick-Up. These APIs aswell as their parameters are Open Service Architecture (OSA)-compliant.In addition, FSS' B2BUA Framework also supports additional APIs tocreate innovative applications.


Salient Features

  • RFC-compliant: RFC 3261-compliant B2BUA
  • Scalability: Highly scalable feature distribution
  • Availability: Reliable high availability support
  • Comprehensive support: Support for multi-party, multimedia call control
  • Flexible: Provides the applications complete access to SIP messages
  • Multiple deployment options: Single node or multi node deployment
  • SIP Interface to proxy/media servers
  • Multi operating system portability

Architectural Features

  • High availability APIs to allow the applications back up serialized critical data and reconstruct the state based on critical data
  • APIs to send SUBSCRIBE, NOTIFY, MESSAGE, and proprietary SIP messages in order to facilitate development of presence-based applications and chat applications
  • APIs to move call-legs from one call to another in order to facilitate development of applications, such as Call Pick-Up
  • In-built Load Monitor to protect against overload conditions
  • Event criteria filtering mechanisms

Key Standards Compliance

SIP Protocol Compliance

  • 'SIP: Session Initiation Protocol', RFC 3261, June 2002, Rosenberg et al.
  • Session Description Protocol, RFC 2327
  • An Offer/Answer Model with the Session Description Protocol (SDP), RFC 3264, June 2002
  • Reliability of Provisional Responses in the Session Initiation Protocol (SIP), RFC 3262, June 2002
  • SIP INFO Method, RFC 2976, October 2000

Open Service Access (OSA) Compliance

  • 3GPP TS 29.198-04-3-600 OSA API Part4-SubPart3-MPCC SCF
  • 3GPP TS 29.198-04-3-600 OSA API Part4-SubPart4-MMCC SCF
  • 3GPP TS 29.998-04-4-500 Part4-SubPart4-MPCC ISC

'Software' 카테고리의 다른 글

CVS/Subversion Resources  (0) 2006.08.31
MOM - xmlBlaster  (0) 2006.08.30
SIP Server from Flextronics Software Sys  (0) 2006.08.26
The Softswitch Framework solution from Flextronics Software Systems (FSS)  (0) 2006.08.25
PDF2HTML download and review  (0) 2006.08.24
태터의 이미지 처리  (0) 2006.07.03

Posted by BlogZin


Leave a comment
Softswitch solutions for CLASS 4 and CLASS 5 services from Flextronics Software Systems

FSS' Softswitch Framework

FSS' Softswitch conforms to TIPHON distributed gateway architecture. Softswitch solution from FSS supports a wide variety of signaling protocols, like SS7, R1/R2 and ISDN and has a potential to incorporate GR-303 and V5.2. FSS Softswitch can control media remotely through MEGACO and MGCP.


Softswitch Framework Context in System



Softswitch Configuration

The design of FSS' Softswitch enables easy deployment in the network. FSS Softswitch provides the flexibility to configure all external network elements like Gatekeeper, Media Gateway, Signaling Gateway, Application Server, etc. Policies can be configured by customizing Routing, Service Control and Address Translation. Further, product related configurations for initialization, provisioning and redundancy are available through open APIs.


Softswitch Service Architecture

  • Services targeted – address translation, routing, IVR, Charging, Emergency, Network based, third party call handling, web based
  • Service Interface provides support for – CLASS services/supplementary services, IN services, SIP based
  • Architecture independent of signaling, but support for SIP, H.323, SS7, ISDN, R2, POTS ensured

FSS' Softswitch Framework : Functions

The FSS Softswitch is offered both as a product and a software framework with source license. FSS has already integrated the Softswitch into different product architectures and offers its services in integrating and porting the Softswitch solution onto the target.

Services

  • Low-level call management APIs for INAP interfaces
  • High-level call management APIs for Parlay adapter
  • SIP interface to Application server
  • CLASS services hosted natively
  • Legacy and Enhanced services supported


Softswitch Framework Functional Block


Interworking Call Control

  • IN CS2 – AIN 0.3 BCSM based call control
  • Signaling Adaptations Supporting diverse SCN and packet protocols
  • Enables easy integration of new signaling protocols

PSTN Interfaces

  • SS7 termination (ANSI or ITU-T) either through external SG or direct
  • Dual-seizure, reset, group blocking/unblocking supported
  • Supports third-party pause and re-routing
  • CAS R1/R2 supported on PSTN & H.323 v2 on packet network
  • ISDN Q.931 interface supported

Packet Interfaces

  • H.323 subscriber and trunk interface
  • SIP subscriber and SIP-T trunk interface
  • MGCP (RFC 2705) gateway interface
  • MEGACO/H.248 gateway interface

Bearer Control

  • H.248/MGCP based Gateway Control
  • Ability to manage multiple transactions
  • Enabling media control for packet-TDM inter-working
  • Ability to manage various gateway types (Access, Trunking and Residential)


Resource Management

  • Route Information maintained
  • SCN and PDN terminations and associated data maintained
  • Resource allocation, de-allocation and maintenance
  • Local and External Address Translations supported
  • Single point routing and distribution of messages to multiple MGs

powered by performancing firefox

Posted by BlogZin


Leave a comment

PDF2HTML download and review

PDF2HTML download and review - convert PDF to HTML from SnapFiles

Pdftohtml is a command-line tool that translates .pdf documents into html format. It offers several parameters, including options to create output with or without using HTML frames,ignore or include images, translate internal pdf links and more.

PDF to HTML - convert Adobe PDF document into html file with pdf to html converter
PDF2HTML (PDF to HTML) software product converts PDF files to HTML files while seeking to preserve the original page layout (as best as technically possible). PDF2HTML enables the conversion of layout originally designed for paper to be used on the Internet.
PDF2HTML (PDF to HTML) software is a standalone program and does not require Adobe Acrobat, or even Acrobat Reader.

Archisoft PDF2HTML - Pdf2html, PDF to HTML software converter
Pdf formatted documents are one of the most widely used electronic document formats on the internet and CD-ROM. Their advantage is that they can faithfully preserve the layout and appearance of the original in a ready-to-print format. They can only be searched however once the user opens them.
HTML files have the advantage of being able to be read by anyone with a web browser and can be found and searched by any major internet search engine. Use HTML to reach a wide audience.

powered by performancing firefox

Posted by BlogZin


Leave a comment

태터의 이미지 처리

태터에서 사진을 올려보면 현재 버젼의 버그가 있군요. 좌/우 정렬로 사진을 본문에 붙이는 것은 태그처리를 제대로 하지 못해 사진 아랫부분으로 갈려면 엔터를 계속 쳐야 합니다.

작은 사진을 첨부하면 원본 그대로 포스트에서 보여줍니다.


태터에서 큰 사진을 포스트에 붙일 경우에 치리님의 Lightbox TT EX 플러그인은 큰 효과를 발휘합니다. 아래 큰그림에서 사진을 클릭해 보면 놀랍니다.

Posted by BlogZin


Leave a comment

BlogZin.Net에 사용된 태터 플러그인

태터 업그레이드 0.951 -> 1.0.6를 하고, 은빛기타님의 [TT1.0]기본 + mp3플레이어를 좀 수정해서 스킨을 입혔으니, 이제 사용할 만한 플러그인을 설치한다. BlogZin.Net에 사용된 플러그인은 아래와 같습니다.
  1. RSSNews는 Ajax로 제작된 RSS Reader인데, 태터의 RSS Reader의 RSSNews 카테고리에 수집된 글의 목록을 태터 메뉴에 표시해 주는 역할을 한다.
  2. Tattertools on Wikipedia는 포스트의 내용중에 wp 태그가 있으면, 해당 단어를 [wp]위키피디아[/wp] 백과사전의 해당 페이지로의 링크를 자동으로 만들어준다.
  3. Statistics Graph는 접속 통계를 그래프로 그려준다.
플러그인 제작하신 inureyes, GemSiN, 페릿님께 고마운 마음을 전합니다. 그래서 아래와 같이 깔끔한 모양이 되었군요.


이제부터 잠시동안 태터1.0의 자세한 해부를 해 봐야겠습니다.

Posted by BlogZin


Comments List

  1. Favicon of http://www.gemsin.pe.kr/ BlogIcon GemSiN 2006.07.04 01:45 # M/D Reply Permalink

    제꺼 쓰는 사람이 있긴 있군요.-_-;

Leave a comment

Flash Control의 인터페이스

플래시 OCX의 인터페이스인 FSCommand, SetValue를 이용하여, 플래시를 윈도즈 어플리케이션에서 직접 사용할 수 있다.

flash2app.PNG 

Posted by BlogZin


Leave a comment

Calendar

«   2019/11   »
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30

Site Stats

Total hits:
138,060
Today:
0
Yesterday:
0