Be the first to post a text review of Technical Library Template Interface. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Decision: Project is to be Orphaned

  I have decided to commit my final libTekLTI works to SF.net's CVS space that it allocated for libTekLTI. I also authorized the SF.net team to remove me from the 'libteklti' and 'teklang' projects, essentially orphaning them both. For fifteen years, I had interest in film creation. libTekLTI is a library that would take years to complete, along with TekLang, a task I no longer wish to devote a large chunk of my lifetime to. I hope some one else will be willing to pick up the tabs on libTekLTI some time in the future, as it's a library and new programming language that has the capability to help those Visual Basic programmers get out of the Micro$oft code. It's now time for me to move on to my new 'stick2xyz' utility program.

  posted by garitaiya 810 days ago

• Code committed

  garitaiya committed patchset 76 of module libteklti to the Technical Library Template Interface CVS repository, changing 1 files

  posted by garitaiya 810 days ago

• Code committed

  garitaiya committed patchset 75 of module libteklti to the Technical Library Template Interface CVS repository, changing 177 files

  posted by garitaiya 810 days ago

• Project Orphaning Under Consideration

  My recent desire on creating a professional-like film shifted me into putting my programming efforts onto my new "Stick Figure/Viewer" project. This puts me into a position where I need to consider orphaning the libTekLTI and TekLang projects. The assembly code I've written for those projects is the factor that is delaying my decision. If any one wants to take over those projects, interested parties should use SF.net's project takeover procedure. Project UNIX names are 'libteklti' and 'teklang', and more than likely, I will orphan the two projects. The Stick Figure Viewer/Converter project's SF.net URL is: http://sourceforge.net/projects/stick2xyz

  posted by garitaiya 811 days ago

• Project Status - February 11, 2007

  The Technical Library Template Interface is a library capable of providing standardized interfaces in Creative Commons EAL-4 standards to the open source community. These standards include an open source alternative to the Access Control List (ACL) ideas found in proprietary operating systems and/or programs. As we all know, the project has gone through a lot of major changes. The teklti namespace was created, the documentation was changed to suit the doxygen standards, and most problems in the build tree has been cleaned out. After finally going through the major overhauls, here's the new milestone for the project: 1. Implement teklti::Std (completed) 2. Implement teklti::File interfaces (in progress) 3. Implement Config interfaces 4. Implement Data Compression interfaces 5. Implement Database interfaces 6. Implement Technical Standard Interface Protocol 7. Draft RFC for the Technical Standard Interface Protocol 8. Make all changes that will allow libTekLTI to be EAL-4 compliant. 9. Finalize all documentation 10. Make a final release of libTekLTI-1.0.

  posted by garitaiya 1002 days ago

• Source File Overhaul adds New Namespace

  The Technical Library Template Interface is a library capable of providing standardized interfaces in Creative Commons EAL-4 standards to the open source community. These standards include an open source alternative to the Access Control List (ACL) ideas found in proprietary operating systems and/or programs. A recent overhaul of the libTekLTI source code has created a new namespace: teklti. The Standard Template Library documentation inspired me to make such a change. All the libTekLTI interfaces have been moved into the teklti namespace with the 'Tek' prefix removed from the names. Although code utilizing libTekLTI <= 1.0pre6 will require a recompile to run on libTekLTI-1.0pre7, there should not be a need to change code due to typedefs in the headers that allow for backward compatibility. All the structs and global functions will continue to remain in the global namespace however, due to the need to support ordinary "C" code that utilizes libTekLTI. The Technical Library Template Interface project is still in need of help from those who understand the concept of Access Control Lists (ACLs) that would conform to the Creative Commons EAL-4 standards. libTekLTI will be programmed to use the operating system's ACL system whenever possible. In cases like Linux, the ACL system will be overlayed over the existing file system since it is not possible to add a EAL-4 conforming system to the kernel without a massive re-write. Developers who provide actual contributions to libTekLTI will be added to the project and be given access to Planet Saphire's CVS repository. Any contribution that is relevant enough to the project will be accepted, ACL contributions in particular.

  posted by garitaiya 1002 days ago

• Documentation and Build System Overhaul Complete

  The Technical Library Template Interface is a library capable of providing standardized interfaces in Creative Commons EAL-4 standards to the open source community. These standards include an open source alternative to the Access Control List (ACL) ideas found in proprietary operating systems and/or programs. The documentation and build system of the Technical Library Template Interface (libTekLTI) has undergone a major overhaul. libuuid, a critical dependency of libTekLTI, has been imported to CVS and will be available in the next release, libteklti-1.0pre7. I also hope to create the new release within the next few months. Additionally, the Technical Library Template Interface project needs help from those who understand the concept of Access Control Lists (ACLs) that would conform to the Creative Commons EAL-4 standards. libTekLTI will be programmed to use the operating system's ACL system whenever possible. In cases like Linux, the ACL system will be overlayed over the existing file system since it is not possible to add a EAL-4 conforming system to the kernel without a massive re-write. Developers who provide actual contributions to libTekLTI will be added to the project and be given access to Planet Saphire's CVS repository. Any contribution that is relevant enough to the project will be accepted, ACL contributions in particular.

  posted by garitaiya 1022 days ago

• libTekLTI Development Resumed

  I have decided to resume development of the libTekLTI project. I have also decided to add shell script support as well as an Access Control List (ACL) platform. These changes have shifted the focus of the project: it is not only going to support a new language, it is going to be an aim to make a truly free open source EAL-4 security subsystem within Linux. Development toward the EAL-4 standard will start with the creation of a shell. For those not familiar with the EAL security levels, EAL stands for Evaluation Assurance Level, a term used in the Common Criteria certification. Levels 1-7 are available, with 4 being common for operating systems. EAL-4 permits a developer to gain maximum assurance from positive security engineering based on good commercial development practices which, though rigorous, do not require substantial specialist knowledge, skills, and other resources. Although libTekLTI may be disqualified from the certification (because libTekLTI is open source), the aim of libTekLTI is to be on par with the EAL-4 requirements.

  posted by garitaiya 1031 days ago

• File released: /libTekLTI - Prereleases/libteklti-1.0pre6/libteklti-debuginfo-1.0pre6-1.i686.rpm.sha1

  posted 1177 days ago

• File released: /libTekLTI - Prereleases/libteklti-1.0pre6/libteklti-debuginfo-1.0pre6-1.i686.rpm

  posted 1177 days ago