Re: [Flashcoders] Site structure with classes

[Muzak]

Not having used Gugga yet and by having a quick look at the docs it seems nice, 
but..
it seems quite heavy.

ARP is lightweight and in fact you can use ARP without really using ARP ;-)
What I mean is, you can apply the layout/workflow logic of ARP (as I explained 
earlier), without using the ARP framework/classes at 
all.

regards,
Muzak

- Original Message - 
From: "Hans Wichman" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, May 29, 2007 7:05 PM
Subject: Re: [Flashcoders] Site structure with classes


> have a look at guggaf too, might be applicable here as well i think, it goes
> further then an application framework, it present a website-application
> framework.
>
> greetz
> JC


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Re: [Flashcoders] Site structure with classes

[Muzak]

http://www.gugga.com/flashblog/
http://osflash.org/guggaff

;-)

- Original Message - 
From: "Hans Wichman" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, May 29, 2007 7:05 PM
Subject: Re: [Flashcoders] Site structure with classes


> have a look at guggaf too, might be applicable here as well i think, it goes
> further then an application framework, it present a website-application
> framework.
>
> greetz
> JC


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Re: [Flashcoders] Site structure with classes

[Pedro Taranto]

you also can use Pixlib framework
www.osflash.org/projects/pixlib

--Pedro Taranto


Hans Wichman escreveu:
have a look at guggaf too, might be applicable here as well i think, 
it goes

further then an application framework, it present a website-application
framework.

greetz
JC



On 5/29/07, Muzak <[EMAIL PROTECTED]> wrote:


Have a look at ARP
http://osflash.org/projects/arp

With ARP you don't use the main timeline at all.

A base MovieClip/Class acts as the root (because of the lack of being 
able

to assign a class to the main stage - without hacks).
The base Class is usually called "Application" and all the content 
goes in

there.

The Application MovieClip is the only thing on stage.
Content inside the Application is made visible/invisible as needed.

This comes close to using the Form fla document type (which you can also
use with ARP by the way), but without actually using the v2
component framework.

Here's what an Application looks like in the IDE, including the Project
Panel.
http://muzakdeezign.com/arp/arp_application.jpg

There's no ActionScript in the FLA (part from some stop actions here and
there).
Everything goes in Classes, assigned to MovieClips.

This kind of approach easily 'translates' into Flex as well, using a
ViewStack container with custom MXML Components.

Oh, and classes should be named after their purpose..
   - Application, Home, Products, Contact, etc.. for Form/View type
classes.
   - ScrollBar, MenuButton, Preloader, etc.. for control type classes.

regards,
Muzak

- Original Message -
From: "misa" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, May 29, 2007 5:02 PM
Subject: [Flashcoders] Site structure with classes


> Hello group,
> I'm wondering is there something like 'the best way to structure a 
flash

site'. How should the classes be named, should we use
> frames in the root timeline and should we use frames at all (expect 
for

animations)? Any advice or help is welcome!
>
> Thanks,
> Mihajlo Nikolic


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Re: [Flashcoders] Site structure with classes

[Hans Wichman]

have a look at guggaf too, might be applicable here as well i think, it goes
further then an application framework, it present a website-application
framework.

greetz
JC



On 5/29/07, Muzak <[EMAIL PROTECTED]> wrote:


Have a look at ARP
http://osflash.org/projects/arp

With ARP you don't use the main timeline at all.

A base MovieClip/Class acts as the root (because of the lack of being able
to assign a class to the main stage - without hacks).
The base Class is usually called "Application" and all the content goes in
there.

The Application MovieClip is the only thing on stage.
Content inside the Application is made visible/invisible as needed.

This comes close to using the Form fla document type (which you can also
use with ARP by the way), but without actually using the v2
component framework.

Here's what an Application looks like in the IDE, including the Project
Panel.
http://muzakdeezign.com/arp/arp_application.jpg

There's no ActionScript in the FLA (part from some stop actions here and
there).
Everything goes in Classes, assigned to MovieClips.

This kind of approach easily 'translates' into Flex as well, using a
ViewStack container with custom MXML Components.

Oh, and classes should be named after their purpose..
   - Application, Home, Products, Contact, etc.. for Form/View type
classes.
   - ScrollBar, MenuButton, Preloader, etc.. for control type classes.

regards,
Muzak

- Original Message -
From: "misa" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, May 29, 2007 5:02 PM
Subject: [Flashcoders] Site structure with classes


> Hello group,
> I'm wondering is there something like 'the best way to structure a flash
site'. How should the classes be named, should we use
> frames in the root timeline and should we use frames at all (expect for
animations)? Any advice or help is welcome!
>
> Thanks,
> Mihajlo Nikolic


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Re: [Flashcoders] Site structure with classes

[Muzak]

Have a look at ARP
http://osflash.org/projects/arp

With ARP you don't use the main timeline at all.

A base MovieClip/Class acts as the root (because of the lack of being able to 
assign a class to the main stage - without hacks).
The base Class is usually called "Application" and all the content goes in 
there.

The Application MovieClip is the only thing on stage.
Content inside the Application is made visible/invisible as needed.

This comes close to using the Form fla document type (which you can also use 
with ARP by the way), but without actually using the v2 
component framework.

Here's what an Application looks like in the IDE, including the Project Panel.
http://muzakdeezign.com/arp/arp_application.jpg

There's no ActionScript in the FLA (part from some stop actions here and there).
Everything goes in Classes, assigned to MovieClips.

This kind of approach easily 'translates' into Flex as well, using a ViewStack 
container with custom MXML Components.

Oh, and classes should be named after their purpose..
- Application, Home, Products, Contact, etc.. for Form/View type classes.
- ScrollBar, MenuButton, Preloader, etc.. for control type classes.

regards,
Muzak

- Original Message - 
From: "misa" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, May 29, 2007 5:02 PM
Subject: [Flashcoders] Site structure with classes


> Hello group,
> I'm wondering is there something like 'the best way to structure a flash 
> site'. How should the classes be named, should we use 
> frames in the root timeline and should we use frames at all (expect for 
> animations)? Any advice or help is welcome!
>
> Thanks,
> Mihajlo Nikolic


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Re: [Flashcoders] Site structure with classes

[Mark Winterhalder]

On 5/29/07, misa <[EMAIL PROTECTED]> wrote:

Hello group,
I'm wondering is there something like 'the best way to structure a flash
site'.


Sure, but unfortunately the diagram has been used as a coaster for the
holy grail and is stained beyond readability. :)


How should the classes be named, should we use frames in the root
timeline and should we use frames at all (expect for animations)? Any
advice or help is welcome!


It really depends on what you plan to do and what you're comfortable
with. Maybe check out  or some other
framework -- maybe you'll find something that fits.
Personally, I don't particularly like the timeline and perceive it as
limiting, although I recognize that it can be useful in certain cases.
As for naming classes, 'descriptive' would be the word I'd use to
describe best practice.

Mark
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

[Flashcoders] Site structure with classes

[misa]

Hello group,
I'm wondering is there something like 'the best way to structure a flash 
site'. How should the classes be named, should we use frames in the root 
timeline and should we use frames at all (expect for animations)? Any 
advice or help is welcome!


Thanks,
Mihajlo Nikolic
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com