the mapguide templates have been recently moved into <br><a href="http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Oem/fusionMG/templates/mapguide">http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Oem/fusionMG/templates/mapguide</a><br>
<br>I'm all for making this as painless as possible, not having the preview template breaks studio,<br>plus they are great examples of fusion, not having them in the build is a loss<br><br>z<br><br><br><br><div class="gmail_quote">
On Sat, Nov 1, 2008 at 11:53 PM, Paul Spencer <span dir="ltr"><<a href="mailto:pspencer@dmsolutions.ca">pspencer@dmsolutions.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I must be slow on the uptake, but reading Jason's 'how to install' post made me realize that you are absolutely right. For mapguide users at least we should be bundling Fusion packages with all the mapguide templates as separate packages - especially the ones that don't get released with specific versions of mapguide.<br>
<br>
Not sure about storing them in the SVN vault or not, that would be something that perhaps the PSC should make a call on.<br>
<br>
I think you should raise this on the dev list and I'll definitely support with +1<br><font color="#888888">
<br>
Paul</font><div><div></div><div class="Wj3C7c"><br>
<br>
On 22-Oct-08, at 8:32 AM, Zac Spitzer wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
the mg 2.1 release is why i was putting my hand up to test 1.1 :)<br>
<br>
what I was suggesting with subversion is an easy way for someone like<br>
myself who<br>
is happy to update often to just replace the current fusion tree in<br>
mapguide with a version<br>
directly checked out of the fusion ' builds' tree. rather than having<br>
to build it from the svn src.<br>
<br>
I am not really much of a fan of the way fusion and other things are<br>
snapshoted version wise tied to<br>
the long points between mapguide releases.<br>
<br>
having the compiled builds in the subversion would allow me to do<br>
something like this to a mg install<br>
<br>
cd /mgos2.0/webserverextensions/wwww<br>
mv fusion fusion_release<br>
svn co <a href="http://svn.osgeo.org/fusion/builds/development" target="_blank">http://svn.osgeo.org/fusion/builds/development</a> fusion<br>
<br>
that way I just have to svn update to grab the latest build to test<br>
<br>
z<br>
<br>
<br>
<br>
On Wed, Oct 22, 2008 at 10:40 PM, Paul Spencer <<a href="mailto:pspencer@dmsolutions.ca" target="_blank">pspencer@dmsolutions.ca</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Zac,<br>
<br>
I think Mike has been steadily working on bugs for 1.1 as well as finishing<br>
up features for 2.0. I'd personally like to see 1.1 finalized soon, so if<br>
you want to do some testing that would help a lot. One of the things we<br>
added to 1.1 was a compatibility mode for the existing templates so that it<br>
can be a drop-in replacement for the existing fusion code, which should make<br>
upgrading easier!<br>
<br>
I believe mgos 2.1 is tracking Fusion trunk which will be branched for a 2.0<br>
version shortly too, so my fears of 1.1 slipping between releases seem to<br>
have materialized, but no matter - both contain important code and 1.1 might<br>
get rolled into another 2.0 minor update if I can convince Tom its a good<br>
idea :)<br>
<br>
>From this point forward, I believe that mgos is using svn externals to<br>
include fusion, so checking in built versions would only apply up to the<br>
current point in time I think (unless I am missing the point somehow)<br>
<br>
Paul<br>
<br>
<br>
On 22-Oct-08, at 4:05 AM, Zac Spitzer wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How is 1.1 going?, it been a while since RC1 I'm happy to do some more<br>
testing.<br>
<br>
When 1.1 is released, I'm thinking about a few ideas which would make<br>
adoption easier.<br>
<br>
Once is to create a windows installer which is MGOS and MGE aware so<br>
people can<br>
easily update (replace) older fusion installs.<br>
<br>
Secondly, what do people think about checking in built releases of<br>
fusion into subversion?<br>
<br>
builds\stable<br>
builds\development<br>
builds\1.06<br>
builds\1.1RC1<br>
<br>
That way users can a simple svn update to update fusion.<br>
<br>
<br>
<br>
<br>
--<br>
Zac Spitzer -<br>
<a href="http://zacster.blogspot.com" target="_blank">http://zacster.blogspot.com</a> (My Blog)<br>
+61 405 847 168<br>
_______________________________________________<br>
fusion-dev mailing list<br>
<a href="mailto:fusion-dev@lists.osgeo.org" target="_blank">fusion-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fusion-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/fusion-dev</a><br>
</blockquote>
<br>
<br>
__________________________________________<br>
<br>
Paul Spencer<br>
Chief Technology Officer<br>
DM Solutions Group Inc<br>
<a href="http://research.dmsolutions.ca/" target="_blank">http://research.dmsolutions.ca/</a><br>
<br>
<br>
</blockquote>
<br>
<br>
<br>
-- <br>
Zac Spitzer -<br>
<a href="http://zacster.blogspot.com" target="_blank">http://zacster.blogspot.com</a> (My Blog)<br>
+61 405 847 168<br>
</blockquote>
<br>
<br>
__________________________________________<br>
<br>
Paul Spencer<br>
Chief Technology Officer<br>
DM Solutions Group Inc<br>
<a href="http://research.dmsolutions.ca/" target="_blank">http://research.dmsolutions.ca/</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Zac Spitzer -<br><a href="http://zacster.blogspot.com">http://zacster.blogspot.com</a> (My Blog)<br>+61 405 847 168<br>