Before we can start LCM with you, I must know that you can do it. I need to be convinced that you must understand the concept of what to build I really need a short functional design to see if we are talking about the same thing

Description
1.10 LCM.NET RE-DESIGN
LCM-Builder Project.

LCM-Builder is a ASP development tool to create easy ASP pages.
LCM-Builder is not comparable to products like frontpage or Dreamweaver as it is NOT intended to
work in a reverse engineering mode.
LCM-Builder depends on 4 items:
1. SQL-Server database with:
a. Tables
b. Views
c. Stored Procedures
d. Custom functions
2. LCM VB6
a. server object
b. Install program
3. WEB
a. LCM-Builder web tool
b. LCM-Builder web based CMS
c. LCM-Builder export/import language wizard
4. Program based Install program
The SQL-Server database is available from script and can be re-created any time.
A script to fill the database with the complete Like2Date project (8 languages included)
A complete set of all available help is (downloadable) available in PDF.
The Client tool, web application can be viewed online: http://lcm-demo.296.com (Select the
Like2Date project from the project list box and fill in the userID and password admin/admin)
The content management web application can be viewed and used form:
http://cms-demo.like2date.com
This is usually behind NT-Security with AD security, but the demo can be viewed freely. The data is
all real data from the web site WWW.Like2Date.com. (try it, don’r worry about mixing up things, it
takes 10 minutes to reinstall the databases if it is corrupted.)
The re-design project is to create a Dot.Net server object that works with the LCM-Database. The
new object must be downwards compatible with the database.
The output must meet the DOT.Net languages VB and C# (Selectable by page)
New-Web Tool:
The new web client for LCM-Builder tool must also read/write data from ODBC connections, native
read/write from Oracle, mySQL and file based XML.
New Web CMS:
The new CMS web client must be downwards compatible with the SQL-Server database and must
also read/write data from ODBC connections, native read/write from Oracle, mySQL and file based
XML.
For editing of text, the classic version use the cute editor but there are better opensource editors.
Important in choice or development is that full support for UTF-8 as else the text will not be
portable and show wrong on the web site (data that looks good within the database, not necessarily
shows ok on a web page)
Translating tool:
For easy export and import of languages, a wizard must be programmed for export all data into an
XML sheet that can be translated and then imported into the database. The export must have two
fields for each record. A field for the original language and a field for the translated record.
Any kind of language can be the source.
The translation tool must be a web based tool for easy translation all over the world. The Translate
tool must have a user discriminator so more translator can work on different projects at the same
time.
The length of the wizard page defense on the number of records. When the wizard is opened for a
project, the user retrieve a list of all words to trans late with to the right the translated word. On the
same row, a toggle checkbox for showing or hiding the translated text (only translated text can be
hidden)
On the top of the page (frame based) a button can change the state of the list
1. Show all record
2. Show all records not translated
3. Show all records translated
A summary field with:
1. the number of all words to translate
2. the number of words translated
3. the number of words not translated
These statistics must be available for admin view for all translators/projects
Install:
The new setup must install a database on SQL-Server, Oracle, MySQL and file based XML
The use of LCM-Builder:
We use LCM-Builder to develop multi-lingual web sites that also have an build in CMS.
Each project has his own data database and his own LCM database.
Example:
A project for n-Review will have a database:
??db_N_Review
??db_LCM_N_Review
each project is called with his own confidential.
To open the web based tool, you have to supply this URL:
http://194.269.296.100/LCM/start.asp?SQL-Server=SQL-02&LCM_Catalog=db_LCM_N_Review
To open the web based CMS, you have to supply this URL:
http://194.269.296.100/LCM/start.asp?SQL-Server=SQL-02&LCM_Catalog=db_LCM_N_Review&LC
M_Project=16
Better of course to have a custom CMS or tool page where you call this URL from .
When the LCM-Builder web tool is open, you can:
1. create/modify new projects (Projects)
264 LCM-Builder
? 2008 Mike Cabolet
2. create/modify new forms (Forms)
3. create/modify new labels (Labels)
4. create/modify languages (Languages)
5. Export a page to ASP (Views)
Study the online demo for good understanding of the functionality
http://lcm-demo.296.com/
The output of an ASP page is always the same. (download the full document for a more explanation.)
functionality support the use of classes. You can find all the used classes in the
documentation of this helpfile
LCM-GRID control;
Some of the pages have a grid control. In classic ASP that need to be an external object. ASP/C# .NET
has this functionality build in. Therefore, these objects do not need to be re-created.
Conclusion:
The new LCM.Net must have at least the same functionality as the classic object and can connect to
other databases and file based XML.

The LCM-Builder functionality has this items:
1. LCM.Net Object
2. LCM-Database (already exists for SQL-Server)
3. LCM functionality for all databases that are not SQL-Server based.
4. LCM web tool for creating ASP.NET,VB.NET or PHP based web page
5. LCM cms tool
6. LCM Language tool
7. LCM ASP classes

NB:
Full documentation about LCM and Sources can be downloaded on this link:
http://www.296-software.com/download/lcm-download.htm
The sources are password protected and can only opened when you sign a no-disclosure agreement.
The documentation file is free to open
If you make a serious quote, we will supply you with the sources