[isf-wifidog] WifiDog UI Diagrams and page map
Rob Janes
janes.rob at gmail.com
Lun 14 Nov 12:12:30 EST 2005
awesome. if i understand you correctly, you are saying you are going to
do exactly what i was suggesting. to whit -
* split stylesheet.css into two files, one very large and suitable for
<link> tag usage, the other very small and made for smarty template
inclusion.
* based the smarty template css in the local_content subdirectories.
if that's so, i could help things along a bit ... since i have already
made all the necessary code changes to my copy of wifidog-auth.
-rob
Proulx François wrote:
> The reason for this is that we could not simply put absolute url
> because wifidog could be installed in a sub-directory of your
> webserver like http://myserver.com/wifidog/... Since we will adopt a
> new standard , one main css and optionnal overriding css for portal
> pages, this will be simplified by having an external css. This should
> be done soon ... (read before december)
>
>
> On 14-Nov-2005, at 11:50 , Rob Janes wrote:
>
>> sorry, brain freeze ...
>>
>> in classes/SmaryWifidog.php
>>
>> $smarty->assign('base_url_path', BASE_URL_PATH);
>>
>> then in local_content/default/stylesheet.css:
>>
>> div.navigation {
>> background-image: url({$base_url_path}images/01_nav.gif);
>> }
>> div.avis {
>> background-image: url({$base_url_path}images/03_avis.gif);
>> }
>>
>> all paths in the stylesheet should either be absolute, or written
>> similarily to this.
>>
>> if all this code stuff is too much for this list, just let me know,
>> i'll shut up.
>>
>> -rob
>>
>> Rob Janes wrote:
>>
>>> *snap* the url's are templated because you need to fudge the
>>> relative path for the background-image urls. but, significantly,
>>> the smarty template directives to accomplish this are missing.
>>> Failing this, all smarty includes of the stylesheet template must
>>> be done from php files exactly one directory under the base
>>> directory, no more, no less.
>>>
>>> so, if somebody would fix the templating code you'll be able to
>>> retain the ability to customize the background images to each
>>> location, and allow any php UI to include the stylesheet template
>>> regardless of it's relative path. Like if someone were to put
>>> DEFAULT_CONTENT_URL into the smarty variable pool ...
>>>
>>> in MainUI.php:
>>>
>>> $smarty->assign('defcon_url', DEFAULT_CONTENT_URL);
>>>
>>> and then modify the local_content/default/stylesheet.css file:
>>>
>>> div.navigation {
>>> background-image: url({$defcon_url}images/01_nav.gif);
>>> }
>>> div.avis {
>>> background-image: url({$defcon_url}images/03_avis.gif);
>>> }
>>>
>>> everything should be hunkydorry.
>>> -rob
>>>
>>> Rob Janes wrote:
>>>
>>>> I had the same problem. Here's what I did. seems to work well.
>>>> my css is missing the bg_body, so I guess it's not up to date.
>>>> still, what i'm suggesting should work.
>>>>
>>>> in the stylesheet.css, the fatal pieces are the parts bracketed by
>>>> {literal} and {/literal} in the stylesheet, which are smarty
>>>> template directives. the only reason for doing that is to allow
>>>> the background-image in DIV.AVIS and DIV.NAVIGATION to be dynamic,
>>>> driven by some database location specific stuff that to the best
>>>> of my knowledge is yet to be implemented.
>>>>
>>>> that seems like some useful functionality. what i think will work
>>>> well is to compose a static stylesheet, local_content/common/
>>>> stylesheet.css, which has default background images specified,
>>>> with correct paths for that css file. ie
>>>>
>>>> div.navigation {
>>>> ...
>>>> background-image: url(../../images/01_nav.gif);
>>>> ...
>>>> }
>>>>
>>>> and
>>>>
>>>> div.avis {
>>>> ...
>>>> background-image: url(../../images/03_avis.gif);
>>>> ...
>>>> }
>>>>
>>>> This file would be included by a link in the header, as generated
>>>> by classes/MainUI.php:
>>>>
>>>> $html .= "<link rel='stylesheet' type='text/css'
>>>> href='".COMMON_CONTENT_URL.STYLESHEET_NAME."' />\n";
>>>>
>>>> To allow a dynamic background, I believe all we have to do is have
>>>> a subsequent smarty template for the stylesheet.css, which only
>>>> has the parts we want to override:
>>>>
>>>> local_content/default/stylesheet.css:
>>>>
>>>> div.navigation {
>>>> background-image: url(../images/01_nav.gif);
>>>> }
>>>> div.avis {
>>>> background-image: url(../images/03_avis.gif);
>>>> }
>>>>
>>>> The smarty fetch in MainUI.php would remain asis. The change to
>>>> the relative path for the url is because the basepath the browser
>>>> is using is for MainUI.php, not stylesheet.css.
>>>>
>>>> Thus, the bulk of the current local_content/default/ stylesheet.css
>>>> would be copied to local_content/common/ stylesheet.css, and
>>>> everything but the templated stuff would be stripped from the
>>>> original file stylesheet.css.
>>>>
>>>> -rob
>>>>
>>>> Proulx François wrote:
>>>>
>>>>> It's a recurring problem, we will drop the old style
>>>>> local_content stuff, this will fix the problem ... we will
>>>>> definitely switch to external css since we do not benefit from
>>>>> caching , makes our pages twice as big for most of the simple
>>>>> pages ...
>>>>> On 14-Nov-2005, at 10:02 , Max Horváth wrote:
>>>>>
>>>>>> This might be partly off-topic, but it's an error to be fixed soon.
>>>>>>
>>>>>> The newest CVS version contains a slightly modified version of
>>>>>> the CSS file.
>>>>>>
>>>>>> Due to the CSS is not an accessible file but directly included
>>>>>> in each HTML file I get error from the Apache webserver due to
>>>>>> file that could not be found.
>>>>>>
>>>>>> The files are:
>>>>>> /wifidog/images/bg_body.gif
>>>>>> /wifidog/images/01_nav.gif
>>>>>> /wifidog/images/03_avis.gif
>>>>>>
>>>>>> These file are included in the new CSS file like this:
>>>>>>
>>>>>> background : #dbffa8 url("../images/bg_body.gif") repeat-x fixed
>>>>>> 0px 0px;
>>>>>>
>>>>>> It should be clear that this doesn't work on every html page. It
>>>>>> works in the administration interface, but it doesn't work in
>>>>>> the wifidog root directory.
>>>>>>
>>>>>> We should be switching to a single CSS file which gets included
>>>>>> via HTML and which is not directly embedded into a HTML file.
>>>>>>
>>>>>> Cheers, Max!
>>>>>>
>>>>>> Am 09.11.2005 um 23:10 schrieb Rob Janes:
>>>>>>
>>>>>>> looks nice, but the error message or status message area seems
>>>>>>> kind of lost.
>>>>>>>
>>>>>>> Benjamin Crulli wrote:
>>>>>>>
>>>>>>>> Sweet !
>>>>>>>> I can help with the sample css if you want ...
>>>>>>>>
>>>>>>>> On 11/7/05, Proulx François <fproulx at edito.qc.ca
>>>>>>>> <mailto:fproulx at edito.qc.ca>> wrote:
>>>>>>>>
>>>>>>>>>> a) indicate how to break up the pages to maximize reusable
>>>>>>>>>> components (this should be mostly clear)
>>>>>>>>>> b) indicate the permissions for each page and/or section of
>>>>>>>>>> each page
>>>>>>>>>>
>>>>>>>>>> Does someone who is more familiar with the internal design of
>>>>>>>>>> WifiDog want to take a shot at 2b? We can do this by giving
>>>>>>>>>> a red
>>>>>>>>>> background to any page/component that requires admin level
>>>>>>>>>> access,
>>>>>>>>>> and maybe a blue background for any component that requires
>>>>>>>>>> registered user level access.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I will have a look tomorrow. Send you the list of pages that
>>>>>>>>> must be
>>>>>>>>> secured.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Also, it would be helpful if the person who put together the
>>>>>>>>>> content management system wrote down a 1 page description
>>>>>>>>>> about how
>>>>>>>>>> it works.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> There you go :
>>>>>>>>> http://old.ilesansfil.org/wiki/WiFiDog/ ContentDistributionSystem
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> WiFiDog mailing list
>>>>>>>>> WiFiDog at listes.ilesansfil.org
>>>>>>>>> <mailto:WiFiDog at listes.ilesansfil.org>
>>>>>>>>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Ben Crulli
>>>>>>>> _______________________________________________
>>>>>>>> WiFiDog mailing list
>>>>>>>> WiFiDog at listes.ilesansfil.org
>>>>>>>> <mailto:WiFiDog at listes.ilesansfil.org>
>>>>>>>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> WiFiDog mailing list
>>>>>>> WiFiDog at listes.ilesansfil.org
>>>>>>> <mailto:WiFiDog at listes.ilesansfil.org>
>>>>>>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> WiFiDog mailing list
>>>>>> WiFiDog at listes.ilesansfil.org
>>>>>> <mailto:WiFiDog at listes.ilesansfil.org>
>>>>>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> -----
>>>>>
>>>>> _______________________________________________
>>>>> WiFiDog mailing list
>>>>> WiFiDog at listes.ilesansfil.org
>>>>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>>>>
>>>>
>>>>
>>>
>>>
>>
>> _______________________________________________
>> WiFiDog mailing list
>> WiFiDog at listes.ilesansfil.org
>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
>
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
More information about the WiFiDog
mailing list