Jen deHaan

Just want to draw a bit of attention to the new documentation for the Flash 9 preview. It's all in LiveDocs, so you can leave your comments for the writers involved - this will help improve the final documentation, so I encourage you to let them know what you think. Do you want samples of something? More info on how to migrate? Coverage of a particular API? Let them know!

Overview of ActionScript 3.0 Language Reference
Flash Programming ActionScript 3.0

On the developer center, you should check out:

Exploring the Flash Professional 9 ActionScript 3.0 Preview (an article Peter deHaan and I wrote on how to get started with AS3 in the Flash Preview).

ActionScript 3.0 Overview

Posted by Jen deHaan at 01:18 PM | Permalink | Comments (11)

The Flash 8 Best Practices document has been posted on the Developer Center. This is an updated version of the Flash MX 2004 Best Practices document that was out there, but doesn't contain the ActionScript stuff (which is here instead: http://www.macromedia.com/devnet/flash/articles/as_bestpractices.html).

Most of this can be found somewhere in the documentation, but it wasn't consolodated into a single place. Hopefully it will be in the future ;) But for now, it's here on the Developer Center:

http://www.macromedia.com/devnet/flash/articles/flash8_bestpractices.html

Enjoy!

And if you have things to add (there are always best practices to add), let me know and we'll consider everything for a future revision!

Posted by Jen deHaan at 03:59 PM | Permalink | Comments (2)

A new version of the AS best practices guide has been posted on the developer center. It's mostly what you can find in the documentation, but reformatted and relinked. The Flash 8 ActionScript version has also been seriously trimmed from the 2004 version (much of the Flash-centric best practices will be in an upcoming Flash Best Practices).

Check "ActionScript 2.0 Best Practices" out here:

http://www.macromedia.com/devnet/flash/articles/as_bestpractices.html

Print version:

http://www.macromedia.com/devnet/flash/articles/as_bestpractices_print.html

ALSO (update):

In PDF format: http://www.helpexamples.com/pdf/actionscript2bp.pdf

In your Help panel:[i] [b]Learning ActionScript 2.0 in Flash > Best Practices and Coding Conventions for ActionScript 2.0[/b] [/i]

In LiveDocs: http://livedocs.macromedia.com/flash/8/main/00001640.html

Any suggestions/additions welcome! Stay tuned for the Flash 8 Best Practices guide.

Posted by Jen deHaan at 02:55 PM | Permalink | Comments (8)

Yesterday I turned in my offer letter to Adobe, so officially I'm now working on Adobe Flash documentation. Which feels pretty weird to type (and see - check out http://www.adobe.com/motiondesign and click on the About this Site link!) My partners in crime (other writers on Flash and Flash Player teams) are exactly the same as well. No departures - good news.

Things are business as usual for the Flash team as well - see Mike Downey's post about that here: weblogs.macromedia.com/md/archives/2005/12/things_still_mo.cfm

It has been a pretty tense/intense week around here. Lots of emotions (nervous, sadness, relief). Although there's a lot of good news, there's also some sad news about departures from both companies. I wish all of those people leaving the best of luck - I know they won't need it because they're all so talented. Actually, speaking of which, Alan Musselman summed some things up very nicely in his post here.

I do look forward to continuing on with the Flash team and documentation. The department I'm in is now called the "Learning Resources team" (it was called "IMD" at Macromedia). It's pretty exciting to be in a much bigger group, with more resources (or so it seems) - meaning we'll be able to offer you better "stuff".

(PS: Sorry for the temporary fugly blog design - I lost the original and needed to update it on the asap. Will make a new one soon!)

Posted by Jen deHaan at 09:42 AM | Permalink | Comments (7)

When you perform a search in the Help panel in Flash 8, you can filter your search by a pre-determined set of categories. For example, you can search only the components content, or just the tutorials and samples content. This can be very useful if you don't want to scroll through 10 billion results when you search.

However, what if you want to choose your own content to search? For example, what if you want to exclude the mobile books because you're not creating mobile content (yet)? You can by following these steps!

TO CREATE A CUSTOM HELP SEARCH CATEGORY IN FLASH 8:

1. Close Flash.

2. Find the categories.xml file, in which you will add a new category for your custom search. Find the categories.xml file here:

C:\Documents and Settings\All Users\Application Data\Macromedia\Flash 8\en\Configuration\HelpPanel\categories.xml

HD:Users:Shared:Library:Application Support:Macromedia:Flash 8:en:Configuration:HelpPanel:categories.xml

4. Save a back-up of this file, just in case.

5. Modify the categories.xml file. Add this to categories.xml alongside the other categories:

<category title="Not Mobile" keyword="notmobile"></category>

6. Then find the Help folder here:

C:\Documents and Settings\All Users\Application Data\Macromedia\Flash 8\en\Configuration\HelpPanel\Help

HD:Users:Shared:Library:Application Support:Macromedia:Flash 8:en:Configuration:HelpPanel:Help

You see a bunch of book files, each of which contains a help_toc.xml file. You need to go into each folder of a book you want to add, and add the keyword you chose above ("notmobile") and add that inside of each help_toc.xml file.

So, I'm going to start with the ActionScriptLangRef: find help_toc.xml in that folder (scroll right to the end), and in that file modify this line (line 2):

<book title="ActionScript 2.0 Language Reference" directory="ActionScriptLangRef" categories="languagereferences,as2" language="en" version="2.0" sort="mm_7">

<book title="ActionScript 2.0 Language Reference" directory="ActionScriptLangRef" categories="languagereferences,as2,notmobile" language="en" version="2.0" sort="mm_7">

7. Repeat this for each book you want to search in the notmobile category.

When you're done, reopen Flash and open the Flash panel. You'll see the new category in the Search pop-up menu:

Posted by Jen deHaan at 06:11 PM | Permalink | Comments (1)

You can download the ActionScript Language Reference in HTML format at the following location:

http://www.macromedia.com/support/documentation/en/flash/

Click on the ActionScript tab, and find the link to "Download stand-alone HTML".

Let us know what you think!

Posted by Jen deHaan at 10:43 AM | Permalink | Comments (13)

I originally posted in August about customizing your Help panel in Flash 2004 (http://weblogs.macromedia.com/dehaan/archives/2005/08/customize_your.cfm). Now I'll update the steps for Flash 8 - very similar stuff.

First of all, you might have noticed a new feature in the Help panel that does search highlighting. This useful little feature has saved me a bunch of time.

But what if you're not a fan of nasal yellow? Or even search highlight? Well, you're in luck. You can control the highlight feature (modify, remove) by editing a simple CSS file. You can also change other elements of the Help panel the same way. Read on...

Caution: Before you start, remember to save a backup of the CSS files that you plan to modify "just in case".

1. Close Flash and navigate to C:\Documents and Settings\All Users\Application Data\Macromedia\Flash 8\en\Configuration\HelpPanel\_sharedassets (Windows)

or

HD:Users:Shared:Library:Application Support:Macromedia:Flash 8::Configuration:HelpPanel:_sharedassets (Mac).

2. Open the help_pc.css file in a CSS editor (such as TopStyle or Dreamweaver, or a text editor such Notepad), or open help_mac.css if you're on a Mac.

3. To change the search highlight color, find and modify this section of the file. I've modified the yellow (#DFDF00) to:

.searchhilite {
background-color: #AFE28B
}

To change the background color for procedures, find the line starting with "div.procedure, div.welcomehelp, div.welcomehowdoi {" (around line 224): Add the following line to change the background color for procedures to a light purple (new text in bold):

div.procedure, div.welcomehelp, div.welcomehowdoi {
display:none;
background-color: #F0FDFF;
}

5. That's it! Save the CSS file, and then reopen Flash/Help panel.

I'll post soon about other customizations you can make, such as creating a custom search category (that pop-up menu under the Search text box).

Posted by Jen deHaan at 07:02 PM | Permalink | Comments (3)

As the title says! In earlier versions of Flash, Ctrl+F just didn't work in conjunction with Help. Well, now it does. Go to a help page in Flash 8 docs, and press Ctrl+F or Command+F on the Mac -- the Find box opens like magic. Really helps you locate stuff in those longer Help pages...

Posted by Jen deHaan at 06:37 PM | Permalink | Comments (2)

There is a lot of terminology in ActionScript, and Flash of course. One of the later efforts in documenting Flash was a brand new terminology page for ActionScript, which you can see on LiveDocs here:

http://livedocs.macromedia.com/flash/8/main/00001702.html

Or search "Terminology" in the Help panel, you'll find it here:

Learning ActionScript 2.0 in Flash > Terminology

If you are an ActionScript expert, then this page will be of little use to you. But if you're learning ActionScript, hopefully this page will be useful.

But that's not why I'm blogging.

This page is not comprehensive (it's manual and was kinda developed unofficially while going along, instead of consciously as a specific project. Sorry... but better than nothin'? heh.) Actually, I'm sure it could easily quadruple its length, at which time I think we'd need to reconsider the format. I digress...

What I'd like to ask is any terms - about ActionScript specifically (not necessary Flash, unless it's a feature related to AS) - please comment on LiveDocs (Terminology page on LiveDocs) and say "Please add this term ____". You don't need to define it unless you'd like to, but it will greatly help develop this page into something increasingly useful for everyone.

Thanks!

Posted by Jen deHaan at 02:09 PM | Permalink | Comments (0)

Documentation includes a page that lists the new ActionScript you can use with Flash Player 8. I am "reprinting" that information here. It's available in the Help panel here (search "additions to" with quotes):

Learning ActionScript 2.0 in Flash > What's New in Flash 8 ActionScript > New in ActionScript 2.0 and Flash 8 > Additions to the ActionScript language

And on LiveDocs here:

http://livedocs.macromedia.com/flash/8/main/00001133.html

Note that there is new information in the LiveDocs and this blog (ie: developments after "print time").

Read the extended entry for the entire lists!

Continue reading "New ActionScript in Flash 8" »

Posted by Jen deHaan at 01:45 PM | Permalink | Comments (12)

There are a couple large PDFs that are additional documentation for your reading and learning pleasure. First off is the VideoPlayer class API, new in Flash 8, which is over 100 pages of bonus documentation.

"This article contains application programming interface (API) documentation for the VideoPlayer class. The VideoPlayer class is a wrapper class for the Video, NetConnection, and NetStream classes, and makes it easy to play FLV files and create custom video players."

You can download it here:

http://download.macromedia.com/pub/documentation/en/flash/fl8/VideoPlayer.pdf

Next up is the XPath API class, which was available in Flash 7 but now officially documented here:

http://download.macromedia.com/pub/documentation/en/flash/fl8/XpathAPI.pdf

Enjoy!

Posted by Jen deHaan at 11:39 AM | Permalink | Comments (2)

You can change the way your help panel looks in Flash 2004 by modifying the Help panel CSS files that install with Flash. Want to know how? Read on, readers.

Caution: Before you start, remember to save a backup of the files that you plan to modify "just in case".

1. Close Flash and navigate to C:\Documents and Settings\All Users\Application Data\Macromedia\Flash MX 2004\en\Configuration\HelpPanel\_sharedassets

2. Open the help_pc.css file in a CSS editor (such as TopStyle or Dreamweaver, or a text editor such Notepad). Open help_mac.css if you're on a Mac.

3. To change the background color for code, find the line starting with "pre, .code {" (roughly line 128).

Add the following line to change the background color of code to gray (new text in bold):

pre, .code {
font-family: "Courier New", Courier, mono;
font-size: 100%;
background-color: #F6F6F6;
}

4. To change the background color for procedures, find the line starting with "div.procedure, div.welcomehelp, div.welcomehowdoi {" (around line 217):

Add the following line to change the background color for procedures to a light purple (new text in bold):

div.procedure, div.welcomehelp, div.welcomehowdoi {
display: none;
background-color: #F0FDFF;
}

5. That's it! Save the CSS file, and then reopen Flash/Help panel.

Posted by Jen deHaan at 11:06 AM | Permalink | Comments (2)

Somebody emailed me recently about this topic, so I came up with a quick and dirty solution. Not sure if there's a better way, but thought that somebody out there may find this useful, so here it is:

1. Drag a ScrollPane component onto your Stage and give it an instance name of my_scrollPane.

2. Add the following ActionScript to frame 1 of the main timeline. (Watch for wrapping lines!)

my_scrollPane.addEventListener("complete", myLoaderCompleteListener); function myLoaderCompleteListener(eventObj:Object):Void { if (eventObj.target.getBytesTotal() == -1) { eventObj.target.visible = false; var t:TextField = eventObj.target._parent.createTextField("error_txt", 10, eventObj.target.x, eventObj.target.y, 100, 20); t.autoSize = "left"; t.text = "unable to load file"; return; } // continue setting up. } my_scrollPane.contentPath = "http://www.deseloper.com/thisImageFileDoesntExist.jpg";

3. Save and test.

Because the image file doesn't exist, the complete event is dispatched to the ScrollPane instance and getBytesTotal() returns -1. The complete listener checks that the image was successfully loaded. If not, the ScrollPane instance is hidden and a text field is created and displays an error message.

Voila.

Posted by Jen deHaan at 04:47 PM | Permalink | Comments (7)

Why, clever readers, did you know that you can use Flash MX Professional 2004's Alert component to create non-modal pop-up windows instead of the default modal mode?

If you did, well, you can stop reading.

If you didn't, you're probably already typing up an angry email to me complaining how I haven't defined the term "modal" or "nonmodal". So, rest your ten angry digits and read on.

From our very own docs: A nonmodal window allows a user to interact with other windows in the application.

So, what this all means is that a modal Alert window prevents users from clicking on anything but the displayed Alert window itself. Therefore, a user can't go any further until they dismiss the pop-up, similar to how the OS displays some error messages. A nonmodal Alert window lets users merrily click on either the Alert window or any components on gizmos underneath the Alert.

Enough of my jibber-jabber, on with some code...

Before you can test the code, add a copy of both the Button component and Alert component to your library. Add the follow code to Frame 1 of the main Timeline:

import mx.controls.Alert;

this.createClassObject(mx.controls.Button, "modal_button", 10, {_x:10, _y:10});
this.createClassObject(mx.controls.Button, "nonmodal_button", 20, {_x:120, _y:10});

modal_button.label = "modal";
modal_button.addEventListener("click", modalListener); function modalListener(evt_obj:Object):Void {
var a:MovieClip = Alert.show("This is a modal Alert window", "Alert Test", Alert.OK, this);
a.move(100, 100);
}

nonmodal_button.label = "nonmodal";
nonmodal_button.addEventListener("click", nonmodalListener); function nonmodalListener(evt_obj:Object):Void {
var a:MovieClip = Alert.show("This is a nonmodal Alert window", "Alert Test", Alert.OK | Alert.NONMODAL, this);
a.move(100, 100);
}

Test the movie, and click on the "modal" button to launch a modal window. This means you can no longer click on either of the Button instances on the Stage. Close the Alert and click the "nonmodal" button. Even though the nonmodal Alert window is visible, you can still click on either of the button instances on the Stage.

Thar ye be havin' 't. Dasn't say I neredo anythin' fer ye. YAR!!!

Posted by Jen deHaan at 12:02 PM | Permalink | Comments (4)

If anyone be like me, you like pirates. And on occassion (to the irritation of co-workers), you speak in Pirate.

So I was thinking, why don't we localize the documentation to Pirate? Would any of you strapping young buckaneers read it? Would it help make Flash easier? We'd easily have the capability to translate to Pirate, thanks to online Pirate translators.

For example, might see something along the lines of:

Usin' layers
Layers be like transparent sheets o' acetate stacked on top o' each other. Layers help ye organize th' artwork in yer document. Ye can draw an' edit objects on one layer without affectin' objects on another layer. 'ere thar be nothin' on a layer, ye can be seein' through 't t' th' layers below. T' draw, paint, or otherwise modify a layer or folder, ye select th' layer t' make 't active. A pencil icon next t' a layer or folder name indicates that th' layer or folder be active. Only one layer can be active at a time (although more than one layer can be selected at a time). When ye create a new Flash document, 't contains one layer. Ye can add more layers t' organize th' artwork, animation, an' other elements in yer document. Th' number o' layers ye can create be limited only by yer computer`s memory, an' layers do nay increase th' file size o' yer published SWF file. Ye can hide, lock, or rearrange layers. Ye can also organize an' manage layers by creatin' layer folders an' placin' layers in them. Ye can expand or collapse layers in th' Timeline without affectin' what ye be seein' on th' Stage. `Tis a good idee t' use separate layers or folders fer sound files, actions, frame labels, an' frame comments. This helps ye find these items smartly when ye need t' edit them. In addition, ye can use special guide layers t' make drawin' an' editin' easier, an' mask layers t' help ye create sophisticated effects. Fer an interactive introduction t' workin' wi' layers in Flash, select Help > How Do I > Basic Flash > Work wi' Layers.

This section contains th' followin' topics:
* Creatin' layers an' layer folders
* Viewin' layers an' layer folders
* Editin' layers an' layer folders
* Organizin' layers an' layer folders
* Usin' guide layers

Ya horn swollgin' swabbie!

[This pirate-speak version of our documentation is courtesy of the much awesome web site: www.syddware.com/cgi-bin/pirate.pl.]

YAR!!!

Posted by Jen deHaan at 07:17 PM | Permalink | Comments (11)

Get better results with the ObjectDumper! Try this out.

1. Add the DataBindingClasses to your Library (find it in the Classes common library).
2. Add the following ActionScript code to Frame 1 of the Timeline:

import mx.data.binding.ObjectDumper;
var my_dp:Array = new Array({name:'Grissom, M.', avg:0.279}, {name:'Bonds, B.', avg:0.362}, {name:'Cruz, D.', avg:0.292}, {name:'Snow, J.', avg:0.327});
trace(my_dp);

3. Test the SWF. Your output should be:

[object Object],[object Object],[object Object],[object Object]

Not very helpful.

4. Comment out this: trace(my_dp);

5. Now add the following line to the end of your code:

trace(ObjectDumper.toString(my_dp));

6. Test the SWF again, and marvel at the improved results:
[{avg: 0.279, name: "Grissom, M."},
{avg: 0.362, name: "Bonds, B."},
{avg: 0.292, name: "Cruz, D."},
{avg: 0.327, name: "Snow, J."}]

Posted by Jen deHaan at 12:22 PM | Permalink | Comments (23)

Earlier I had a request from a user for a Menu component example, because they were trying to create a menu and running into some problems. Given that it seemed like an area that did need a bit more "coverage", the following examples might help.

Now, there are two ways you can work with the menu components - using inline or external XML. The following example shows how you can load Menu items based on an external XML file. Next blog, inline.

For the set up, do the following.

1. Add an instance of the MenuBar component to the Stage.
2. Give it the instance name myMenuBar (in hurry, forgot to use a suffix).
3. Add the following code to Frame 1 of the Timeline.

myMenuBar.setStyle("fontSize", 10);
//
var ds:XML = new XML();
ds.ignoreWhite = true;
ds.onLoad = function(success:Boolean) {
if (success) {
myMenuBar.dataProvider = ds.firstChild;
}
};
ds.load("ds.xml");
//
var menuListener:Object = new Object();
menuListener.change = function(evt:Object) {
switch (evt.menuItem.attributes.instanceName) {
case "file_new" :
trace("File > New");
break;
case "file_open" :
trace("File > Open");
break;
case "file_openFromSite" :
trace("File > Open from Site");
break;
case "file_openRecent" :
trace("File > Open Recent");
break;
case "file_openRecent_01" :
case "file_openRecent_02" :
case "file_openRecent_03" :
case "file_openRecent_04" :
case "file_openRecent_05" :
case "file_openRecent_06" :
case "file_openRecent_07" :
case "file_openRecent_08" :
trace("File > Open Recent > "+evt.menuItem.attributes.fileName);
break;
case "file_close" :
trace("File > Close");
break;
case "file_closeAll" :
trace("File > Close All");
break;
default :
trace("unknown instance name for: "+evt.menuItem.attributes.label);
}
};
myMenuBar.addEventListener("change", menuListener);

Before you test your code, save the following XML file into the same directory as the FLA: http://www.flash-mx.com/mm/xml/ds.xml. Or, you can target this XML file instead.

That's it!

Posted by Jen deHaan at 12:34 PM | Permalink | Comments (27)

A new Developer Center article goes live on runtime data binding. You can read the article here:

www.macromedia.com/devnet/mx/flash/articles/databinding_classes.html.

As always, comments, corrections, tips, and suggestions about related topics you'd like to see documented or things that'd make this article better are most welcome. I know there is a lot more that could be covered on this topic (in part limited due to word count contraints!)

Sorry, but I might not be able to personally answer additional questions in the comments below due to current and severe time constraints. However, still ask them. If you have questions you'd like to see answered in future docs, or examples added to future documentation or articles - please let us know in the comments.

Posted by Jen deHaan at 05:33 PM | Permalink | Comments (2)

Hope you all had a nice and safe holiday.

Today is Tuesday survey day! Today I'd like to get your feedback on the areas where you use the Flash docs the most, and the areas where you'd like to see the most improvement, focus, examples, etc.

You might notice that the documentation is separated into books. If you go to the Flash Help panel and click the "Table of Contents" button, you can see their titles. Examples of the books are:

* Getting Started tutorials
* Using Flash
* Using ActionScript in Flash (the chaptery sections on ActionScript)
* ActionScript Language Reference (aka: dictionary)
* Using Components (which contains the Components Dictionary - please feel free to count that as a separate book!)
* Flash JavaScript Dictionary
* Data Tutorials

And ones after that are books that likely installed with your components.

Anyway, please consider the following for this survey:

* What book(s) do you use the most?
* Where would you personally like to see the "most improvement" or attention? (Maybe you don't read a book now becuase it's poor - but you would read it if it was good/improved).
* How do you use the books? (Ie: do you look for tutorials, code snippets, high-level workflow stuff, etc?)
* What are you: a developer, a designer, or a hybrid between the two - a deseloper?
* Any other feedback?

Thanks!

Posted by Jen deHaan at 11:05 AM | Permalink | Comments (14)

Today is Tuesday LiveDocs day. Sometimes questions are posted in LiveDocs. Although please note that LiveDocs is not the place for questions about how to do things in Flash: the proper place is in the Macromedia forums. But at times, there are sections of the docs that could use some fleshing out, perhaps an additional example is necessary. So, this blog from time to time will "document" some areas where an extra example might be helpful.

First one up to bat is DataGrid.headerRelease. This example shows you how to change the direction of the DataGrid by clicking the column.

1. Drag a DataGrid onto the Stage.
2. In the property inspector, add the instance name my_dg.
3. Add the following ActionScript to frame 1 of the Timeline:

var my_dg:mx.controls.DataGrid;
my_dg.setSize(150, 100);
my_dg.spaceColumnsEqually();
var myListener:Object = new Object();
myListener.headerRelease = function(evt:Object) {
trace("column "+evt.columnIndex+" header was pressed");
trace("\t current sort order is: "+evt.target.sortDirection);
trace("");
};
my_dg.addEventListener("headerRelease", myListener);
//
my_dg.addColumn("a");
my_dg.addColumn("b");
my_dg.addItem({a:'one', b:1});
my_dg.addItem({a:'two', b:2});

By accessing the sortDirection property, you can then tell the sort order is ascending or descending. The sortDirection is actually a string, so it traces as either ASC or DESC.

Posted by Jen deHaan at 05:12 PM | Permalink | Comments (1)

A chapter from Using ActionScript has been put on the Developer Center.

www.macromedia.com/devnet/mx/flash/articles/as_bestpractices.html

Oh, and it isn't just any chapter (suuuuuuuuure dehaan, you say). It's the Best Practices chapter, that includes coding conventions and the like. I'll quote what it says on Dev Center (well, I did write it initially... so I suppose it's acceptable to plagiarize myself).

Best practices are particularly useful when you share FLA files with other Flash developers, or you want to create consistent and readable ActionScript. Adopting best practices can help you increase productivity and improve your workflow whether you're working solo or on a team. The "Using Best Practices" chapter covers recommended practices and naming conventions in Flash development, as well as best practices for writing ActionScript 2.0.

There are many other best practices that you might adopt when developing projects and writing ActionScript, and the Macromedia documentation team would love to hear about them. One way to submit feedback is by using the LiveDocs system. You can browse to the beginning of the "Using Best Practices" chapter here:

http://livedocs.macromedia.com/flash/mx2004/

Alternatively, you can find a page of this chapter in the Flash Help panel and click the View Comments on LiveDocs link at the bottom of the page. This opens a browser window where you can submit your own "best practice" recommendations into the LiveDocs system.

Sure, this stuff is already in the docs. Why put it up on the Dev Center?! Truth be told, many people didn't know it was there. Many people were still sayin' "Flash documentation people, Macromedia, why aren't there best practices/code conventions in the docs? You're missing something important!!" -- well... it was already in the docs! But no one found it. So here it is up on the dev center, so perhaps people will find it.

But it's hard to agree on best practices. Trust me, I know - there were many conflicting opinions that were no fun to deal with when compiling practices. And yes, best practicing Behaviors is no easy task. So let us know what you think or what to add. This is one behemoth document already (partly why some areas might not feel as fleshed out as they could be, and why other topics might not be in there-- yet), but your feedback will help form future documents. So - let's hear it.

Thanks and merry Thanksgiving!

Posted by Jen deHaan at 10:51 AM | Permalink | Comments (0)