Thanks. Its great to see some other code. I have learned a few things just
checking it out.
But one question. In looking at your code, I noticed
that the remoteObject stuff is at the application level. Does this mean that you
cant put remoteObjects in MXML components? I was hoping to modularize that.
Thanks
Hank
On 6/23/06, Shannon
Hicks <[EMAIL PROTECTED]>
wrote:
Check out
my little flex project...
Nothing special, but it does
what you're asking. Right-click to view the source.
Shan
Ok, so I just created a component. It needs to access remoteObjects. I
defined the component as a canvas. But I guess canvas's cant have sub items
that are remoteObjects, so a compiler error is thrown. But the whole purpose
of this component is to display remoteObject data in a scrolling list. It
makes sense to me that the remoteObject be "close" to the list. Although
perhaps not. Perhaps ultimately the RemoteObjects should be in one place and
the display in another to keep things highly factored (I know cairngorm
again). So I would like to know how to place remoteObjects in a component, and
how to place then in another component that might serve data to this
component.
Thanks
Hank
PS At some point I am sure I will use
cairngorm, but I need to understand how the real system works before I start
using something that obscures or "simplifes" how things work. Otherwise I dont
think I will be a good MXML coder.
--
No virus found in this incoming message.
Checked by
AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.2/372 - Release
Date: 6/21/2006
--
No virus found in this outgoing message.
Checked by
AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.2/372 - Release
Date: 6/21/2006
