Organizing for stock library. Projects, folders or albums?

This may have been talked about to death, but I cannot find a thread that fits my question.
I have a growing library of images in Aperture. I am also a stock photographer by living. My library in Aperture is somewhat haphazard and I'm trying to organize it so that I can have it make sense. I do not sell my photos as stock myself (I submit to several agencies) so I'm not sure that I need to file my images so that I can get to them if a client needs a shot. That's what the agencies are for.
My work flow is something like this:
1 - shoot pix
2 - import and edit (read: delete) images in Aperture
3 - prepare and submit images to agencies
4 - next....
I do find myself taking pix of many of the same subjects, so I do want to organize them in Aperture.
My main question is, what is the best, or most efficient, way to organize major subjects in the library, with Projects, Folders, or Albums?
For instance, I shoot a production with models. That could be a project titled " August 14 production." When the submission is done, i could archive the entire project to save space. But, suppose I want to keep some around to submit to a different agency. Is a project the best way to store this?
Also, I find myself shooting a lot of NYC landmarks. Should each landmark be in its own project, or have it be an album in a project called NYC, or should it be a project in a folder called NYC?
I'm really not sure what the most efficient filing method is for my business.
Any discussion and/or advice is GREATLY APPRECIATED!
Antonio

gustavus:
n attempting to relocate a folder it did not end up where intended and I cannot find it.
I hope you are referring to doing the relocation from within iPhoto and not in the Finder and the library package. Any moving, renaming of files and/or folder inside the iPhoto Library Package while in the Finder is tantamount to the cardinal sin of iPhoto, Don't tamper with files in the iPhoto Library folder from the Finder. That will mess up your library to where you may have to start over with a new library.
Can you describe where these folders and albums were located when you were moving them?
Do you Twango?
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.

Similar Messages

  • Importing iPhoto `11 Library Lost Folders & Nested Albums

    Been using iPhoto since its' inception. Currently at iPhoto `11. Had created many Albums and Smart Albums based on Keywords and had most of them organized into Folders in iPhoto.
    Just bought Aperture 3 and, following the video tutorial provided by Apple, imported my 9,000+ iPhoto Library into it. However, only albums that resided at the top level in the sidebar of iPhoto made it into Aperture. All Folders and any Albums and Smart Albums that resided inside those Folders were not imported into Aperture.
    I have verified that all photos contained within the missing Folders and Albums have made it into Aperture, just not the Folder and Album hierarchies I had created over the years.
    Do I need to delete the Aperture Library and re-import the iPhoto Library again using other settings?

    Thanks for the reply Terrence. I'm still a bit confused by some contradictory behavior of Aperture.
    The Aperture Manual states (p.112):
    +"The organization of your iPhoto images and albums is maintained as projects in the Projects panel."+
    Well, not actually. Only EVENTS seem to be maintained as Projects when imported from iPhoto. My iPhoto library contains 1189 Events. Aperture now has 1185 Projects after the iPhoto import. But Projects does not contain any of the album organization that had been created in iPhoto.
    The Aperture Manual further states (p.112):
    "+You cannot import slideshows, books, and Smart Albums from your iPhoto Library."+
    Well, actually, Aperture DID import 5 of my Smart Albums. But these were only the Smart Albums at the top level of iPhoto's sidebar. All other Smart Albums nested inside folders in iPhotos sidebar were not brought over.
    So I'm confused.

  • Making best use of projects, folders, and albums

    I do think I understand the difference between how these function. For example, an image can be in only one project, but can be in multiple albums while in that project. Not sure if the same is true of folders. My question is how do experienced users utilized these three things to create an efficient filing system? I have one other caveat—I want to be able to sync photos manually to my iPad without have an extra layer to navigate. For example, when I created a project called iPad Photos and then had albums in the project, even though I checked only the albums for syncing, they still showed up on the iPad as nested within the Project.
    I hope this makes sense—if need be, ignore the iPad issue and please help me create a filing system that will be efficient and effective over the long haul.
    Many thanks—I know this seems simple but I am sure it would be easy to create a system that works well with 100 images but is a disaster with 1,000 images when it comes to putting those images to various kinds of use: slideshows, photo books, simple prints, etc.
    Ben

    Ben,
    have you looked at Kirby Krieger's user tip?
                     The Well-Trod Path: a Beginner's Guide to how Aperture's major parts inter-relate
    For example, an image can be in only one project, but can be in multiple albums while in that project.
    Pojects are the basic longterm storage structure - an image needs to be stored somewhere, and only once. That is, why an image and all its different versions are contained in one project. I have basically one project for each occasion - I create a new project, each time I download new images to Aperture, and related projects are grouped by folders. A typical folder with images taken during a holiday trip would have a project for each day of taking pictures at different stations of the journey.
    Albums are your own shortterm retrival structure. You group you images differently for different purposes, depending on how you want to use them.  The same image can have different uses at the same time, so it can be used in different albums. For example, a photo showing an orchid in Peru would go ino three albums: an album of Peru images, an album of flowers, and album of my latest trip to Peru. I also group my albums by folders - a folder of travel albums, a folder with thematic albums (flowers, lighthouses, vulcanos, wildlife,etc.), a folder with family albums, a folder with albums used for teaching, for research, for testing.
    Many of my albums are smart albums. Rather than adding photos manually to albums, I tag them with keywords, places, faces, and ratings, and they will be added to the corresponding albums automatically. My keywords have different flavors - there are keywords for categories (flowers, animals,landscape, buildings), for different uses (screensaver, web, books, iPad), for the technical quality (the camera or scanner, the kind of processing of raytraycing). So my album for my screensaver of lighthouse pictures would be based on the keywords _Screensaver, building:lighthouse, *****.
    Albums I sync to my iPad are also smart albums, and are not grouped with the projects but in a separate folder and also smart albums. I only sync the albums with 5* images for specific topics to the iPad. wildlife pictures, flower pictures, birds, some family meetings, travel albums.
    Regards
    Léonie

  • Tables for Stock and project stock

    Hi Friends,
                               I have to create a report consists of Material No. Stock Qty, WBS Element, Batch NO..So Please convey the Tables and fields.
    Regards

    Hi Prasanna,
    Find below the details for
    1. Project stock:
    Material No. MSPR-MATNR
    Stock Qty -> MSPR-PRLAB (Unrestricted), MSPR-PRINS (QI stock), MSPR-PRSPE (Blocked), MSPR-PREIN (Total stock of all restricted stock)
    WBS Element -> MSPR-PSPNR
    Batch NO -> MSPR-CHARG
    2. Stock:
    Material No. MARD-MATNR
    Stock Qty -> MARD-LABST (Unrestricted), MSPR-INSME (QI stock), MARD-SPEME (Blocked), MARD-EINME (Total stock of all restricted batches)
    Hope the above helps.
    Regards,
    Vivek

  • AIR for iOS, Library Project

    Is there (or will there be) any way to compile an actionscript mobile project, using AIR for iOS, as a library project so that other objective c applications could integrate the AIR library project within them ?

    http://custardbelly.com/blog/2011/09/21/air-native-extension-example-ibattery-for-ios/
    This is a very good example you can look, there are many others. try to google something like:"native extension for air on IOS" or if you know which component you want then go with "native extension air ios ComponentX", etc.

  • Can Watch Folder watch for After Effects project files?

    I set up a watch folder in Media Encoder but it only appears to pick up or watch for video and audio files.  is there a way to set it to watch for After Effects project folders?

    No, just media files (movie files).

  • Ideas for structure of projects ans albums

    Hi!
    I am new at Aperture and i do not have any idea how to import my existing folders of pics into the Aperture library. My pics are organized in folders and subfolders like year / month / shoot-name.
    When I imported by "Folders as Projects" I saw, that I counldn´t move the masters from the project folders, which were named as year.
    I´m thinking about project-names at top level like "holidays", "Studio-shoots", "family" a.s.o. Has anyone got a ready-for-use structure which I could use or modify?
    thanks in advance!
    Sandro

    Hi!
    I am new at Aperture and i do not have any idea how
    to import my existing folders of pics into the
    Aperture library. My pics are organized in folders
    and subfolders like year / month / shoot-name.
    When I imported by "Folders as Projects" I saw, that
    I counldn´t move the masters from the project
    folders, which were named as year.
    I´m thinking about project-names at top level like
    "holidays", "Studio-shoots", "family" a.s.o. Has
    anyone got a ready-for-use structure which I could
    use or modify?
    First of all the way that Aperture works best is along the lines of who the folders imported - you have top level folders, then more folders under those to some depth, then under those (eventually) you have projects.
    If you start with a project at the top level it will grow really big and be hard to manage in terms of import and export - and folders will not work quite like you might think in terms of seeing images.
    You can't actually add images into folders themselves, they have to go into projects. If you want images at the level of a folder the thing to do is place a new project in that folder.
    As far as organization goes, I am currently using a structure that looks like:
    Subject->Year->Month->ProjectName
    It's kind of wierd to keep using dates in the title of folders when you have things like smart folders but I find it easier to navigate and find things.
    Also I have albums that live somewhat outside that structure like:
    Subject->BestOfAlbum
    Some are smart folders (something like a best of album can just query ratigns) or collections I manually assemble.

  • "Library" Projects vs "Projects & Albums" Projects

    Hello all,
    I have been using Aperture for about three years. I have Aperture 3 on three different Macs.
    Prevously I have been using Windows XP and have been storing photos in directories on the hard drive the old fashioned way.
    I have some questions about the storage structure of Aperture and I cannot find the answer in the Manual nor online.
    Here we go.
    1. When I import photo's into Aperture, it creates a "Project" both under "Library" Projects and under "Projects & Albums."
    Q: If I delete a project under "Library" do the photo's contained in that project get deleted from Aperture's Library?
    Q: If I delete a project under "Projects & Albums" do the photo's contained in that project get deleted from Aperture's Library?
    2. I have been a user of Mobile Me gallery since it came out, even before I bought Aperture.  I have synced the Mobile Me galleries with my copy of Aperture 3 on each of the mac's so I have redundant copies.  I understand that Aperture will automatically sync changed photos so I am pretty sure all the image files for each mobile me gallery now exists on my hard drives.
    Q: As Mobile Me Gallery will not longer be supported in June, if I delete a Moble Me Gallery via Aperture, will the images in my Aperture Library still be there?
    I know this question seems odd, but the manual is not really clear on this issue.
    3. While I am here asking the pro's this is a question I think I have figured out.
    Q: The Vault list shows a Bar for each vault.  It has a caption that says something like
    The Bar has hashes on the right side and solid color on the left. I assume this shows The total Drive side, and the total amount of free space availble at that moment, yet it does not show the size of the actual vault. And Green means plenty of room left, red means getting close to full.  Dum quesiton but I need varification.
    Thank you very much for your patients with a relatively new Aperture User.
    Mike

    Hello Mike,
    All images (and all versions of an image) are stored in one and only one project. All versions of the same image are always part of the same project.
    The "Photos" view shows you all versions of all of your images for quick access and filtering and searching, but it does not store the images - it is not a container like the projects, it's more like a smart album.
    Then that new "Project" would contain "Versions" of the orginal files in the "Photos" section??
    If you drag an image by accessing it from the Photos View, you will not drag it from the Photos View but move it from its original project to a the new project - this does not create new versions in the new project. The Photos View is just a neat feature to select all your images in one place, independent of the project they are stored in, like having a file of index cards to all your images.
    If so, then if I delete that new "Project" under "Projects and Albums" it should just delete the "Versions" in that project??? and not the originals under "Library?"
    Oh yes, deleting any project will certainly delete your original images. The only originals you see under "library" are projects in the "Projects" view, and that are exactly the same projects as under "Projects and  Albums" - just different ways to access the same content.
    What I was trying to find out is that if I delete a project, then that grouping created under that project would disappear but the original images would still be in the libary, just no longer assigned to that deleted project.
    If you delete a project, from whatever view you use, the images stored in that project are gone. And since each image - and all its versions - belongs to only one project, that image will be removed from the library for good, if its project is deleted!
    You really need to get a better understanding of the basic organizational structure of Aperture:
    If you not have found it already, here is the User Manual, really worth reading:
         Aperture 3 User Manual: http://documentation.apple.com/en/aperture/
    and here are well-polished, introductory posts by Kirby Krieger:
    Kirby Krieger: The Well-Trod Path:
    https://discussions.apple.com/message/16003277#16003277
    Kirby Krieger: Re: Organizing in Aperture, concise long version:
    https://discussions.apple.com/message/12616449#12616449
    Kirby: Krieger: Best way to managing libraries?
    Post back, if you need further clarification; I am sure someone else will drop in on this discussion.
    Regards
    Léonie

  • Organizing Photos in Folders or Albums

    Hello
    I have hundreds of high res photos from a film project, and I'd like to organize them for easy viewing.
    As I understand the way iPhoto works, it is basically taking/referring to actual images from their original source. (like an external drive).
    I'd like to know the best way to bring all of these photos into iPhoto;
    Do I need to import ALL of then into the Main iPhoto Library, or can I import them into separate folders or albums? I was led to believe that in order to put them into separate folders, they all need to appear in the Main Library first? Is that right?
    And what type of sub group do I need? Separate Folders? Or Separate Albums?
    What is the basic difference between them?
    Thank you
    Mike

    Mike
    it is basically taking/referring to actual images from their original source. (like an external drive).
    No, actually by default it's quite the opposite. It prefers to copy the files into the iPhoto Library Folder and manage them. You can change this setting, but I do not recommend it. Very strongly. However, you can run an entire library from an external, so if you're worried about space, that's not a problem.
    Do I need to import ALL of then into the Main iPhoto Library,
    iPhoto uses exactly the same metaphor as iTunes: All pics are in the Library, albums are subsets of the library. Albums (like iTunes playlists) are virtual. A pic can be in 1, 10 or 100 albums with no disk space wasted through duplicate files.
    So, import the pic, they go in the library. Then create albums (File -> New Album) and drag the pics to the albums in whatever way you prefer. You can also tag the pics and create Smart Albums in a variety of ways.
    If your files are already sorted into folders, then drag a folder to the Source (or left-hand) pane and iPhoto will import and create an Album of the same name as the folder.
    File -> New Folder will allow you to create Folders. Folders can contain nested folders and albums, but not loose pics. A pic must be in an album to go into a folder.
    Regards
    TD

  • Exporting a library with its folders and albums

    I scanned over 1700 slides into my aperture library.  AFter spending a considerable amount of time putting them into folders and albums, I would like to export the project so my husband can put it into his aperture library.  I exported the whole project onto my desktop so I could put it in dropbox to enable him to put it into his computer.  However, when I exported the library, It came across as just one big library of photos, with no structure.  I don't care to reorganize the photos into folders and albums again, as it would be very time consuming.  Is there any way to export the library and keep its structure?
    Thanks in advance
    Nancy

    Nancy,
    what is your Aperture version, and how did you export?
    In the current Aperture version 3.4.5 all projects and albums should be preserved, when you export a library with "File > Export > Projects/Albums/Items as new library"
    For example, I selected two albums in the library Inspector simultaniously, made sure, that I only selected the albums in the panel, but not single images within the albums, and then used the command "File > Export > Albums as new library".
    The exported library had the two albums, as well as all projects and folders necessary to fill he albums.
    Did you perhaps only select one big project of scanned images? Then try again by selecting the albums you want to export. My two albums exported like this: You see, the exported library has quite a few folders with projects inside, as well as my two albums:
    Regards
    Léonie

  • Keeping Synced Backup of Library - In Project Folders

    Can't find a way to do this online - probably because I can't think of the right way to get any sensible results from a search.
    Basically, I have my Aperture library which is ~100GB (which is already backed up in a couple of places). I also want JPEG versions of everything in my library so I can keep a copy online (ideally via iDisk, part of MobileMe - but I can do that as a separate step if necessary), and want photos kept in their project folders.
    Any ideas how I can do that? Looks like i'll need a plugin or automator to do it, but there may be a function I've missed somewhere. Seems like it should be simple enough, but I'm struggling (bearing in mind I don't want a complete re-export each time, just export whatever was updated since the last export)...
    David

    Hi christian,
    For future reference, backup the entire iPhoto Library folder. You need all the data files in there for it to work correctly.
    For your situation now, there is no way to relink originals with the modified versions.
    You can manually go through the modified folder and see if you want the modified version of a photo instead of the original. If you do, drag the modified version into the same roll in the Originals folder and it will replace the original as they have the same name.
    Then create a new library and import just the Originals folder.

  • Organizing project folders

    Hi
    While developing large Flex projects, I often find myself wanting to organize the project folders so that everything is neat and logical.
    One of my main concerns in doing so was that the bin-release folder had only whatever necessary items there were to run the project, and nothing extra. Therefore, I found I should place any assets loaded at compile time NOT in the src folder, but in a separate folder somewhere outside the src (any non-code files in src or subfolders seem to be exported in the bin-release).
    This raised one minor issue: Whenever I embed something into my code, using @Embed directives, I need to specifiy the location starting with "../", as to get out of the default src folder. I really hate this, for one it reminds me I could always use "../../" to look for stuff even outside the whole project folder, which is ugly to do; plus I think "../" is bad practice in any code and should always be worked around.
    What I would prefer is a way to mark folders as being part of the compile-time library path, but not to be exported in the bin-release. Is there such an option in Flash Builder? I needn't mention I prefer not to delete the assets from the bin-release folder myself.
    Thanks,
    Liviu

    asuch:
    Terence may have a good idea there about replacing the alias files with the original "source" files. I'd do it for one small roll first to see if it will work satisfactorily. If so then proceed folder by folder, checking as you go along.
    The fact that the source file does not get deleted when you delete in iPhoto is one of the caveats of that system. One way to find and delete the source file before deleting from iPhoto is to Control-click on the thumbnail and select Show File or Show Original File if it's been edited. That will take you to that file already selected in the Finder and all you'll need to do is type CommandShiftDelete to move it to the Trash. Then go back to iPhoto and delete it from the library.
    I suppose an Applescript could be written to do that from iPhoto. If you want to keep the alias system ask in the Applescript forum if anyone has one or can write one.
    If you keep that system you might get some helpful tips from my Tutorials that I've written. The are primarily for converting to one but there may be something that will be of interest.
    Do you Twango?
    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.
    G5 Dual Core 2GHz, 2G RAM, 250G HD; G4 Dual 1Ghz, 1.5G RAM, 80G HD,   Mac OS X (10.4.8)   QT 7.1.3, 22 LCD, 200 & 160G FW HDs, Canon S400, i850 & LIDE 50, Epson R200

  • How do I apply programmatic skins for completely custom drawn components of a Flex library project?

    Hello folks,
    I am looking for best practices advice when (1) creating
    custom components and (2) styling and skinning.
    I already know how to skin a component part of the Flex
    framework. I can make a class extending ProgrammaticSkin and have
    my component skinned using CSS to link the component with the
    reference to my custom class.
    However what about those cases when you are completely
    creating a component from scratch?
    Imagine a "Freehand Drawing Canvas" component that allows the
    user to draw on it and has some buttons to set color styles, line
    styles, etc., or imagine a "Screen Flow Gallery" component that
    displays visual objects in a fashion similar to Cover Flow in the
    Mac.
    In many components I am aware you may reuse other components
    part of the Flex framework but I am trying to picture an scenario
    where you would need to draw everything yourself because there just
    isn't something to base it upon so you will end up drawing it from
    scratch.
    To learn how instead of building one of those components I
    mentioned previously I decided to start with something simple that
    would illustrate this like a LiteButton component that will behave
    just like the Flex mx.controls.Button but will extend UIComponent
    and be completely custom drawn.
    The component will have a default look and will also be
    style-able and skin-able. I will provide styles for users of the
    component to modify and regarding skinning anyone can create a
    custom ProgrammaticSkin adding its own drawing logic and link it to
    the component via CSS with the ClassReference applied to the skin
    selector.
    So far so good and it's clear what I want to achieve. I
    actually know how to do most of the stuff here but I have one
    single problem.
    Here is my question, where should I put my custom drawing
    logic? If I do it in the updateDisplayList inside the class
    extending UIComponent it works, however I thought that it would be
    a better practice to do it using programmatic skins, that way I
    could provide different skin themes for my component set.
    The problem is that I can't make the programmatic work in
    this scenario. I tried instantiating the custom programmatic skin
    during the updateDisplayList of the LiteButton component and adding
    it to my display object via addChild but that didn't do anything. I
    also tried creating a "default.css" stylesheet and tried to use
    ClassReference as I would normally do to skin an already existing
    component (or composite component as well) but that didn't do
    anything either.
    So how do I apply programmatic skins for completely custom
    drawn components of my Flex library project?
    I could do it inside the updateDisplayList of the LiteButton
    class extending UIComponent but again I would like to provide
    different theme sets for my components so it makes sense using
    programmatic skins.

    "jbucaran" <[email protected]> wrote in
    message
    news:[email protected]...
    > Hello folks,
    >
    > I am looking for best practices advice when (1) creating
    custom components
    > and
    > (2) styling and skinning.
    >
    > I already know how to skin a component part of the Flex
    framework. I can
    > make
    > a class extending ProgrammaticSkin and have my component
    skinned using CSS
    > to
    > link the component with the reference to my custom
    class.
    >
    > However what about those cases when you are completely
    creating a
    > component
    > from scratch?
    >
    > Imagine a "Freehand Drawing Canvas" component that
    allows the user to draw
    > on
    > it and has some buttons to set color styles, line
    styles, etc., or imagine
    > a
    > "Screen Flow Gallery" component that displays visual
    objects in a fashion
    > similar to Cover Flow in the Mac.
    >
    > In many components I am aware you may reuse other
    components part of the
    > Flex
    > framework but I am trying to picture an scenario where
    you would need to
    > draw
    > everything yourself because there just isn't something
    to base it upon so
    > you
    > will end up drawing it from scratch.
    This may help with that
    http://livedocs.adobe.com/flex/3/html/help.html?content=skinstyle_3.html
    > To learn how instead of building one of those components
    I mentioned
    > previously I decided to start with something simple that
    would illustrate
    > this
    > like a LiteButton component that will behave just like
    the Flex
    > mx.controls.Button but will extend UIComponent and be
    completely custom
    > drawn.
    >
    > The component will have a default look and will also be
    style-able and
    > skin-able. I will provide styles for users of the
    component to modify and
    > regarding skinning anyone can create a custom
    ProgrammaticSkin adding its
    > own
    > drawing logic and link it to the component via CSS with
    the ClassReference
    > applied to the skin selector.
    >
    > So far so good and it's clear what I want to achieve.
    Actually after
    > playing
    > with the weekend and today I know how to do most of the
    stuff but I have
    > one
    > single problem. So here is my question, where should I
    provide my custom
    > drawing logic? If I do it in the updateDisplayList
    inside the class
    > extending
    > UIComponent it works, however I thought that it would be
    a better practice
    > to
    > do it using programmatic skins, that way I could provide
    different skin
    > themes
    > for my component set.
    These aren't mutually exclusive. When you provide a skin with
    a
    TypeSelector, you have to add it to the display list
    somewhere, and this is
    typically done in updateDisplayList or addChildren. I prefer
    to do it in
    updateDisplayList, because you can then change it if the
    style changes.
    > The problem is that I can't make the programmatic work
    in this scenario. I
    > tried instantiating the custom programmatic skin during
    the
    > updateDisplayList
    > of the LiteButton component and adding it to my display
    object via
    > addChild but
    > that didn't do anything.
    Exactly what did you do?
    > I also tried creating a "default.css" stylesheet and
    > tried to use ClassReference as I would normally do to
    skin an already
    > existing
    > component (or composite component as well) but that
    didn't do anything
    > either.
    I've never had any problem using an approach similar to
    this...but I will
    say that I couldn't see any advantage in creating a
    default.css style sheet,
    since it's not really default in the way that the one that
    comes with Flex
    is. It's much more obvious to anyone using your component
    what's going on
    there if you create a style sheet where they're likely to
    spot it.
    > So how do I apply programmatic skins with the default
    look for custom
    > drawn
    > components?
    It seems like your approach is fine, but maybe you've made a
    mistake in your
    implementation.
    > I could do it inside the updateDisplayList of the
    LiteButton class
    > extending
    > UIComponent but again I would like to provide different
    theme sets for my
    > components so it makes sense using programmatic skins.
    You might want to consider also adding an instance of
    HaloBorder to your
    component. That brings a lot of functionality with it.
    HTH;
    Amy

  • HT200183 If I wanted to include apple loops in the assets of Logic project folders that are part of a tutorial available for download on a paid educational website would that be ok?

    If I wanted to include apple loops in the assets of Logic project folders that are part of a song that follows a tutorial available for download on a paid educational website would that be ok? No one would be paying for the file itself that's part of the membership. I don't want to get into any copyright problems. I understand that they are royalty free and you can include them in your music no problem but the individual loops would be in the audio folder if I saved all the assets to the project file.
    Also, would it be ok to include screen shots I take myself of apple programs in my downloadable content?
    Just trying to figure out exactly how I should go about it to avoid any legal issues.

    Hi
    trainedmind wrote:
    No one would be paying for the file itself that's part of the membership. I don't want to get into any copyright problems.
    My gut reaction is that you may well run into © issues if you re-distribute the original AppleLoops.If your customers are paying for the training, they are also paying for the content you provide, so I feel that you would be re-selling the loops.
    Given that anyone who has a copy of Logic would likely have installed all the loop content, there should be no need to distribute them with the project files. Alternatively, make your own loops.
    CCT

  • Bug with swc folders and library projects?

    Hi guys, hope someone can help here. We are just in the
    process of starting a fairly large flex project and we were trying
    to work out a solution so that I as a designer can view and edit
    custom components with visual styles applied.
    Now I know that you aren't meant to add a style tag into the
    component but it was working for me and I could at least preview
    the styles in 'design mode'.
    The problem arises though when you have a large project with
    shared assets across projects. I had 3 projects set up in my
    workspace:
    Project 1: Library project with css files, swc and graphics
    Project 2: Library project with components for Project 3
    Application
    Project 3: Application project
    What I did was to add a external source folder to Project 2
    & 3 both of which was Project 1. So far so good, the css loaded
    into my application from Project 1 and I could view my styles in my
    custom componants in Project 2
    But, I needed to add swc files for custom buttons etc in my
    application. So, I thought I would just add an swc folder source to
    my build path in both my Project 2 & 3 which referenced an swc
    folder in Project 1. Well, it did work and I could view everything
    fine but (and here is the main problem) this corrupts the
    workspace. Once Flex has closed and tries to reopen my workspace it
    hangs, same if I change workspace in Flex from another workspace to
    this one.
    Can anyone help? Is this a flex bug?
    TIA
    Steve

    Section 6.3.9 of RFC3501 expands on previous RFCs and clarifies the LSUB command, confirming that this is a bug in JavaMail. http://www.isi.edu/in-notes/rfc3501.txt

Maybe you are looking for