hello all,
> >
> > > If no CSS is defined in the view then *no* css will be linked in the
> presentation.
> >
> > I don't think this is a very good idea. First users of forrest are
> > often novices, and by default, we want to output a slick-looking site.
> > We've already heard reports of peop
Diwaker Gupta wrote:
Due to the way CSS works, if I have to define new properties for
the nav-bar say, then I first have to UNDO all of the changes made by
the CSS files loaded by default, and then define the CSS properties
the way I want them to.
...
A simple option that controls inclusion of defa
Juan Jose Pablos wrote:
Diwaker Gupta wrote:
Awesome! While we're at it, I wonder why we have those elaborate color
definitions in skinconf.xml? Since we are going to use CSS for
skinning anyways, doesn't it make more sense to put the color
definitions into CSS as well? Just a thought.
+1
These wer
Diwaker Gupta wrote:
Awesome! While we're at it, I wonder why we have those elaborate color
definitions in skinconf.xml? Since we are going to use CSS for
skinning anyways, doesn't it make more sense to put the color
definitions into CSS as well? Just a thought.
+1
Hi all,
this week I am at a client, so my answer can take a while.
On Sat, 2005-04-16 at 19:54 -0700, Diwaker Gupta wrote:
> > > Due to the way CSS works, if I have to define new properties for
> > > the nav-bar say, then I first have to UNDO all of the changes made
by
> > > the CSS files loaded
> > Due to the way CSS works, if I have to define new properties for
> > the nav-bar say, then I first have to UNDO all of the changes made by
> > the CSS files loaded by default, and then define the CSS properties
> > the way I want them to.
> > ...
> > A simple option that controls inclusion of d
I opened up a new thread to respecify the focus.
*Point 1 - css linking*
On Sat, 2005-04-16 at 14:54 -0700, Diwaker Gupta wrote:
> After some playing around, I seriously think the CSS should be
> *completely* decoupled from the nugget contracts. The problem with the
> current implementation is th
After some playing around, I seriously think the CSS should be
*completely* decoupled from the nugget contracts. The problem with the
current implementation is that it includes all the default CSS files
(eg: basic.css, contracts-.css and so on) and then it loads
the CSS file specified by forrest:cs
I will have to go right now, but a quick response on that.
On Sat, 2005-04-16 at 13:05 -0700, Diwaker Gupta wrote:
> I was looking at nav-main.ft, and found that the background images in
> the CSS were using URLs of the form '/skin/images/.gif' -- this
> assumes that the deployed forrest site
That bug is fixed in trunk.
On Sat, 2005-04-16 at 15:59 +0200, Thorsten Scherler wrote:
> On Fri, 2005-04-15 at 21:32 -0700, Diwaker Gupta wrote:
> > > I made some changes to add custom css to the view.
> >
> > Great!
> >
> > >
> > >
> > > This tag has to be direct son from forrest:view!
> > >
I was looking at nav-main.ft, and found that the background images in
the CSS were using URLs of the form '/skin/images/.gif' -- this
assumes that the deployed forrest site is deployed a domain whose top
level contains a skin directory. That is, this will NOT work if my
website is deployed at s
Awesome! While we're at it, I wonder why we have those elaborate color
definitions in skinconf.xml? Since we are going to use CSS for
skinning anyways, doesn't it make more sense to put the color
definitions into CSS as well? Just a thought.
On 4/16/05, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
On Fri, 2005-04-15 at 21:32 -0700, Diwaker Gupta wrote:
> > I made some changes to add custom css to the view.
>
> Great!
>
> >
> >
> > This tag has to be direct son from forrest:view!
> >
> > In the above link you will find:
> >
> >
> > That means e.g.
> >
> >
> > would expect (with defau
Hi Diwaker,
firstly thanks for taking the time to test and give feedback. That is
helping us so much. :)
On Fri, 2005-04-15 at 21:53 -0700, Diwaker Gupta wrote:
> > I made some changes to add custom css to the view.
> >
> >
>
> Life's good so far. Now, from what I see, it seems that the nugge
> I made some changes to add custom css to the view.
>
>
Life's good so far. Now, from what I see, it seems that the nugget for
generating "tabs" is currently not doing much (atleast it doesn't
generate any content for me. did I miss anything?) Is this intentional
or you just haven't gotten arou
replying to my own mail -- sheesh! Sorry, I think I've figured it out
:) Will ping again if I have some problems. Ciao
On 4/15/05, Diwaker Gupta <[EMAIL PROTECTED]> wrote:
> > I made some changes to add custom css to the view.
> >
> >
>
> Sorry for being obtuse, but where exactly does this go? A
> I made some changes to add custom css to the view.
>
>
Sorry for being obtuse, but where exactly does this go? As in, in
which file? Somehow, I feel as if the CSS separation is not as neat as
the contracts separation. Ideally, I should be able to define my own
CSS and forrest should pick it up
On Fri, 2005-04-15 at 16:33 -0700, Diwaker Gupta wrote:
> Hi everyone,
>
> I'm playing around with view/viewHelper -- pretty cool! Its easy to
> define new views by placing them in ${content-dir}/conf/. I can either
> use default.fv or define per-page views. All rocks.
>
:)
> However, I wasn't
Hi everyone,
I'm playing around with view/viewHelper -- pretty cool! Its easy to
define new views by placing them in ${content-dir}/conf/. I can either
use default.fv or define per-page views. All rocks.
However, I wasn't very sure where to put the relevant CSS stuff? The
plugin itself contains s
19 matches
Mail list logo
