Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've struggled with this myself, and I can't tell you anything other than:</p> <ol> <li>No code in FLAs, ever</li> <li>Divide content semantically into separate FLAs where appropriate</li> <li>Make a change document for FLAs, and enter a note for every single change.</li> </ol> <p>The first point is obvious enough. The second is to recognize that there's no getting around the fact that FLAs are binary blobs that hold all your visual assets and don't play well with versioning, but you can recognize the fact that some contents change frequently while others tend to be created once and then left alone. By dividing your assets into different FLAs, you can keep the large majority of changes into a small number of unstable FLAs, and the difference between stable and unstable content will be reflected in your versioned files.</p> <p>Note that even if you can't load assets at runtime, compile-time sharing still lets you divide assets into an arbitrary number of FLAs. (Compile-time sharing is often overlooked - if you're not familiar with it, open a MovieClip's properties and check out the "Source" section at the bottom.) How to divide things will depend your project. The best I can suggest is to make divisions semantically - perhaps one FLA for each character, or one FLA for each section, or one FLA for each interface element, etc. As with all development the goal is to group related assets and eliminate duplication.</p> <p>The third point is, since diffs are impossible, there's just no way around keeping a change document. My preferred way is to check the FLAs into versioning and note all changes in the check-in note, but the changes could also be in a separate document. (Note that it's vital that you keep the libraries in each FLA orderly, or someone reading the change description will have trouble finding the change.) However, since this can be a pain for some contents, it's also useful to designate certain FLAs as "unstable", and not bother with a change list. But if such files have a lot of dependencies on other files, you'll regret it later.</p> <p>Unfortunately this is all I've discovered so far. Adobe has talked about changing to a text-based FLA format in a future version, but until that arrives, there's no easy solution.</p>
    singulars
    1. This table or related slice is empty.
    1. POVersion control for Adobe Flash projects
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USfenomas
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POVersion control for Adobe Flash projects
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYour notes are very useful, thanks. There is no way I'll get developers to maintain a change document - it will be too much overhead and no one will do it (seriously or at all). My purpose is to get control without increasing developer overhead. I'm having hard time enough getting people to write meaningful comments in their commits :-(. The change log might have been a good change document if not for the fact that files tend to get deprecated, deleted and replaced with new code.
      singulars
      1. PO
      1. USGuss
    2. COWell, you have to work with what you work with. I didn't keep detailed change documents until a file was more or less feature-complete - so I only documented changes and bug fixes, not initial development. And commit comments are fine - as I said, that's where I documented my changes.
      singulars
      1. PO
      1. USfenomas
    3. COThanks fenomas - I'm going to accept your answer because (a) its the most details and.. well.. best; (b) no one has come up with something new in a while; and (c) - I'm kind of moving away from the entire problem...
      singulars
      1. PO
      1. USGuss
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload