Font auto conversion

Every time I place text into the InDesign document it is automatically converted to Arial Unicode MS Bold with underlines.  I want to turn this off, but can't figure out how.
metskate

^Right. It helps to remember that all the settings which are shown (in effect) when nothing is selected will be applied to eligible new content that is introduced. So, with nothing selected, if Arial Unicode MS Bold with underlines is set before you place text, the newly placed text will take on those settings.

Similar Messages

  • Raw auto conversion & showing items in modified folder

    Hi,
    When I shoot photo's, I let my camera create RAW and JPEG images. I manage to import those into iPhoto and show up nicely in the (event) viewer. I understand that iPhoto puts these into the original folder and while I'm also importing a RAW image, it also auto converts a JPEG copy and puts it into the modified folder.
    So far so good. However, when I need to modify a photo I normally use the RAW image file. What I would expect to happen after the RAW image modification is that :
    1)iPhoto makes an auto conversion and puts it in the modified folder (this happen and I find the modified JPEG in this folder)
    2)The original JPEG photo that is shown in the event viewer is "overlayed" with the modified one. I tried a lots of things till now but nothing seems to help?
    Does anyone know how to accomplish 2)??
    Further when I remove an event from the library (move to trash in viewer) I noticed the Photo files remain in the library package. It is possible to let iPhoto also remove the files from the library?
    Can I let iPhoto create (rebuild) a blank iPhoto library package, i.e. after I renamed the active one ( I want to create one for each year)?
    Thanks for your help

    MacFan_RJ:
    Welcome to the Apple Discussions. Regarding removing the files, are you emptying the iPhoto trash bin after moving the photo into it?
    Launch iPhoto with the Option key depressed and, when asked, select the option to create a new library. If you play on having multiple libraries I suggest you use iPhoto Library Manager to manage them and allow you to easily move between them. I have 18 libraries that I manage. With the paid version of iPLM you can copy events or album between libraries while maintaining keywords, comments and titles.
    On editing RAW and saving the new jpg, I've not found a way to get the new edited version into the correct Modified folder, replace the current modified file and update the thumbnail to reflect the edit. It appears that those edits will have to be saved to the desktop and imported a new files.
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • Font Auto-Activation Not Working After First Use

    Anyone else seeing this problem, or have a fix? Font auto-activation stops working after the first use. Here's what happens: Open a file that contains a font that is installed, but is disabled in Font Book. The dialog box "Application wants to use the font XXX". Click on Allow. The font will be available, as you expect. Now quit the application. Open the file again - you won't get the dialog box asking permission to use the font, and the font is not available. This happens in Pages 3.0.1 and TextEdit 1.5. It happens for each individual font - in other words, continuing my description, if you now open a second file that has another font that is disabled in Font Book, you'll be asked permission to use it. But once you've allowed a particular font to be used, you won't be asked permission again.

    Make a backup.  Restore the device as new.  Test the issue again.  If it persists, your device needs service.  If the issue disappears, restore your backup.  If it then reappears, then there is some form of corrupt data on the device from the backup.  You'll have to restore that data one portion at a time to determine what is causing it, or set up the device as new.

  • Auto conversion of planned order to production orders

    Hi Gurus,
    Few days back I posted a question on; Auto conversion of planned order to production orders.
    http://forums.sdn.sap.com/thread.jspa?threadID=2135568&tstart=0
    There is standard SAP Transaction to run a batch job. no need to use - user exit or a BAPI
    Follow this procedure:
    TCode: COHV
    on the initial screen; select "CHECK BOX" for planned orders and deselect production orders.
    select mass processing tab.
    Function: 210 Convert planned orders.
    On Menu-Programs-Execute in background
    Thanks

    HI Alok,
    I was looking at CO41 and there is only one small problem with that. You have to give an 'Order Type' as a input. And I don't see 'Execute in the background' anywhere. I think I have to create a job using wizard in SM36.
    Please correct me if I'm wrong.
    Thanks

  • Temporary disable Font auto-activation(UTC)

    Is there a way via javascript to temporarily disable and then reenable the Extensis UTC Font auto-activation for Indesign files?
    I have a script that loops through and opens a file, edits it, exports it and then reverts and does it again for x number of pages. The script used to work fine when manually enabling and disabling fonts but not we have had a few font issues in the PDFs and we're thinking it has to to with the auto-activation interrupting the script or something like that.
    Since the file is opened manually the first time that would allow the auto activation to occur once. The script would then run and disable it, do all the edits. exports. and reverts and then when its done enable auto-activation again.
    Let me know if you have any ideas or if you happen to already know the about the issue.
    Thank you

    Hi,
    Everything is normal, it's the result of the command
    To disable auto activating font
    autoactivation -d
    Result -->  auto activation globally changed to AutoActivationDisabled
    To enable auto activating font
    atsutil autoactivation -e
    Result --> auto activation globally changed to AutoActivationEnabled

  • InDesign CS5 crashing on launch due to font auto-activator issue

    I was having a problem where all the jobs I had been collecting would no longer open in InDesign CS5 without crashing on startup. Just found out today it has to do with the new feature in CS5 that reads fonts from your "Document Fonts" folder. Once I renamed the folder the files started opening up just fine again. Is there a way to disable that feature in InDesign, or has anyone else found another workaround that doesn't involve renaming the folder on every job I collect?
    I'm sure it's a known issue by now, but I didn't see anything come up when I did a search.

    Same problem here. Whenever I want to open a packaged InDesign document which includes a Document Fonts folder containing some fonts which are identical to my system fonts (10.7.3 in my case) InDesign hangs. The best way to avoid these problems is to clean all system font folders and start managing fonts yourself. Check what fonts are needed for a certain document, avoid using fonts installed by the system. Although it is very generous from Apple, Adobe and Microsoft to give us a lot of fonts for free it is wise to manage them yourself. Check the following font locations:
    ~Library/Fonts
    ~System/Library/Fonts
    ~User/Library/Fonts (first make the Library visible: from within Terminal type the following command and press Return: chflags nohidden ~/Library)
    Remove all fonts installed by Adobe (109 fonts) and Microsoft (154 fonts) to a differrent location. I manage them with FontExplorer 3.0 but you are ofcourse free to use any other font manager you prefer. Clear out any system font which is not needed by the system. Make sure the removed fonts can be enabled when needed. In FontExplorer you can create a set like 'Adobe CS5 Fonts' and put all Adobe fonts in there. This also counts for Apple system fonts which you remove. Create a new set in FontExplorer and call it OS Lion Fonts for example and move all fonts in there. I'd like to point out that I choose to manage fonts myself and I keep FontExplorer's capabilities to organaise fonts turned off (Preferences > Advanced > Organise font files). This way the Finder structure I use to manage my fonts (which is by foundry/designer) is maintained.
    Clearing all unneeded fonts keeps the font list short and uncluttered which makes it easy to select fonts in InDesign or any other app. When you are designing things you want to make a selection of fonts you want to use in advance so keeping a lot of fonts available to the system is pointless in my opinion anyway.
    Also, this process gets rid of a lot of fonts which you don't use/need  like Chinese or whatever other language fonts. It shortens the font list dramatically. Setup font auto activation/deactivation so that fonts are disabled automatically after reboot or when you close a document to prevent the font list from growing out of proportions.
    Below is the list of fonts which I keep installed/enabled by default in my ~System/Library/Fonts folder:
    Apple Color Emoji.ttf
    Apple Symbols.ttf
    AppleGothic.ttf
    Courier.dfont
    Geneva.dfont
    HelveLTMM
    Helvetica LT MM
    Helvetica.dfont
    HelveticaNeue.dfont
    HelveticaNeueDeskUI.ttc
    Keyboard.ttf
    LastResort.ttf
    LucidaGrande.ttc
    MarkerFelt.ttc
    Menlo.ttc
    Monaco.dfont
    Symbol.ttf
    Times LT MM
    Times.dfont
    TimesLTMM
    ZapfDingbats.ttf
    I haven't checked Times yet but I think it can be disabled. If you think Times is causing problems and you rather want to activate it yourself when it is needed or you want to use it you can remove it from the ~System/Library/Fonts folder. Drag the font to the desktop to make a copy first. Next trash the font file. Enter your admin password end you're done. If a font is needed by the system it gets restored automatically and you get a notification like "The system font 'HelveticaNeue.dfont' had been restored. This font was removed. Mac OS X needs this font to display text onscreen."
    If you don't use FontExplorer you can use Onyx to clean font caches when you are done clearing out unwanted fonts. Always reboot afterwards.
    Hope this helps.

  • Universal Type Client font auto activation?

    My font auto activation using Universal Type Client does not seem to work. I have to open my file using Illustrator 5.5 to auto activate the font, then re-open the same file in CC for it to work.
    Any ideas?

    It's so odd. I have a file that I rebuilt using Keith Gilbert's method, That got two of us to be able to open the file, Now some users report slow performance on the file others can work in it fine. Same deal with other files, I can work in a file with no slowdowns, Others complain about poor performance. I believe all things are equal on the machine/ software side.
    If the network were funky, could this be a cause since all the images are linked to the network? I would not think it is that because the trouble is only in these files, not other ones we work in. I think it has something to do with changing the 'Basic" style to a different typeface. That is the time when we seemed to experience trouble. I am stumped. Thanks for the replies Peter.

  • Why are these fonts auto activating?

    I've just updated to Tiger 10.4.8. One day later I install CS2 (previously had CS).
    I use FontAgent Pro. Now, whenever I open Safari or any CS2 app. (just the app, not an actual document) a bunch of fonts are auto activated which I don't want to be activated, and as far as I know don't need to be activated. They are Devangari MT, Geeza Pro, Gujarati MT, Gurmukhi MT, Hirangino Kaku Gothic Pro, LiHei Pro, STHeiti, Times, and Photoshop also auto activates Osaka.
    Can anyone throw any light on this? I've posted in the Adobe forum (as not really sure if it's a mac thing or an adobe thing) but had no answers. Thanks

    Hi Kathydate,
    It doesn't matter what manager a person may be using. If any of the Fonts folders have something in them, they will be active. Check these folders for the fonts.
    /System/Library/Fonts/
    /Library/Fonts/
    ~/Library/Fonts/ (the tilde means your home account)
    The Adobe apps have their own folder at:
    /Library/Application Support/Adobe/Fonts/
    If there are any fonts in that folder you want to remove, do not remove the folder "Reqrd" or any of the items in it. The Adobe apps need those fonts to operate.
    For more details on font locations and which you can remove, see my article, Font Management in Mac OS X Tiger and Panther.

  • Auto conversion of Perchase req to Po

    Hi,
    How to convert a req to po. As I checked auto po in material(purchaisng tab) and checked in purchasing data(control tab) of this vendor also. Where couild I be wrong? When I look at Stock requirements(MD04), it stays as req?
    Thanks in advance.

    Hi,
    I forgot to run me59. Thanks for the same.

  • Missing fonts auto replacement

    Hi,
    Please help me with my font issue.
    When I open *.psd file in Photoshop Elements 10 it gives me warning message about font Helvetica I have used.
    I know that the Helvetica fonts have already been added to the Photoshop font list.
    Here is a warning message:
    That happens because the original Text layer has been created using Helvetica fonts.
    If I navigate to Layer>Type>Replace Missing Fonts PE10 replaces them to "Myriad Pro" instead of "Helvetica".
    If I ignore warning and navigate to layer with missing fonts PE10 popups this warning message:
    "The following fonts are missing for text layer "layername": 
    HelveticaNeueCE Bold
    Font substitution will occur. Continue? "
    When I am hitting "Continue" button PE10 replaces font to "Myriad Pro". Same replacement occurs with HelveticaNeue Roman.
    After that I have to manually change font type of this layer to "Helvetica Neue LT Std". 
    I have checked what Helvetica fonts are installed in the Windows, here is a list:
    Helvetica Neue LT Std 45 Light 
    Helvetica Neue LT Std 75 Bold 
    Helvetica Neue LT Std 85 Heavy
    How to force PE10 to automatically replace fonts to  "Helvetica Neue LT Std" instead of "Myriad Pro"?
    Why does Photoshop ignore a font installed in the font directory?
    Kind Regards,
    Egor.

    Form my understanding you can't replace missing fonts until the document is open. To avoid the missing fonts modal dialog, you can set
    app.scriptPreferences.userInteractionLevel = UserInteractionLevels.NEVER_INTERACT;
    before opening the document and then make your font substitutions. Don't forget to reset the userInteractionLevel when your script is done!

  • DW CS3: Auto Conversion of Special Characters?

    In DW 8 special characters entered or pasted into the text in
    Design view, were automatically converted to & encoded values.
    If you were typing ø, ø was inserted in the code.
    This was very usefull when pasting large portions of non-English
    text.
    It seems that this feature has been disabled in DW CS3. Why?
    How do I enable this feature again?

    BennyO wrote:
    > It seems that this feature has been disabled in DW CS3.
    Why? How do I enable
    > this feature again?
    The feature has not been disabled. The default encoding in
    CS3 is UTF-8,
    which supports accented characters without the need to
    convert them to
    HTML entities, such as ø. All modern browsers
    support UTF-8, so
    there should be no need to use HTML entities, unless you are
    saving
    content in a database that doesn't also support UTF-8 (MySQL
    3.23 or
    4.0, for example).
    If you want to go back to using HTML entities, change the
    default
    encoding to Western European (iso-8859-1).
    David Powers, Adobe Community Expert
    Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
    Author, "PHP Solutions" (friends of ED)
    http://foundationphp.com/

  • Why to auto conversion?

    Working on a PC with PS5. Why are RAW files automatically being converted to JPGs when opened in PS5? I want them to stay RAW files until I've processed them, then I will export them as JPGs. What is happening?

    Hudechrome wrote:
    First off, there is a missing post before post #3 by Noel.
    I was sent a private eMail.
    Hudechrome wrote:
    When you click "Open" in ACR, you get a screen which gives options for saving; Location and output parameters desired, The options for output include jpeg, dng, tiff, etc. Open the last drop down menu and tell ACR what form you want it. ACR will then pick the correct extension. I suspect it's set for jpeg.
    That's not at all what I see.
    With Bridge open, I'm looking at the CONTENT tab, in which I have several of my .CR2 raw files.
    I highlight two of them, using the Control key to add the second one to the batch that have a darker background.
    I double-click either of the highlighted raw files, and voila, Camera Raw opens.
    I click the [Select All] button at the upper left, then the [Open Images] button and after a few seconds both images open in Photoshop as Raw files.
    I apparently missed the dialogs you mentioned, Lawrence.
    -Noel

  • Packed decimal auto conversion

    Hi
    I have an input field that is of type P , with decimals 3.
    so if I enter 3000 , then it will take 3.000 .
    I want it to be so ,, when user enters 3 , it automatically converts it to 3.000 and if the user enters 3.2 , then it converts it to 3.200 , .
    How can I achieve this.
    Thankyou

    Hi Krish,
    I understand what you need, please look this code:
    DATA: lenght(2), cont(2), contv(1), teste(1), lenghtv(1).
    PARAMETERS: p1(10).
    lenght = strlen( p1 ).
    cont = 0.
    contv = 0.
    DO lenght TIMES.
      teste = p1+cont(1).
      cont = cont + 1.
      IF teste = ',' OR teste = '.'.
        contv = 1.
        lenghtv = lenght - cont.
        IF lenghtv = '0'.
          CONCATENATE p1 '000' INTO p1.
        ELSEIF lenghtv = '1'.
          CONCATENATE p1 '00' INTO p1.
        ELSEIF lenghtv = '2'.
          CONCATENATE p1 '0' INTO p1.
        ENDIF.
      endif.
    ENDDO.
    if contv = 0.
      CONCATENATE p1 ',000' INTO p1.
    endif.
    WRITE p1.
    Regads
    Allan Cristian

  • Font to auto size

    How do you make the font auto size to fit in the text field, so that you can view everything that has been typed in and not get the black box with the plus sign?  I have checked the auto fit for width and length, but it still does not auto fit.
    Thank you very much,
    EC

    Select the Object
    Go to Font Palette
    Make sure you are edting Value properties only (Not Caption or both)
    Change Font size to "0" (zero)
    Preview in PDF. The font will be large and then decrease as more characters are added.
    Make sure under Paragraph you are aligned in the Middle or Top (it doesn't seem to work when aligned on the Bottom.

  • Conversion of 1.2 JATO project (non-Forte IDE) to S1AF (JATO) 2.0

    JATO Team,
    First of all, thank you very much for the Studio integration. It
    looks very promising in terms of development time consumption,
    deployment to S1AS7, etc., etc. It is impossible to observe all
    advantages for so short period of time.
    The SOAF (JATO) 2.0 is installed on the top of the Sun ONE Studio 4,
    update 1 (EE) with JDK 1.4 along with the Sun One Application Server
    7 (W2000). Everything looks okay, at least all basic tasks listed in
    the "Getting Started" manual (project/view/model creation, basic db
    connection, running of a test application with the usage of the
    Studio's default Tomcat container, etc.) work proper.
    During the installation of S1AF module on the top of the Sun ONE
    Studio 4, update 1 (EE) I've got an invitation to convert the
    existing project to the new environment. As I realized the only JATO
    project integrated/created with Forte IDE is applicable for this auto-
    conversion (please correct me, if I am wrong. It could solve a lot of
    my problems).
    Since we are using JBuilder5 IDE and our JATO 1.2 project is
    integrated with this IDE I manually re-created project in the Studio
    with its file structure, adjusted the project web.xml file, etc. This
    new project looks like a proper one (Studio recognize all methods,
    fields, bean patterns, e.g.) except at least one "small" thing. All
    java files (project viewBeans, Models, custom viewBeanHelpers a.k.a.
    pure java) came up with the same wizard image:java class. Stutio with
    the S1AF module reserves the special images (and appropriate studio
    properties, of course!) for View and Model. Namely this allows to see
    the following structure for a ViewBean, for example, in the Studio:
    Modules
    ProjectName.ModuleName
    FooViewBean
    JavaSource
    JSPs
    Non-Visual Components
    View Components
    On the other hand, I could add either new View or Model in my
    manually converted project and add any View Component or bind the
    Model fields, for example. Also, the ProjectModuleServlet has been
    converted proper. I tried to convert each View/Model class inside the
    Studio to its proper wizard image and failed. Addition of a View
    Components (with an appropriate code fragments) via the Studio or
    auto-binding of model fields is an essential part of 2.0 and should
    drastically speed up the development process as it is designed.
    Questions:
    1. What I missed in my manual conversion of 1.2 JATO project to the
    SOAF (JATO) 2.0 realm? What should I correct in my JATO 1.2
    compatible classes (Views and Models) to be recognizable by Studio
    wizard (JATO 2.0)?
    To be more specific. Some deltas between JATO 1.2 and JATO 2.0 are as
    follows (related to a ViewBean):
    ====++++++++++++++======
    JATO 1.2 viewBean extension upon creation:
    public class FooViewBeanViewBean extends ViewBeanBase
    implements ViewBean
    ========================
    JATO 2.0 (S1AF) version: viewBean extension upon creation:
    public class FooViewBean extends BasicBeanBase
    ====++++++++++++++======
    JATO 1.2 viewBean createChild(...) method for one static looks
    like:
    protected View createChild(String name)
    if (name.equals(CHILD_STATICTEXT1))
    StaticTextField child = new StaticTextField
    (this,
    getDefaultModel(),
    CHILD_STATICTEXT1,
    CHILD_STATICTEXT1,
    CHILD_STATICTEXT1_RESET_VALUE,
    null);
    return child;
    ========================
    JATO 2.0 (S1AF) version: viewBean createChild(...) is renamed (as
    a least) to createChildReserved(...):
    protected View createChildReserved(String name) {
    if (name.equals(CHILD_STATICTEXT1)) {
    com.iplanet.jato.view.BasicDisplayField child =
    new com.iplanet.jato.view.BasicDisplayField(this,
    STATICTEXT1);
    return child;
    ====++++++++++++++======
    JATO 1.2 viewBean registerChildren() method for the basic field
    types looks like:
    private void registerChildren() {
    registerChild(CHILD_STATICTEXT1, StaticTextField.class);
    registerChild(CHILD_TEXTFIELD1, TextField.class);
    registerChild(CHILD_BUTTON1, Button.class);
    ========================
    JATO 2.0 (S1AF) version: viewBean registerChildren() method:
    private void registerChildren() {
    registerChild(CHILD_STATICTEXT1,
    com.iplanet.jato.view.BasicDisplayField.class);
    registerChild(CHILD_TEXTFIELD1,
    com.iplanet.jato.view.BasicDisplayField.class);
    registerChild(CHILD_BUTTON1,
    com.iplanet.jato.view.BasicCommandField.class);
    Is it correct to say that all existing custom Views/Models
    (compatible with JATO 1.2) should be converted to their JATO 2.0
    variants to be visible by the Studio?
    On the other hand, fast overview of 2.0 API shows that the JATO 1.2
    is a sub-set of the 2.0 (BasicViewBean extends ViewBeanBase, for
    example). What exactly (only deprecated methods?) should be adjusted
    in the project code (1.2), if necessary, to be visible by Studio as a
    View or Model component?
    2. Where it is possible to find the list of deprecated methods (from
    JATO 1.2 to JATO 2.0 versions). It is difficult sometimes to compare
    two versions of API docs (1.2 and 2.0) or compare logs between
    versions. Also, JATO 2.0 is significantly larger than 1.2 version. If
    the later obviously inherits the ND conversion stage (via the
    previous versions), the former obviously has additions incoming from
    the integration with the Studio (a.k.a. Forte 4.0).
    3. What is the current/future Sun/JATO Team policy with regards to
    JATO source code access (version 2.0, at least)? The reason of this
    question is as follows: in order to display dates formatted on the
    screens we adjusted a couple of JATO 1.2 core classes, for example.
    The only minimal, absolutely necessary changes in JATO 1.2 was made,
    but anyway...
    Sorry for so long multiple question. As Todd wrote in his
    announcement mail: "We think you will be very pleased with the new
    product...". This is exciting moment, I believe, for JATO Team as
    well as for any team involved into the conversion of the full size
    application/product from ND to J2EE realm with the JATO as
    an application framework (1.0, 1.1.x, 1.2.X, and 2.0 finally). The
    last step is left in this spiral process to enjoy the ND_Studio
    attractive features in the open source environment.
    Thank you very much in advance.
    Vladimir Ivanov

    I'll get some file templates ASAP and provide them to the group.
    As for source code, I'm not sure what the policy is. JATO 1.2 is very
    close to what JATO 2.0 is, so that should suffice for now.
    The community will be informed when we know more about source availibility.
    craig
    vivanov4114 wrote:
    Craig,
    Thank you for the answer. To be honest with you I tried to do exactly
    the same: I created the small test project and made an attempt to
    adjust the existing *.xml files to the new ones. I got some results,
    otherwise I couldn't even see my original 1.2 project in the Studio.
    Since I am a newcomer in the Studio, I definitely missed something in
    my adjustments. I'll try to observe my changes with the fresh head.
    On the other hand, I am afraid that my samples are very pure. If you
    could post or send me examples of jatoapp.xml and web.xml files (say
    for any of you test project) or excerptions from them with the
    appropriate patterns (ViewBean and Model peers, at least), I would be
    very appreciated. My mail is: vivanov@b...
    In the worst-case scenario I see the workaround: to re-create the
    project for one of our releases with the Forte 4.1 IDE and auto-
    convert it into the JATO 2.0/Studio world using the Studio
    facilities. We must get the current project fully
    integrated/converted with/to the Studio (at certain point) because,
    first, we expect massive coding with the GUI components involved soon
    and, secondly, we have around thousand classes related to JATO only
    (and a lot of extras).
    Coming back to the question #3 from this post. Now we have full
    access to the version 1.2, not only to the JATO 1.2 jar file(I
    explained some reasons below). Would we expect the same Sun/JATO Team
    policy with JATO 2.0?
    Thank you again,
    Vlad
    --- In SunONE-JATO@y..., "cvconover" <craig.conover@s...> wrote:
    It doesn't appear that anyone has responded to this so I am goingto
    give you the short answer:
    The reason you don't see your ViewBeans and Models showing up with
    there "wizard created" icons is because of just that. They weren't
    created via the wizards. The wizards create xml formatted filesthat
    contain metadata of how/what to generate for the ViewBeans and
    Models.
    ViewBeans will have a .viewbean fiel, Models will have a .sqlmodel
    file (for SQL Models), etc. The content of these files describesthe
    code that needs to be generated in the corresponding Java classfile.
    So LoginViewBean.java will have a peer LoginViewBean.viewbean file.
    The code that is generated is place in protected code blocks thatcan
    not be modified in the Studio and should not be modified outsidethe
    Studio because the code will likely be regenerated and custom mods
    inside the protected blocks will be lost.
    Now you can make a JATO 1.2 app appear in the Studio just like aJATO
    2.0 app by adding a jatoapp.xml file with the proper content and
    adjusting your web.xml properly, but it's much more work to getyour
    v1.2 ViewBeans and Models to show up like wizard created versions.
    Furthermore, even more work to get the display fields to show up
    visually.
    The good news is that v1.2 ViewBeans will work with newly wizard
    created ViewBeans. And if you do go through the trouble of making
    your ViewBeans Studio visible like your wizard created ViewBeans,
    adding new display fields visually will work along side yourmanually
    created fields.
    Try creating a new JATO app using the Studio wizards and then go to
    the Filesystems tab and look for the jatoapp.xml file and theweb.xml
    file.
    I am looking for an email that I have that explains how to do a
    partial, manual upgrade.
    Also, you will get rid of your JATO 1.2 jar and replace with theJATO
    2.0 jar in your lib dir.
    Hope this will suffice for now.
    craig
    --- In SunONE-JATO@y..., "vivanov4114" <vivanov@b...> wrote:
    JATO Team,
    First of all, thank you very much for the Studio integration. It
    looks very promising in terms of development time consumption,
    deployment to S1AS7, etc., etc. It is impossible to observe all
    advantages for so short period of time.
    The SOAF (JATO) 2.0 is installed on the top of the Sun ONE Studio4,
    update 1 (EE) with JDK 1.4 along with the Sun One ApplicationServer
    7 (W2000). Everything looks okay, at least all basic tasks listedin
    the "Getting Started" manual (project/view/model creation, basic
    db
    connection, running of a test application with the usage of the
    Studio's default Tomcat container, etc.) work proper.
    During the installation of S1AF module on the top of the Sun ONE
    Studio 4, update 1 (EE) I've got an invitation to convert the
    existing project to the new environment. As I realized the onlyJATO
    project integrated/created with Forte IDE is applicable for thisauto-
    conversion (please correct me, if I am wrong. It could solve a
    lot
    of
    my problems).
    Since we are using JBuilder5 IDE and our JATO 1.2 project is
    integrated with this IDE I manually re-created project in theStudio
    with its file structure, adjusted the project web.xml file, etc.This
    new project looks like a proper one (Studio recognize all
    methods,
    fields, bean patterns, e.g.) except at least one "small" thing.All
    java files (project viewBeans, Models, custom viewBeanHelpersa.k.a.
    pure java) came up with the same wizard image:java class. Stutiowith
    the S1AF module reserves the special images (and appropriate
    studio
    properties, of course!) for View and Model. Namely this allows tosee
    the following structure for a ViewBean, for example, in the
    Studio:
    Modules
    ProjectName.ModuleName
    FooViewBean
    JavaSource
    JSPs
    Non-Visual Components
    View Components
    On the other hand, I could add either new View or Model in my
    manually converted project and add any View Component or bind the
    Model fields, for example. Also, the ProjectModuleServlet hasbeen
    converted proper. I tried to convert each View/Model class insidethe
    Studio to its proper wizard image and failed. Addition of a View
    Components (with an appropriate code fragments) via the Studio or
    auto-binding of model fields is an essential part of 2.0 and
    should
    drastically speed up the development process as it is designed.
    Questions:
    1. What I missed in my manual conversion of 1.2 JATO project tothe
    SOAF (JATO) 2.0 realm? What should I correct in my JATO 1.2
    compatible classes (Views and Models) to be recognizable byStudio
    wizard (JATO 2.0)?
    To be more specific. Some deltas between JATO 1.2 and JATO 2.0are
    as
    follows (related to a ViewBean):
    ====++++++++++++++======
    JATO 1.2 viewBean extension upon creation:
    public class FooViewBeanViewBean extends ViewBeanBase
    implements ViewBean
    ========================
    JATO 2.0 (S1AF) version: viewBean extension upon creation:
    public class FooViewBean extends BasicBeanBase
    ====++++++++++++++======
    JATO 1.2 viewBean createChild(...) method for one static looks
    like:
    protected View createChild(String name)
    if (name.equals(CHILD_STATICTEXT1))
    StaticTextField child = new StaticTextField
    (this,
    getDefaultModel(),
    CHILD_STATICTEXT1,
    CHILD_STATICTEXT1,
    CHILD_STATICTEXT1_RESET_VALUE,
    null);
    return child;
    ========================
    JATO 2.0 (S1AF) version: viewBean createChild(...) is renamed(as
    a least) to createChildReserved(...):
    protected View createChildReserved(String name) {
    if (name.equals(CHILD_STATICTEXT1)) {
    com.iplanet.jato.view.BasicDisplayField child =
    new com.iplanet.jato.view.BasicDisplayField(this,
    STATICTEXT1);
    return child;
    ====++++++++++++++======
    JATO 1.2 viewBean registerChildren() method for the basic field
    types looks like:
    private void registerChildren() {
    registerChild(CHILD_STATICTEXT1,
    StaticTextField.class);
    registerChild(CHILD_TEXTFIELD1, TextField.class);
    registerChild(CHILD_BUTTON1, Button.class);
    ========================
    JATO 2.0 (S1AF) version: viewBean registerChildren() method:
    private void registerChildren() {
    registerChild(CHILD_STATICTEXT1,
    com.iplanet.jato.view.BasicDisplayField.class);
    registerChild(CHILD_TEXTFIELD1,
    com.iplanet.jato.view.BasicDisplayField.class);
    registerChild(CHILD_BUTTON1,
    com.iplanet.jato.view.BasicCommandField.class);
    Is it correct to say that all existing custom Views/Models
    (compatible with JATO 1.2) should be converted to their JATO 2.0
    variants to be visible by the Studio?
    On the other hand, fast overview of 2.0 API shows that the JATO1.2
    is a sub-set of the 2.0 (BasicViewBean extends ViewBeanBase, for
    example). What exactly (only deprecated methods?) should beadjusted
    in the project code (1.2), if necessary, to be visible by Studio
    as
    a
    View or Model component?
    2. Where it is possible to find the list of deprecated methods(from
    JATO 1.2 to JATO 2.0 versions). It is difficult sometimes tocompare
    two versions of API docs (1.2 and 2.0) or compare logs between
    versions. Also, JATO 2.0 is significantly larger than 1.2
    version.
    If
    the later obviously inherits the ND conversion stage (via the
    previous versions), the former obviously has additions incomingfrom
    the integration with the Studio (a.k.a. Forte 4.0).
    3. What is the current/future Sun/JATO Team policy with regards
    to
    JATO source code access (version 2.0, at least)? The reason ofthis
    question is as follows: in order to display dates formatted onthe
    screens we adjusted a couple of JATO 1.2 core classes, forexample.
    The only minimal, absolutely necessary changes in JATO 1.2 wasmade,
    but anyway...
    Sorry for so long multiple question. As Todd wrote in his
    announcement mail: "We think you will be very pleased with the
    new
    product...". This is exciting moment, I believe, for JATO Team as
    well as for any team involved into the conversion of the fullsize
    application/product from ND to J2EE realm with the JATO as
    an application framework (1.0, 1.1.x, 1.2.X, and 2.0 finally).The
    last step is left in this spiral process to enjoy the ND_Studio
    attractive features in the open source environment.
    Thank you very much in advance.
    Vladimir IvanovTo download the latest version of JATO, please visit:
    http://www.sun.com/software/download/developer/5102.html
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    [Non-text portions of this message have been removed]

Maybe you are looking for