Using Linux at Lectra-Systèmes
The first graphic applications under MILOS had a very spartan look, due to the weak performances of the graphic controllers at that time (beginning of the 1980s). The screens, although graphical, could manage only 16 colours, and moreover, they did not use multiple windows. Hastened by competition, in 1990 Lectra decided to develop the graphic interfaces to a multi-window system facilitating the operator's work for basic operations, such as launching applications or working with files. This tool, called OpenPartner, was initially developed for the MILOS target using a low level owner library (similar to Xlib calls). The structure of the interface seemed very similar to that of the Xt/Intrinsics Widgets hierarchy.
The port of OpenPartner to the Unix environment comes with the addition of the administrative functions of the station by a privileged user, in particular:
Adding and removing Lectra packages
The network management (adding/removing stations, NFS mount management)
Serial lines and modem management
Printer management
Licenses and Lectra applications management
User management, in particular the applications authorised for each one
Figure 2 is an example of the main window in the OpenPartner environment with the package management utility, P-Manager.
Figure 2. OpenPartner with the Package Management Utility P-Manager
One of the important tasks was to develop a printer management system that could be extended and was easy to use. Even while supporting Unix, we have to admit the print system on MS Windows or even MacOS is much clearer and easier to use than on our favourite operating system. Furthermore, all the printers currently on the market are supplied with their own Windows or MacOS driver.
Our print system (operating customer/server) uses the Ghostscript program which manages different types of printers (PCL, PostScript, raster) on varied connections—serial line, Centronics, network, SCSI. A graphic tool integrated in OpenPartner, I-Manager, is used to select only the printer characteristics that are actually used. The list then appears in the print selector of Lectra applications.
The applications are intended for industrial professionals in apparel. The garment is designed in various stages and corresponds to different trades. One of the characteristics of the apparel industry is the use of sub-contractors and delocalisation. Various stages of the apparel might be realised by the apparel maker, yet production could be sub-contracted to another country. Some countries deal only with the design or the production, and supply several major brands.
The result of this situation for a company like Lectra is that it is absolutely essential to design open software, as very few customers will buy a complete series, and it is therefore necessary to know how to communicate with competing software.
Another important constraint is to support lots of languages, such as Japanese, Chinese or Russian, by using tools such as the Asiatic front-end-processor under X11.
On first approach, we can expect the following stages when designing a garment.
The designer has to create a garment model, like an artistic drawing. His/Her work is mainly based on the choice of shapes, colours, and types of fabrics that can be used. The advantage of having a data processing tool is clear. Other than the possibility of working on an “electronic sheet”, the software enables the pattern maker to import fabric motifs in an electronic form or even by using a scanner, to file the suggestions of different collections, and to make fabric simulations in 2D or 3D.
The ProStyle software offers all the above functions on a high performance Linux PC (Pentium 120 with Diamond Stealth S3-968 graphics board, 16 million colours). Sublimation printouts are also available. The software also works with the Silicon Graphics architecture.
The pattern makers must create the pattern of the garment, i.e., the plan with quotation, from the information given by the designer. He/She must also manage the different sizes, or grading, available. The information in this phase is one of the most interesting with the marker (see below) as it has a high turnover—the number of patterns produced.
Figure 5 is a view of the initial screen of the Modaris application, designed for the pattern maker.
Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
| Trying to Tame the Tablet | May 08, 2013 |
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Home, My Backup Data Center
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Linux Backup and Recovery
Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.
In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.




1 hour 2 min ago
1 hour 31 min ago
2 hours 29 min ago
3 hours 57 min ago
5 hours 6 min ago
5 hours 52 min ago
6 hours 14 min ago
12 hours 28 min ago
18 hours 7 min ago
1 day 6 min ago