Re: [flexcoders] Im new, and this is an old question

2009-01-20 Thread Haykel BEN JEMIA
RIA doesn't mean no pages. There are situations where you have simply
different pages. How you implement them, as different apps, modules or as a
viewstack depends. But among other things, a RIA reduces page loading in
many cases. In your example, the login can be a page and the calendar
another page. But in the calendar page, if the user chooses to see the
details of an item, edit an item, add a new one or add a comment for
example, then you can do all this in one page. So I would split the app by
functionality and implement the different parts independently, then you
could put them on different pages or load them as modules.


Haykel Ben Jemia

Allmas
Web  RIA Development
http://www.allmas-tn.com




On Sun, Jan 18, 2009 at 7:54 PM, nycynik m...@theinfluence.net wrote:

   I am new to flex and RIA in general. I have been working with .net
 and java for a while now, and I am just starting to try to create a
 new interface for some projects of mine, and thought flex might be the
 answer, but I am having trouble wrapping my head around the idea that
 its less like a web page, and more like a desktop application, to stop
 thinking about page reloads, and start thinking about ViewStacks.

 So my original thought was to begin with multiple swf applications,
 and convert parts of the site over one part at a time (for instance,
 user registration, and then move on to the shared calendar, or another
 part of the site).

 But after doing some reading, it seems that its better to build the
 whole site as one application. Well I hope i can get some help, here
 is my question..

 --
 I did a lot of searching, and found a lot of posts that seem to
 disagree. The basic question is:

 I am building a big application for a website, using flex/swf as a
 front end, and .net as a back end. How do I control the project so
 that its not one monster swf file?

 Answers seem to range between using a single ViewStack, to using
 modules that you load in. Almost everyone wrote, to not build
 multiple swf/flex projects and try to communicate between them using
 .net or directly between swf files.

 --

 I hope that is clear enough, so i should begin by learning about
 loading and unloading modules? Is that right?

 Thanks,
 Mike

  



[flexcoders] Im new, and this is an old question

2009-01-19 Thread nycynik
I am new to flex and RIA in general.  I have been working with .net
and java for a while now, and I am just starting to try to create a
new interface for some projects of mine, and thought flex might be the
answer, but I am having trouble wrapping my head around the idea that
its less like a web page, and more like a desktop application, to stop
thinking about page reloads, and start thinking about ViewStacks.

So my original thought was to begin with multiple swf applications,
and convert parts of the site over one part at a time (for instance,
user registration, and then move on to the shared calendar, or another
part of the site).  

But after doing some reading, it seems that its better to build the
whole site as one application.  Well I hope i can get some help, here
is my question..

--
I did a lot of searching, and found a lot of posts that seem to
disagree.  The basic question is:

I am building a big application for a website, using flex/swf as a
front end, and .net as a back end.  How do I control the project so
that its not one monster swf file?

Answers seem to range between using a single ViewStack, to using
modules that you load in.  Almost everyone wrote, to not build
multiple swf/flex projects and try to communicate between them using
.net or directly between swf files.

--

I hope that is clear enough, so i should begin by learning about
loading and unloading modules?  Is that right?

Thanks,
Mike