[fusion-users] Implementing Fusios

[Paul Spencer]

Hi Warren,

first you need to be subscribed to the fusion users list to be able to  
post, please go to http://lists.osgeo.org/mailman/listinfo/fusion- 
users and subscribe if you plan to post other questions (I've  
administratively accepted your question this time).

I'm not sure I follow your question, but I'll blindly give some  
answers anyway in the hope that I do answer your question.  If I  
don't, please feel free to say so (after subscribing of course) :)

Fusion needs two pieces to get started, a 'template' and an  
ApplicationDefinition.  The template is just an HTML file, and the  
ApplicationDefinition is a MapGuide resource document that may exist  
in the MapGuide repository (or it may exist outside the repository).

So you can create a single 'template' and start fusion by pointing to  
one of many ApplicationDefinitions thus controlling the functionality  
of the application while preserving the same basic layout and look &  
feel between them.  Alternately, you can have multiple 'template's all  
pointing to the same ApplicationDefinition, thus sharing functionality  
between different layouts and look & feels.

Cheers

Paul

On 1-May-08, at 3:18 PM, Warren M wrote:

>
> Hello,
>
> I’m digging into Fusion, and I’m curious how I might tackle a specific
> scenario.
>
> I want to build a Fusion based application that is essentailly a  
> wrapper for
> multiple MG Layouts.
>
> Here’s an example of what I’m looking to do with an existing  
> application
> structure/hierarchy:
> Root
>                App1
>                                Layouts
>                                Maps
>                                Etc..
>                App2
>                                Layouts
>                                Maps
>                                Etc..
>                Etc..
>
> Using the regular Layouts you could pass a querystring (App1) and  
> drill down
> to a specific Layout to load, ie
> App1\Layouts\App1.LayoutDefintion
>
> Now with the Fusion Layouts these details are stored in the
> ApplicationDefinition.xml, and I would like to avoid having to have  
> separate
> fusion apps for each child or writing to this xml file each time.   
> So I
> would like some guidance from them on the best way to structure  
> this.  I
> hope this makes sense.
>
> <MapGroup id="sheboygan" xsi:type="MapType">
>      <Map xsi:type="MapGuideLayerType">
>        <Type>MapGuide</Type>
>        <SingleTile>true</SingleTile>
>        <Extension>
>
> <ResourceId>Library://Samples/Sheboygan/Maps/ 
> Sheboygan.MapDefinition</ResourceId>
>        </Extension>
>      </Map>
>    </MapGroup>
>
> Thanks so much
> Warren Medernach
>
> -- 
> View this message in context: http://www.nabble.com/Implementing-Fusios-tp16995020p16995020.html
> Sent from the Fusion Users mailing list archive at Nabble.com.
>
> _______________________________________________
> fusion-users mailing list
> fusion-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fusion-users


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://www.dmsolutions.ca/