|
If you use the same ModelLocator, yes. I'd
assume, however, each would have their own ModelLocator. Additionally
there is no reason you couldn't share the same one. Still, depends on the
project, and I usually only have borrewed views between proejcts, not command
& model stuff.
----- Original Message -----
Sent: Thursday, July 27, 2006 9:53 AM
Subject: Re: [flexcoders] Backend/Frontend Application Development
(Cairngorm)
righto on that. Say I have a command GetUserCommand() that
returns a userVO for the current user in session. This is returned to the
apps modellocator, has stuff like name, etc, in it.
so we have
com.company.project.admin.model.AModLoc
com.company.project.client.model.CModLoc
How
does GetUserCommand() stick the userVO result into the proper model?
Typically the model is hardcoded in the Command, eh? What I've done so far
is used a generic model so to speak in com.company.project.model.GModLoc
say. Then the client app and admin app can access it as well as their
respective model.
DK
On 7/27/06, JesterXL
<[EMAIL PROTECTED]>
wrote:
// Assuming your in your Client Application for
example
import
com.company.project.admin.events.SomeEvent;
import
com.company.project.client.events.ClientEvent;
var e:SomeEvent = new
SomeEvent(SomeEvent.EVENT_NAME, false, true);
CairngormEventDispatcher.getInstance().dispatchEvent(e);
You could do the reverse in the admin. As a
GUI guy, I probably would care more about sharing commonly used View's and
utility classes vs. events and commands that were probably created for their
specific projects, but it could be done.
----- Original Message -----
Sent: Thursday, July 27, 2006 9:25 AM
Subject: Re: [flexcoders] Backend/Frontend Application Development
(Cairngorm)
curious how to share resources with this, say using
Cairngorm. How to share a command that returns data to a
modellocator? How to return th edata to the current model locator for a
sub app?
DK
On 7/27/06, JesterXL <[EMAIL PROTECTED]> wrote:
Put
'em in seperate projects, or
sub-projects. Like:
com.company.project.admin.*
com.company.project.client.
Or:
com.company.projectadmin.*
com.company.projectclient.*
You
should take advantage of the fact you may be using similiar code; both
of the above in the same Flex project allows you to easily do
that.
----- Original Message -----
From: "Stefan Schmalhaus"
<[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, July 27,
2006 4:38 AM
Subject: [flexcoders] Backend/Frontend Application
Development (Cairngorm)
I'm going to develop a Flex
(Cairngorm-based) intranet application for
training resources. There
will be a backend part for user and content
administration, and there
will be a frontend for the end user.
Both parts, backend and fronted,
will presumably share a lot of the
underlying data structure, value
objects, views, etc. They will
definitely use the same AMFPHP services.
What's the best way to tackle
this? Should I treat them as two different
Flex projects? Or can I
develop them within one Flex project but with two
different MXML
application files?
Your ideas and thoughts are
very much appreciated.
Stefan
--
Flexcoders
Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups
Links
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo!
Groups Links
<*> To visit your group on the web, go
to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email
to:
[EMAIL PROTECTED]
<*>
Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
--
Douglas Knudsen
http://www.cubicleman.com
this is my signature, like it?
--
Douglas Knudsen
http://www.cubicleman.com
this is my
signature, like it?
__._,_.___
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
![]()
SPONSORED LINKS
YAHOO! GROUPS LINKS
__,_._,___
|
