headers
Thorsten Scherler (JIRA | 1 May 2006 01:37
Picon
Favicon

[jira] Commented: (FOR-811) shine and polish the pelt theme so that it closely resembles the pelt skin

    [ http://issues.apache.org/jira/browse/FOR-811?page=comments#action_12377201 ] 

Thorsten Scherler commented on FOR-811:
---------------------------------------

David changed status to reopen on the 27.02.06. 

However the attached patches are applied.

David, what is missing to resolve this issue?

> shine and polish the pelt theme so that it closely resembles the pelt skin
> --------------------------------------------------------------------------
>
>          Key: FOR-811
>          URL: http://issues.apache.org/jira/browse/FOR-811
>      Project: Forrest
>         Type: Sub-task

>   Components: Dispatcher (aka views), Skins (general issues)
>     Reporter: David Crossley
>  Attachments: pelt.fv.diff, pelt.screen.css.diff, siteinfo-credits.ft.diff
>
> So that they can just switch from "pelt skin" to "pelt theme" and not get any surprises, e.g. "pelt skin' has
no "xml doc" link.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley (JIRA | 1 May 2006 02:04
Picon
Favicon

[jira] Commented: (FOR-811) shine and polish the pelt theme so that it closely resembles the pelt skin

    [ http://issues.apache.org/jira/browse/FOR-811?page=comments#action_12377202 ] 

David Crossley commented on FOR-811:
------------------------------------

Well Gavin's previous comments said that patches were partially addressing the issues, so someone needs
to check to see what else. Then there is the tables issue that he mentions. Also last time i looked there were
some defaults that were different, e.g. IIRC two search boxes.

> shine and polish the pelt theme so that it closely resembles the pelt skin
> --------------------------------------------------------------------------
>
>          Key: FOR-811
>          URL: http://issues.apache.org/jira/browse/FOR-811
>      Project: Forrest
>         Type: Sub-task

>   Components: Dispatcher (aka views), Skins (general issues)
>     Reporter: David Crossley
>  Attachments: pelt.fv.diff, pelt.screen.css.diff, siteinfo-credits.ft.diff
>
> So that they can just switch from "pelt skin" to "pelt theme" and not get any surprises, e.g. "pelt skin' has
no "xml doc" link.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brian M Dube | 1 May 2006 02:50
Picon

[Dispatcher] Common theme navigation contracts invalid

I looked for a relevant issue in JIRA, but I did not see one.

There is a FIXME note [1] in pelt's nav-main-sub contract to use the 
contract from common instead. Before that happens, the common contracts 
should be changed. Both common/html/nav-main.ft and 
common/html/nav-main-sub.ft add div tags with  <at> id="tabs" and that won't 
validate.

Brian

[1] FIXME - With a little css work, we should use the common contract 
and suppress this one (no need of level2tabs)
Permalink | Reply | 3 comments |
headers
David Crossley (JIRA | 1 May 2006 09:05
Picon
Favicon

[jira] Assigned: (FOR-824) HowTo DTD 2.0 <a> elements not transformed correctly

     [ http://issues.apache.org/jira/browse/FOR-824?page=all ]

David Crossley reassigned FOR-824:
----------------------------------

    Assign To: David Crossley

> HowTo DTD 2.0 <a> elements not transformed correctly
> ----------------------------------------------------
>
>          Key: FOR-824
>          URL: http://issues.apache.org/jira/browse/FOR-824
>      Project: Forrest
>         Type: Bug

>   Components: Skins (general issues)
>     Versions: 0.7
>     Reporter: Steve Masover
>     Assignee: David Crossley
>     Priority: Minor

>
> The v0.7 howto2document.xsl in $FORREST_HOME/main/webapp/resources/stylesheets does not process a
HowTo DTD 2.0 <a> section correctly. Transformation to document v1.3 should transform <a> to <link>

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley (JIRA | 1 May 2006 09:13
Picon
Favicon

[jira] Updated: (FOR-824) HowTo DTD 2.0 <a> elements not transformed correctly

     [ http://issues.apache.org/jira/browse/FOR-824?page=all ]

David Crossley updated FOR-824:
-------------------------------

    Version: 0.8-dev

> HowTo DTD 2.0 <a> elements not transformed correctly
> ----------------------------------------------------
>
>          Key: FOR-824
>          URL: http://issues.apache.org/jira/browse/FOR-824
>      Project: Forrest
>         Type: Bug

>   Components: Skins (general issues)
>     Versions: 0.7, 0.8-dev
>     Reporter: Steve Masover
>     Assignee: David Crossley
>     Priority: Minor

>
> The v0.7 howto2document.xsl in $FORREST_HOME/main/webapp/resources/stylesheets does not process a
HowTo DTD 2.0 <a> section correctly. Transformation to document v1.3 should transform <a> to <link>

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley (JIRA | 1 May 2006 09:31
Picon
Favicon

[jira] Closed: (FOR-824) HowTo DTD 2.0 <a> elements not transformed correctly

     [ http://issues.apache.org/jira/browse/FOR-824?page=all ]

David Crossley closed FOR-824:
------------------------------

    Fix Version: 0.8-dev
                 0.7
     Resolution: Fixed

Thanks Steve. I added a fix to both 0.8-dev trunk and to 0.7 branch, to transform howto-v20 to the current
internal format document-v13.

> HowTo DTD 2.0 <a> elements not transformed correctly
> ----------------------------------------------------
>
>          Key: FOR-824
>          URL: http://issues.apache.org/jira/browse/FOR-824
>      Project: Forrest
>         Type: Bug

>   Components: Skins (general issues)
>     Versions: 0.7, 0.8-dev
>     Reporter: Steve Masover
>     Assignee: David Crossley
>     Priority: Minor
>      Fix For: 0.7, 0.8-dev

>
> The v0.7 howto2document.xsl in $FORREST_HOME/main/webapp/resources/stylesheets does not process a
HowTo DTD 2.0 <a> section correctly. Transformation to document v1.3 should transform <a> to <link>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thorsten Scherler | 1 May 2006 16:38
Picon
Favicon
Gravatar

Re: [Dispatcher] Common theme navigation contracts invalid

El dom, 30-04-2006 a las 19:50 -0500, Brian M Dube escribió:
> I looked for a relevant issue in JIRA, but I did not see one.
> 
> There is a FIXME note [1] in pelt's nav-main-sub contract 

You mean [I], right?

> to use the 
> contract from common instead. Before that happens, the common contracts 
> should be changed. Both common/html/nav-main.ft and 
> common/html/nav-main-sub.ft add div tags with  <at> id="tabs" and that won't 
> validate.

What do you mean with "that won't validate"? With what? 

[II] - The output format is html so I guess against xhtml-strict, right?

salu2

> 
> Brian
> 
> [1] FIXME - With a little css work, we should use the common contract 
> and suppress this one (no need of level2tabs)

[I]
http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/nav-main-sub.ft?view=markup

[II]
http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/common/html/nav-main-sub.ft?view=markup
(Continue reading)

Permalink | Reply | 2 comments |
headers
Gav.... | 2 May 2006 01:11
Picon

RE: [Dispatcher] Common theme navigation contracts invalid

What Brian means is that in both common/nav-main.ft and
common/nav-main-sub.ft there are <div>s declared both with id of 'tabs' . 

In pelt/nav-main-sub.ft the second-level tabs has an id of 'level2tabs'
which is correct.

Having two <divs> with the same id is invalid markup - even in HTML 4.01
Transitional. http://www.w3.org/TR/html4/struct/global.html#adef-id

So we need to change the common/nav-main-sub.ft to match the pelt version.

Gav...

> -----Original Message-----
> From: Thorsten Scherler [mailto:thorsten <at> apache.org]
> Sent: Monday, 1 May 2006 10:39 PM
> To: dev <at> forrest.apache.org
> Subject: Re: [Dispatcher] Common theme navigation contracts invalid
> 
> El dom, 30-04-2006 a las 19:50 -0500, Brian M Dube escribió:
> > I looked for a relevant issue in JIRA, but I did not see one.
> >
> > There is a FIXME note [1] in pelt's nav-main-sub contract
> 
> You mean [I], right?
> 
> > to use the
> > contract from common instead. Before that happens, the common contracts
> > should be changed. Both common/html/nav-main.ft and
> > common/html/nav-main-sub.ft add div tags with  <at> id="tabs" and that won't
(Continue reading)

Permalink | Reply | 1 comment |
headers
David Crossley (JIRA | 2 May 2006 02:18
Picon
Favicon

[jira] Updated: (FOR-681) Include xconf files in plugins using includes, not XPatch

     [ http://issues.apache.org/jira/browse/FOR-681?page=all ]

David Crossley updated FOR-681:
-------------------------------

    Fix Version: 0.8-dev

We should at least try to investigate this for the 0.8 release.

> Include xconf files in plugins using includes, not XPatch
> ---------------------------------------------------------
>
>          Key: FOR-681
>          URL: http://issues.apache.org/jira/browse/FOR-681
>      Project: Forrest
>         Type: Improvement

>   Components: Plugins (general issues)
>     Versions: 0.8-dev
>  Environment: Windows XP Home
>     Reporter: Alex Batlin
>     Priority: Blocker
>      Fix For: 0.8-dev

>
> See http://marc.theaimsgroup.com/?l=forrest-dev&m=112781600212715&w=2
> > I was excited to see the addition of xconf capability into plugins. See
> > http://svn.apache.org/viewcvs?rev=227190&view=rev.
> > 
> > I rebuild cocoon with authentication and session blocks, and added the jars
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley | 2 May 2006 02:19
Picon
Favicon

preparing for 0.8 release

The next step in preparing for the upcoming release
is to assess the state of the issue tracker.

Would people please review the list of unscheduled
issues. This is something that all developers can
assist with, not just the committers.
http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310043

If you see anything that is vital and can be
realistically achieved for the release, then please
provide its issue number and a committer will Edit it
to set the "Fix Version" to 0.8-dev.

Then next step will then be to review the list of
scheduled issues to be more realistic.

If you can add comments or patches to an issue
then please do so.

-David
Permalink | Reply | 2 comments |

Gmane