<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple style='word-wrap: break-word;
-khtml-nbsp-mode: space;-khtml-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi all, <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Changing the header image is not difficult to do. I did this for
WeSahana to change the logo in the top. It involved changing the image in the
theme. So you can look at the theme folder, copy one of the theme and change
the header image to sth you want. The theme can be set to your new theme by
editing the conf file in Sahana. I do not remember the details but that was the
general approach. Hope it helps.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
sahana_proj-bounces@lists.trincoll.edu
[mailto:sahana_proj-bounces@lists.trincoll.edu] <b>On Behalf Of </b>Ralph
Morelli<br>
<b>Sent:</b> Wednesday, April 25, 2007 3:09 PM<br>
<b>To:</b> Marmon, Glenn D.<br>
<b>Cc:</b> Trinity Sahana Project Internal Group Mailing list<br>
<b>Subject:</b> [Sahana_proj] Re: Conflicts with Sahana coding guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi Glenn,<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I'm going to copy this to the list because I think it raises
a good general issue.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Your module looks very nice and you've done a good job of
integrating it visually within the Sahana look-and-feel. But you're right that
your application really isn't about disaster recovery. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<p class=MsoNormal>Does that sound like a more sensible thing to do - have it
be a standalone product that inherits the Sahana framework as opposed to trying
to make it a module for the complete Sahana software?<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal>Yes. That's what I would suggest. You would strip Sahana to
just those modules you want to include---sort of like what we did for the
HelloWorld module at the beginning of the course. This is an appropriate
use of the Sahana (LAMP) framework. In fact, if you did that, it would be
useful for us to show to local non-profits as a way that Sahana/LAMP could be
customized to meet their IT needs. So, in addition to stripping out
extraneous Sahana modules, you'll probably want to use a different Header and
Image and other customizations. That's not difficult to do--post questions on
the list serve for some ideas. You'll also want to acknowledge
Sahana with some kind of link, at the bottom of your main page that says
"Powered by Sahana". This to is not difficult to do.<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Perhaps someone can suggest an example of this??<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>-- ram<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>Ralph Morelli <<a href="mailto:ralph.morelli@trincoll.edu">ralph.morelli@trincoll.edu</a>><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>Professor of Computer Science<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><br>
<br>
</span><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>On Apr 25, 2007, at 12:37 PM, Marmon, Glenn D. wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>"If I understand your question, you're asking about the
code itself, not the look-and-feel of the calendar, which (I'm assuming) uses
the Sahana CSS tags and so looks like any other Sahana page."<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The calendar code uses its own CSS files and tags - not
Sahana's. The calls to the stylesheet are done in a php file seperate from the
calendar.inc that is linked to in our Sahana Module Menu. The .inc file creates
an iframe, with a source file of v_calendar.php, which is the visual calendar
code that uses the Raccuglia Calendar Software stylesheets and CSS tags. We
have taken special care not to mix the two. (And we can't, really, the visual
breaks if you try to include the code from v_calendar.php directly into
calendar.inc) The end result of this system is a page that looks like this (a
screenshot from a recent build of the ERM on my local machine): <a
href="http://oak.conncoll.edu/~gmarmon/erm_calendar.jpg">http://oak.conncoll.edu/~gmarmon/erm_calendar.jpg</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>"I think the answer to this is "it depends on the
details". If there are minor differences in the coding guidelines, such
that the module's functionality does not become problematic as new releases of
Sahana are made, then that should not be a problem. On the other hand, if the
differences are great enough that functionality or compatibility become issues,
then it should probably be revised. These are the kinds of questions/decisions
that would be made by the core team when they review your code."<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>And this ultimately leads me to a rather large question -
does our "module" really belong in the larger Sahana project? I have
always wanted to build this project as a Sahana module in terms of framework
and style - I love the way Sahana is set up and the way it looks. (That, and at
this point, we have a lot of code that isn't worth much if removed from the
Sahana framework) The more I think about it, though, the more I doubt whether
or not our project truly deals with disaster management. It is used for
regular, day to day organization of Response Teams - it is not specialized to
do so specifically for disasters. In fact, in case of a disaster, the needs of
such an organization may overwhelm our system. So, ultimately, I don't know if
the concept of our "module" belongs in the larger Sahana project,
whether or not it follows the coding guidelines. Right now, we still plan to
develop the ERM as a Sahana Module in terms of framework, but I'm not sure what
we want to do about release. I suppose ideally we could release it with a
"stripped down" version of Sahana, ie, release the ERM with the
Sahana framework but with none of the modules of the regular Sahana. (I'm not
quite sure how to go about that, but I'll post questions about that on the
listserve when I have them, as I'm sure that'd be the best place for
information on that) Does that sound like a more sensible thing to do - have it
be a standalone product that inherits the Sahana framework as opposed to trying
to make it a module for the complete Sahana software?<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>