Alex Mandel | 6 Jan 2009 03:48

Persistent CSS

Things are coming along on the new map, feel free to grab the map.py
macro and play with it.

I was wondering though, if I need some CSS to make the map looks good
and deal with the legend etc where should I put the code so that it's
cached and already loaded with the main stylesheets. Or should I put the
reference in the map macro code?

Thanks,
Alex
Brent Laabs | 6 Jan 2009 04:31
Picon

Re: Persistent CSS

For an interim solution, you can always use a personal CSS URL on the user settings page.

In terms of a longer term solution, we can do two things:
 * Divide map layout and map style (color) information into the two existing CSS files.
 * Add a separate map.css, and then hack the code to make that file load too. They're currently just normal uploaded files on Wiki Settings/CSS.

I'm leaning towards the latter, currently.

Brent

On Mon, Jan 5, 2009 at 6:48 PM, Alex Mandel <tech_dev-V1ui0Jp4Xm2ZwHVy+eqOOgC/G2K4zDHf@public.gmane.org> wrote:
Things are coming along on the new map, feel free to grab the map.py
macro and play with it.

I was wondering though, if I need some CSS to make the map looks good
and deal with the legend etc where should I put the code so that it's
cached and already loaded with the main stylesheets. Or should I put the
reference in the map macro code?

Thanks,
Alex
_______________________________________________
Sycamore-Dev mailing list
sycamore-dev-R5Z0CYfGwkJg9hUCZPvPmw@public.gmane.org
http://www.projectsycamore.org/
https://tools.cernio.com/mailman/listinfo/sycamore-dev

<div>
<p>For an interim solution, you can always use a personal CSS URL on the user settings page.<br><br>In terms of a longer term solution, we can do two things:<br>&nbsp;* Divide map layout and map style (color) information into the two existing CSS files.<br>
&nbsp;* Add a separate map.css, and then hack the code to make that file load too. They're currently just normal uploaded files on Wiki Settings/CSS.<br><br>I'm leaning towards the latter, currently.<br><br>Brent<br><br></p>
<div class="gmail_quote">On Mon, Jan 5, 2009 at 6:48 PM, Alex Mandel <span dir="ltr">&lt;<a href="mailto:tech_dev@...">tech_dev@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
Things are coming along on the new map, feel free to grab the map.py<br>
macro and play with it.<br><br>
I was wondering though, if I need some CSS to make the map looks good<br>
and deal with the legend etc where should I put the code so that it's<br>
cached and already loaded with the main stylesheets. Or should I put the<br>
reference in the map macro code?<br><br>
Thanks,<br>
Alex<br>
_______________________________________________<br>
Sycamore-Dev mailing list<br><a href="mailto:sycamore-dev@...">sycamore-dev@...</a><br><a href="http://www.projectsycamore.org/" target="_blank">http://www.projectsycamore.org/</a><br><a href="https://tools.cernio.com/mailman/listinfo/sycamore-dev" target="_blank">https://tools.cernio.com/mailman/listinfo/sycamore-dev</a><br>
</blockquote>
</div>
<br>
</div>
Philip Neustrom | 13 Jan 2009 04:51
Picon
Gravatar

Re: Persistent CSS

Excerpts from Brent Laabs's message of Mon Jan 05 19:31:29 -0800 2009:
> For an interim solution, you can always use a personal CSS URL on the user
> settings page.
> 
> In terms of a longer term solution, we can do two things:
>  * Divide map layout and map style (color) information into the two existing
> CSS files.
>  * Add a separate map.css, and then hack the code to make that file load
> too. They're currently just normal uploaded files on Wiki Settings/CSS.
> 
> I'm leaning towards the latter, currently.
> 
> Brent
> 
> On Mon, Jan 5, 2009 at 6:48 PM, Alex Mandel <tech_dev@...>wrote:
> 
> > Things are coming along on the new map, feel free to grab the map.py
> > macro and play with it.
> >
> > I was wondering though, if I need some CSS to make the map looks good
> > and deal with the legend etc where should I put the code so that it's
> > cached and already loaded with the main stylesheets. Or should I put the
> > reference in the map macro code?
> >
> > Thanks,
> > Alex
> > _______________________________________________
> > Sycamore-Dev mailing list
> > sycamore-dev@...
> > http://www.projectsycamore.org/
> > https://tools.cernio.com/mailman/listinfo/sycamore-dev
> >

Yeah, I'd say a map.css file is best.  It wouldn't need to be versioned on the individual wikis.

You can just output the CSS directly into the page.  Just put some XXX TODO s around it in the code and I can fix it
up when we merge it into trunk.

--philip
Excerpts from Brent Laabs's message of Mon Jan 05 19:31:29 -0800 2009:
> For an interim solution, you can always use a personal CSS URL on the user
> settings page.
> 
> In terms of a longer term solution, we can do two things:
>  * Divide map layout and map style (color) information into the two existing
> CSS files.
>  * Add a separate map.css, and then hack the code to make that file load
> too. They're currently just normal uploaded files on Wiki Settings/CSS.
> 
> I'm leaning towards the latter, currently.
> 
> Brent
> 
> On Mon, Jan 5, 2009 at 6:48 PM, Alex Mandel <tech_dev@...>wrote:
> 
> > Things are coming along on the new map, feel free to grab the map.py
> > macro and play with it.
> >
> > I was wondering though, if I need some CSS to make the map looks good
> > and deal with the legend etc where should I put the code so that it's
> > cached and already loaded with the main stylesheets. Or should I put the
> > reference in the map macro code?
> >
> > Thanks,
> > Alex
> > _______________________________________________
> > Sycamore-Dev mailing list
> > sycamore-dev@...
> > http://www.projectsycamore.org/
> > https://tools.cernio.com/mailman/listinfo/sycamore-dev
> >

Yeah, I'd say a map.css file is best.  It wouldn't need to be versioned on the individual wikis.

You can just output the CSS directly into the page.  Just put some XXX TODO s around it in the code and I can fix it
up when we merge it into trunk.

--philip

Gmane