[JIRA] Commented: (FOR-391) website docs/site split
The following comment has been added to this issue: Author: David Crossley Created: Mon, 11 Apr 2005 9:51 PM Body: The next task is to add entries to the forrest/site/.htaccess file. Some documents need special handling, most redirect to /0.7/ ... cannot do this until ready for 0.7 release. - View this comment: http://issues.cocoondev.org//browse/FOR-391?page=comments#action_12220 - View the issue: http://issues.cocoondev.org//browse/FOR-391 Here is an overview of the issue: - Key: FOR-391 Summary: website docs/site split Type: Task Status: Open Priority: Major Project: Forrest Components: Documentation and website Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: David Crossley Reporter: Dave Brondsema Created: Wed, 24 Nov 2004 10:51 PM Updated: Mon, 11 Apr 2005 9:51 PM Description: Split our website into a standalone documentation site (which will be maintained per version/branch) and the main version-independent site. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-391) website docs/site split
The following comment has been added to this issue: Author: David Crossley Created: Mon, 11 Apr 2005 9:48 PM Body: According to the decision in the last of the abovementioned email threads, the docs have been re-integrated into forrest/trunk/site-author/ and there are now directories in the forrest/site/ repository to hold versions of docs /0.6/ and /0.7/ etc. - View this comment: http://issues.cocoondev.org//browse/FOR-391?page=comments#action_12219 - View the issue: http://issues.cocoondev.org//browse/FOR-391 Here is an overview of the issue: - Key: FOR-391 Summary: website docs/site split Type: Task Status: Open Priority: Major Project: Forrest Components: Documentation and website Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: David Crossley Reporter: Dave Brondsema Created: Wed, 24 Nov 2004 10:51 PM Updated: Mon, 11 Apr 2005 9:48 PM Description: Split our website into a standalone documentation site (which will be maintained per version/branch) and the main version-independent site. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-476) entity resolver not working for plugins development
Message: The following issue has been closed. Resolver: David Crossley Date: Mon, 11 Apr 2005 9:41 PM Added some notes to "Howto build a plugin" about using the forrest-packaged version of Ant. - View the issue: http://issues.cocoondev.org//browse/FOR-476 Here is an overview of the issue: - Key: FOR-476 Summary: entity resolver not working for plugins development Type: Bug Status: Closed Priority: Blocker Resolution: INCOMPLETE Project: Forrest Components: Plugins (general issues) Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Tue, 5 Apr 2005 6:59 AM Updated: Mon, 11 Apr 2005 9:41 PM Description: The catalog entity resolver is failing when doing 'ant docs' or 'ant deploy'. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: site won't build?
Ross Gardler wrote: > I've been doing some work on the building of plugin docs. It now works > with "forrest run", however, with "forrest site" I get broken pipelines > on abs-linkmap and abs-menulinks. > > I'm pretty sure I've not caused this to happen, but I'm going to bed now > so have not verified that this is the case. If anyone is playing with > Forrest between now and tomorrow afternoon (GMT) can you please see if > SVN head will build the forrest site. That'll save me some dignostics > work tomorrow. Sorry, i had some un-committed changes ... fixed now. --David
site won't build?
I've been doing some work on the building of plugin docs. It now works with "forrest run", however, with "forrest site" I get broken pipelines on abs-linkmap and abs-menulinks. I'm pretty sure I've not caused this to happen, but I'm going to bed now so have not verified that this is the case. If anyone is playing with Forrest between now and tomorrow afternoon (GMT) can you please see if SVN head will build the forrest site. That'll save me some dignostics work tomorrow. Thanks. Ross
Re: [Proposal] New format for skinconf
Should I file a JIRA on this (RFE)? Thorsten Scherler wrote: Hi Arik, On Sun, 2005-04-10 at 19:55 +0200, Arik Kfir wrote: I've noticed that the skinconf.xml contains all the skin colors. Generally, that is the place they belong, but I see some problems with this: What I would suggest is to introduce an additional (optional) file called "skin-colors.xml" which will contain the site's color definitions. It should be optional of course. Yeah that would make sense. What's more, with this configuration, we will be able to provide several files - each containing the "skin-colors.xml" file to use (the forrest.properties can have a property that points to it, with a sensible default) so I can have several color configurations and simply "pick out" the one I want by changing a property in forrest.properties. What do you think? I reckon I would not store it in the forrest.properties because the idea is to be able to change this color settings with a cforms tool (or something similar) in webapp mode. That brings us a step forward in the direction of a skinbot. ;-) I reckon it should be stored in the view (the link). Generally speaking I am +1 to split skinconf.xml apart. Since this changes will be post 0.7, anyway, maybe we should generally discuss what belongs in skinconf.xml and what in e.g. contractconf.xml salu2 Thorsten Scherler wrote: Gidday, here is a proposal for a new skinconf format. http://svn.apache.org/viewcvs/forrest/trunk/plugins/org.apache.forrest.plugin.viewHelper/src/documentation/skinconf.proposal.xml?view=auto&rev=160783 This is based on the recent user discussion (skinconf text elements in group.svg) which showed again that our skinconf needs to be more extensible without touching the dtd. e.g. 2005 The Apache Software Foundation. http://www.apache.org/licenses/ The idea is to allow all xml within a forrest:property. WDYT? salu2
Re: problem with docs at forrest.apache.org/docs/dev/
David Crossley wrote: David Crossley wrote: Ross Gardler wrote: How do we link from the main docs-author (or site-author?) part of the site? If we use docs/plugins/ then it will intergrate easily. With the final scheme, we now need to put the generated plugins docs in the forrest/site repository under the /0.7/docs/plugins/ directory. OK, I'm nearly done with that functionality - can't seem to get long enough in one sitting to actually finish it :-( Ross
Re: problem with docs at forrest.apache.org/docs/dev/
David Crossley wrote: > Ross Gardler wrote: > > > > How do we link from the main docs-author (or site-author?) part of the site? > > If we use docs/plugins/ then it will intergrate easily. With the final scheme, we now need to put the generated plugins docs in the forrest/site repository under the /0.7/docs/plugins/ directory. --David
Re: [Proposal] New format for skinconf
On Mon, 2005-04-11 at 13:17 +0200, Nicola Ken Barozzi wrote: > > Can you post the link of the proposal, I could not find it. > > http://issues.cocoondev.org/browse/FOR-144 > Cheers Nicola. Yeah I am +1 to use the one in /etc/. The only addition would be to have @name in element. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: [Proposal] New format for skinconf
Thorsten Scherler wrote: On Mon, 2005-04-11 at 10:36 +0200, Nicola Ken Barozzi wrote: Thorsten Scherler wrote: ... here is a proposal for a new skinconf format. http://svn.apache.org/viewcvs/forrest/trunk/plugins/org.apache.forrest.plugin.viewHelper/src/documentation/skinconf.proposal.xml?view=auto&rev=160783 +0 ... The idea is to allow all xml within a forrest:property. What about the proposal already in SVN, that we have discussed before? Why not make the DTD completely correct without having all xml inside forrest:property? Can you post the link of the proposal, I could not find it. http://issues.cocoondev.org/browse/FOR-144 -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: [Proposal] New format for skinconf
On Mon, 2005-04-11 at 10:36 +0200, Nicola Ken Barozzi wrote: > Thorsten Scherler wrote: > > Gidday, > > > > here is a proposal for a new skinconf format. > > http://svn.apache.org/viewcvs/forrest/trunk/plugins/org.apache.forrest.plugin.viewHelper/src/documentation/skinconf.proposal.xml?view=auto&rev=160783 > > +0 > > > This is based on the recent user discussion (skinconf text elements in > > group.svg) which showed again that our skinconf needs to be more > > extensible without touching the dtd. > > +1 > > > e.g. > > > > > > 2005 > > The Apache Software Foundation. > > http://www.apache.org/licenses/ > > > > > > The idea is to allow all xml within a forrest:property. > > What about the proposal already in SVN, that we have discussed before? > Why not make the DTD completely correct without having all xml inside > forrest:property? Can you post the link of the proposal, I could not find it. ...I could remember the discussion but could not find the proposal. Cheers for the headsup. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: svn commit: r160846 - in forrest/site/plugins: ./ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/samples/ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/samples/openOfficeEmbeddedImage/ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/samples/openOfficeEmbeddedImage/zip-openoffice-impress.sxi/ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/samples/openOfficeEmbeddedImage/zip-openoffice-impress.sxi/file-Pictures/
Thorsten Scherler wrote: On Mon, 2005-04-11 at 08:38 +, [EMAIL PROTECTED] wrote: Author: rgardler Date: Mon Apr 11 01:38:42 2005 New Revision: 160846 URL: http://svn.apache.org/viewcvs?view=rev&rev=160846 Log: Deployment plugins descriptor file (plugins.xml) (deployed by 'deploy-plugins.xml' target of plugin build script) Added: forrest/site/plugins/docs/plugins/org.apache.forrest.plugin.OpenOffice.org/changes.pdf URL: http://svn.apache.org/viewcvs/forrest/site/plugins/docs/plugins/org.apache.forrest.plugin.OpenOffice.org/changes.pdf?view=auto&rev=160846 == --- forrest/site/plugins/docs/plugins/org.apache.forrest.plugin.OpenOffice.org/changes.pdf (added) +++ forrest/site/plugins/docs/plugins/org.apache.forrest.plugin.OpenOffice.org/changes.pdf Mon Apr 11 01:38:42 2005 @@ -0,0 +1,183 @@ +%PDF-1.3 +%ª«¬ +4 0 obj +<< /Type /Info +/Producer (FOP 0.20.5) >> +endobj +5 0 obj +<< /Length 290 /Filter [ /ASCII85Decode /FlateDecode ] + >> ... Hmm, a diff for pdf? That should not be. Thanks for highlighting that, I'm obviously not reading these test commits properly (actually I thought I'd commented out that part of the deploy target). I'll sort the above. Ross
Re: svn commit: r160846 - in forrest/site/plugins: ./ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/samples/ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/samples/openOfficeEmbeddedImage/ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/samples/openOfficeEmbeddedImage/zip-openoffice-impress.sxi/ docs/plugins/org.apache.forrest.plugin.OpenOffice.org/samples/openOfficeEmbeddedImage/zip-openoffice-impress.sxi/file-Pictures/
On Mon, 2005-04-11 at 08:38 +, [EMAIL PROTECTED] wrote: > Author: rgardler > Date: Mon Apr 11 01:38:42 2005 > New Revision: 160846 > > URL: http://svn.apache.org/viewcvs?view=rev&rev=160846 > Log: > Deployment plugins descriptor file (plugins.xml) (deployed by > 'deploy-plugins.xml' target of plugin build script) > Added: > forrest/site/plugins/docs/plugins/org.apache.forrest.plugin.OpenOffice.org/changes.pdf > URL: > http://svn.apache.org/viewcvs/forrest/site/plugins/docs/plugins/org.apache.forrest.plugin.OpenOffice.org/changes.pdf?view=auto&rev=160846 > == > --- > forrest/site/plugins/docs/plugins/org.apache.forrest.plugin.OpenOffice.org/changes.pdf > (added) > +++ > forrest/site/plugins/docs/plugins/org.apache.forrest.plugin.OpenOffice.org/changes.pdf > Mon Apr 11 01:38:42 2005 > @@ -0,0 +1,183 @@ > +%PDF-1.3 > +%ª«¬ > +4 0 obj > +<< /Type /Info > +/Producer (FOP 0.20.5) >> > +endobj > +5 0 obj > +<< /Length 290 /Filter [ /ASCII85Decode /FlateDecode ] > + >> > ... Hmm, a diff for pdf? That should not be. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: [Proposal] New format for skinconf
Thorsten Scherler wrote: Gidday, here is a proposal for a new skinconf format. http://svn.apache.org/viewcvs/forrest/trunk/plugins/org.apache.forrest.plugin.viewHelper/src/documentation/skinconf.proposal.xml?view=auto&rev=160783 +0 This is based on the recent user discussion (skinconf text elements in group.svg) which showed again that our skinconf needs to be more extensible without touching the dtd. +1 e.g. 2005 The Apache Software Foundation. http://www.apache.org/licenses/ The idea is to allow all xml within a forrest:property. What about the proposal already in SVN, that we have discussed before? Why not make the DTD completely correct without having all xml inside forrest:property? -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: status on leather-dev?
Hi Diwaker, leather-dev is dead long live view/viewHelper. ;-) I made a screen shot of the view plugin (using the viewHelper plugin). http://svn.apache.org/viewcvs.cgi/forrest/trunk/site-author/content/xdocs/docs/images/snapshot-view-viewHelper.png?view=markup The viewHelper is using the markup and css elements from scale-dev. ...but I reckon the css would need some patches. ;-) salu2 thorsten On Thu, 2005-03-10 at 14:24 -0800, Diwaker Gupta wrote: > Hi everyone, > > Sometime back there was a discussion on the list on whether to keep > leather purely syntactic (i.e., use containers and named CSS elements > without attaching any notions of containment or placement in the skin > itself). The problem we were facing back then was that CSS is not very > good with absolute placement, and so keeping the skin purely syntactic > and doing all positioning with CSS was not working out very well (as > anyone using leather has seen -- particular notorious with the > "floating" search box and the weirdly placed menu) > > So whats the status on leather now? Are we still with the purely > syntactic model? I really liked the idea implemented in scale-dev, > which honored CSS named elements (branding etc), but also included > some semantic notion of containment within the skin itself (like the > search box going inside the header etc) to make CSS skinning easier. > > TIA -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: problem with docs at forrest.apache.org/docs/dev/
I have the generated versioned documents ready for commit for both 0.7 and 0.6 versions. For those on forrest-svn mailing list, sorry about the size of the commit messages. --David
Re: [Proposal] New format for skinconf
Hi Arik, On Sun, 2005-04-10 at 19:55 +0200, Arik Kfir wrote: > I've noticed that the skinconf.xml contains all the skin colors. > Generally, that is the place they belong, but I see some problems with > this: > What I would suggest is to introduce an additional (optional) file > called "skin-colors.xml" which will contain the site's color > definitions. It should be optional of course. > Yeah that would make sense. > What's more, with this configuration, we will be able to provide > several files - each containing the "skin-colors.xml" file to use (the > forrest.properties can have a property that points to it, with a > sensible default) so I can have several color configurations and > simply "pick out" the one I want by changing a property in > forrest.properties. > > What do you think? > I reckon I would not store it in the forrest.properties because the idea is to be able to change this color settings with a cforms tool (or something similar) in webapp mode. That brings us a step forward in the direction of a skinbot. ;-) I reckon it should be stored in the view (the link). Generally speaking I am +1 to split skinconf.xml apart. Since this changes will be post 0.7, anyway, maybe we should generally discuss what belongs in skinconf.xml and what in e.g. contractconf.xml salu2 > > Thorsten Scherler wrote: > > Gidday, > > > > here is a proposal for a new skinconf format. > > http://svn.apache.org/viewcvs/forrest/trunk/plugins/org.apache.forrest.plugin.viewHelper/src/documentation/skinconf.proposal.xml?view=auto&rev=160783 > > > > This is based on the recent user discussion (skinconf text elements in > > group.svg) which showed again that our skinconf needs to be more > > extensible without touching the dtd. > > > > e.g. > > > > > > 2005 > > The Apache Software Foundation. > > http://www.apache.org/licenses/ > > > > > > The idea is to allow all xml within a forrest:property. > > > > WDYT? > > > > salu2 > > -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
