[Typo3-dev] Flash Front-End for Typo3

[Richard Bausek]

>> I had a look, but the problem I have is that some sort of TS data will have to be send with this sistem not just content because after first Load the Flash Api will be responsable with all layout and rearange/create_new/remove the content.
As the extension is more of a proof of concept, it won't be difficult to 
    include other TS data (for layouts,...)in the XML using custom 
functions.

Or do I missunderstand something? ;-)

>> FLASH_PANEL is a component that can uoutput a MOVIECLIP. The reason I'd use a component is that of allign, scroll, resize, hide / show gadgets so a FLASH_PANEL will provide basic functionalities to handle those and it is a nice way to group objects that a part of the same logical zone HEADER for Ex. Basicly it is a container ... inspired by Java.
>> And because FLASH_PANEL extends MOVIECLIP all the propreiteies of a MOVIECLIP will also be available for FLASH_PAEL.

I agree on your idea of the FLASH_PANEL. As I get it, it is some kind of 
  generic UI component. But a simple MOVIECLIP type should also be 
available as an cObject, which FLASH_PANEL extends with UI functionality.

The more options the better :-)

>>>MOVIECLIP could be a page type so you could build your Flash structure
>>>in the page tree. 
>> 
>> Could this be useful ? I see how it can be useful in creating a sort of SlideShows, but the same thing can be done with normal pages... Do you have an example it might help me understand the usefulnes ;-)
>> 

When MOVIECLIP is a page type, you could enter all the movieclip 
specific properties (width, height, position, rotation,...) inside the 
pageheader (extending the "pages" table a lot). I would compare it to 
the "Movie Explorer" in Flash. There you can also edit a movie in a tree 
structure.

But this would also require that there is a FLASH_FRAME page type. In 
the pageheader of the FLASH_FRAME you could enter the Actionscript for 
that frame in TSconfig (or maybe "ASconfig" :-)), set the frame label 
with the page title,..

So when MOVIECLIP and FLASH_FRAME is a page type, you can add 
"FLASH_FRAME" pages as subpages to MOVIECLIP pages.
On the FLASH_FRAME page you can add content elements (FLASH_PANELS, 
images, videos or other stuff). If there is only a single frame in a 
movieclip, you could also attach the contents directly to the MOVIECLIP 
page (assuming there is always one frame by default).

This could look like this in the tree view:

Root Movieclip(MOVIECLIP)
  |-|News (FLASH_FRAME) #add content to this page
  |
  +-|Products (FLASH_FRAME) #basic content for products section
      |-Specials (MOVIECLIP)# sub movie of products
         |-winter (FLASH_FRAME)#content for winter goes here
         |-summer (FLASH_FRAME)#content for summer goes here

Do you get the idea?
Using the tree view it would be easy to build quite complex movies and 
have your content organised in the regular Typo3 way.



richard


Radu Cocieru wrote:
> Hi Richard				
> 
> 
>>If you want to do the data exchange with XML look at the extension "XML
>>Content Rendering"
>>(http://typo3.org/extensions/repository/search/xml_contentrendering/).
>>Its still a proof of concept, but I think it is the way to go.
> 
> 
> I had a look, but the problem I have is that some sort of TS data will have to be send with this sistem not just content because after first Load the Flash Api will be responsable with all layout and rearange/create_new/remove the content.
> 
> 
>>Using AMFPHP also would be nice, since it is a more OOP approach and the
>>project is quite active again.
> 
> 
> Agree but an XML suport is also required ... just in case 
> 
> 
>>Will that API just take care of the data exchange between Typo3 and
>>Flash (get content, handle users, access schemes) or will it also
>>contain code to display it in Flash? I'd prefer a clean flexible API
>>which only gets the data into Flash and vice versa.
> 
> 
> Yes, Flash API will take kare only of server communication  "(get content, handle users, access schemes)" and instantiate Flash Components used to display content, provide an event passing system. The API will not handle how to display information.
> 
> 
>>Why would you create a "FLASH_PANEL" type? We could also just manage
>>movieclips with all their properties and frames in Typo3.
> 
> 
> FLASH_PANEL is a component that can uoutput a MOVIECLIP. The reason I'd use a component is that of allign, scroll, resize, hide / show gadgets so a FLASH_PANEL will provide basic functionalities to handle those and it is a nice way to group objects that a part of the same logical zone HEADER for Ex. Basicly it is a container ... inspired by Java.
> And because FLASH_PANEL extends MOVIECLIP all the propreiteies of a MOVIECLIP will also be available for FLASH_PAEL.
> 
> 
>>#here we could also apply transition information to the movieclip
>>MainPanel.startTransition = FLASH_TRANSITION
>>MainPanel.startTransition._alpha.begin = 0
>>MainPanel.startTransition._alpha.end = 80
>>MainPanel.startTransition._alpha.animType = easeInOut
>>MainPanel.startTransition._alpha.duration = 500 #ms
> 
> 
> This is a nice Idea :)
> 
> 
>>MainPanel.frames = FLASH_TIMELINE #COA of FLASH_FRAME records
>>MainPanel.frames{
>>1.label = framelabel
>>1.framescript = AS Code to be included
>>1.content = COA
>>1.content.1 = TEXT
>>1.content.1.data.field = title
>>...
>>}
> 
> 
> This one is at STEP 2 of my project as I think it is important to capture people's attention first and then reveal/develop some hidden gadgets... after they are used with the main functions.
>  
> 
>>MOVIECLIP could be a page type so you could build your Flash structure
>>in the page tree.
> 
> 
> Could this be useful ? I see how it can be useful in creating a sort of SlideShows, but the same thing can be done with normal pages... Do you have an example it might help me understand the usefulnes ;-)
> 
> 
>>Did you already think of using Ming(http://ming.sourceforge.net/) for
>>the dynamic generation of .swf files. A possibility would be to have an
>>Action-Script Editor in Typo3 and then compile the finished AS into a
>>.swf. That way you could manage your AS classes on the server. Also you
>>could generate Content .swfs on the fly.
> 
> 
> Yes, Ming is for the STEP 2 as this will call for a very good planing on how do create .SFW's on the fly.
> 
> 
>>What are your ideas regarding text transformation to Flash, as Flash
>>only understands HTML 1 and a little CSS. Will you create a Flash RTE
>>configuration or will you write funtions to strip the code.
> 
> 
> I think a HTML source code conversion to smth FLASH understands better is more suitable, as who knows maybe flashPlayer 8 will suport full HTML and CSS and I'll comment out the transform function :)
> 
> Thank you for your ideas. I will keep the list updated.
> 
> Radu
>