Guidelines for using CM27 & CM28

Plz let me know the step by step guide lines for using CM27 & CM28.

Dear,
CM28 - Capacity Leveling SFC ind. Cap. Tab.
CM29 - Capacity leveling - PI Planning Table.
Selection Objects in CM28
-Work center
-Plant
-Capacity category
-Individual capacity
-Personnel Number
Selection Objects in CM29
-Work center
-Plant
-Capacity category
-Capacity planner grp
Here in CM29 we cant select Individual cpacity In broad CM28 is used for leveling Individual capacity while CM29 is used to level All Capacities in one Go.
Regards
Samunder Singh

Similar Messages

Guidelines for using JPA from an Add-on?

Can somebody post the guidelines for using JPA from within an Add-on?
We are facing issues using JPA (2.0)
Thanks
Pramod

From http://www.sxipper.com/faq#uninstall
To uninstall Sxipper go to your Firefox menu and choose Tools | Add-ons. Select '''Sxipper '''from the list of extensions and click the "Uninstall" button. After restarting your browser Sxipper will be removed.
Sxipper still uses the Firefox Password Manager, so your passwords are all there. Uninstalling Sxipper will restore the default password manager functionality. See http://www.sxipper.com/faq#wherepassword

Developer Guidelines for Using /tmp ?

Is there an Apple document anywhere with an official guidelines for using /tmp?
I know Apple started (explicitly) encouraging developers to use /tmp under Leopard because it's ignored by Time Machine but I can't find any actual definition of what a "temporary" file is or how long it can be guaranteed to exist in /tmp. Does the system regularly flush /tmp files using something like cron or luanchd as a part of system maintain?
I think it is a good idea but I don't want someone to leave the application open and possibly have a support file pulled out from underneath it.
Thanks,
=Tod

Tod Kuykendall wrote:
Is there an Apple document anywhere with an official guidelines for using /tmp?
I don't think Apple's guidelines are any different than the standard /tmp guidelines for UNIX. That being said, I don't know if they are written down anywhere.
I wouldn't use /tmp at all if there were another option. Most UNIX programmers try to avoid it because it is is usually a tiny partition on a local file system. Often, if you need a temp file, you need lots of space. Other times, you need a temp file but you want it to be fast. A common tactic is to create temp files and then hard link them into place when you are done. That usually won't work if using /tmp because the final destination is a different file system.
I know Apple started (explicitly) encouraging developers to use /tmp under Leopard because it's ignored by Time Machine but I can't find any actual definition of what a "temporary" file is or how long it can be guaranteed to exist in /tmp. Does the system regularly flush /tmp files using something like cron or luanchd as a part of system maintain?
They usually go away at reboot. I don't know if it is shutdown or start up. /tmp is a good place for UNIX sockets, but not much else.
I think it is a good idea but I don't want someone to leave the application open and possibly have a support file pulled out from underneath it.
Nothing is going to get pulled out from underneath. I don't know the details of when the flush takes place, but I know it won't touch any open files. Otherwise, some system services (UNIX sockets are on my mind these days) wouldn't work. I wouldn't close any file in /tmp and later expect it to be there. It usually will be there, but it isn't guaranteed.

Guidelines for Using Ovi branded icon inside an ap...

Does anyone have inputs on any guidlines for using ovi branded icons within the application?
Is it ok to have an ovi branded icon within an application to route to the ovi store page of your content?

Bob_Schor wrote:
Wow, a comment from an old Post of mine! I don't use VITs to spawn clones, but am a big fan of Start Asynchronous Call (and Static VI References), which seems to work equally well from Development mode and as a built Executable.
BS
Yes this is the more appropriate way to do this same thing without VITs. I posted a while ago an example using this technique which doesn't require knowing the path to any VI files here:
http://forums.ni.com/t5/LabVIEW/building-an-executable-with-vits-with-Labview-2011/m-p/2384984#M7404...
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Guideline for Using 40 Char in Short Text Field of Material Master

Dear Experts & Forum Members,
In MM01 while creating a Material Master record (spare part) we need to fill in Basic Data. It has a field known as "Short Text Field " This Field has limitation of 40 characters. This is the same field which has Searched associated with it. This description is what we see when we look for Stock Overview of Material in the Stores through MEMBER.
To use this 40 characters efficiently people usually come up with a guideline so that maximum and meaningful information crucial information for identification of spare part/material is VIEWED when we see it.
For example for an AC Motor the description may look like
*MOTOR AC SQ 100KW 1500 RPM 8P CLA FRXYZ
which describes AC Motor, Squirrel Cage Type, 100 KW, 1500 RPM, 8 Pole, Class A, Frame Size XYZ
Request the forum members to provide / share any guideline they might have come up with to use these 40 characters to describe different spare parts.
Thanks in advance for your help.
Regards
Vinay
Edited by: VINAY MAITHANI on Jul 15, 2010 6:51 PM

Hi Vinay,
We are also doing the same activity and we are arranging the material description in a manner which is almost simlar to you.
But, except one thing which is Classification. We have classification feature mapped with material master for the details of Dimension,Brand,Color and Orgin.
For further commets, rever back.
Regards,
NAK
Edited by: abdul kader on Jul 28, 2010 9:36 AM
Edited by: abdul kader on Jul 28, 2010 9:38 AM

What are the best practices for using the enhancement framework?

Hello enhancement framework experts,
Recently, my company upgraded to SAP NW 7.1 EhP6. This presents us with the capability to use the enhancement framework.
A couple of senior programmers were asked to deliver a guideline for use of the framework. They published the following statement:
"SAP does not guarantee the validity of the enhancement points in future releases/versions. As a result, any implemented enhancement points may require significant work during upgrades. So, enhancement points should essentially be used as an alternative to core modifications, which is a rare scenario.".
I am looking for confirmation or contradiction to the statement "SAP does not guarantee the validity of enhancement points in future releases/versions..." . Is this a true statement for both implicit and explicit enhancement points?
Is the impact of activated explicit and implicit enhancements much greater to an SAP upgrade than BAdi's and user exits?
Is there any SAP published guidelines/best practices for use of the enhancement framework?
Thank you,
Kimberly
Edited by: Kimberly Carmack on Aug 11, 2011 5:31 PM

Found an article that answers this question quite well:
[How to Get the Most From the Enhancement and Switch Framework as a Customer or Partner - Tips from the Experts|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0f0373e-a915-2e10-6e88-d4de0c725ab3]
Thank you Thomas Weiss!

Guidelines for when to use SE vs. EE

Are there any guidelines for when to use Standard Edition and when to use Enterprise Edition? Any limits on Standard edition as far as transactions/sec or number of users or size of database? Other than a list features that are not included in SE are there any other limitiations or reasons I should not go with SE over EE?

Have you checked out www.javaworld.com. They usually have very good and in-depth articles. IMHO, it all depends on the sort of use your library is intended for. If its used extensively by native code, use C++ with a Java wrapper. It its the other way around, implement it in Java and use a JNI interface for native code. I would really consider this carefully before implementing stuff in C++ that is used from Java. First of all, Java is after all much simpler than C++, its a more elgant OO-language and you have the platform neutrality. On the other hand, C++ has its sides. I dont use JNI unless its absolutely neccessary, in situations like using legacy code.
These are just a few of my thoughts, hope it gives you some hints.

Best Practises and Guidelines for SharePoint 2013 Development

Currently We are using SharePoint 2010 and doing a lot of enhancement and customization in the portal.
we are planning to migrate SharePoint 2013 after 6-9 months.
I want to know what are the best practices and guidelines for development in SharePoint 2010 keeping one thing in mind that customization should be compatible or can easily migrate to SharePoint 2013 so that re-engineering effort would be as minimum
as possible.
We have every possible piece of customization in SharePoint 2010 portal like web part, event receivers, workflows, master page, page layout, custom search etc.
Please do the needful.

Best practices don't really apply here. They are generally rules of thumb that you can apply without thinking too much and be pretty much right. Development is by it's nature too varied to allow that sort of best practice guidance.
Having said that the main thing you should be concerned with around the choice of development approach in 2013 is the intended future of your client and the application. If they are making a move to the cloud you should be concentrating on the app model
and rapidly phasing out farm solutions. If they are considering it then you can still consider using the more old-school options of farm solutions and sandboxed solutions. If they can't go to the cloud because of data security etc. then you are more or less
free to use what you like.
Also, try to move to client side processing wherever possible. MS are only going to make server side work less pleasant in future.
Beyond that, get to some conferences and start chewing through some of the blogs on the topic.

FAQ: User Interface Guidelines for CRM 2007 are now available

The CRM UI Concept Team has made the UI Guidelines for CRM Web Client User Interface (CRM 2007 UI) available to the BPX community:
This document provides an overview of the on-premise as well as the off-premise versions of the SAP CRM Web Client User Interface (UI). It contains the properties and principles of the SAP CRM Web Client UI that are already committed and available. For planned features, refer to the corresponding specification documents.
The information in the guidelines starts with general topics, followed by details. The sections are organized with high-level topics like Page Types and Navigation Schema first, followed by the consecutive sections describing which building blocks and elements of the UI populate the various pages. A section typically starts with one or more screenshots of a central UI element with a generic explanation. The subsequent sections explain the detailed aspects of each element.
We hope that you will find this information useful.
Enjoy the new CRM UI! [UI Guidelines for CRM Web Client User Interface (CRM 2007 UI)_ |http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf]
Edited by: Zhaojie Liu on Jun 10, 2009 10:08 AM

Hi,
not sure why your download stops.. you can also try to download via this link: [http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf|http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf] (Document is 17,4MB of size)
Here the guidelines also have been posted together with an article about the CRM 2007 Web Client UI.
Hope this helps
Best regards
Ingo

User Interface Guidelines for CRM 2007 are now available

The CRM UI Concept Team has made the [UI Guidelines for CRM Web Client User Interface (CRM 2007 UI)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/302d8152-002b-2b10-34bd-9ff3c712dd4b] available to the BPX community:
This document provides an overview of the on-premise as well as the off-premise versions of the SAP CRM Web Client User Interface (UI). It contains the properties and principles of the SAP CRM Web Client UI that are already committed and available. For planned features, refer to the corresponding specification documents.
The information in the guidelines starts with general topics, followed by details. The sections are organized with high-level topics like Page Types and Navigation Schema first, followed by the consecutive sections describing which building blocks and elements of the UI populate the various pages. A section typically starts with one or more screenshots of a central UI element with a generic explanation. The subsequent sections explain the detailed aspects of each element.
We hope that you will find this information useful.
Enjoy the new CRM UI!
Feel free to provide your feedback.
Edited by: Florian Weigmann on Jul 17, 2008 9:14 PM

Hi,
not sure why your download stops.. you can also try to download via this link: [http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf|http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf] (Document is 17,4MB of size)
Here the guidelines also have been posted together with an article about the CRM 2007 Web Client UI.
Hope this helps
Best regards
Ingo

Putting fileinfo data on bottom of image for use in building a photobook for printing/binding

I wonder if someone on here could help me with a problem I have? I am not a script expert by any means. The term "amateur" is probably pretty accurate!
I have a few hundred pictures I want to include into a (to be printed) photobook. I want to put some key EXIF/Fileinfo data on the images so that they remind me of what file, when it was taken, with what and with what settings. I found an excellent script (by JJmack?) which does what i want with one exception. The script (below) puts the info on the image starting on the top left (0,0) and I really want it to start on the bottom left (so that it looks like a caption). I have tweaked the original 5 lines of data down to one line, and have reduced the font size but I simply do not have the skills to amend it to add the selected text to the bottom left.
I was hoping that someone on this forum might be kind enough to help - not least because I am sure there are others who would want to the same thing? Or am I being a complete idiot and there is a simpler way to achieve what I am trying to do?
Grateful for any help
Michael.
Apologies - can't find way to insert file so had to copy and paste:
// This script was hacked from one I downloaded from the web JJMack 2008
/* Script to stamp copyright and camera data of shot   */
// This script is supplied as is. It is provided as freeware.
// The author accepts no liability for any problems arising from its use.
<javascriptresource>
<about>$$$/JavaScripts/StampExif/About=JJMack's Stamp Exif.^r^rCopyright 2009 Mouseprints.^r^rScript utility for action.^rNOTE:Add Text Layer with Fomatted EXIF Data!</about>
<category>JJMack's Action Utility</category>
</javascriptresource>
// enable double-clicking from Mac Finder or Windows Explorer
#target photoshop // this command only works in Photoshop CS2 and higher
// bring application forward for double-click events
app.bringToFront();
// ensure at least one document open
if (!documents.length) {
    alert('There are no documents open.', 'No Document');
// if at least one document exists, then proceed
else {
    main();
// main - main function
function main() {
    /* Null business owner */
    var Biz = "";
    var Owner = "";
    /* Variables You can hard code your business owner here */
    // var Biz = "Mouseprints";
    // var Owner = "John J McAssey";
        /* sizeFactor influences text size 1 will use largest font 2 will half that font size    */
    var sizeFactor = 1.5;
        /* textX and TextY positions text placement 0 and 0 Top Left corner of image in pixels    */
    var textX = 0;
    var textY = 0;
    /* Internal Photoshop Text name                                */
        var fontName = "ArialMT";
    var fontName = "TimesNewRomanPSMT";
    var fontName = "Tahoma";
    /* Text Color                                        */
    textColor = new SolidColor;
    textColor.rgb.red = 255;
    textColor.rgb.green = 255;
    textColor.rgb.blue = 255;
    /* END Variables You can hard code your business owner here */
        // remember users Ruler avd Type Units and set ours
    var strtRulerUnits = app.preferences.rulerUnits;
    var strtTypeUnits = app.preferences.typeUnits;
    app.preferences.rulerUnits = Units.PIXELS;
     app.preferences.typeUnits = TypeUnits.PIXELS;
    /* Trying to figure out font size for the number of lines to cover the document height        */
    /* and getting setting text area to cover the document was a trip. Adobe Postscript trip    */
    /* I believe that 72 or 72.27 Point/Pica Size Photoshop Preference maybe I should see if    */
    /* I could retrieve it. Anyway mine is set to 72 Setting the document resolution taking        */
    /* the document width and dividing by 72 would probably yield number of characters that        */
    /* would fit in the document width. Setting the documents resolution comes into play        */
    /* with Photoshop text support. Using the documents height and dividing the by the number    */
    /* of lines of text I needed I hoped would yield the font size I needed. However that        */
    /* did not work the text area was correct the number of text lines did not fit. I needed    */
    /* to use a smaller font. When the document resolution is set to 72 DPI and I set a text    */
    /* layer font size to 72 and the text area the number of pixels I want and observing        */
    /* Photoshop's text options bar there I see a one 1 to one relationship. 72 px = 72 px.        */
    /* If I set the documents resolution lower and set a Photoshop text layer font size to        */
    /* 72 px I see Photoshop scale the number to a lower number of pixels in the option bar.    */
    /* Just what I needed. Setting the Documents resolution to 60 DPI let the number of line    */
    /* I needed fit on the document. However Photoshop also scaled the text area I set down        */
    /* in size and that number of lines did not fit within that area. I needed to scale the        */
    /* text area up. Scaling the Text area up using 72/resolution did the trick...             */
        var testres = 60;
    res = app.activeDocument.resolution;
    if(res!=testres){ app.activeDocument.resizeImage(app.activeDocument.width.value,app.activeDocument.height.v alue,testres); }
    /* Define var to be used to avoid undefined */
    var expTime = "";
    var expPgm = "";
    var expCmp = "";
    var mtrMode = "";
    var ev = "";
    var flshCode = "";
    var flshMode = "";
    var focLength = "";
    var Fstop = "";
    var ISO = "";
    var Model = "";
    var CameraModel = "";
    var Artist = "";
    var maxF = "";
    var wbMode = "";
    var phoTime = "";
    var picYr = "";
    var lens = "";
    var cpyrt = "";
    var remShutter = "";
    var remAperture = "";
    var remISO = "";
    var lat = "";
    var latRef = "";
    var lon = "";
    var lonRef = "";
    var docName = app.activeDocument.name;
    /* END var to be used to avoid undefined */
    try {   // get active document
        var doc = app.activeDocument;
    catch (e){
        alert("No Document Open..." );
    var exifInfo = "";
try {
        // alert( "doc.info.exif=" + doc.info.exif );
        var numExifItems = doc.info.exif.length;
        // alert( "numExifItems=" + numExifItems );
                for (var i = 0; i < doc.info.exif.length; i++){
             exifInfo = exifInfo + doc.info.exif[i][0] + " = " + doc.info.exif[i][1] + "\r";
/* ---------------------------------- Extracting Data I want to Stamp formated ----------------------------------------------------------------------- */
                        checkThisItem(doc.info.exif[i][0], doc.info.exif[i][1])
            key=doc.info.exif[i][0];
            keyData=doc.info.exif[i][1];
            if (key == "Artist") {
                // alert ("Key=" + key + " Data=" + keyData );
                Artist =("By " + keyData + " ");
             if (key == "Date Time Original") {
                // alert ("Key=" + key + " Data=" + keyData );
                var phoTime = keyData;
                var dateArray1 = phoTime.split(" ", 2);
                phoTime = dateArray1[0];
                phoHour = dateArray1[1];
                var dateArray2 = phoTime.split(":");
                var monthsArray = ["January","February","March","April","May","June","July","August","September","October", "November","December"];
                phoTime = monthsArray[dateArray2[1]-1]+" " + dateArray2[2]+ ", " + dateArray2[0] +" @ " + phoHour;
                var picYr = dateArray2[0];
            if (key == "Model") {
                // alert ("Key=" + key + " Data=" + keyData );
                Model = (keyData + " ");
            if (key == "Max Aperture Value") {
                // alert ("Key=" + key + " Data=" + keyData );
                maxF = ("maxF " + keyData + " ");
                maxF = ( keyData + " ");
            if (key == "Focal Length") {
                // alert ("Key=" + key + " Data=" + keyData );
                focLength = ("@ " +keyData + " ");
            if (key == "Exposure Program") {
                // alert ("Key=" + key + " Data=" + keyData );
                expPgm = (keyData + " ");
                if (expPgm == "Not defined") { expPgm = "Exposure Program Not Recorded "; }
            if (key == "Exposure Bias Value") {
                // alert ("Key=" + key + " Data=" + keyData );
                expCmp = ("Bias " + keyData + " ");
            if (key == "Metering Mode") {
                //alert ("Key=" + key + " Data=" + keyData );
                mtrMode = (keyData + " Metering ");
            if (key == "White Balance") {
                // alert ("Key=" + key + " Data=" + keyData );
                wbMode = ("White Balance " + keyData + " ");
            if (key == "ISO Speed Ratings") {
                // alert ("Key=" + key + " Data=" + keyData );
                ISO = ("ISO " + keyData + " ");
                remISO = keyData;
            if (key == "Exposure Time") {
                // alert ("Key=" + key + " Data=" + keyData );
                expTime = (" " + keyData + " ");
                remShutter = keyData;
            if (key == "F-Stop") {
                //alert ("Key=" + key + " Data=" + keyData );
                Fstop = (" " + keyData + " ");
                remAperture = keyData;
            if (key == "Flash") {
                // alert ("Key=" + key + " Data=" + keyData );
                var flshCode = keyData;
                var flshMode = "Flash Code=" + flshCode + " ";
                if(flshCode==1){var flshMode = "Firing Flash   ";}
                if(flshCode==9){var flshMode = "Firing Flash   ";}
                if(flshCode==13){var flshMode = "Firing Flash   ";}
                if(flshCode==15){var flshMode = "Firing Flash   ";}
                if(flshCode==25){var flshMode = "Firing Flash   ";}
                if(flshCode==29){var flshMode = "Firing Flash   ";}
                if(flshCode==31){var flshMode = "Firing Flash   ";}
                if(flshCode==65){var flshMode = "Firing Flash   ";}
                if(flshCode==69){var flshMode = "Firing Flash   ";}
                if(flshCode==71){var flshMode = "Firing Flash   ";}
                if(flshCode==73){var flshMode = "Firing Flash   ";}
                if(flshCode==77){var flshMode = "Firing Flash   ";}
                if(flshCode==79){var flshMode = "Firing Flash   ";}
                if(flshCode==89){var flshMode = "Firing Flash   ";}
                if(flshCode==93){var flshMode = "Firing Flash   ";}
                if(flshCode==95){var flshMode = "Firing Flash   ";}
                if(flshCode==0){var flshMode = "without Flash   ";}
                if(flshCode==16){var flshMode = "without Flash   ";}
                if(flshCode==24){var flshMode = "without Flash   ";}
                if(flshCode==88){var flshMode = "without Flash   ";}
                if(flshCode==32){var flshMode = "No Flash   ";}
            if (key == "GPS Latitude") {
                //alert ("Key=" + key + " Data=" + keyData );
                lat= ("Lat: " + keyData.replace(/\.00/g,'') + " ");
            if (key == "GPS Latitude Ref") {
                //alert ("Key=" + key + " Data=" + keyData );
                latRef= (keyData + " ");
            if (key == "GPS Longitude") {
                //alert ("Key=" + key + " Data=" + keyData );
                lon= ("Lon: " + keyData.replace(/\.00/g,'') + " ");
            if (key == "GPS Longitude Ref") {
                //alert ("Key=" + key + " Data=" + keyData );
                lonRef= (lon + keyData + " ");
        /* Copyright Year(s) */
        var thisYr, toDay
        var toDay = new Date();
        var thisYr = toDay.getYear() + 1900;
        if(picYr!="" && thisYr!=""){ var cpyrt = picYr + "-" + thisYr + " ";}
        if(picYr=="" && thisYr!=""){ var cpyrt = thisYr + " ";}
        if(picYr==thisYr){ var cpyrt = thisYr + " ";}
        /* For cameras that don't set Artist or set unknown in the Exif substitute Owner if set */
        if(Artist=="" && Owner!=""){var Artist = "By " + Owner + "   ";}
        if(Artist=="By unknown " && Owner!=""){var Artist = "By " + Owner + "   ";}
        /* Lens info */
        xml = app.activeDocument.xmpMetadata.rawData;
        lensOffset = xml.indexOf("<aux:Lens>") + "<aux:Lens>".length;
        if(lensOffset > 0) {
            lens = xml.substr(lensOffset, xml.length - lensOffset);
            lens = lens.substr(0,lens.indexOf("</aux:Lens>"));
        /* Hack for my cameras with fixed lens */
        if(lens=="" && Model=="E990 "){var lens = "9-28mm";}
        if(lens=="" && Model=="E-20,E-20N,E-20P "){var lens = "9-36mm";}
        if(lens=="" && Model=="E-10 "){var lens = "9-36mm";}
        if(lens=="" && Model=="E-10          "){
            var Model = "E-10 ";
            var lens = "9-36mm";
        if(lens=="" && Model=="Canon PowerShot SD700 IS "){var lens = "5.8-23.2mm";}
        if(lens!=""){var lens = lens + " ";}
        else {var lens = "Unknown Lens ";}
        /* Hack for my ultra compact cameras program mode not recorded */
        if(Model=="Canon PowerShot SD700 IS "){var expPgm = "Ultra Compact Camera ";}
        //alert (remShutter + " " + remAperture + " " + remISO);
                ev = calcEV(remShutter, remAperture, remISO);
/* ---------------------------------- END Extracting Data I want to Stamp formated -------------------------------------------------- */
    catch (e){
        alert("No EXIF data exists..." );
    if ( exifInfo == "" ) {
        alert( "No EXIF data exists..." );
    else {
        // alert( "exifInfo=" + exifInfo );
        text_layer = doc.artLayers.add();                        // Add a Layer
        text_layer.name = "EXIF Stamp";                            // Name Layer
        text_layer.kind = LayerKind.TEXT;                        // Make Layer a Text Layer
        text_layer.textItem.color = textColor;                        // set text layer color
/* Do not set TextType to Pargarph Text for StampEXIF so action can position text layer
         text_layer.textItem.kind = TextType.PARAGRAPHTEXT;                // Set text layers text type
        text_layer.textItem.font = fontName;                        // set text font
        text_layer.blendMode = BlendMode.NORMAL                        // blend mode
        text_layer.textItem.fauxBold = false;                        // Bold
        text_layer.textItem.fauxItalic = false;                        // Italic
        text_layer.textItem.underline = UnderlineType.UNDERLINEOFF;            // Underlibn
        text_layer.textItem.capitalization = TextCase.NORMAL;                // Case
        text_layer.textItem.antiAliasMethod = AntiAlias.SHARP;                // antiAlias
//        var fontSize = Math.round((doc.height- textY) / ((numExifItems +1) * sizeFactor)); // Calulate font size to use Item nomber + last \r
        /* Calulate font size to use for StampExit keep size same for landscape and portrait base on document size */
        if (doc.width >= doc.height) {var fontSize = Math.round(doc.height / (30 * sizeFactor));}
        else {var fontSize = Math.round(doc.width / (30 * sizeFactor));}
        if (fontSize<10){fontSize=10};                            // don't use Font size smaller then 10
        text_layer.textItem.size = fontSize;                        // set text font Size
//        text_layer.textItem.position = Array(textX, textY );                // set text layers position in and down
        text_layer.textItem.position = Array(textX, (textY + fontSize ));        // set text layers position in and down for Stamp add in fontsize
        textWidth = ((doc.width - textX) * 72/testres );                // Text width document width - offset
        textHeight = ((doc.height - textY) * 72/testres );                // Text height document height - offset
/* Do not set Text Area for StampEXIF so action can position text layer
        text_layer.textItem.width = textWidth;                        // set text area width
        text_layer.textItem.height = textHeight;                    // set text area height
         alert(
        "res=" + res + " sizeFactor=" + sizeFactor + " numExifItems=" + numExifItems
        + "\r" + "fontsize=" + fontSize + " font=" +fontName
        + "\r" + "Image area width=" + doc.width + " height=" + doc.height
        + "\r"    + "text area width=" + textWidth + " height=" + textHeight
        + "\r"    + "Text Position top left=" + textX + "," + textY
        + " bottom right=" + (textX + textWidth )+ "," + (textY + textHeight )
        try{
            text_layer.textItem.contents = exifInfo;
        catch (er) {
            alert("Error Setting Contents...");
/* ----------------------------------------- Data Stamp format ----------------------------------------------------------------------- */
        if (!app.activeDocument.info.copyrightNotice=="") {var Notice = app.activeDocument.info.copyrightNotice; }
        else { var Notice = "Copyright \u00A9 " + Biz + " " + cpyrt; }
        if (lat!="" && lon!="") { gps = "\r" + lat +latRef + lon + lonRef;}
        else {gps = ""; }
        text_layer.textItem.contents = docName + " " + Model + lens + ISO + expTime + Fstop;
        if (app.activeDocument.info.instructions == "" ) {
            app.activeDocument.info.instructions = docName + " " + Model + lens + ISO + expTime + Fstop;
    if(res != testres){ app.activeDocument.resizeImage(app.activeDocument.width.value,app.activeDocument.height.v alue,res); }
    app.preferences.rulerUnits = strtRulerUnits;
    app.preferences.typeUnits = strtTypeUnits;
// END - main function
// calcEV()
function calcEV(shutter, aperture, iso) {
    evString = new String("");
    isoValue = new Number(0);
    shutterValue = new Number(0);
    apertureValue = new Number(0);
    evValue = new Number(0);
    apertureValue = aperture;
    apertureValue = apertureValue.substr(2,apertureValue.length -2); // Strip off "f/"
    shutterValue = shutter;
    shutterValue = shutterValue.substr(0,shutterValue.indexOf(" ")); // Strip off ending " sec"
    if ( shutterValue.indexOf("/") != -1) {
        topShutter = shutterValue.substr(0,shutterValue.indexOf("/"));
        bottomShutter = shutterValue.substr(shutterValue.indexOf("/") + 1,shutterValue.length -(shutterValue.indexOf("/") + 1));
        shutterValue = topShutter / bottomShutter;
    isoValue = iso;
    //alert ("apertureValue = " + apertureValue + " shutterValue = " + shutterValue + " isoValue = " + isoValue );
    if (isoValue>0 && shutterValue>0 && apertureValue>0) {
        evValue = Math.LOG2E * Math.log(Math.pow(apertureValue, 2) * (1 / shutterValue) * (100 / isoValue));
        evValue = Math.round(evValue * 10) / 10;
        evString = "EV " + evValue;
    return evString;;
function checkThisItem(key, keyData) {
    // alert("Key=" + key + " Data=" + keyData );

I wrote that script to be used within an Action. The Action uses the script to add the text layer. The text layer becomes the current active layer. The action can then position the layer anywhere over the document by aligning the layer to a selection. Also add a layer style like set fill to 0 and adding a drop shadow and emboss. That is the un-expanded step below the set current layer is setting a style and is lengthy.
Crafting Actions Package UPDATED Aug 10, 2014 Added Conditional Action steps to Action Palette Tips.
Contains
Action Actions Palette Tips.txt
Action Creation Guidelines.txt
Action Dealing with Image Size.txt
Action Enhanced via Scripted Photoshop Functions.txt
CraftedActions.atn Sample Action set includes an example Watermarking action
Sample Actions.txt Photoshop CraftedActions set saved as a text file.
More then a dozen Scripts for use in actions
Example
Download

If you need help quickly... Guideline for posting an effective question.

Whenever you have a question that you would like answered, do pose that question effectively.
First, do not assume that because you have tried many, many times that your question is understood by someone else. What is obvious to you may not be for another. So please state in a very detailed and structured way what steps you have taken to cause your problem, how you can replicate this problem, under what circumstances on what hardware/software.
The fact that you have nearly given up because of your problem does not mean that someone else can readily understand this problem. When you go to your doctor and say: "I have a pain in my stomach" he will ask you a lot of questions. Same applies here. Your doctor may need to know about any medication you have taken, your blood pressure, history, etc. If you want help, be as PRECISE and ACCURATE as possible.
Second, this is a USER TO USER forum. So ranting will not help. What may help is a STRUCTURED approach to describing the problem you have.
Third, do a thorough search of posts here, on other fora and with Google before repeating what has been asked a thousand times and has worn out the patience of regulars here, who have answered your question a dozen times already. Use the FAQ and the Wiki to find answers to questions that have been posed and answered repeatedly. Do not assume you are unique with your problem. Well, you are unique, the problem you have most likely is not.
Fourth, realize that even though it may be highly frustrating to you to not be able to solve YOUR problem, by posting your question here, you are dependent on fellow editors to help you on their free time without compensation, so bear with them to help identify what EXACTLY is your problem. If you lack that decency, you may forfeit their help, so why did you come here?
Fifth, consider your work flow in light of the purpose of Premiere, an editing package. If you have problems with rotoscoping, programming with APL, spreadsheets in general, word processing on a mobile phone, importing Panda bears into a local zoo, feeding nearly distinct whales in the Alps, or anything far removed from the purpose of PP, you may be better off in posting your question elsewhere.
Last:
Everybody has to learn, has the right to ask questions and be helped.
If everybody has the decency to pose their urgent, life threatening or other questions in a detailed, structured and comprehensible way, it will vastly improve the chances of speedy and helpful replies, without the need for sarcasm, bundles of to-and-fro posts without meaningful help, just wasting bandwidth.
I know I have been rightly accused of such behavior, which was the result of sheer frustration with absolutely meaningless and often pointless questions without details, structure and the like. Maybe this can be a general guideline for posters on how to ask questions, in addition to Eddie's links and How to ask questions the smart way
The most frustrating issues one can encounter are hangs, BSOD's (blue screens of death), system errors and other cases of seemingly random erros that require rebooting, restarting or similar actions, only to be confronted with the next hang, BSOD or system crash.
These errors are often difficult to locate, due to the large variety of systems, components and driver or software versions in use. This is often further aggravated by sheer lack of expertise, understanding of what needs to be communicated in order for others to help solve the issue at hand. And that list is very long.
So, in order to make it a bit simpler for the average user who encounters these problems, follow the following steps when posting a problem:
1. Clearly describe the main problem in the topic, but be brief. Not so brief as to only say: "Help!" or "URGENT" or another meaningless statement but get to the point, like: "PP crashes on opening, requiring a reboot" or "Using DL the system hangs upon return to PP". You get the point.
2. Briefly describe your hardware, software, OS and versions in use, including disk setup, video card and driver versions, etc.
3. Describe source material, including codec (not AVI, which is not a codec), project settings and other relevant info.
4. Describe as accurately as possible what you did, what steps you took, what happened at what moment and what you did to try to resolve it.
5. Go to Start/Run, type in DXDIAG, enter and save all information to a TXT file. Include a link to that file in your post.
6. Go to Start/Run, type in MSINFO32 (or similar for 64 bit OS), enter and save the results as a .NFO file. Include a link to that file in your post.
7. Download Process Explorer , and either post a screen shot or a link to the results.
8. Make a screen shot of the results of SpeedFan or HW Monitor and include that in your post.
When you perform these basic steps, you avoid endless questions about your system and people may be able to help you faster.
If you feel up to it, take a look at The Case of the Unexplained to start your own troubleshooting.
Hope this helps to post more meaningful questions and get an answer much quicker.

Whenever you have a question that you would like answered, do pose that question effectively.
First, do not assume that because you have tried many, many times that your question is understood by someone else. What is obvious to you may not be for another. So please state in a very detailed and structured way what steps you have taken to cause your problem, how you can replicate this problem, under what circumstances on what hardware/software.
The fact that you have nearly given up because of your problem does not mean that someone else can readily understand this problem. When you go to your doctor and say: "I have a pain in my stomach" he will ask you a lot of questions. Same applies here. Your doctor may need to know about any medication you have taken, your blood pressure, history, etc. If you want help, be as PRECISE and ACCURATE as possible.
Second, this is a USER TO USER forum. So ranting will not help. What may help is a STRUCTURED approach to describing the problem you have.
Third, do a thorough search of posts here, on other fora and with Google before repeating what has been asked a thousand times and has worn out the patience of regulars here, who have answered your question a dozen times already. Use the FAQ and the Wiki to find answers to questions that have been posed and answered repeatedly. Do not assume you are unique with your problem. Well, you are unique, the problem you have most likely is not.
Fourth, realize that even though it may be highly frustrating to you to not be able to solve YOUR problem, by posting your question here, you are dependent on fellow editors to help you on their free time without compensation, so bear with them to help identify what EXACTLY is your problem. If you lack that decency, you may forfeit their help, so why did you come here?
Fifth, consider your work flow in light of the purpose of Premiere, an editing package. If you have problems with rotoscoping, programming with APL, spreadsheets in general, word processing on a mobile phone, importing Panda bears into a local zoo, feeding nearly distinct whales in the Alps, or anything far removed from the purpose of PP, you may be better off in posting your question elsewhere.
Last:
Everybody has to learn, has the right to ask questions and be helped.
If everybody has the decency to pose their urgent, life threatening or other questions in a detailed, structured and comprehensible way, it will vastly improve the chances of speedy and helpful replies, without the need for sarcasm, bundles of to-and-fro posts without meaningful help, just wasting bandwidth.
I know I have been rightly accused of such behavior, which was the result of sheer frustration with absolutely meaningless and often pointless questions without details, structure and the like. Maybe this can be a general guideline for posters on how to ask questions, in addition to Eddie's links and How to ask questions the smart way
The most frustrating issues one can encounter are hangs, BSOD's (blue screens of death), system errors and other cases of seemingly random erros that require rebooting, restarting or similar actions, only to be confronted with the next hang, BSOD or system crash.
These errors are often difficult to locate, due to the large variety of systems, components and driver or software versions in use. This is often further aggravated by sheer lack of expertise, understanding of what needs to be communicated in order for others to help solve the issue at hand. And that list is very long.
So, in order to make it a bit simpler for the average user who encounters these problems, follow the following steps when posting a problem:
1. Clearly describe the main problem in the topic, but be brief. Not so brief as to only say: "Help!" or "URGENT" or another meaningless statement but get to the point, like: "PP crashes on opening, requiring a reboot" or "Using DL the system hangs upon return to PP". You get the point.
2. Briefly describe your hardware, software, OS and versions in use, including disk setup, video card and driver versions, etc.
3. Describe source material, including codec (not AVI, which is not a codec), project settings and other relevant info.
4. Describe as accurately as possible what you did, what steps you took, what happened at what moment and what you did to try to resolve it.
5. Go to Start/Run, type in DXDIAG, enter and save all information to a TXT file. Include a link to that file in your post.
6. Go to Start/Run, type in MSINFO32 (or similar for 64 bit OS), enter and save the results as a .NFO file. Include a link to that file in your post.
7. Download Process Explorer , and either post a screen shot or a link to the results.
8. Make a screen shot of the results of SpeedFan or HW Monitor and include that in your post.
When you perform these basic steps, you avoid endless questions about your system and people may be able to help you faster.
If you feel up to it, take a look at The Case of the Unexplained to start your own troubleshooting.
Hope this helps to post more meaningful questions and get an answer much quicker.

Guidelines for setting Application Module Pool Size Parameters?

Are there guidelines for setting the application module pool size parameters, such as initial pool size, maximum pool size, etc., based on the expected number of users or other factors? I've read the developer guide sections (ch 28-29), but still don't have a good feel for how to correctly set the optimal values for the pool configuration parameters? Even more importanty, how do I monitor the pool's efficiency during runtime to determine if the pooling parameters are configured correctly?
This will be critical to performance and scalability, so I'm looking for a way to get some visibility into how the pooling is working during production operation to assess whether there are bottlenecks/constraints/ineffeciencies?
Note I am using Tomcat as the java runtime container; ADF BC / JSF jdev 10.1.3.1
Thanks in advance and Merry Christmas!

KUBA - were you able to resolve these issues and if so are there any lessons learned you can share?
I'm hoping someone from the ADF team can answer our original question including guidelines for setting pool parameters and how to monitor the pool's performance while running in production.
thanks

Open multiple PDFs in Photoshop at specific size for use with Actions

I am having a bit of a roadblock with batch Automate in Photoshop. I'd like to open multiple PDFs at 630p x 630p, 72 dpi in greyscale. I have 2000 files to do this on. If files are already open, the rest of my action works, does a few things, then saves for web as PNG. It is just the open which is not working. It tries to give all files the same filename. Taking the filename out of the Action is not an option. Scan of msg boards say that this feature stopped working around CS3. Any ideas? Much appreciated.

Open opens images the same size and resolution they are saved. If you want the images to be a particular size you need to do that in the action.
If you download my crafting actions package. You will find the there are over a dozen scripts I wrote to be used with in action. One is a plugin script that would be particularly helpful to you to do the resize you want to do. The first three steps would be Step 1 menu File>Automate>AspectRatioSelection.... You would set in a 1 to 1 Aspect ratio. Centered, rectangle. replace, selection and 0 feather. In its dialog. Those settings will be recorded into the Actions step. Step 2 menu Image Crop. that will make you image square. Step 3 menu File>Automate>Fit Image... In the Fit image dialog you would set 630 in the width and height fields. These settings will be recorded into the actions step. When the action is played no dialog will be displayed. The recorded settings will be used.
Crafting Actions Package UPDATED Aug 10, 2014 Added Conditional Action steps to Action Palette Tips.
Contains
Action Actions Palette Tips.txt
Action Creation Guidelines.txt
Action Dealing with Image Size.txt
Action Enhanced via Scripted Photoshop Functions.txt
CraftedActions.atn Sample Action set includes an example Watermarking action
Sample Actions.txt Photoshop CraftedActions set saved as a text file.
More then a dozen Scripts for use in actions
Example
Download

Looking for some creative guidelines for book formatting

I am formatting a book, my first one, and am about to start refining the overall formatting to make it look beautiful. I'm running into a bit of a creative block, and am looking for some basic guidelines for book formatting. I'm wondering about fonts, how many to use, ideas about heading heiarchy's, fonts for tables relative to the rest of my text, etc. I have everthing formatted, but it just looks ackward and ugly because I don't have a sensitivity to the standards.
Does anyone know of a resource where I could find some guidance on this?

craigatadobe12345 wrote:
I am formatting a book, my first one, and am about to start refining the overall formatting to make it look beautiful. I'm running into a bit of a creative block, and am looking for some basic guidelines for book formatting. I'm wondering about fonts, how many to use, ideas about heading heiarchy's, fonts for tables relative to the rest of my text, etc. I have everthing formatted, but it just looks ackward and ugly because I don't have a sensitivity to the standards.
Does anyone know of a resource where I could find some guidance on this?
Self-Publishers Start Here: Planning Your Book
This site is mostly about self-publishing, but don't dismiss it until you've searched through its archives and followed its links to other resources. There's plenty of good stuff!
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices

Guidelines for using CM27 & CM28

Similar Messages

Maybe you are looking for