http://www.microsoft.com/downloads/details.aspx?familyid=048DC840-14E1-467D-8DCA-19D2A8FD7485displaylang=en
http://www.microsoft.com/downloads/details.aspx?familyid=e25cb1e5-209c-4a58-b283-23e84b616477displaylang=en
its free, or you allergic to microsoft? ;-)
--- In flexcoders@yahoogroups.com,
On Wednesday 24 Oct 2007, [EMAIL PROTECTED] wrote:
http://www.microsoft.com/downloads/details.aspx?familyid=048DC840-14E1-467
D-8DCA-19D2A8FD7485displaylang=en
its free
There doesn't seem to be a specific Linux download option.
I tried this weird .exe they gave me, but it didn't work :-)
, or
Wow. You're developing flex apps on Linux? cool.
--- In flexcoders@yahoogroups.com, Tom Chiverton [EMAIL PROTECTED]
wrote:
On Wednesday 24 Oct 2007, [EMAIL PROTECTED] wrote:
http://www.microsoft.com/downloads/details.aspx?familyid=048DC840-14E1-467
D-8DCA-19D2A8FD7485displaylang=en
its
Why not just have a DAODelegate with methods like getUserDAO(),
getProductDAO(), etc?
Ben
--- In flexcoders@yahoogroups.com, Bjorn Schultheiss
[EMAIL PROTECTED] wrote:
Hey Doug,
My backend is mainly DAO's and I've got one delegate pers DAO in my
company lib, that gets used across
On Tuesday 23 Oct 2007, [EMAIL PROTECTED] wrote:
The Idea is that even if you are calling the same webservice you are
to create a new delegate.
Eww, no - I don't know anyone who does that !
--
Tom Chiverton. Are you a great Flex programmer, who knows Cairngorm, and has
done some ColdFusion
I'm with Ben on this one.
If you read through the rest of Jesse Warden's posts, he parses data
in the delegate instead of the command, which means that his delegates
most likely have a lot more code than my 'simple' delegates.
I generally have one delegate per service.
ben.clinkinbeard
Hi
One delegate per service makes sense, whoever would write a delegate
exactly the same as another class as opposed to reuse would have to be
insane in my book.
I've pondered the parsing data in the delegate and in my current
project I chose to do that - the idea to keep everything that's to do
I've not seen anything saying 'Cairngorm is 1 to 1 e-c-d' steadfastly. Why
can't a single event be registered with say 2 commands? Event
initialiseApplicationEvent could be registered with fetchUSStatesCommand(),
fetchFoodChoicesCommand(), and fetchOpenDinnerDatesCommand(). Asynchronous
vs
Thats what ive got.
Ideally what i'm saying is i would have a single delegate for each
command that makes a dao call.
Bjorn
On 23/10/2007, at 10:50 PM, ben.clinkinbeard wrote:
Why not just have a DAODelegate with methods like getUserDAO(),
getProductDAO(), etc?
Ben
--- In
the 1 to 1 event-command-delegate methodology
I've heard that mentioned indirectly a couple of times before but
don't remember ever reading it as a suggested methodology. Maybe I
just missed that instruction but I don't follow that practice. I have
one delegate per Web Service, so several
Hey Ben,
The Idea is that even if you are calling the same webservice you are
to create a new delegate.
The sequence is Event - Command - Delegate.
Not saying that i follow it, but I'm sure in it's strictest
implementation its 1 to 1.
Check this
Yea, I just don't buy into that. I am all for short files and clear
separation of responsibilities, but I don't see what
single-method-delegates buys you. My delegates are pretty dumb, they
just contain methods that take params and pass em along to web
methods. I don't access the model or anything
me2 :) I usually use one delegate per application or major division of the
app, eg Modules. This delegate can access how ever many services it needs
to to do the job. Further, it can rely on utility classes to massage
incoming data if need be too. Now if I have to switch from WebService to
Hey Doug,
My backend is mainly DAO's and I've got one delegate pers DAO in my
company lib, that gets used across multiple projects.
But I'm pretty sure thats not Cairngorm.
Cairngorm is 1 to 1 e-c-d.
regards,
Bjorn
On 23/10/2007, at 2:33 PM, Douglas Knudsen wrote:
me2 :) I usually
14 matches
Mail list logo
