The following comment has been added to this issue:
Author: David Crossley
Created: Sun, 17 Apr 2005 12:43 AM
Body:
The workaround for FOR-156 was so close to working. Its trouble was only that
it needed to deal with docs in sub-directories as well as at top-level. This
needed on
> > 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
On Fri, 2005-04-15 at 13:06 +0200, Thorsten Scherler wrote:
> On Thu, 2005-04-14 at 17:33 +0100, Ross Gardler wrote:
>
> > So, unless there is a -1 before by the end of the weekend I will move
> > the following plugins to whiteboard/plugins next week.
>
> > o.a.f.p.internal.views
> > o.a.f.p
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
11 matches
Mail list logo
