flex
Submitted by jrowny on Wed, 05/26/2010 - 11:08
I previously posted how I solved the problem of RadioButtonGroups inside repeaters, you can see that post here. Unfortunately, today, I discovered that radio button groups are a scam. You don't need them at all!? Why, you ask? If you just set the "groupName" property, they are automatically created.
<mx:Repeater id="someRepeater">
<mx:HBox>
<mx:RadioButton id="Yes" groupName="{someRepeater.currentIndex}"/>
Submitted by jrowny on Tue, 04/27/2010 - 11:08
If you've got an app and are hoping to test it using FlexMonkey, be careful that you don't have any references to Application.application. This would normally return you a nice reference to your main app MXML file, but since MonkeyAgent is doing the loading, it will return you a reference to MonkeyAgent instead. Rather than change your code, I'd recommend using MonkeyLink. You need to include a bunch of stuff, but at least it works.
Submitted by jrowny on Fri, 04/02/2010 - 11:08
For years, many Flex developers have known the secret to fixing many a UI problem was using either callLater() or validateNow() methods. Much to my surprise, some of these developers do not understand WHY these fix problems, what the difference is, and which method to use.
The Problem
Submitted by jrowny on Tue, 03/23/2010 - 11:08
If there's one thing I've learned from writing a lot of jQuery, it's that you can write a whole lot of code without pressing the enter key. Between all the method chaining and inline functions, you can do quite a bit with a small amount of code.
Submitted by jrowny on Fri, 03/19/2010 - 11:08
Once again I let my jQuery habits get into my ActionScript code.
this.addEventListener(MouseEvent.MOUSE_OVER,
function():void{
cursorId = CursorManager.setCursor(Cursors.MOVE,CursorManagerPriority.HIGH,-16,-16); });
this.addEventListener(MouseEvent.MOUSE_OUT,
function():void{ CursorManager.removeCursor(cursorId); });
What do you think? Should I leave it?
Submitted by jrowny on Wed, 10/22/2008 - 07:00
I've heard of quite a few people lately being turned off of PureMVC because it's "Needlessly complicated." I truly respect Cliff Hall and I love his creation, PureMVC, but the documentation for PureMVC is what's needlessly complicated, not PureMVC. As a community we need to step up and help Cliff advertise this wonderful framework better. So let's get one thing straight,
PureMVC is not complicated. It's actually incredibly simple..
Submitted by jrowny on Wed, 10/22/2008 - 07:00
Getting a roll over to work properly in Flex is no fun.
The Scenario
Mouse rolls over a tab, then the tab "slides out" revealing a tool bar or something.
The Tutorial
There are a few things you need to do to get this working right, let's walk through the steps.
- There's a few ways to do this, but I'm shooting for easiest. Let's say you have a top-oriented menu (top-right) that needs to slide down from 25 pixels to 80 pixels tall. Start by making our canvas.
Submitted by jrowny on Wed, 10/22/2008 - 07:00
Well, as you may have noticed, I finally went through all the posts and used a standard way to do code highlighting. It's called Syntax Highlight and you can get it here: http://alexgorbatchev.com/wiki/SyntaxHighlighter
Fortunately, there's a Drupal Plugin so I didn't actually have to do anything except edit all my old posts to use this format:
<pre class="brush:as3">
This is my code
</pre>
The one thing I wish it could do is combine brushes, so I can have MXML and AS3 in one block.
Submitted by jrowny on Wed, 10/22/2008 - 07:00
So me and the other people in my team got in a small argument over the proper use of PureMVC's mediators. We've read in various blogs that it is not a good practice to call a Proxy directly from a mediator. If you're going to call a proxy, it needs to be done from a command.
In this particular case, we're asking for the proxy to refresh some data. That's it... one call.
someProxy.refresh(). The refresh will send it's notification and our mediator will update.
Submitted by jrowny on Wed, 10/22/2008 - 07:00
PureMVC has two ways to dispatch a Notification. A "note" for short, is like a Flex Event but that's another story. So what's the difference? The main difference is that sendNotifiaction builds the note and sends it at the same time. It's arguments are the same as Notification.
