Versions naming conventions

If I create versions of masters, the versions are named: "[name of master] Version 1".
I want to change der part "Version xy" to "-xy" so that the word "Version" is replaced by a dash to keep names short.
Is this possible?
regards,
Markus

Select the images you want to change. Go to Metadada, Batch Change. At Current version name choose edit. Erase what's in the box and select Custom name with counter. Type the name and select the number of digits and the starting number. Click OK and then click OK in the Batch Change box and you're done.
Jeff

Similar Messages

JDK version naming convention?

When I run "java -version" from command line, the output is:
C:\>java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
I wonder what do the "1.4.2" and "build 1.4.2-b28" and "build 1.4.2-b28 mixed mode" mean separately?
What about Sun Java 2 SDK 1.4.2_03?
As for java version, does sun have an official naming convention?
Any help will be appreciated.
-yunfeng

I hope these documents answer your question:
http://java.sun.com/j2se/versioning_naming.html
http://java.sun.com/j2se/codenames.html
I think "mixed mode" refers to the level JIT compilation; "mixed mode" means that the virtual machine interpretes parts of the byte code and compiles parts to machine code. If you run the VM in interpreted mode instead (java -Xint -version) it will say "interpreted mode."

Versions naming conventions on Duplicate Project

I love adding "v001" at the end of project name, but when I duplicate the project:
[project name] v001
[project name] v001 1
[project name] v001 2
and I hope it will be:
[project name] v001
[project name] v002
[project name] v003
and I found if you fcpx just allow this naming convention
[project name] 1
[project name] 2
[project name] 3
and I thought it was the "v" problem, then I remove the v from "v001", it results:
[project name] 001
[project name] 2
[project name] 3
the "00" disappear! so will fcpx fix that? so I can use v001, v002 or someone v01, v02 or 001,002,003

Andy Scott3 wrote:
Maybe someone could help me out here.
In L7 I was able to open a page where I could name tracks before recording them but now in 9 I still haven't found out how to do this so land up with numbered tracks which I then rename in the bin.
As for track, channel, mixer naming...what a nightmare! I often land up having to rename almost everything twice per session and even then the mixer often displays something else! I'm almost at the point of having to just ignore names and go by region names and track numbers instead.
Create the amount of audio tracks you want and double click on their title (i.e. Audio 1, Audio 2 etc) on the arrangement layout or their title on the mixer layout and rename the track/s to what you want before you record.
If you forget to do this prior to recording and you name the tracks later, you can easily rename all the regions at once by selecting region > track names to regions
I would recommend setting up a template file with all your common recording tracks named so that you don't have to do this each time you start a project.

Version Naming Convention for Internet Explorer

Notice on the far right side there is a
Emoticon smiley face on the far right side. This comes directly out of something I read and also did almost twenty years ago. Did this cause the version update to 11? I am not familiar with the metrics to call for a higher
version. It also appears to be deactivated. I believe the w3c html is readily available as well as the specific compliers to develop a browser.

Hi, the emoticon is actually a feedback tool for Internet Explorer incorporated into the 9879 build. It's supposed to work by clicking on the icon when you come across a problem for whatever web page your on and reporting the problem on the spot instead
of using the windows feedback app.

Production Version naming convention

Hi all,
We are using PDS and it is being transferred from R/3.
The problem is in R/3, in many cases different materials are having the same production version numbers.
If we have the same production version number will it cause any problem / confusion while transfer to APO and in further planning process in APO ?
Current situation in R/3 :
Product A : Production Versions 0011,0012,0013....
Product B : Production Versions 0012,0013,Z014..... Is this ok ?
Or is it better to delete and create with unique production version number in R/3 before transferring ?
Kindly guide.
Durai

Hi Durai,
The PDS will get the combo structure of product-location-version no only.
So, there is no harm in having different products having same production version numbers.
Regards
R. Senthil Mareeswaran.

Inconsistent naming conventions for Adobe Reader in software scan

I just want to see if anyone knows why Adobe's free pdf Reader appears both as "Adobe Reader" AND "Adobe Acrobat Reader". I manage software licenses for an organization of 400+, and it's difficult to know if, for instance Adobe Acrobat - Reader 6.0.2 Update - 6.0.2, should or should not be counted as a purchased license without actually visiting each workstation to verify. I've spoken with our network operations personnel and they confirmed that it is not manually entered by our personnel, but that it is something in the software. ??
Furthermore, why are the naming conventions not consistent even among those that can be identified easily? The list below is what I see when I run a report for all Adobe software on our network.
Adobe Acrobat - Reader 6.0.2 Update - 6.0.2
Adobe Acrobat 4.0 - 4.0
Adobe Acrobat 5 -- SC Install
Adobe Acrobat 5.0
Adobe Acrobat 5.0 - 5.0
Adobe Acrobat 5.0 - 5.1
Adobe Acrobat 5.0 SC Support
Adobe Acrobat 6.0 Professional - 006.000.000
Adobe Acrobat 6.0 Standard - 006.000.000
Adobe Acrobat 6.0.1 Professional - 006.000.001
Adobe Acrobat 6.0.1 Standard - 006.000.001
Adobe Acrobat 7.0 Professional - 7.0.0
Adobe Acrobat 7.0.1 and Reader 7.0.1 Update - 7.0.2
Adobe Acrobat 7.0.2 and Reader 7.0.2 Update - 7.0.3
Adobe Acrobat 7.0.3 and Reader 7.0.3 Update - 7.0.4
Adobe Acrobat 7.0.5 Professional - 7.0.5
Adobe Acrobat 7.0.7 Professional - 7.0.7
Adobe Acrobat 7.0.8 Professional - 7.0.8
Adobe Acrobat and Reader 6.0.3 Update - 6.0.3
Adobe Acrobat and Reader 6.0.4 Update - 6.0.4
Adobe Acrobat and Reader 6.0.5 Update - 6.0.5
Adobe Acrobat Reader 3.01
Adobe Acrobat Reader for Pocket PC 1.0
Adobe Reader 6.0 - 6.0
Adobe Reader 6.0.1 - 006.000.001
Adobe Reader 7.0 - 7.0.0
Adobe Reader 7.0.5 - 7.0.5
Adobe Reader 7.0.5 Language Support - 7.0.5
Adobe Reader 7.0.7 - 7.0.7
Adobe Reader 7.0.8 - 7.0.8
Adobe Reader Chinese Simplified Fonts - 1.0
Adobe Reader Japanese Fonts - 1.0
Adobe Reader Korean Fonts - 1.0
If anyone can answer this, I'd appreciate it. Thanks.

Junlie et al,
Starting with Acrobat 9 (announced on 6/2/08), Adobe will support the new ISO/IEC 19770-2 standard for universal software tagging. The new standard will allow customers to correctly identify the name, version, type and licensing status of Adobe software (starting with the Acrobat 9 family and later on as new versions of the products are introduced later this and next year).
I DO understand your frustration with the in consistencies in the naming of our software, but the problem of software discovery goes well beyond our lack of discipline. This is one of the many reasons why Adobe invested time and effort with the industry group defining the new open standard, and in software asset management in general.
More information about tagging standard can be found here: http://www.agnitioadvisors.com/info/content/view/44/1/
- Juan-Carlos

-cvs, -git, -snv... is really a good naming convention?

The unstable packages have the name of their relative stable one with added in suffix the concurrent version system installed.
I think it is a bad convention since it mixes implementer choices with the the concept of lastest unstable version.
I think it is better decide a single suffix (e.g., -unstable or -dev) and always use it without difference between the implementer choices of programming.
Moreover it avoids renaming headaches if someone changes program for keeping versions.
No flame wars. I decide nothing. It is only a thought.

Profjim wrote:
I've seen this discussed before on the forums...
Edit: http://bbs.archlinux.org/viewtopic.php?id=25938
I found this in the forum search: http://bbs.archlinux.org/viewtopic.php?id=25938
It doesn't seem like anything came out of that discussion. I haven't really found the naming convention confusing; it is the large variety of SCMs that is confusing, and that is not going to change anytime soon. The current package naming conventions are unproblematic for me so you'd have to point out exactly where a real problem has cropped up.

Question about Best Practices - Redwood Landscape/Object Naming Conventions

Having reviewed documentation and posts, I find that there is not that much information available in regards to best practices for the Redwood Scheduler in a SAP environment. We are running the free version.
1) The job scheduling for SAP reference book (SAP Press) recommends multiple Redwood installations and using export/import to move jobs and other redwood objects from say DEV->QAS->PROD. Presentations from the help.sap.com Web Site show the Redwood Scheduler linked to Solution Manager and handling job submissions for DEV-QAS-PROD. Point and Shoot (just be careful where you aim!) functionality is described as an advantage for the product. There is a SAP note (#895253) on making Redwood highly available. I am open to comments inputs and suggestions on this issue based on SAP client experiences.
2) Related to 1), I have not seen much documentation on Redwood object naming conventions. I am interested in hearing how SAP clients have dealt with Redwood object naming (i.e. applications, job streams, scripts, events, locks). To date, I have seen in a presentation where customer objects are named starting with Z_. I like to include the object type in the name (e.g. EVT - Event, CHN - Job Chain, SCR - Script, LCK - Lock) keeping in mind the character length limitation of 30 characters. I also have an associated issue with Event naming given that we have 4 environments (DEV, QA, Staging, PROD). Assuming that we are not about to have one installation per environment, then we need to include the environment in the event name. The downside here is that we lose transportability for the job stream. We need to modify the job chain to wait for a different event name when running in a different environment. Comments?

Hi Paul,
As suggested in book u2018job scheduling for SAP from SAPu2019 press it is better to have multiple instances of Cronacle version (at least 2 u2013 one for development & quality and other separate one for production. This will have no confusion).
Regarding transporting / replicating of the object definitions - it is really easy to import and export the objects like Events, Job Chain, Script, Locks etc. Also it is very easy and less time consuming to create a fresh in each system. Only complicated job chains creation can be time consuming.
In normal cases the testing for background jobs mostly happens only in SAP quality instance and then the final scheduling in production. So it is very much possible to just export the verified script / job chain form Cronacle quality instance and import the same in Cronacle production instance (use of Cronacle shell is really recommended for fast processing)
Regarding OSS note 895253 u2013 yes it is highly recommended to keep your central repository, processing server and licencing information on highly available clustered environment. This is very much required as Redwood Cronacle acts as central job scheduler in your SAP landscape (with OEM version).
As you have confirmed, you are using OEM and hence you have only one process server.
Regarding the conventions for names, it is recommended to create a centrally accessible naming convention document and then follow it. For example in my company we are using the naming convention for the jobs as Z_AAU_MM_ZCHGSTA2_AU01_LSV where A is for APAC region, AU is for Australia (country), MM is for Materials management and then ZCHGSTA2_AU01_LSV is the free text as provided by batch job requester.
For other Redwood Cronacle specific objects also you can derive naming conventions based on SAP instances like if you want all the related scripts / job chains to be stored in one application, its name can be APPL_<logical name of the instance>.
So in a nutshell, it is highly recommend
Also the integration of SAP solution manager with redwood is to receive monitoring and alerting data and to pass the Redwood Cronacle information to SAP SOL MAN to create single point of control. You can find information on the purpose of XAL and XMW interfaces in Cronacle help (F1).
Hope this answers your queries. Please write if you need some more information / help in this regard.
Best regards,
Vithal

Implementing Transport Naming convention with the help of BAdIs (Urgent)

Hi Gurus,
We need to implement Transport Naming convention in our landscape.
Transport request should follow the following naming conventions and to enable this we have to enable some necessary BAdIs?
Scenario would be like this....!
Customization
LC-<Track>-<Description> (Non Transportable Request)
<Module>-<Track>-<Configuration Type>-<Change No>-<Description of the Customisation.>
ABAP Developments
AB-<Track>-<Configuration Type>-<Development No>-<Description of the Development>
OSS Notes
BC-<Track>-OSS#<OSS Note No>-<Version>-<Patch Number>-<Process Team>-<Note Description>
Authorization
BA-<Track>-<Version>-<Authorisation Description>
Details :
Track : 01 u2013 Hot fixing, 02 u2013 Implementation, 03 u2013 BIW / EP, 04 u2013 Support
Module : SAP Module (FI, CO, MM, SD, PP, etc..)
Configuration Type : I u2013 Initial Configuration, R u2013 Change due to TPR or Additional Functionality
Change No / Development No : Unique no to trance the base documentation
Please suggest .....................!
Which are the necessary BAdIs needs to be enabled and what other configuration needs to be done.
If anybody has any document please provide.
Thanks in advance..............!!!
Regards,
Jai Sach

Hello,
SPRO --> SAP NetWeaver --> Application Server -->
System administration --> Change & Transport domain
--> BADI -->Business Add-In when Editing Requests
IF_EX_CTS_REQUEST_CHECK~CHECK_BEFORE_CREATION
Happy Tony

Standard Naming Conventions in XI

Hello,
Pls send pdfs/links for Naming Conventions in XI
Regards

Hi Henry,
These r the naming conventions to be followed in XI :
1) For Software Component, the naming convention should be :
   SAP_<SID>
where <SID> is the system ID if the applicable system
2) For Software Component Version, the naming convention should be :
    X.X
which shows the applicable version as of this date. Eg. SAP_ECC is at version 5.0
3) For Namespace the naming convention should be :
http://ERPGenie.COM/xi/<SCENARIO>/<SID>
where scenario refers to the interface being developed for and <SID> is the component where that object has relevance.
Eg. http://ERPGenie.COM/xi/OrderOutput/ECC will contain all the objects relevant to the Order Output scenario in the ECC system.
4) In Interface Objects ,
a) Message Interface should have the following naming convention :
MI_<meaningful name>_<IN/OUT/AB>
where:
IN = Inbound
OUT = Outbound
AB = Abstract (For BPM)
Remember to evaluate the IN and OUT based on the point of view from the source system to the target system. Eg. If we send an XML message from xEXTERNAL to an IDoc in ECC, then the XML Message is an OUT and the ECC is an IN interface.
b) Message Type should have the following naming convention :
MT_<meaningful name>
c) Fault Message Type should have the following naming convention :
FMT_<meaningful name>
d) Data Type should have the following naming convention :
DT_<meaningful name>
e) Data Type Enhancements should have the following naming convention :
DTE_<meaningful name>
f) Context Object should have the following naming convention :
CO_<meaningful name>
g) External Definition should have the following naming convention :
ED_<meaningful name>
5) In Mapping Objects,
a) Message Mapping should have the following naming convention :
MM_<meaningful name>_<source type>_<target type>
Eg. MM_ORDERSCENARIO_ORDERS05_OrderXML
b) Interface Mapping should have the following naming convention :
IM__<meaningful name>_<source type>_<target type>
Eg. IM_ORDERSCENARIO_ORDERS05_OrderXML
c) Mapping Templates should have the following naming convention :
MT__<meaningful name>_<source type>_<target type>
d) Imported Archives should have the following naming convention :
IA_<meaningful name>
6) In Services
a) Business Systems should have the following naming convention :
SAP<SID>
Where <SID> is the relevant system ID number
E.g.. SAPECC, SAPCRM, SAP46C
b) Business Services should have the following naming convention :
SRV_<XXXXXX>
Where XXXXXX is up to 6 characters to describe the type of service.
E.g. SRV_MAIL, SRV_FTP, SRV_SEEBRG
7) In Adapter Objects,
a) Adapter Meta Data should have the following naming convention :
AM_<meaningful name>
b) Communication Channel should have the following naming convention :
CC_<meaningful name>_<sender/receiver>
            E.g. CC_MAIL_SENDER
8) In Integration Objects,
a) Integration Process should have the following naming convention :
IP_<meaningful name> (Keep to 10 or less characters ALL CAPS)
            Store these in namespace http://ERPGenie.COM/xi/<SCENARIO>
b) Actions should have the following naming convention :
<meaningful name>
Use Send_ or Receive_ to denote the sending or receiving of messages
Store these in namespace http://ERPGenie.COM/xi/<SCENARIO>/<SID> where <SID> is system where the action is to be performed.
c) Integration Scenarios should have the following naming convention :
IS_<meaningful name> (Keep to 10 or less characters ALL CAPS)
The following web-sites may be helpful for complete naming standards in XI :
http://tsr.strain.at/space/SAP+XI(This web-site gives all detailed information about XI)
http://www.erpgenie.com/sap/netweaver/xi/namingconventions.htm
*********Please reward points if u find this useful.
cheers,
gyanaraj

Can default target naming convention be altered?

Dear All
We are using Oracle EM Grid Control 11gR2 to manage databases in the environment which hosts about 60+ databases in 11.0.1.7, 11.0.2.1 and 11.0.2.2 versions..
More often than not due to application restrictions, we are forced to use the same DB_NAME for many databases. Atleast 45+ of them have the same DB_NAME running on different machines with different HOSTNAME....
Each time we add a new target after installing the agent on the new target machine we see the Grid control identify this database using DB_NAME. Since often we have the same value for DB_NAME for the database, we happen to first delete the target identified by GRID after agent installation. Later, we manually add the target as HOSTNAME_DB_NAME and thus we are identifying them seperately from Grid Control Console..
At this point, I was wondering if there is some thing that could work around on the OEM Grid so that every time a target is added, the agent instead of supplying the DB_NAME would automatically supply HOSTNAME_DB_NAME... I did search on net and am not successful yet..
Meanwhile I thought I could post this query here and get your views or ideas... hopefully if you happened to come across such situation and share your experiences.. it would help..
Many thanks in advance.
Regards!
Sarat.

Hello Sarat,
I could direct you to the perl script that is used when discovering new targets and let you modify the default naming convention, however:
- This is not Oracle supported !
- This will result in issues not being able to recover a database using OEM GC. At least this was my experience with OEM GC 10.2.0.3, pretty sure this will be the same in OEM GC 11.1
I would choose to use unique naming for your database in your GRID. (Thi is probably not what you are waiting for...)
Regards
Rob
http://oemgc.wordpress.com

PSA Table Naming convention

Hi Experts,
Currently I am working on the BW3.5 version. I would like to delete the old PSA req through Process Chain. I need some clarification. Please provide me your suggestions.
I have collected full list of PSA Table in Development system through excel, then i can filter out by source system.
While create the Process Chain for the PSA deletion, i want to add the collected PSA tables(Object Name).
Please refer the screen shot. But i noticed that "differing in naming convention for PSA from Dev to quality & prod!!".
So if i transport this Process chain to quality & production, this will not work same as in Dev.
I have already referred the form and found the thread that discuss about the same issue. But resolution not given.
Please help me to get it this issue resolved. Thanks in advance.
Similar issue thread:
psa
Screen shot:
http://img818.imageshack.us/img818/3963/psa1.jpg
Thanks,
RR

To explain this I will take the systems with this naming Convension.
Dev BW: BWD
Dev ECC: E01
Quality BW: BWQ
Quality ECC: Q01
When we take the conversion in the quality system you should have the below parameters.
BWD to BWQ
E01 to Q01
Q01 to Q01
FLAT File to FLAT FILE.
So lets say the source system related object is goign from D to Q lets say transfer rule, the same will be converted to Quality system based on the conversions maintained in this table: RSLOGSYSMAP.
So the source system related objects will gets converted to the target system objects using the refernce maintained in this place.
Hope this is clear for you now.
Thanks
Murali

XML Schema Component Naming Convention

Is there a naming convention when you create an XML Schema? For example,
When you create a Type component, then the first letter of its name should be upper case ie. BMW, Honda, AutombileEngine ...etc.
When you create an Element component, then the first letter of its name is lowercase ie. engine, car, guestCar ..etc.
Do we have such naming convention for XML Schema?
Thanks

I am giving this from my document which i prepared for one of my customer
2     General Guidelines for design of XML schema documents
The representation of data in an XML format will be a key component of development within SOA. Therefore, the design and development of XML schemas should be as rigorous an activity as designing and developing code or designing database schemas. As such, when creating an XML schema you should be working within a development process and working to a set of design guidelines and coding standards (when writing the XML schema file). XML schemas should be reviewed for accuracy and compliance with guidelines and standards. Each of the requirements in the list below is a general requirement for all XML schemas to be deployed in the SOA environment.
•     Understandable: XML schemas should be clear, consistent and unambiguous. They should contain human readable documentation and, where appropriate, links to requirements or design documents.
•     Semantically Complete: An XML schema should define, for one or more target XML documents, each and every element and attribute that is understood by your solution when processing target documents.
•     Constraining: XML schemas are used as contracts between both publisher and consumer. As such, they must be able to be validated as concisely as possible. When designing an XML schema constraints should be identified for the values for all the elements and attributes that the application uses and relies on to the set of values that the application can handle. A valid document should imply valid data within the limits of what can be specified by the XML Schema language.
•     Uniquely identifiable: XML schemas should import and include other XML schema files rather than duplicating types and elements locally.
•     Reusable: XML schemas should be specified in such a way that types and other XML schemas can leverage elements. Every type defined in an XML schema that is the content type of an attribute or an element should be defined globally (i.e., at the top level in the Schema). Types that are defined globally can be reused in other XML schemas. Schemas should be separated into logical sections which can be included into the main schema file.
•     Extensible: Schemas should be designed to be extensible—that is, new elements and attributes can be inserted throughout the document.
Every schema should use at least two namespaces – the targetNamespace and the XML Schema (http://www.w3.org/2001/XMLSchema) namespace.
Create typed elements that can be referred to by object elements:
Example:
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.soa.com"
xmlns="http://www.soai.com"
elementFormDefault="qualified">
<xsd:complexType name="PersonType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="SSN" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.company.org"
xmlns="http://www.company.org"
elementFormDefault="qualified">
<xsd:include schemaLocation="Person.xsd"/>
<xsd:include schemaLocation="Product.xsd"/>
<xsd:element name="Company">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Person" type="PersonType" maxOccurs="unbounded"/>
<xsd:element name="Product" type="ProductType" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
•     Recognize that with XML Schemas you will not be able to express all your business rules.
o     Express those business rules using XSLT.
•     Use type definitions
Elements vs Attributes
•     Use attributes for metadata about the parent element.
•     Use attributes for data that is semantically tied to the enclosing element.
•     Use elements for data that have a meaning separate from the enclosing element.
•     Use attributes when the value will be frequently present in order to improve the human readable form of an XML instance document or reduce its size.
•     If you don't know which to use, then use the element form (which is more extensible).
2.1.1     Element, Types and attribute names
Create a descriptive name without it being excessively long (no more than 32 characters).
Elements and Types should be named in Upper Camel Case. Upper Camel Case capitalizes the first character of each word and compounds the name (remove all whitespace).
Attributes should be named in Lower Camel Case. Lower Camel Case capitalizes the first character of each word except the first word and compounds the name.
Simple and Complex type names
XML Schema has separate symbol space for elements and types so they may have the same name. The best practice is to append the word "Type" to all simple and complex type names to aid in human readability and comprehension.
Element, attribute and type names MUST be in a singular form unless the concept itself is plural.
2.1.1.1     XML Schema versioning
Use major and minor version tracking:
Major—completely different structure and semantics, most likely not backward compatible
Minor—backward compatible changes which introduce new features without removing or changing the semantics of existing structures
2.1.1.2     Indication of version in the namespace URI
Specify a namespace URI as follows
http://$domain/$groupSpecifier/$namespaceTitle/$version
The groupSpecifier can include several levels, e.g., /www.soa.com/SOA/USA/.
An example namespace could be:
http://www.soa.com/SOA/order/2

Naming conventions for Members

Hi,
Is there any naming convention for dimension members? To be more specific, can I create a member called 'Current' or would this affect the keyword current used for reporting and hence not allowed?
Shehzad

Hi,
I have an application in which there is a member called 'Current' in the Version dimension. Whenever I deploy the application this member is never created in the first iteration. If I redeploy the application and refresh the dimensions, this member is then created.
Now in a further enhancement of the application, there are some Account members that have a reference to this member in their Member Formula's. Since in the first iteration this member isn't created, the dependent members also fail with an error and the application doesn't deploy.
Is there a fix around for this?
Shehzad
Off the top of my head, I imagine that I can deploy the previous version. Redeploy it to make sure 'Current' is created. Update the dimension library with the enhanced version of the application and redeploy again. This seems like a really cumbersome process, so I would love to know how I can ensure that this member gets created in the first go!

Image naming convention

Hi,
I want to know the naming conventions used for image files in iPhone and iPad.
I've seen it's like
name~iphone.png
name@2x~iphone.png
name~ipad.png
name@2x~ipad.png
What about iPhone 5? How are we going to name images created for iPhone 5.
I have seen some thing like this [email protected] What is this 568h is?
And also if I have images for landscape and portrait mode separately how can I reflect it in the file name? Is there any convention for that?
I'm using story boards to create my UI. If I have these images in the project, does it automatically load the correct image to load depending on these names or do we have to write code to load image correctly for retina version and normal version and correct iphone version etc..
Thanks

568h i believe is because the images is 568 points in (h)eight
if it was non-retina that would be 568pixels.
at the moment iphone doesnt support landscape launch images. For the iPad, however, you use:
Default-Portrait.png                      768 x 1004
Default-Landscape.png              1024 x 748 pixels
[email protected]             536 x 2008 pixels
[email protected]       2048 x 1496 pixels
When you drag images with these names in to your project xcode automatically assigns them as the launch images. You can double check by viewing the summary tab for your project target.
Click the top most folder in the left hand pane. then in the right hand click the name of your app under "target", then click the summary tab. You can also drag and drop files into these "buckets" if they are name incorectly.

Versions naming conventions

Similar Messages

Maybe you are looking for