Flex Week 2 :)

Flex in a Week covered a lot of the basic steps which were helpful.  Any chance of a sequel? covering missed topics or intermediate/advanced stuff...you can call it Flex Week 2 or something

e2dev,
I did create a component MyLoginPanel and dispatch the login information back to the main application for evaluation.
However after vaidation when I try to do something like   
<s:Fade target="{MyLoginPanel.login}"/>  it does not work - I can not access that login panel to fade or apply any transition.
I know I'm missing something and I'm desperate for some explanation how to structure and access the code.
HJ

Similar Messages

  • Flex in a week: error Could not resolve s:Application to a component implementation

    Hi All, I've seen other posts mentioning this error but seems no fix has come up.
    Was just trying out the example project for Flex in a Week and out of the box am stuck on
    " Could not resolve <s:Application> to a component implementation "
    the namespace and all expected attributes are in the s:Application tag.
    Is there a common fix for using these samples?
    thanks everyone for your consideration.

    Thanks, I am using Flex Builder 3.

  • Flex 3 in a Week vs. Flex 4 in a Week

    Comparing Flex 3 in a week and Flex 4 in a week video tutorials is easy to verify that some important subjects were left out, while another important where introduced. Bellow there are a list of some important subjects of Flex 3 tutorial left out in Flex 4 tutorial:
    Using XML with E4X
    Creating SWC components (static and RSL)
    Using Shared Objects
    Localization using resource bundles
    Splitting your application into modules
    Are the contents of the subjects mentioned above covered only in Flex 3 tutorial?
    Are the contents of these subjects compatible with the new features of Flex 4?
    Best regards,
    Rogério Moraes de Carvalho

    Hi Deepa,
    You confirmed my suspects. I will study the complementary topics in "Flex 3 in a Week" video tutorial series.
    Thanks a lot,
    Rogério Moraes de Carvalho

  • I am not able to access flex 3 in a week vedios ?

    Hi,
    From past two weeks I am searching for vedios of flex 3 training. I am not able to find anywhere. Please help me out in my projext we are using flex 3 not flex 4 or 4.5.
    Thanks

    Hi,
    These videos may help you.
    Flex 3 Videos
    1) http://www.5min.com/Video/How-to-Create-a-Simple-Flex-Builder-3-80731275
    2) http://www.5min.com/Video/How-to-Create-a-Main-Application-Page-in-Flex-Builder-3-80731242
    3) http://www.5min.com/Video/How-to-Create-Properties-and-Methods-in-a-Component-in-Flex-Buil der-3-80731320
    4) http://www.5min.com/Video/How-to-Use-the-Inline-ActionScript-in-Flex-Builder-3-80731339
    5) http://www.5min.com/Video/A-Review-of-the-Flex-Application-in-Flex-Builder-3-80731251
    6) http://www.5min.com/Video/Understanding-the-Event-Object-in-Flex-Builder-3-80731360
    7) http://www.5min.com/Video/How-to-Use-an-Event-Handler-Method-in-Flex-Builder-3-80731348
    8) http://www.youtube.com/watch?v=xrjmImF0CKE
    Thanks and Regards,
    Vibhuti Gosavi | [email protected] | www.infocepts.com

  • How to get flex in a week flex 3 version

    hi all
    I just need to know is it possible to view flex 3 version of flex in a week?if it is then how?
    thanks in advance

    Hi,
    You can access Flex 3 in a Week training through the link "archive" at the top right of the Adobe Flex 4 and Flash Builder in a week main page. The note was copied bellow:
    "Note: If you haven't upgraded to Flex 4 yet, you can find Flex 3 in a Week training in our archive."
    Clicking the link "archive" will direct you to the Flex 3 in a Week Training.
    Regards,
    Rogério Moraes de Carvalho

  • Where to get source code of Flex in a Week training

    Hello, where to download source code of Flex in a Week
    training? Thanks!

    Here's a download link to my source files up to exercise 9.
    http://www.2shared.com/file/4204375/2060f179/up_to_9.html
    They can be opened in a text editor.

  • Flex in a week training

    Hi Folks,
    I installed Adobe Media player and am trying to go through the flex in a week training.
    http://www.adobe.com/devnet/flex/videotraining/
    using the rss feed at http://www.adobe.com/devnet/flex/videotraining/
    But at times when I am trying to open up a video it starts and then within seconds stops....(for example Video 3 Flex Builder Workspace and project is supposed to be 7+ minutes but does not start)
    How can I down load the video again ?
    Maybe it has not downloaded fully ? (though the icon shows up as the "downloaded and ready to play" breen down arrow with a cd behind)
    Appreciate any guidance !
    Regards,
    Naresh

    Try removing then reinstalling the media player. Also your download may be corrupted..

  • Links error in "flex in a week video training"

    can someone explain me why all links in the page http://www.adobe.com/devnet/flex/videotraining.html which don't have an icone before don't work?
    for exemple on my computer, Creating a user interface, Adding data to your application, Handling a user event... don't work
    a message says to me : IE cannot open page... operation aborted
    please, this tutos look goods but how can I acceed to them?
    cédric, a french user
    best regards    

    Hey,
      I googled your problem and it could be a couple of things with the code for the exercise pages depending on your version of IE. What version of IE do you have?
    An easy fix might be to try a different browser such as Firefox or Chrome or you could try using  a proxy site such as http://www.liveoxy.com/ to open the exercises.

  • The last lesson in the 1st day videos of Flex in a Week is a repeat of "Scrollbars"

    If anyone knows how to access the last video, please let me know. Or, if you are out there Adobe people, can you please correct the link issue?
    Thank you!
    Holly

    Ok. The formula didn't have to be that fancy after all. We can use COUNT to count the number of entries, then use INDEX to return the corresponding entry.
    If the actual weights are in column B and goal weight in E2, then in D2 enter this formula:
    =E2-INDEX(B,COUNT(B),1)
    So, a couple caveats:
    1) Must start entering the weights in the top body cell (whether table has header or not, see below).
    2) Column B cannot have any extraneous numbers (this will throw the count of entries off).
    Free Image Hosting
    If you are actually using Numbers '09 and the table has headers, then for some reason the formula is slightly different depending on how many header cells are in column B. E.g. if one header, then enter =INDEX(B,COUNT(B)+1,1); if two headers, then enter =INDEX(B,COUNT(B)+2,1); Or, simply enter =INDEX(B,COUNT(B)+ROW(B)-1,1), which adjusts to whatever number of header cells.
    Robin
    Message was edited by: sharknca

  • New 2014 X1 Carbon Touch - 1 Week Review

    I've had the New 2014 Carbon X1 for about a week now, so I thought I'd post a review about my experiences thus far.
    The version I received was the high end model, i7 4th gen, 8gb ram, IPS 2560x1440 touch display. This is the first Lenovo device I have purchased, and I did so at the recommendation of my brother who has owned a T series for the last 3 years. I am a film student, so my intention is to do some light video editing (not rendering) and lightroom/ photoshop work on this device (in addition to daily use of OneNote). I was looking for a powerful ultrabook with good build quality, battery life, and cooling when I purchased this laptop.
    Hardware:
    The hardware on this device has highly conservative look, which I appreciate. The laptop doesn't draw attention, but is pleasing to the eye when viewed up close. I like the fact that there are not as many creases or lines that run through the body of the device (when compared to other devices), which results in a more free flowing but unified appearance.
    The matte plastic on the top of the lid has a slightly rubberized texture, making the device easy to grip. My hands get hot and moist consistently, so the lid does occasionally pick up some faint moisture streaks if I carry it without a case. The slightly rubberized texture is pleasant to the touch and is easy to wipe down with a damp cloth. The inside of the device has a similar plastic around the keys and palm rests, but does not attain as much of a rubber (soft) feel as the lid. The texture on the palm rests is good, and stays cool under extended typing conditions.
    At first I was having issues with the keyboard whereby I would press the spacebar too early in a word. This is due to not pressing the letter keys down firmly enough. After adjusting my finger pressure while typing, I have been able to avoid this problem for the most part. The pressure I am applying to the keys is just a hair more than I am used to, but it is something that doesn't cause a major inconvenience. The backlight on the keyboard is excellent, not too bright or too dim at any one moment.
    The fingerprint reader took several tries to set up, mostly because there is a discrepancy between the lenovo fingerprint software and the integrated Windows 8 security fingerprint setting. By installing my index finger for login on both programs, I was able to successfully unlock the computer from sleep with a swipe of my finger. I am really impressed by the integration of a light on the sensor. When my print isn't accepted the first time, an amber color light flashes on site. Its easier to just look at the light than have to switch my glance back to the monitor after every swipe (like my previous HP laptop). Upon a successful swipe, a lime color light flashes on the reader.
    The screen on the device meets my expectations in every way. The display is IPS which is required for accurate photo editing, and it is LED which makes it very power efficient. Viewing angles are fine, but they could be a little better. Brightness is excellent, but the initial settings have Auto Brightness enabled. On this setting, pumping the brightness up to "100%" really means 100% of what the Auto Brightness function deems appropriate for the current ambient light. To have full manual control, Auto Brightness must be disabled. This results in a much brighter screen with beautiful whites, deep blacks, etc. This is a 300nit display so brightness is very well addressed. As a side note, the laptop was shipped with what appears to be an installed screen protector. There are several holes around the microphones and camera, and a tiny seam along the edge of the screen. The protector is virtually unnoticeable, so I'm leaving it on for the time being. It is much cleaner than any other factory installed laptop screen protector (or film) than I've ever seen (no bubbles, peel-off tabs, or misalignment).
    Cooling on the device is good, but it did not exceed my expectations. On power saver mode, the bottom of the laptop is cool to the touch except the back right corner. To the touch the corner feels as warm as something that's been in the sun for 5 minutes or so which is excellent. I have a temp gun so I'll have to check specifics later. On high performance mode, heat significantly increases. Most of the bottom of the laptop heats up even if no intensive tasks are being run. If the laptop is on my lap, I prefer it to be in power saver mode for this reason.
    Battery life is good for such a small laptop. I have 8 hours of back to back classes and I type notes basically the whole time. With this laptop, it is entirely possible to go that full period without a charger. So far I have done this twice. The settings I use are Wifi off, low brightness, and I enable high contrast mode in accessibility center so the glaring white of OneNote doesn't blind me during the film screenings.
    Webcam looks great for google hangouts, and the microphones are the most sensitive I've ever used. They can pick up the voice of someone to the side and across the room with great clarity.
    Overall the weight and feel of the laptop is very pleasing. Such a light weight for its size, and it feels solid to the touch and doesn't flex the slightest when handled different ways (carbon fiber ++). When compared to a macbook air, it is nearly identical in size and weight. However, I find typing on the lenovo is much more pleasant because the front edge of the palm rest isn't sharp enough to dig into my hands.
    Software
    The Lenovo Solution software (pinned to taskbar upon installation) is easy to use and responsive (unlike similar HP suites). I am actually going to rely on this software for updates instead of disabling it.
    For the first few days of use, there was a touch keyboard toolbar button pinned to my start bar that would appear again even after disabling it. I researched the problem and it was permanently removed from the taskbar by uninstalling the touchpad driver and reinstalling it. Odd.
    The adaptive row of keys is a good idea, but it is not as responsive as I'd like. When using the visual gestures or dragon voice control, there is significant lag between pressing the adaptive key and the program actually running. Each time, a lenovo window appears and it takes several mouse clicks to get to a functioning state for each button. One thing I am VERY disappointed about is the lack of any play/pause/stop/next/previous buttons for the adaptive row to use with a media player. These buttons are necessary, and not having them is unacceptable in my opinion.
    Touch responsiveness is liquid smooth in both power saver and high performance modes. Zooming in on bing maps, drawing with all ten fingers, swiping through metro - all a delightfully lag-free experience.
    Windows 8 - ahhhhhh. This is my first device to run windows 8, and it's alright. It'll take some getting used to, but from my experience so far it is responsive and useful in its design. I really want to be able to pin a firefox link to my start screen, but it seems like all I can do is pin the firefox app instead.
    As mentioned in a previous post, there are several issues with programs that aren't adapted to the ultra high res display. That discussion can be found here.
    The sleeve I purchased for this machine was the "V7 Ultra Protective Sleeve for 13.3-Inch Ultrabook and Notebook". The fit is great (the slightest bit loose on the ends) and the quality is above par for such a low price. I spilled a significant amount of apple juice on the case just yesterday (shakes head) and it protected the notebook well.
    Overall Experience:
    I'm pleased with my purchase. High price point? YES. For that amount I think the RAM should be at least 16gb and the SSD could be 500gb. Overall it is a pleasure to use and look at. Honestly so many things are right about this machine, it just allows me to focus on my work and stop worrying about my battery level or my trackpad glitching or the CPU overheating or lag or other petty issues that other notebooks make you deal with. That's what I like - its a smooth connection between me and getting things done while away from my desktop.
    I haven't edited video on it yet, so that will come in a few weeks. I'm planning on buying an external drive to hold the files while I edit, then just plug it into my desktop when I get home ready to render.
    Eli Bottom
    elibottom.com
    imagesalt.com

    ColonelONeill wrote:
    How's the new clickpad?
    Does the keyboard flex under reasonable pressure?
    Is the adaptive bar actually a pixel-based LCD or just a series of predefined patterns like the really old LCD displays?
    The "new" clickpad is very slick. The texture is good but just a little too rubbery for my taste. In comparison with my brother's old T series, I prefer the X1.
    Under reasonable pressure, absolutely not. The amount of force it takes for me to flex it is something I'd never do under normal use. It feels very solid in my opinion.
    Upon a close inspection, the adaptive touch bar appears to be the old LCD type. I really want those media keys.

  • Flex 3/4 Initialization Timing Changes?

    Hi there.  This isn't end-of-the-world critical, but I'm trying to better understand what's going on here.
    We have a relatively large and complex business app (several hundred classes split into a core application framework plus multiple dynamically-loaded product modules), originally written in Flex 3.2.  As part of our new release, we are taking the chance to port it over to Flex 4.5; I've spent the past week doing so.  We're continuing to use the Halo theme for the time being, to minimize the initial disruption.
    I've pretty much gotten it working, but I'm still trying to understand the key behaviour change that I've observed.  A lot of our code is failing at initialization time.  I'm still nailing down exactly what's different, but the most obvious bit is that it seems like, in commitProperties(), properties that refer to other objects in the same parent don't exist yet, where they previously did.  So I'm getting null pointer exceptions where I wasn't previously.
    Similarly, I have a few objects where the property refers to the object itself.  They're graphing objects, which have a property that describes how to set up the dataFunction.  This property is typically set to one of several functions available on the object.  So graph "foo" would set this function to "foo.useDateForY" or some such, using one of these utility functions on the class that says how to set up the graph.  This previously worked, but now the property is failing because "foo" is null when it is trying to resolve the property value.  This seems likely to be related to the above.
    Finally, I've also observed what appear to be differences in the resolution of the lifecycle for non-visible objects.  Again, I haven't had time to nail this down precisely, but it feels like I used to get CREATION_COMPLETE in a bunch of cases that aren't getting it any more -- specifically, this seems to be happening for objects that I'm building up before adding them to the visible graph.  I build lots of screens upfront when a product is loaded, but don't actually add them into the tab structure until they are invoked.  Similarly, we have popups that we want to be populating as we go, long before they are displayed, but I don't seem to be getting CREATION_COMPLETE for them when I used to.
    So it seems like something has changed subtly in the UIComponent lifecycle, having to do with the timing of resolving IDs, setting properties to them, and calling commitProperties(); maybe also something having to do with how parenting relates to finishing the lifecycle.  Does anybody have a clue what I'm talking about here?  And is there a document somewhere that describes the timing changes more clearly?  I've seen several documents talking about 3 -> 4 changes, but haven't noticed anything on this particular topic...

    Yes, the timing of when child objects are created has changed relative to
    when the constructor runs, but the lifecycle methods and events have not
    changed.  If you rely on commitProperties to resolve things, it should be
    ok.
    The only cases I've seen where creationComplete doesn't fire is if there is
    an invalidation loop going on which is slightly more possible if using
    multiline text controls whose height depends on width or vice-versa.

  • Weekly build notes listings

    Since there are major changes going on in the TLF weekly builds, and the ASDocs aren't up to date, and the changes made are not searchable, I thought people might want the list dumped on here so changes to particular classes would show up in a forum search.  To see the changes made in Build 360, check out the TLF Blog post on it ( http://blogs.adobe.com/tlf/2009/02/tlf_api_changes_in_build_370_1.html ).
    Here's the list.  Maybe this could become a common practice.
    Build 432, Fri May 15 2009
    Changes in build 437 (2009/05/22)
        * remove flashx.textLayout.edit.UndoManager and flashx.textLayout.IUndoManager
        * Fix 2330964 BackgroundColor Placed incorrectly from TextLineFactory. Actually was in 436.
        * Fix 2326588 TextContainerManager Does Not Support Background Color
        * Fix 2330946 Remove TextContainerManager.trunctationOptions property
        * Fix 2337918 Please expose the scrollToPosition() API in TextContainerManager
        * Fix 2336672 Preserve selection when switching editingMode in TextContainerManager
        * Setting editingMode to the current editingMode should do nothing in TextContainerManager
    Changes in build 436 (2009/05/22)
        * Fix 2331711 TextContainerManager now sends a DamageEvent from setText().
        * Fix 2326543 bug where selection wasn't being extended on mouse drag.
        * add [RichTextContent] metadata to SpanElement and FlowGroupElement mxmlChildren properties
        * Fix 2337740 Flex bug SDK-20964 TCM rcycling bug
        * Partial fix 2330964 background color placed incorrectly from TextLineFactory
        * Remove vestigal experiment with Tables code
        * Fix 2321538. On the Mac, the keyboard shortcuts for cmd-A,C,V,X were not working.
        * Fix 2326543, "drag select of scrolling flows doesn't expand selection".
        * Fix 2329527. Content bounds being reported was slightly different between the factory and TextFlow composer.
        * Fix 2328695 TextContainerManager Stops Receiving FocusIn Events. This is a complete fix - previously this bug was worked around
        * Added TextLineFactoryBase.isTruncated
        * Fix 2315119 - Graphic will be redrawn when link applied.
    Changes in build 434 (2009/05/22)
        * Fix 2323921: RichText truncation doesn't work in all cases
    Build 432, Fri May 15 2009
    Changes in build 432 (2009/05/14)
        * Fixed regression that broke truncation feature
        * Added TextLineFactoryBase.isTruncated
        * Changed text line factory behavior such that scrolling is turned off when truncation options are set
    Build 427, Fri May 8 2009
    Changes in build 427 (2009/05/07)
        * Fix bug - RTE in computeSelectinIndexInContainer
        * Namespace change -- mxml namespace for TLF was "library:adobe/flashx/textLayout". Now it is: library://ns.adobe.com/flashx/textLayout".
        * Fix bug - Scrolled TextContainerManager Can be Difficult To Create Point Selection
    Changes in build 426 (2009/05/06)
        * Fix bug - TextFlow double-deletes text when pressing the backspace or delete key
    Build 422, Fri May 1 2009
    Changes in build 422 (2009/04/30)
        * API Changes: TextContainerManager now has a getContentBounds function, in place of individual getters for contentLeft, contentTop, etc. ContainerController also now has a getContentBounds function, in place of individual getters. Added functions to TextContainerManager to support custom classes for ISelectionManager and IEditManager (see createSelectionManager and createEditManager).
        * API changes for TextContainerManager:
              o getInteractionManager renamed to beginInteraction(), and added a new function endInteraction() which clients should use after beginInteraction() to signal that they are done with selecting/editing. This tells the TextContainerManager that it can go back to factory mode, which is more efficient.
              o invalidateInteractionManager() removed and replaced with two new functions, invalidateSelectionFormats() which clients should called when SelectionFormats have changed, and invalidateUndoManager which clients should call to change the undo manager.
        * API Changes for InputManager
              o InputManager renamed as TextContainerManager
              o IInputManagerClient removed, now you can subclass InputManager and override its methods
        * API Changes:
              o InputManager
                    + damaged property renamed to isDamaged() function
                    + focusSelectionFormat renamed to focusedSelectionFormat
                    + container retyped to Sprite
                    + compositionWidth and compositionHeight removed as constructor parameters, now you need to set the properties on the InputManager you create
              o ContainerController
                    + container retyped to Sprite
              o ISelectionManager
                    + focusSelectionFormat renamed to focusedSelectionFormat
              o IConfiguration & Configuration
                    + focusSelectionFormat renamed to focusedSelectionFormat
        * API Changes:
              o ISelectionManager
                    + setSelection deselects if negative numbers are passed in.
                    + selectAll removed, you can call ISelection.setSelection() to get the same behavior, if you need to redraw the selection, call ISelectionManager.textFlow.flowComposer.updateAllControllers().
                    + flushPendingEvents moved to IInteractionHandler
                    + notifyInsertOrDelete moved to IInteractionHandler
              o IUndoManager
                    + clear renamed to clearAll().
                    + undoLastOperation renamed to undo()
                    + redoLastOperation renamed to redo()
        * API Change: SelectionEvent now contains a SelectionState, not an ElementRange; this is much cheaper for us to provide. ElementRange is now tlf_internal. ElementRange.firstLeafPosition renamed to absoluteStart, ElementRange.lastLeafPosition renamed to absoluteEnd.
        * API Change: TextScrap.copyTextScrap renamed to clone.
        * API Changes to InputManager. defaultInputManagerConfiguration renamed to defaultConfiguration. composeToController renamed to compose(), and updateToController renamed to updateContainer().
        * API Changes:
              o ISelectionManager:
                    + Event handling functions moved out of ISelectionManager into new interface, IInteractionHandler
                    + selectionFormat renamed to currentSelectionFormat
                    + selectionState renamed to function getSelectionState()
                    + setSelection now takes default parameters to select the entire flow
                    + noFocusSelectionFormat renamed to unfocusedSelectionFormat
              o SelectionFormat:
                    + blockAlpha reanmed to rangeAlpha
                    + blockBlendMode renamed to rangeBlendMode
                    + blockColor renamed to rangeColor
              o IEditManager:
                    + added get undoManager()
                    + added changeElementID()
                    + added changeElementStyleName()
              o SelectionManager:
                    + activeMark and anchorMark are now private
                    + selectionChanged is private
                    + setSelectionState is tlf_internal
              o EditManager:
                    + stage is private
                    + ChangeElementIdOperation renamed to ChangeElementIDOperation
    Changes in build 420 (2009/04/28)
        * API change: Removed the misleadingly named and superfluous TextFlowLine.textIndent. Documented and ensured consistent use of TextFlowLine.lineOffset as lhe line's offset in pixels from the appropriate container inset (as dictated by paragraph direction and container block progression), prior to alignment of lines in the paragraph.
        * API change: more changes to the factory classes. ITextLineCreator is now a property of the base class, so instead of passing it in the constructor you construct and then set the property in the factory. bounds property renamed to compositionBounds, and measuredBounds renamed to contentBounds. containerController property is now private.
        * API Change: moved ITextLineCreator interface from the elements package to the compose package.
        * PlainTextExporter is now public and has methods for controlling the paragraphSeparator and whether discretionary hyphens are included in the export. To use it, you can either construct it directly, or via the TextFilter class. Removed the newlineIndicator string from IConfiguration.
        * Fixed a bug where tabs in RTL text were being being offset by textIndent and marginRight values.
    Changes in build 419 (2009/04/24)
        * Once a mouseWheel event has been handled, mark with preventDefault so client applications don't also try to handle it.
        * Don't start compose if text is already composed. Optimization for callers of composeToPosition.
        * Always call resetContentTopLeft, to give more accurate top left positions, particularly for cases where the text is outdented and left aligned.
        * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
    Build 418, Fri Apr 24 2009
    Changes in build 418 (2009/04/23)
        * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
    Changes in build 417 (2009/04/22)
        * Fixed Vertical Justification behavior; it now increases the spacing between consecutive lines proportionally rather than spacing lines uniformly.
        * API Changes: Renamed DisplayObjectContainerController to ContainerController, and removed IContainerController and IInternalContainerController. Wherever you used to use "IContainerController" or "DisplayObjectContainerController" now just use "ContainerController".
              o Moved some functions that were public into the tlf_internal namespace: effectivePaddingLeft, effectivePaddingTop, effectivePaddingRight, and effectivePaddingBottom.
              o ColumnState.createColumnState removed. A ColumnState constructor now takes all the relevant values, so whereever you used to do this:
                    + var columnState:ColumnState = ColumnState.createColumnState(...your values here...);
              o you can now do this:
                    + var columnState:ColumnState = new ColumnState();
              o ColumnState.getColumnAtIndex(index) has been renamed to getColumnAt(index). So, once you have the columnState, you do, for instance:
                    + var columnRect:Rectangle = getColumnAt(0);
        * Fixed bug where spaces at end of a line would "overflow" into neighboring columns. New code keeps drawing of cursor at the column boundary and limits block selection drawing to the same bounds.
        * Enhancement to cursor navigation for Right to Left text systems. Previous code moved cursor according to logical order vs. visual order. Result was that a right arrow key press in Arabic, Hebrew or other RTL languages meant that the cursor actually moved left. New code moves cursor according to the visual order of the text based on the direction of the entire text flow. Note that changing the direction on a paragraph will not alter the behavior of the cursor, nor will the presence of LTR text within a RTL text flow. This means that if a TextFlow is set to Right to Left and a given paragraph is entirely in English and the paragraph is set to be Left to Right, the cursor will seem to move in the wrong direction. TLF does not support customization of cursor movement based on the locale or direction of anything except the parent TextFlow.
        * Fixed a bug that caused undoing an ApplyFormatToElementOperation to have no effect.
        * API Changes:
              o DisplayObjectContainer event handling functions renamed:
                    + processMouseOverEvent -> mouseOverHandler
                    + processMouseOutEvent -> mouseOutHandler
                    + processMouseWheelEvent -> mouseWheelHandler
                    + processMouseDownEvent -> mouseDownHandler
                    + processMouseUpEvent -> mouseUpHandler
                    + processMouseMoveEvent -> mouseMoveHandler
                    + processMouseDoubleClickEvent -> mouseDoubleClickHandler
                    + processFocusInEvent -> focusInHandler
                    + processFocusOutEvent -> focusOutHandler
                    + processActivateEvent -> activateHandler
                    + processDeactivateEvent -> deactivateHandler
                    + processKeyDownEvent -> keyDownHandler
                    + processKeyUpEvent -> keyUpHandler
                    + processTextInputEvent -> textInputHandler
                    + processContextMenuSelectHandler -> menuSelectHandler
                    + eventHandler -> editHandler
              o ISelectManager & SelectionManager & EditManager renamings:
                    + eventHandler -> editHandler
        * API Changes: renamed IContainerController.scrollLines to getScrollDelta, renamed InputManager.scrollLines to getScrollDelta, and removed constants for default container width and height.
    Changes in build 412 (2009/04/10)
        * API CHANGE: DisplayObjectContainerController methods processCopyEvent, processCutEvent, processPasteEvent, processSelectAllEvent collapsed into a single processEvent that handles all these basic events. Added to ISelectionManager a new function, processEvent for handling these same events in the SelectionManager, and removed processSelectAll, which is no longer used. cutTextScrap and pasteTextScrap moved from ISelectionManager to IEditManager, since these are editing operations.
    Build 411, Fri Apr 10 2009
    Changes in build 411 (2009/04/09)
        * Fixed a bug where noFocus selection format was not being set on re-activation
        * API CHANGES. These functions in IFlowComposer were renamed:
              o updateContainer -> updateToController
              o updateAllContainers -> updateControllers
              o composeContainer -> composeToController
              o composePosition -> composeToPosition
        * API CHANGE: Changing name of TextFlow.hostTextLayoutFormat to hostFormat
    Changes in build 410 (2009/04/08)
        * Fix bug where leading info used for composing the next line was being saved prematurely, causing incorrect layout if the current line needed to be composed in multiple passes.
    Build 409, Tue Apr 7 2009
    Changes in build 409 (2009/04/07)
        * Fix bug where clicking on container when height or width NaN doesn't work. When measuring, transparent hit detect region wasn't being redrawn to correct size after composition.
        * API CHANGE: Plain-text import/export changes. Newline indicators exported based on setting in IConfiguration.newLineIndicator. On import, LF/CR/CR+LF are all recognized as new line indicators.
        * Compose to container size with scrolling on -- previously was composing to double composer size. This may flush out some invalid line bugs.
        * Fixed a bug with blockProgression="rl" and compositionWidth=NaN, lines were getting improperly clipped out so that no text appeared.
        * API CHANGE: Renaming functions in IFormatResolver. invalidateAllTargets is now invalidateAll, and invalidateTarget is now invalidate. resolveTextLayoutFormat is now resolveFormat.
        * API CHANGE: eventMirror on FlowLeafElement and SubParagraphGroupElement is now tlf_internal.
        * API CHANGE: Moving TextRange from the edit package to the elements package.
    Changes in build 406 (2009/04/02)
        * API CHANGE: Renaming DamageEvent.damageStart to damageAbsoluteStart.
        * API Change: IConfiguration.includePartialLine renamed to overflowPolicy. Defined new class OverflowPolicy that describes the different policies that can be used to control whether lines that fall at the end of the container are included in the container, or not.
    Changes in build 405 (2009/04/01)
        * API CHANGE: IFlowComposer.firstDamagePosition renamed to damageStartPosition.
        * API CHANGE: Rename GeometryUtil.getRangeBounds to GeometryUtil.getHighlightBounds.
        * API CHANGE: ParagraphElement.getText now takes an additional optional parameter that specifies the terminator for the paragraph. By default, this is the Unicode paragraph terminator character (\u2029), but you can make it whatever you want, including a simple newline by passing a String for the paragraphTerminator. This change is backwards compatible for current callers of getText().
        * Fix clipping problem when text is placed above the container (6 lines aligned verticalAlign = bottom in a space that fits 4 lines).
    Changes in build 404 (2009/03/31)
        * Updating typgraphic case --Markup and API Change-- Now uses a new class TLFTypographicCase, and has different options. Support for "title" and "caps" dropped. Use TLFTypographicCase with TLF in preference to flash.text.engine.TypographicCase. "smallCaps" renamed to "capsToSmallCaps". "capsAndSmallCaps" renamed to "lowercaseToSmallCaps". Also made AUTO the default setting for kerning, which matches FXG spec.
    Changes in build 403 (2009/03/30)
        * format Markup Changes:
              o <TextLayoutFormat> now <format>
              o When referring to a format id, don't use brackets. So this:
                <TextLayoutFormat id="english" locale="en" fontFamily="Minion Pro"/>
                <p marginBottom="15" ><span format="{english}">This text is supposed to be in Minion Pro via a named character attribute</span></p>
                Is now this:
                <format id="english" locale="en" fontFamily="Minion Pro"/>
                <p marginBottom="15" ><span format="english">This text is supposed to be in Minion Pro via a named character attribute</span></p>
        * API Changes:
              o Rename FlowElement.textLayoutFormat -> format
              o Rename FlowElement.computedTextLayoutFormat -> computedFormat
              o Rename IContainerController.textLayoutFormat -> format
              o Rename IContainerController.textLayoutFormat -> computedFormat
              o Rename DisplayObjectContainerController.textLayoutFormat -> format
              o Rename DisplayObjectContainerController.textLayoutFormat -> computedFormat
    Changes in build 402 (2009/03/27)
        * verticalAlign of "middle" or "bottom" will now align to the compositionHeight (or compositionWidth in vertical text) even if the height of the text exceeds the compositionHeight. This means that lines that don't fit may be get pushed above the box, or (for middle) pushed both above and below. It also means that all lines will forced to compose to the end, so it will be quite slow to use verticalAlign in large text flows. Made some corresponding fixes to scrolling to make it work with text off the start of the container. Added some new test cases to exercise this functionality in all the different alignment settings.
        * Scrolling fixes for next/previous line with arrow keys. Fix a bug where the arrow key would move to the end of the line if the line required composition (e.g., the line was not previously in view). Also fixed a bug when scrolling up by a line where it would scroll down instead.
        * doOperation used to return an SelectionState, but with the exception of two places that were using it internally, all external callers only checked to see if it was null or not. null was being used to indicate failure, or nothing changed, which means that the operation is not placed on the undo stack. Now it returns a Boolean, true for success, false for failure. There may be further changes in this area to make FlowOperations simpler.
    Changes in build 397 (2009/03/20)
        * Made DisplayObjectContainerController's and FlowElement's TextLayoutFormat properties read/write (used to be write-only).
        * Merge ContainerControllerBase class into DisplayObjectContainerController.
        * Mark TextFlow class as final
    Changes in build 396 (2009/03/19)
        * Fix RTE in StandardFlowComposer.releaseLines
        * Fix possible source of the RTE on null reference from findFirstAndLastVisibleLines in ContainerControllerBase.
    Changes in build 394 (2009/03/17)
        * Fix issue with changes made in StatusChangeEvent to embedded graphics by blocking recursive composition. Bug 2298043
        * Add IFlowComposer.composeInProcess property.
        * Fixed problem where first part of a link could not be replaced by a new link. New code allows partial replacement of a link element with a selection which starts at the first character.
        * Fixed a problem where the cursor was getting set to the I-beam, and wouldn't set back.
    Changes in build 393 (2009/03/16)
        * Fix a bug where keyboard navigation with linked containers was causing a scroll because it was trying to scroll to a position not in the container.
    Changes in build 392 (2009/03/13)
        * Removed optimization that was preventing scrolling in the logical width direction if scrolling in the logical vertical direction was turned off.
        * Removed the container-level mouseMove and rollOver handlers which were changing the link state. These are now part of the LinkElement, and added only when they are needed.
    Changes in build 390 (2009/03/11)
        * Fix for application of attributes to a point selection where only the last attribute would be applied. New code applies all attributes applied to the point.
        * IContainerController.contentWidth (or contentHeight in vertical text) is now based on the actual text width, not the unjustified text width. This fixes some problems where scrolling wasn't working correctly because the reported width of the text was greater than the compositionWidth, but lines were wrapped. It does mean that to get the unjustified width you will have to set the textAlign to something other than "justify", recompose, and then get the resulting width.
        * Fix for unintended scroll when at the end of a TextFlow.
        * Fix for RTE when dragging over text generated from a factory, or non-TLF TextLines.
        * Changes for alignment and measurement. You can now set NaN for compositionWidth or compositionHeight, and TLF will compose and use the generated contentWidth or contentHeight for alignment, scrolling, etc. The composer now generates a topLeft for the bounds, so you can make a full "content bounds" using contentLeft, contentTop, contentWidth, and contentHeight.Note that this is logical bounds and not inked bounds, so there are some circumstances where ink will not fit in the content bounds.Fixed bugs in how the factory was doing vertical alignment that caused it to be a few pixels off.Fixed some incosistencies between how the standard flow composer worked and how the factory's simple composer works -- composition results should now be more uniform. Added a new test program, MeasurementGrid, for testing all this. It's still a work in progress.
    Changes in build 388 (2009/03/09)
        * Fixed issue where applying link or TCY to the last span of a paragraph caused a dangling span to remain with the para terminator.
        * Fixed issue where text would go into a link when it was the last element in a paragraph. Newly typed text now goes into a new span when the selection marker is at the last index.
    Changes in build 386 (2009/03/06)
        * Fixed issue with placement of underline and strikethrough on inline images.
        * Fixed placement of underline and strikethrough on text which has a baseline shift applied to it.
    Changes in build 385 (2009/03/04)
        * Combined SWC 'textLayout.swc' now included in the libs directory of the build. This includes everything from textLayout_core, textLayout_edit, and textLayout_conversion.
        * Combined RSLs now included in the rsl directory of the build. Both an unsigned SWF and signed SWZ are created. These include everything from textLayout_core, textLayout_edit, and textLayout_conversion.
    Changes in build 382 (2009/03/02)
        * Fix issue with composing a TextFlow containing just an empty ParagraphElement.
        * TextLineFactory will generate lines that included InlineGraphics whose source is a "class" - normally an embedded graphic.
        * Expose eventMirrors - use FlowElement.getEventMirror function to access the eventMirror.
    Changes in build 381 (2009/02/27)
        * Fixed issue with graphic assigned to ILG getting the wrong sizing.
        * Factory instance functions renamed to textLinesFromString and textLinesFromTextFlow. Static functions renamin unchanged.
    Changes in build 380 (2009/02/26)
        * Made backgroundColor work with TextLineFactory. This required an API change - the callback to the factory now must take a DisplayObject as its parameter, since it won't always be passed TextLines. Also, the background shapes themselves no longer include leading, so they do not exactly coincide with the selection bounds. This was another change to support calculating the shapes during composition as opposed to afterward. Also added a snapshot test as part of FactoryImportTest that uses backgroundColor, in addition to updating the existing unit tests.
    Changes in build 379 (2009/02/25)
        * Fixed for multiple containers ( we were getting incorrect textLength in the containers), as well as a fix that forces scrollToPosition to compose if the text isn't composed yet.
        * Fix so that we scroll to the active position of the selection after we extend the selection with a keyboard event. Also fixed some of the TextRangeUtil functions used for nextLine, etc. to make sure text is composed through selection before processing that depends on composition results.
        * Plain text import now consistently converts \r to space; previously it was converting only the first one. Still not clear what correct behavior should be.
    Changes in build 377 (2009/02/23)
        * Fix bug with importing trailing empty div elements.
    Changes in build 374 (2009/02/18)
        * Added support for TextField-style leading. A new leading model value allows lineHeight to be interpreted as the distance of line's ascent from the previous line's descent. Further, lineHeight can be negative. which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
    Changes in build 372 (2009/02/16)
        * Added "enableAccessibility" property to IConfiguration, defaults to false. Allows clients to avoid paying price for TextAccImpl objects unless needed.
        * Added support for truncation for text composed using TextLineFactory. The TextLineFactory methods now take a truncation options parameter, which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
    Changes in build 371 (2009/02/13)
        * Fixed a number of bugs relating to scrolling by line.
        * Measurement changes. Changed the way contentHeight and contentWidth are calculated, now they reflect the size of the text, regardless of alignment. Eliminated unjustifiedContentHeight and unjustifiedContentWidth; use contentHeight and contentWidth instead.
        * Fix RTE in damage when we try to damage back one line, for textFlow that doesn't have any leaf nodes.
        * Changed InlineGraphicElement so that GraphicElements (and the TextBlocks they are part of) don't get released. Fixes RTE on null pointer in places where we access the GraphicElement.
        * Fix bug deleting all of the last Span of a paragraph, plus some of the following paragraph.
    Changes in build 370 (2009/02/12)
        * Removed textFlow property from CompositionCompletionEvent. Use event.target to get to the TextFlow.
    Changes in build 369 (2009/02/11)
        * Fix issues in usage of hostTextLayoutFormat
        * Fix FXG export to not export styles with value "inherit"
        * lineBreak property no longer inherits by default
    Changes in build 368 (2009/02/10)
        * Fix for RTE that happens after cancelling an operation (calling preventDefault on a FlowOperationEvent).
    Changes in build 367 (2009/02/09)
        * ported to Flex 4.0.0.4836. All SWCs now build with this SDK.
    Changes in build 366 (2009/02/06)
        * FlowGroupElement addChild, addChildAt and replaceChildren methods now automatically delete new elements from any existing parents. Previously the code would test for parent on new elements and throw.
        * mxmlChildren FlowElement property which is normally used for mxml compilation of TextFlow objects now always deletes existing children
        * Fix a memory leak issue with the TextLayoutFormat cache
        * Fix cascade bug with non-inheriting attributes getting inherited
    Changes in build 365 (2009/02/05)
        * Changed TextLayoutFormat.backgroundColor to allow setting value of "transparent" (now the default). Because of this new value for backgroundColor, backgroundAlpha now defaults to 1.
    Changes in build 364 (2009/02/04)
        * Performance improvement for handling of TextFlow.hostTextLayoutFormat. The code now assumes that once set by the client the supplied object won't be changed. This avoids a copy.
    Changes in build 363 (2009/02/03)
        * Performance work. Remove getCanonical from TextLayoutFormat.
        * Fix for RTE cancelling SplitParagraphOperation.
        * Fixing some float bugs.

    Try searching discussions--see: http://discussions.apple.com/thread.jspa?threadID=684662
    only caveat is link is dated-I googled for newer...
    MacBook Pro 17" Mac mini (Intel)   Mac OS X (10.4.8)  

  • 1 week with my X100e

    I was compelled to write my own review after reading some bad ones out there (mostly about the MV-40)...
    My Specs:
    AMD Turion Neo X2 Dual Core (L625)
    4GB RAM
    160GB intel X25-M SSD
    Bluetooth
    Windows 7 Pro x64
    -plus all other standard equipment.
    The PROs:
    Form factor:
    Thin and small enough (without being ridiculous). Fits nicely in a standard leather portfolio and light enough to forget in a backpack. It's a true ultra-portable with size and weight similar to an X200, slightly smaller with the 3-cell battery (a recommended extra). Just the right amount of ports, in generally the right places. The design looks very minimalist with only necessities: left side with 2 USB, one audio, one LAN - the right side has just one USB and one mem card slot. VGA and power in the back. Simple compared to my X60s and its many seams and ports and latches, etc.
    Build Quality:
    Great. No roll cage - and who cares. I'm not rolling my laptop, and my drive is SSD. Seriously, I would guess that in this size, ABS plastic is just as durable as Magnesium alloy. I have cracked pieces of metal broken off my X60s from slight bumps where the metal was just too brittle and cracked off. ABS does not do that. Flex in the laptop is minimal, fit and finish is very good - note the missing hood latch complaint below.
    Screen: 
    At 11.6 inches, it is just big enough for me to work comfortably due to the higher resolution screen, which I have not seen on any laptop or netbook of this size. It is quite bright, with lots of adjustment from nearly off through full brightness (15 steps) - and in my experience nobody has made an LCD yet that looks good in direct sunlight - so stop putting that bit in reviews, please!
    Keyboard:
    Lots of talk about ThinkPadders resisting the change, but honestly, it is better than my X60s old-school ThinkPad keyboard. Solid, great feel.
    UltraNav (trackpoint and trackpad):
    Coming from an X60s, I could live without the trackpad (and have disabled it on my X100e) but it is very nice to the touch and useful especially if sharing with your less-trackpoint-friendly friends. The Trackpoint is just as it is on all ThinkPads - exceptionally comfortable to operate, adjustable to your sensitivity, and with soft but sure left/right/scroll keys perfectly positioned under your thumb. It is always funny to me to see some people operate a little ultra-portable with two hands controlling the trackpoint - sorry, but that's just strange to watch.
    Performance:
    Note: Heavily dependent on latest BIOS, drivers (especially video) and latest Flash (if applicable to you). Otherwise, performance depends heavily on your needs, mine are fairly normal I guess: 
    Office apps and Outlook, some light Photoshop work, Acrobat PDF creation, web browsing with Chrome, watching HD movies in a hotel room or airplane, occasional flash video on web, Skype with video, iTunes syncing with iPod …that's about all. 
    If that sounds like you, then you're probably going to be happy with X100e performance - I cannot see a lag in any of these but Photoshop CS5 (seems optimized to intel somehow). Keep in mind that some of my impression is enhanced by the SSD I added - mostly load times of each app and maybe playback reliability of video to some extent (?) on some really big files (4+GB, 1080p).
    The CONs:
    Battery:
    Okay, let's get this over with - the battery life is weaker than a 6-cell should be, and yes, it is due to the processor. But I willingly chose to trade (best guess) 25% battery life for 25% more performance when that extra performance gets me HD video, better GPU, and generally better usability on all that I do - compared to a weaker, more efficient netbook. My solution - buy another battery - Lenovo makes it pretty easy to change on the fly. I bought a 3-cell, so in total I measure that I can last about 5 hours watching movies in the air, or web browsing in the coffee shop. Much longer if I'm just working in Word or PowerPoint with screen dimmed to usable levels. The SSD helps - adding about 20 minutes on the 6-cell.
    I generally understand the complaints about the battery as the X100 is ultra-portable, but it's not an X200 or X300 ULV ultra-portable. You sacrifice battery life and other things for a significantly lower price. Again, buy a spare and get over it. For the record, the 6-cell lasts an hour longer than my old X60s with a new 4-cell (standard shipping battery) doing the same tasks.
    No fingerprint reader or security chip:
    Comparing to my X60s which has both, but just miss the quick and cool logins with my finger. I installed a face-recognition tool - cool, but buggy.
    No Lid latch:
    The lid holds position nicely, but without latch, it will open slightly when you carry with like a book, hinge down. It does not snap tightly shut. ThinkPads have long come with finger grips for the lid and (again comparing to my X60s) I miss these especially on a laptop with no latch, and no "grabbing point" on the lid. There is a very small raised area on the right front of the lid, but it is more likely that you grab the center - where the trackpad buttons are - don't force those open! I have gotten used to opening from the left and right corners of the lid instead.
    No Thinklight:
    Would be nice, but honestly I have never used this for working on my X60s, only for "finding that sleep Fn key" or something similar. The Thinklight key was always easy to find as it is in the top right corner.
    No HDMI, or other digital display port:
    Although not needed for me, it would be nice - on a laptop that has HD capability - and a laptop with no docking station to speak of. Most all screens are digital these days - seems logical to ditch VGA.
    Power vs. LAN port placement:
    Okay, time for the picky small things - I would prefer these two on the same area, so cables aren't coming from both sides, when you need to go fully wired. If the cables are coming from anywhere other than behind the laptop, you will possibly trip over one or the other.
    PCIe card lockout:
    Lenovo is one of only a few vendors left that restrict the cards you can add to their own OEM branding. Why do they give you access to cards that cannot be replaced yourself! I would love to change the WiFi card to an intel card that I know will work (and supports 5GHz 802.11n) but cannot. I would love to put my own WWAN card inside in the future, but can't. So it's really just RAM and HDD. Thanks for teasing me! I know it simplifies technical support, but that's just mean.
    No "Soft-Touch" paint:
    I like it on my X60s and would prefer it here - but consider it the smallest of my complaints - really nice looking in smooth finish matte black. All other X-series have had it.
    Concluding remarks:
    In my view, the ThinkPad X100e is targeting two types of buyers from opposite ends of the portable spectrum:
    1. Netbook buyers looking for better specs, more performance.
    For these buyers, the X100e has better build quality, better screen, better keyboard and pointing device, and about 25% more real-world performance with about 25% less battery life - my bold estimate. An intelligent buyer would ask "how much should I pay for these extra features?" In this case, I think it is priced spot-on compared to a netbook.
    2. Laptop buyers wanting more portability, while running office tasks, web browsing, and email (which is most consumers I have to guess).
    For this group, I suppose the main concern is to minimize sacrifices going from an average 14-15-inch laptop to a (formerly too expensive) ultra-portable. If running Office/Outlook, web browsing, Skype, playing HD video and music is all you do, then X100e shrinks those capabilities into a smaller more portable package that still has full-sized screen resolution, keyboard, trackpad and trackpoint.
    Simply put, the X100e is not as big and as powerful as a big laptop, but that's not the point in an 11.6-inch laptop - you expect compromise when going smaller. Conversely, the X100e is not as small, cheap and efficient as most netbooks, but you gain power and features not available on netbooks.
    For me, the X100e was the first chance to get a brand-new ultra-portable with "good-enough" performance and ThinkPad quality at a low price - next step being an X201 starting at 1100 USD. On another note, I have a company-owned X60s that will be replaced by another X201 (or like) in the next 6 months - I would also guess that some X100 users are like me - buying their first private-owned Thinkpad, due to their experience with the brand, and the good price/performance/features mix of the X100e.
    Overall very, very happy with my buy. I have not yet formed a bond as with my X60s, but that does not happen in just 1 week.
    ...just my 2 cents.

    Windows 7 Pro (x64) gets from power button to login screen in 20.1 seconds (with startup animation disabled).  From login to "desktop ready" is dependent on how many services, processes are running - but in my case about 8 seconds until cursor is idle, ready.  If I'm fast with my password, I can get in in under 30 total!  Kidding - I rarely reboot now that apps are all in place.
    Photoshop CS5 (x64) loads in 5.2 seconds.  Nothing is cached as Windows 7 senses an SSD and turns off caching.  Indexing is also off as it is virtually instant as you type in search.  It's quite nice.
    ...loving the SSD.  Friends have claimed it's overkill in X100e - probably right - but could not in good faith buy some RAM-brand drive or even a smaller drive - want to keep everything on this drive.  Wanted a silent, safe, quick, large enough drive - and SSD is a scary world of confusing benchmarks for now.  I played it safe (worth the 20% higher cost to me) and chose the intel.
    Last thing to configure before I am settled in... I'm in the process of tuning my fan speed to suit the different Power Manager settings I've made - cutting noise and heat, and getting a little more battery.

  • I've never seen flex for sell.. how do I obtain a copy of it and whats the difference between it and flash?

    Hey;
    I've heard great stuff about flex but I've never seen it for sale. I've read that it is better for real time programs than flash. I don't know if thats true or not. What does flex offer that flash doesn't and how is the flex language better than the flash language? Or am I totally confused and is flex like an addon to flash??? any guidance would be really appreciated. I'm working on something Object oriented that needs to be in real time so I'm looking for the best program that offers that.

    I'm pretty new at all thsi stuff too, and all these terms killed me for my first few weeks in this arena, but I've got my feet under me now.
    Flex is an opensource SDK provided by Adobe (previously Macromedia). It used to be something they sold, but they opensourced it, Hoorah!!
    Flash is the set of APIs that start with flash.*, and you can fully create flash animations with just the standard flash APIs.
    Flex comes with a ton of very useful components, features, and functionalities that are built on top of flash. You should definitely download and get familiar with flex.
    The flex api's start with mx.*
    Flex also provides the ability to compile MXML documents into flash. MXML documents make it very easy to build Flash, full with animations, customizations, etc. in an HTML-like format. Take a look at the component explorer link below and you'll see the MXML generated for the example components. You can copy and paste that MXML (simple looking stuff eh?) and get a working app that you can expand on and play with as you learn.
    Here are a few helpful links to get you moving in the right direction:
    An interactive list of GUI components available in Flex (Flex isn't limited to just GUI components, but this is a nice place to whet your appetite):
    http://examples.adobe.com/flex3/componentexplorer/explorer.html
    http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html
    A good list of Flex links:
    http://seantheflexguy.com/blog/2009/02/27/how-do-i-learn-flex/
    The documentation available from Adobe is second to none:
    http://www.adobe.com/devnet/flex/quickstart.html
    http://livedocs.adobe.com/flex/3/html/help.html?content=Part2_DevApps_1.html

  • I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build.  The same call works fine when running on the device

    I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
    I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
    The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
    I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
    I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
    By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
    Anyone have an idea on other things to try to debug/resolve this?
    Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
    Thanks!

    After a week's worth of debugging, I found the issue.
    The Java type returned from the call was defined as ArrayList.  Changing it to List resolved the problem.
    I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid.  And, why it works in Debug mode and not in Release build is even stranger.  Maybe someone can shed some light on the logic here to me.

Maybe you are looking for