Template:Ombox/doc: Difference between revisions

From Zoophilia Wiki
Jump to navigationJump to search
meta>Varunjose99
meta>STL Johnny
m revert to template documentation - not the right place to start an article
Line 1: Line 1:
SATTVA eTECH INDIA PVT LTD, formerly known as VXL eTECH PVT LTD is a Bangalore based embedded product design and engineering services company, incorporated on June, 2000.
{{documentation subpage}}
{{high-use| 80,000+ }}
<!-- PLEASE ADD CATEGORIES AND INTERWIKIS AT THE BOTTOM OF THIS PAGE -->
{{mbox templates}}
This is the {{tl|ombox}} or '''other pages message box''' meta-template.


==About Us ==
It is used to build message box templates for pages of the types: User, Wikipedia, MediaWiki, Template, Help, Portal and any new future namespaces. That is, page types not covered by {{tl|ambox}}, {{tl|tmbox}}, {{tl|imbox}} or {{tl|cmbox}}. Thus it should ''not'' be used for boxes for articles, talk pages, image pages or category pages.


SATTVA eTECH India Pvt Ltd is a Bangalore based embedded product design and engineering services company. It was incorporated on June 01, 2000. SATTVA eTECH has been providing embedded product designs and engineering services to multi-nationals in USA, Europe, Asia and leading Indian public sector organizations for over 10 years.
This template works almost exactly like {{tl|ambox}} and uses the same parameters.


SATTVA eTECH provide end-to-end services for product design, development and low/medium volume manufacturing in the embedded space. Sattva eTech is a single source for both hardware and software engineering expertise. Our expert design and development services have significantly improved the quality and accelerated the time-to-market for a broad range of embedded systems.
=== We are deploying! ===


At SATTVA eTECH, we are committed to quality & excellence and the products designed, developed and manufactured by us meet and qualify for global standards such UL, CE, CSA marks. We have an in-house NABL Accredited EMI Lab for conducting pre-qualifications tests. The products or the sub-systems that we build for our customers have inherent ability for IPR / Patent Building.
After discussions on the [[Template talk:Ombox|talk page]] of this template and announcing it at several places for some time we are now deploying this template. Feel free to convert any message boxes used on "other pages" to use this meta-template. If you find any tricky cases then list them on the talk page of this template and you'll get help.


Our services cover a vast spectrum of industries like Industrial Automation, Medical Instrumentation, Data Communication and Networking, Civil and Military Aerospace and Automotive.
When this template is used to build other pages message boxes those boxes should contain explanatory texts just like before. (The same texts as before or new improved texts.) If there are more specific images in the boxes or you know a better image, then use them instead of the default images shown here.


The scope of services include electronics printed board design (digital and analog designs), developing the firmware (DSP, CPLD, FPGA PROGRAMMING), user interface software development, design and develop the mechanical/plastic enclosures, pre- certification for UL/CE/TUV etc compliance, assembly, integration and testing.
=== Usage ===


=== History ===
Simple usage example:


<pre>
{{ombox | text = Some text.}}
</pre>


* 2000 - Starting the VXL eTECH
{{ombox | text = Some text.}}
* 2010 - Name Changed to SATTVA eTECH INDIA PVT LTD


== Quality ==


'''Values'''
Complex example:
Sattva eTech is a ISO 9001-2008 Certified company. At Sattva eTech, we have a system of values that has helped us offer a range of services of exceptional quality to our clients & created a very stimulating environment within the organization ---an environment that fosters both teamwork & individual performance. It has helped sustain a long-standing relationship with its stake holders, customers, suppliers and business partners.


    * Having systems and processes in place bringing out transparency in its communications
<pre>
    * Adopting fair trade practices in dealing with customers and partners
{{ombox
    * Adopting ethical business practices
| type      = style
     * Taking necessary measures in all its activities to ensure compliance with the laws of land.
| image     = [[Image:Emblem-question-yellow.svg|40px]]
     * Providing equal employment opportunities to all citizens
| style     = width: 400px;
    * Providing a healthy and creative work environment
| textstyle = color: red; font-weight: bold; font-style: italic;
    * Being a socially responsible organization
| text      = The message body text.
}}
</pre>


'''Quality & Process'''
{{ombox
| type      = style
| image    = [[Image:Emblem-question-yellow.svg|40px]]
| style    = width: 400px;
| textstyle = color: red; font-weight: bold; font-style: italic;
| text      = The message body text.
}}


    * VXL eTech has fully equipped EMI LAB for the product certification.
=== Other pages message box types ===
    * The processes for product development life cycles are in place and the preliminary audits for ISO certification have been conducted.
    * A separate product testing team is in operation.
    * Design & development processes are in line with CMM level 3
    * Documentation is in line with IEEE Standards.
    * Procedures are in line ISO 9001:2000


=== Management ===
The following examples use different '''type''' parameters but use no image parameters thus they use the default images for each type.


{{ombox
| type = speedy
| text = type=<u>speedy</u> – Speedy deletion templates.
}}
{{ombox
| type = delete
| text = type=<u>delete</u> – Deletion templates.
}}
{{ombox
| type = content
| text = type=<u>content</u> – Major warnings and problems, such as {{tl|high-risk}}.
}}
{{ombox
| type = style
| text = type=<u>style</u> – Minor warnings and problems. {{tl|intricate}} should perhaps use this type.
}}
{{ombox
| type = notice
| text = type=<u>notice</u> – Notices and messages of any kind, both permanent and temporary. Such as {{tl|guideline}} and {{tl|how-to}}.
}}
{{ombox
| type = move
| text = type=<u>move</u> – Merge, split, rename and transwiki messages and proposals.
}}
{{ombox
| type = protection
| text = type=<u>protection</u> – Protection templates such as {{tl|pp-protected}} when shown on "other pages".
}}


The Board of Directors of VXL eTech comprises of the following:
=== Examples ===


    * N.V. Maslekar - CEO, Full time Director
Some examples using the "notice" style:
    * Kumar Shyam - CTO, Full time Director


Brief profiles of the Directors are given below:
{{ombox
| text  = No type and no image given ('''default''')
}}
{{ombox
| image = none
| text  = No type and '''image=none''' – No image is used and the '''text''' uses the whole message box area.
}}
{{ombox
| image = [[Image:Gnome globe current event.svg|42px]]
| imageright = [[Image:Nuvola apps bookcase.svg|40px]]
| text  = image = <nowiki>[[Image:Gnome globe current event.svg|42px]]</nowiki> <br> imageright = <nowiki>[[Image:Nuvola apps bookcase.svg|40px]]</nowiki>
}}


N. V. Maslekar, CEO and full-time Director
{{ombox
| type      = notice
| image      = [[Image:Blue check.svg|30px]]
| imageright = {{shortcut|WP:SHORT}}
| text      =
'''This page documents an English Wikipedia [[Wikipedia:Policies and guidelines|guideline]].''' It is a generally accepted standard that editors should follow, though it should be treated with [[Wikipedia:Use common sense|common sense]] and the [[Wikipedia:Ignore all rules|occasional exception]]. When editing this page, please ensure that your revision reflects [[Wikipedia:Consensus|consensus]]. When in doubt, discuss on the [[{{TALKPAGENAME}}|talk page]].
}}
{{ombox
| type      = notice
| image      = [[Image:Nutshell.png|30px]]
| text      =
'''This page in a nutshell:''' This template is used to build message boxes for all pages that are ''not'' articles, talk pages, image pages or category pages.
}}


    *MSc and MBA with 30 years of experience in the IT industry
=== Parameters ===
    *Successfully built up a software export company, Eurolink (now Velocient Technologies Ltd.)
    from start-up to about USD 8 million sales turnover in a span of 5 years
    *As CEO of Eurolink Systems Ltd., he successfully delivered software export projects to US,
    Europe and South East Asia. He also set up overseas subsidiaries in Europe and South East Asia
    *Prior to Eurolink, he has worked with ISRO, IIMA, HMT & HAL
    *Received Rajiv Gandhi award for Best CEO in 1998


Kumar Shyam, CTO and full-time Director
List of all parameters:


    *B.Tech (IIT, Madras) with 29 years of experience in R&D, product development and design and
<pre>
    deployment of IT solutions
{{ombox
    *Promoter Director of VXL; experience includes development and deployment of cable modems and
| type  = speedy / delete / content / style / notice / move / protection
    Linux servers for ISPs, designing network monitoring solutions and special purpose medical
| image = none / [[Image:Some image.svg|40px]]
    solutions
| imageright = [[Image:Some image.svg|40px]]
    *Currently responsible for managing technology, project delivery and technical support
| style = CSS values
| textstyle = CSS values
| text  = The message body text.
| small = {{{small|}}} / yes
| smallimage = none / [[Image:Some image.svg|30px]]
| smallimageright = none / [[Image:Some image.svg|30px]]
| smalltext  = A shorter message body text.
}}
</pre>


'''type'''
:If no '''type''' parameter is given the template defaults to type '''notice'''. That means it gets a gray border.


== Quality ==
'''image'''
:'''No parameter''' = If no '''image''' parameter is given the template uses a default image. Which default image it uses depends on the '''type''' parameter.
:'''An image''' = Should be an image with usual wiki notation. 40px - 50px width are usually about right depending on the image height to width ratio. (But the message box can handle images of any size.) For example:
::<code><nowiki>image = [[Image:Crystal package settings.png|40px]]</nowiki></code>
:'''none''' = Means that no image is used.


== '''Professional Partnership''' ==
'''imageright'''
:'''No parameter''' = If no '''imageright''' parameter is given then no image is shown on the right side.
:'''An image''' = Should be an image with usual wiki notation. 40px - 50px width are usually about right depending on the image height to width ratio. (But the message box can handle images of any size.) For example:
::<code><nowiki>imageright = [[Image:Nuvola apps bookcase.png|40px]]</nowiki></code>
:'''Anything''' = Any other object that you want to show on the right side.


===Partnership & Alliances===
'''style'''
:Optional [[Cascading Style Sheets|CSS]] values used by the entire message box table. Without quotation marks <code>" "</code> but with the ending semicolons <code>;</code>. For example:
::<code>style = margin-bottom: 0.5em;</code>


    * Sattva eTech is a Design Alliance partner of Free scale Semiconductors, USA
'''textstyle'''
    * Sattva eTech has a Lead Referral Agreement with Underwriters Laboratories Inc, to market
:Optional [[Cascading Style Sheets|CSS]] values used by the text cell. For example:
      various certification services of UL.
::<code>textstyle = text-align: center;</code>
    * Sattva eTech is a strategic partner of Aero Accessories & Systems Private Limited, a System
      Integration company for Civil and Military, Aerospace projects. The Quality procedures are
      in line for certification of design/development and manufacturing by DGCA, CEMILAC,
      DRDO labs,  NAL.
    * Sattva eTech has an understanding with Implantaire, Detroit, USA and Novolex, GmbH,
      Switzerland for selling our services in the respective geographies
    * Sattva eTech has partnered with CBI, Netherlands for Export promotion program for Europe market


===Professional Membership’s===
'''text'''
:The message body text.


  Sattva eTech is a professional member of NASSCOM and Instrumentation Society of America. We do get
==== The small parameters ====
invited for the relevant industry vertical meeting of BCCI and FKCCI. In addition to this we are
design alliance partners for Free Scale Semiconductors, AMD.
great value for our customer’s to market their products overseas.


==Services==
{{ombox
| small = yes
| text = small = yes
}}
{{ombox
| type = style
| small = yes
| text = type = style <br> small = yes
}}
'''small'''
:'''yes''' = Makes it a smaller right floating message box. This also makes the default images smaller. Note that any data fed to the '''smallimage''', '''smallimageright''' and '''smalltext''' parameters is only used if "small=yes". To make it so your template also understands the small parameter you can use this code:
::<code><nowiki>small = {{{small|}}}</nowiki></code>


==='''Embedded Product Design'''===
{{ombox
| small = yes
| image      = [[Image:Replacement filing cabinet.svg|50px]]
| smallimage = [[Image:Replacement filing cabinet.svg|32px]]
| text =
small = yes <br> image = <nowiki>[[Image:Replacement filing cabinet.svg|50px]]</nowiki> <br> smallimage = <nowiki>[[Image:Replacement filing cabinet.svg|32px]]</nowiki>
}}
'''smallimage'''
:'''No parameter''' = If no '''smallimage''' parameter is given then this template falls back to use the '''image''' parameter. If the '''image''' parameter also is empty then a small default image is used.
:'''An image''' = Should be an image with usual wiki notation. 30px width is usually about right. For example:
::<code><nowiki>smallimage = [[Image:Replacement filing cabinet.svg|30px]]</nowiki></code>
:'''none''' = Means that no image is used. This overrides any image fed to '''image''', when "small=yes".


We address the product realization from a system perspective and cover all layers from hardware, firmware, system software, protocols, embedded applications, management software and GUI.
{{ombox
| small = yes
| imageright = [[Image:Nuvola apps bookcase.png|50px]]
| smallimageright = none
| text =
small = yes <br> imageright = <nowiki>[[Image:Nuvola apps bookcase.png|50px]]</nowiki> <br> smallimageright = none
}}
'''smallimageright'''
:'''No parameter''' = If no '''smallimageright''' parameter is given then this template falls back to use the '''imageright''' parameter. If the '''imageright''' parameter also is empty then no image is shown on the right side.
:'''An image''' = Should be an image with usual wiki notation. 30px width is usually about right. For example:
::<code><nowiki>smallimageright = [[Image:Nuvola apps bookcase.png|30px]]</nowiki></code>
:'''Anything''' = Any other object that you want to show on the right side.
:'''none''' = Means that no right side image is used. This overrides any image fed to '''imageright''', when "small=yes".


We have built expert teams in board design, FPGA design, embedded software, application software, mechanical design and product styling. Design experience and domain knowledge garnered over the years help our product design teams deliver quality, cost effective solutions in the shortest time frame.
'''smalltext'''
:A shorter version of the message body text. If no '''smalltext''' parameter is given then this template falls back to use the '''text''' parameter.


This expertise coupled with capability of low/medium volume manufacturing for prototyping and in-house EMI Lab for conducting pre-qualifications tests help us offer end to end design services under one roof that benefit our customers immensely.
=== Technical details ===


Sattva eTech’s scope of Product design involves -
If you need to use special characters in the text parameter then you need to escape them like this:


    * Concept Generation
<pre>
    * Requirement Engineering & Analysis
{{ombox
    * Design & Development
| text  = <div>
    * Verification & Validation
Equal sign = and a start and end brace { } work fine as they are.
    * Proto-typing & Production
But here is a pipe {{!}} and two end braces &lt;nowiki>}}&lt;/nowiki>.
And now a pipe and end braces &lt;nowiki>|}}&lt;/nowiki>.
</div>
}}
</pre>


Our Hardware Design Experience involves building -
{{ombox
| text  = <div>
Equal sign = and a start and end brace { } work fine as they are.
But here is a pipe {{!}} and two end braces <nowiki>}}</nowiki>.
And now a pipe and end braces <nowiki>|}}</nowiki>.
</div>
}}


    * Motherboards
This template uses the ombox CSS classes in [[MediaWiki:Common.css]] for most of its looks, thus it is fully skinnable.
    * Connectivity Boards
    * Adapters
    * Power Supply & DC-DC Converters
    * Mechanical Enclosure Designs
    * Debug & Test Jigs
    * Assembly and Testing


Proven quality processes designed for embedded product designs, and over 250 man-years of embedded development experience makes us an ideal partner for the most challenging embedded tasks
This template calls {{tl|ombox/core}} which holds most of the code for {{tl|ombox}}, while {{tl|ombox}} itself does parameter preprocessing.


Sattva eTech’s collaboration with the major Certification bodies like UL, TUV, CE etc. provides
Internally this meta-template uses HTML markup instead of wiki markup for the table code. That is the usual way we make meta-templates since wiki markup has several drawbacks. For instance it makes it harder to use [[m:Help:ParserFunctions|parser functions]] and special characters in parameters.  


==='''Embedded Product Re Engineering'''===
The default images for this meta-template are in png format instead of svg format. The main reason is that some older web browsers have trouble with the transparent background that MediaWiki renders for svg images. The png images here have hand optimised transparent background colour so they look good in all browsers. Note that svg icons only look somewhat bad in the old browsers, thus such hand optimisation is only worth the trouble for very widely used icons.
Re-engineering is the re-analysis and re-design of a system, not bound by the previous design approach. Often customers find that they have a good product, a legacy system, which has ended up having obsolete components and hence cannot be manufactured anymore. This makes it all the more important for them to ensure that the replacement has minimal or no impact on the rest of the solution.


Our product design experience gives us a great edge in providing top quality Re-engineering services and to meet our customer’s technology and functional expectations.
For more technical details see the [[Template talk:Ombox|talk page]]. Since this template works almost exactly like {{tl|ambox}}, {{tl|tmbox}}, {{tl|imbox}} and {{tl|cmbox}} their talk pages and related pages might also contain more details.


Our Product Re-engineering solutions focus on retaining the core features and logic of the existing system, while bolstering the system by migrating it to emerging technologies. Agile and timely, our re-engineering services will help you make a smooth transition from old, redundant systems to new, advanced technology environments and at a fraction of the estimated costs.
=== See also ===


Sattva eTech's hardware design team has the expertise and skill required for re-engineering the entire product, using an identical technology but incorporating the latest components. This process is usually done for either obsolescence or cost reduction. It is also used to reproduce a cost-effective alternative to ensure a competitive edge our customers.
{{Mbox templates see also}}


== See also ==
<includeonly>
<!-- CATEGORIES AND INTERWIKIS HERE, THANKS -->
[[Category:Wikipedia metatemplates|{{PAGENAME}}]]


* [http://www.vxletech.com/index.html Web site]
[[cy:Nodyn:Ombox]]
* [http://vxletech.blogspot.com/ Blog]
[[hsb:Předłoha:Ombox]]
[[ja:Template:Ombox]]
[[mk:Шаблон:Ombox]]
[[mn:Загвар:Ombox]]
[[pt:Predefinição:Ombox]]
[[ro:Format:Meta-casetămap]]
[[uk:Шаблон:Ombox]]
</includeonly>

Revision as of 11:24, 1 August 2010

Template:Mbox templates This is the {{ombox}} or other pages message box meta-template.

It is used to build message box templates for pages of the types: User, Wikipedia, MediaWiki, Template, Help, Portal and any new future namespaces. That is, page types not covered by {{ambox}}, {{tmbox}}, {{imbox}} or {{cmbox}}. Thus it should not be used for boxes for articles, talk pages, image pages or category pages.

This template works almost exactly like {{ambox}} and uses the same parameters.

We are deploying!

After discussions on the talk page of this template and announcing it at several places for some time we are now deploying this template. Feel free to convert any message boxes used on "other pages" to use this meta-template. If you find any tricky cases then list them on the talk page of this template and you'll get help.

When this template is used to build other pages message boxes those boxes should contain explanatory texts just like before. (The same texts as before or new improved texts.) If there are more specific images in the boxes or you know a better image, then use them instead of the default images shown here.

Usage

Simple usage example:

{{ombox | text = Some text.}}


Complex example:

{{ombox
| type      = style
| image     = [[Image:Emblem-question-yellow.svg|40px]]
| style     = width: 400px; 
| textstyle = color: red; font-weight: bold; font-style: italic;
| text      = The message body text.
}}

Other pages message box types

The following examples use different type parameters but use no image parameters thus they use the default images for each type.

Examples

Some examples using the "notice" style:

Parameters

List of all parameters:

{{ombox
| type  = speedy / delete / content / style / notice / move / protection
| image = none / [[Image:Some image.svg|40px]]
| imageright = [[Image:Some image.svg|40px]]
| style = CSS values
| textstyle = CSS values
| text  = The message body text. 
| small = {{{small|}}} / yes
| smallimage = none / [[Image:Some image.svg|30px]]
| smallimageright = none / [[Image:Some image.svg|30px]]
| smalltext  = A shorter message body text.
}}

type

If no type parameter is given the template defaults to type notice. That means it gets a gray border.

image

No parameter = If no image parameter is given the template uses a default image. Which default image it uses depends on the type parameter.
An image = Should be an image with usual wiki notation. 40px - 50px width are usually about right depending on the image height to width ratio. (But the message box can handle images of any size.) For example:
image = [[Image:Crystal package settings.png|40px]]
none = Means that no image is used.

imageright

No parameter = If no imageright parameter is given then no image is shown on the right side.
An image = Should be an image with usual wiki notation. 40px - 50px width are usually about right depending on the image height to width ratio. (But the message box can handle images of any size.) For example:
imageright = [[Image:Nuvola apps bookcase.png|40px]]
Anything = Any other object that you want to show on the right side.

style

Optional CSS values used by the entire message box table. Without quotation marks " " but with the ending semicolons ;. For example:
style = margin-bottom: 0.5em;

textstyle

Optional CSS values used by the text cell. For example:
textstyle = text-align: center;

text

The message body text.

The small parameters

small

yes = Makes it a smaller right floating message box. This also makes the default images smaller. Note that any data fed to the smallimage, smallimageright and smalltext parameters is only used if "small=yes". To make it so your template also understands the small parameter you can use this code:
small = {{{small|}}}

smallimage

No parameter = If no smallimage parameter is given then this template falls back to use the image parameter. If the image parameter also is empty then a small default image is used.
An image = Should be an image with usual wiki notation. 30px width is usually about right. For example:
smallimage = [[Image:Replacement filing cabinet.svg|30px]]
none = Means that no image is used. This overrides any image fed to image, when "small=yes".

smallimageright

No parameter = If no smallimageright parameter is given then this template falls back to use the imageright parameter. If the imageright parameter also is empty then no image is shown on the right side.
An image = Should be an image with usual wiki notation. 30px width is usually about right. For example:
smallimageright = [[Image:Nuvola apps bookcase.png|30px]]
Anything = Any other object that you want to show on the right side.
none = Means that no right side image is used. This overrides any image fed to imageright, when "small=yes".

smalltext

A shorter version of the message body text. If no smalltext parameter is given then this template falls back to use the text parameter.

Technical details

If you need to use special characters in the text parameter then you need to escape them like this:

{{ombox
| text  = <div>
Equal sign = and a start and end brace { } work fine as they are. 
But here is a pipe {{!}} and two end braces <nowiki>}}</nowiki>. 
And now a pipe and end braces <nowiki>|}}</nowiki>.
</div>
}}

This template uses the ombox CSS classes in MediaWiki:Common.css for most of its looks, thus it is fully skinnable.

This template calls {{ombox/core}} which holds most of the code for {{ombox}}, while {{ombox}} itself does parameter preprocessing.

Internally this meta-template uses HTML markup instead of wiki markup for the table code. That is the usual way we make meta-templates since wiki markup has several drawbacks. For instance it makes it harder to use parser functions and special characters in parameters.

The default images for this meta-template are in png format instead of svg format. The main reason is that some older web browsers have trouble with the transparent background that MediaWiki renders for svg images. The png images here have hand optimised transparent background colour so they look good in all browsers. Note that svg icons only look somewhat bad in the old browsers, thus such hand optimisation is only worth the trouble for very widely used icons.

For more technical details see the talk page. Since this template works almost exactly like {{ambox}}, {{tmbox}}, {{imbox}} and {{cmbox}} their talk pages and related pages might also contain more details.

See also

There are seven metatemplates in the Module:Message box family:
  • {{Ambox}}, for messageboxes on article pages.
  • {{Cmbox}}, for messageboxes on category pages.
  • {{Imbox}}, for messageboxes on file (image) pages.
  • {{Tmbox}}, for messageboxes on talk pages.
  • {{Fmbox}}, for header and footer messageboxes.
  • {{Ombox}}, for messageboxes on other types of page.
  • {{Mbox}}, for messageboxes that are used in different namespaces and change their presentation accordingly.

Closely related metatemplates:

  • {{Asbox}}, for messageboxes in article stubs.
  • {{Dmbox}}, for messageboxes on disambiguation or set-index pages.
  • {{Ivmbox}}, a simple full-width box with default ivory background intended to frame important messages or notices.

Templates intended to be used in conjunction with Mboxes: