Friday, April 2, 2010

[svn:fx-trunk] 10073: Fix...

Revision: 10073

Author: egeorgie@adobe.com

Date: 2009-09-08 16:37:19 -0700 (Tue, 08 Sep 2009)

Log Message:

***********

Fix http://bugs.adobe.com/jira/browse/SDK-22375 wireframe Toggle Button wireframe skin has a host component of Button instead of a Toggle Button.

QE notes: None

Doc notes: None

Bugs: SDK-22375

Reviewer: Hans

Tests run: build

Is noteworthy for integration: No

Ticket Links:

************

http://bugs.adobe.com/jira/browse/SDK-22375

http://bugs.adobe.com/jira/browse/SDK-22375

Modified Paths:

**************

flex/sdk/trunk/frameworks/projects/wireframe/src/spark/skins/wireframe/ToggleBu ttonSkin.mxml

Is there a no scale parameter in...

Hi,

I have a portfolio page where I open a swf in a new window. Because there are photographs, I would like the new window to be the document size of the swf. Is there a way to do it?

This is my code now:

function goChap(e:MouseEvent):void{

navigateToURL(new URLRequest(''http://www.mogulmarketing.com/flash/case/chappaqua.swf''),''_new'');

}

There are publish settings for html where you can control scaling, but since I'm getting it from another swf...

Help would be greatly appreciated.

My email is cindy@mogulmarketing.com.

Thanks!

PS This is the page that invokes the new page -- all the Jim Quinn pieces -- http://www.mogulmarketing.com/casestudies/web.htm

Is there a no scale parameter in...

open the embedding html, instead of the swf.?or use javascript to control the window size when opening the swf.

Books

What are the pros and cons of working in Books, as opposed to Documents? When should a Document become a Book? Is it determined by the number of pages, graphic content, or something else? To me, it appears that Documents are easier to manage鈥ut I may be wrong. Any thoughts?

Books

bbsydney wrote:

What are the pros and cons of working in Books, as opposed to Documents? When should a Document become a Book? Is it determined by the number of pages, graphic content, or something else? To me, it appears that Documents are easier to manage鈥ut I may be wrong. Any thoughts?

Books

Anything with more than 1 chapter.

I use it for magazine layout. I can keep each article separate for sending to clients/authors/typeseetters/proofreaders etc.

I find it a much more efficient way to handle the file. If you have a 200 page magazine and you're using a lot of InDesign effects it will degrade the performance of InDesign. And if the file becomes corrupt you've lost a whole magazine. If you keep it in separate indesign files you will only have one section to redo if a file becomes corrupt.

It's all about efficiency and splitting your files up into manageable sizes, plus using the book features, like automatic chapter numbering, book page numbering options and there's loads of other things a book can offer than an individual files.

You won't have a tonne of styles to fudge through, you clean up your styles, etc. and speed up your workflow. Plus others that need to work on the document and don't know聽 your system, they will get a file with only the styles used for that section etc.

And don't forget a document with many master pages, and someone says ''I want chapter 25 moved to chapter 3'' and that's a lot of fudging about with master pages and page flow. With a book you can simply move the chapter up to the new position, then update the book numbering and if you've used Chapter Heading numbering and things like that all the chapters automatically change to their new number and so on.

How Does the Book Get Into My Reader?

My message says I should go to my reader and I will find my book there, but when I oredered it, nothing asked me about my reader.?I have a Sony-e-book.?So how do I get the book into my ''list'' so that I can download it??The Adobe Format I have is 9 (something)

  • red lipstick
  • Where is the Download Link?

    I ordered a book and receaived an e-mail saying there would be a download link next to the name of the book I ordered.?There was no such link anywhere in the e-mail.?So what do I do now??I have been trying to get through to customer suport for 3 days. I will never order another e-book.?You guys just don't want to provide service.?Youwant to give as little as possible and claim your on-line information is sufficient.?It's not!!!

    Tuesday, March 30, 2010

    I get stuck on the dumbest things.

    ok, before i begin, a little rant.

    i can't help but think that the problem i came across today is entirely unneccessary. the crux of the issue is a lack of communication between skins and their host components. but what's that? you say the issue has been solved by the newest and greatest spark classes? yes, that's true, the spark classes are pretty cool and i like the way adobe has revisioned how we skin things. unfortunately, mx dinosaur components still roam gumbo and will probably feature in many flash programs to come (like this one). I hope the adobe gods are listening and i beg that they see it as their mission to replace all remaining mx classes because this current s/mx hodgepodge is RIDICULOUS!! ;-)

    anyway, moving on...

    today i got stuck on skinning the mx:LinkButton. I thought this was the best component to work with and the only additional requirement i had was to place horizontal bars on either side of the label with each bar extending flush to the walls of the container (i think you'll see exactly what i mean if you compile the code below).

    the strategy was to change the linkbutton skin to have two additional bars of varying width (the width would have to vary depending on the width of the label.text). this would have been easy with something like s:linkButton because then the skin class would have had access to the hostComponent; as it was the hostComponent property was always NULL for the mx:linkButton object.

    I thought I came up with a brilliant workaround by using a static variable in the skin class which could be used to set the bar lengths, but my solution fell flat on its face. The initial (or final) bar length did initialize properly, but each additional linkButton kept using the initial (or final) bar length setting. I don't know exactly why this is, I was hoping that once the linkButtons were created the static variable would lose its effect.

    here's the code:

    ------------------------ application - example.mxml --------------------------

    %26lt;?xml version=''1.0'' encoding=''utf-8''?%26gt;

    %26lt;s:Application

    xmlns:fx=''http://ns.adobe.com/mxml/2009''

    xmlns:s=''library://ns.adobe.com/flex/spark''

    xmlns:mx=''library://ns.adobe.com/flex/halo''

    xmlns:comp=''comp.*''

    minHeight=''200'' minWidth=''500''

    backgroundColor=''white'' %26gt;

    %26lt;mx:Canvas backgroundColor=''black'' alpha=''.7'' color=''white'' height=''100%''%26gt;

    ?%26lt;s:Group height=''100%'' width=''350''%26gt;

    %26lt;s:VGroup id=''loginLinks'' width=''100%'' bottom=''0''%26gt;

    ?%26lt;comp:MenuLinkBar label=''a bc de fg'' width=''100%'' /%26gt;

    ?%26lt;comp:MenuLinkBar label=''hi jk lm nop qrs tuv w'' width=''100%'' /%26gt;

    ?%26lt;comp:MenuLinkBar label=''xyz'' width=''100%'' /%26gt;

    %26lt;/s:VGroup%26gt;

    ?%26lt;/s:Group%26gt;

    %26lt;/mx:Canvas%26gt;

    %26lt;/s:Application%26gt;

    -------------------------- /comp/MenuLinkBar.mxml ------------------------------------

    %26lt;?xml version=''1.0'' encoding=''utf-8''?%26gt;

    %26lt;mx:LinkButton xmlns:fx=''http://ns.adobe.com/mxml/2009''

    xmlns:s=''library://ns.adobe.com/flex/spark''

    xmlns:mx=''library://ns.adobe.com/flex/halo''

    skin=''skins.MenuLinkBarSkin''

    creationComplete=''init()''%26gt;

    %26lt;fx:Script%26gt;

    %26lt;![CDATA[

    import skins.MenuLinkBarSkin;

    private function init():void {

    // find the length in pixels of the label

    var lineMetrics:TextLineMetrics = measureText(this.label);

    // variable that are dependant on our menu system

    var offset:int = 25; // accounts for the wall spacings

    var padding:int = 10; // for a little extra padding btw label and line

    // set the widths of the bar lines by setting the static variable of our skin class.

    MenuLinkBarSkin.barLineWidths = (this.width - 2*offset - 2*padding - lineMetrics.width ) / 2;

    }

    ]]%26gt;

    %26lt;/fx:Script%26gt;

    %26lt;/mx:LinkButton%26gt;

    ---------------------------- /skins/MenuLinkBarSkin.mxml ---------------------------------------------

    %26lt;?xml version=''1.0'' encoding=''utf-8''?%26gt;

    %26lt;s:Skin xmlns:fx=''http://ns.adobe.com/mxml/2009''

    xmlns:s=''library://ns.adobe.com/flex/spark''

    minWidth=''21'' minHeight=''21''

    alpha.disabledStates=''0.5''%26gt;

    %26lt;fx:Metadata%26gt;

    [HostComponent(''comp.MenuLinkBar'')]

    %26lt;/fx:Metadata%26gt;

    %26lt;fx:Script%26gt;

    %26lt;![CDATA[

    [Bindable] static public var barLineWidths:int = 0;

    ]]%26gt;

    %26lt;/fx:Script%26gt;

    ?%26lt;!-- states --%26gt;

    ?%26lt;s:states%26gt;

    ?%26lt;s:State name=''up'' stateGroups=''upStates''/%26gt;

    ?%26lt;s:State name=''over'' stateGroups=''overStates''/%26gt;

    ?%26lt;s:State name=''down'' stateGroups=''downStates'' /%26gt;

    ?%26lt;s:State name=''disabled'' stateGroups=''disabledStates''/%26gt;

    ?%26lt;s:State name=''selectedUp'' stateGroups=''upStates''/%26gt;

    ?%26lt;s:State name=''selectedOver'' stateGroups=''overStates''/%26gt;

    ?%26lt;s:State name=''selectedDown'' stateGroups=''downStates''/%26gt;

    ?%26lt;s:State name=''selectedDisabled'' stateGroups=''disabledStates''/%26gt;

    ?%26lt;/s:states%26gt;

    ?%26lt;!-- layer 1: fill --%26gt;

    ?%26lt;s:Rect left=''0'' right=''0'' top=''0'' bottom=''0'' excludeFrom=''upStates,disabledStates'' %26gt;

    ?%26lt;s:fill%26gt;

    ?%26lt;s:SolidColor color.overStates=''0xCEDBEF'' color.downStates=''0xA8C6EE'' alpha=''1'' /%26gt;

    ?%26lt;/s:fill%26gt;

    ?%26lt;/s:Rect%26gt;

    ?%26lt;!-- layer 2: fill --%26gt;

    ?%26lt;s:Rect left=''25'' width=''{barLineWidths}'' verticalCenter=''0'' height=''1.2''%26gt;

    ?%26lt;s:fill%26gt;

    ?%26lt;s:SolidColor color=''0x000000'' color.upStates=''0xffffff'' alpha=''1'' /%26gt;

    ?%26lt;/s:fill%26gt;

    ?%26lt;/s:Rect%26gt;

    ?%26lt;!-- layer 3: fill --%26gt;

    ?%26lt;s:Rect right=''25'' width=''{barLineWidths}'' verticalCenter=''0'' height=''1.2''%26gt;

    ?%26lt;s:fill%26gt;

    ?%26lt;s:SolidColor color=''0x000000'' color.upStates=''0xffffff'' alpha=''1'' /%26gt;

    ?%26lt;/s:fill%26gt;

    ?%26lt;/s:Rect%26gt;

    %26lt;/s:Skin%26gt;

    -------------------------------------------------------------------------------- -----------------------------------------------------

    that's it. any comments constructive or otherwise, would love to hear it. thanx,

    - e

    Illustrator CS4 doesnt detect Intel proc

    Hello,

    I have a new imac 2.8GHz C2D machine.. I installed the CS4 design premium upgrade.. While i didnt have the previous product installed, i did enter my CS1 serial and that enabled me to continue the install.

    What i was noticing was that the illustrator component was VERY slow.?When i look under the illustrator-%26gt;help-%26gt;system info section, it shows me :

    OS: OS X

    Version: 41.92

    System Architecture: PowerPC

    Built-In Memory: 2047 MB

    Yet my machine has C2D with 4GB of ram.

    Anyone know why its doing this?

    I did the same thing under the photoshop component and it showed the right proc.

    Thanks

    Tom