You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Diwaker Gupta <di...@gmail.com> on 2005/06/23 20:18:38 UTC

Roadmap

Now that the release is just around the corner (since the website is
already updated, I guess we're just waiting for the announcement,
perhaps we should jot down a priority list of new features for 0.8.

Personally, I'd like to see the following happening:

o views -- polished, with atleast 2 supplied skins and a cleaned up
plugin structure (or going into the core, I'm not sure whats the plan)

o Support for Google sitemap -- since this is a Google proposal, I'm
pretty sure that sites using Google sitemaps will get more visibility
than those not using it. So in general it would be a good idea. And
with Forrest, it should be pretty easy to generate the sitemap in
whatever format we want

o XHTML2 -- the Forrest team should make sure that this transition is
as smooth as possible. So for instance, supply a simple script that
will convert existing document-v20 to XHTML2 automagically :)

o So far the focus has been on improving the HTML output (since thats
the most visible). I know there has been some work into customizing
the PDF output, but I think both the PDF and Text output formats need
a bit more work to bring them upto speed.

Looking forward to exciting times! 

Diwaker
-- 
Diwaker Gupta
http://resolute.ucsd.edu/diwaker

Re: Properties for views (Re: logic filters in views)

Posted by Thorsten Scherler <th...@apache.org>.
On Mon, 2005-06-27 at 10:33 -0700, Diwaker Gupta wrote:
> > Without per directory we need three files for every page - bad.
> 
> I agree. If Forrest requires me to create 3 files for each page, I'm
> going to be concerned.
> 

Yeah, I will try to implement it today. 

One question:
<map:match pattern="prepare.view.**">
      <map:select type="exists">
        <!--
          Here we will have to test, whether the requested page needs a
specific view.
          This will be assumed as soon there is a .fv
          e.g. index.xml + index.fv
          -->
        <map:when test="{project:content.xdocs}{1}.fv">
          <map:generate src="{project:content.xdocs}{1}.fv"/>
        </map:when>

Now after this match we need to add the directory default view. How can
I determine the dir part (substring-before the last '/') in that match.
Has somebody an idea?

> > With per directory config we need three files for each directory - good.
> 
> And of course, Forrest should always fall back to a default
> configuration should these files be not present. IMHO, per file
> configuration should be made possible (I'm sure there are some use
> cases where this is required), but not mandated; and a per directory
> configuration should be preferred; while the default stays how it is
> now (or something close)


Yes, the default.fv from the view-skin is the ultimate fallback always.
The processing should become:
1) page-specific
2) dir-specific
3) project-default
4) view-skin-default

Views *are* and *should be* fully functional even if the user do not add
any config files. If (s)he provide them they will change the default
behavior. 

salu2
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


Re: Properties for views (Re: logic filters in views)

Posted by Diwaker Gupta <di...@gmail.com>.
> Without per directory we need three files for every page - bad.

I agree. If Forrest requires me to create 3 files for each page, I'm
going to be concerned.

> With per directory config we need three files for each directory - good.

And of course, Forrest should always fall back to a default
configuration should these files be not present. IMHO, per file
configuration should be made possible (I'm sure there are some use
cases where this is required), but not mandated; and a per directory
configuration should be preferred; while the default stays how it is
now (or something close)
-- 
Diwaker Gupta
http://resolute.ucsd.edu/diwaker

Properties for views (Re: logic filters in views)

Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
> On Mon, 2005-06-27 at 16:00 +0100, Ross Gardler wrote:
> 
>>Thorsten Scherler wrote:

...

>>>The *.prop would contain the view specific extra content dispatcher
>>>(nuggets) that are now stored in the view. 
>>
>>Sorry, I'm not familiar enough with views terminology yet. Can you give 
>>me this in English, or even with a code example?
>>
> 
> 
> Actually our favorite example: ;-)
> <forrest:contract name="feeder">
>     <forrest:properties contract="feeder">
>       <forrest:property name="feeder" nugget="get.nugget.feeder">
>         <url>/feeds/somefeed.xml</url>
>       </forrest:property>
>     </forrest:properties>
> </forrest:contract>

I thought that was what you meant, I'm not sure I agree. Lets explore...

> The forrest:properties should go in a file for their own. that would
> make: 
> in *.fv:
> <forrest:contract name="feeder"/>

Well this is cleaner, I like that. What I am uncomfortable with is the 
creation of yet another file we need to edit in order to get the page to 
look the way we want it. Admittedly it is unlikely that we will need to 
create all three files for many pages. This brings me back again to the 
per directory config (see below)

> and in *.prop.xml:
> <forrest:properties contract="feeder">
>  <forrest:property name="feeder" nugget="get.nugget.feeder">
>    <url>/feeds/somefeed.xml</url>
>  </forrest:property>
> </forrest:properties>

[ASIDE] I think we need to create a more generic contract instead of 
this feeder one, it looks exactly the same and behaves exactly the same, 
but it is called "embed" or something like that. This can be used to 
embed any content within a view based page - this gives us a portal.

> Actually here you see that it is a kind of skinconf, but especially for
> the one file. That is the reason why we need to harmonize the
> skinconf/forrest:properties. Where I see the skinconf as
> default.prop.xml. ;-)

This is also why we need the per directory configs. Imagine a site with, 
for example, a number of subsections, lets say Human Resources, Product 
News and Market Analysis. The RSS feed for each section will be 
different, but it will not be different for each page within each section.

Without per directory we need three files for every page - bad.

With per directory config we need three files for each directory - good.

Of course, you said you think you can make this work. I'm now saying I 
think we *have* to make this work, unless...

> Another thing that I noticed that each contract/properties should be
> linked via unique id, to better reuse dynamic contracts in the view. 

Does this impace my concern abouve?

Ross

Re: logic filters in views (was Re: Roadmap)

Posted by Thorsten Scherler <th...@apache.org>.
On Mon, 2005-06-27 at 16:00 +0100, Ross Gardler wrote:
> Thorsten Scherler wrote:

> > Seriously, coming back to metadata: 
> > I recommend to split the forrest:properties from the view. Ross was
> > never really comfortable with their existence in the view and I agreed
> > saying they are right now a later entry point into the processing
> > pipeline (that I have in mind). 
> > 
> > I agree on an earlier mail from nicola (about metadata) and suggest:
> > index.fv
> > index.prop
> > index.meta
> > index.xml
> > 
> > or:
> > index.fv.xml
> > index.prop.xml
> > index.meta.xml
> > index.xml
> 
> Just to confirm, these are optional right? We have default files:
> 
> default.fv
> default.prop
> default.meta
> 
> and the above override the per file versions above.
> 

yes that is right.

> It would be great to have per directory defaults too that could override 
> the defaults, but be overridden by the files above.
> 

I will think about something to make this possible. ;-)

> 
> > Actually I am unsure which one is better because one invents fancy (e.g.
> > *.meta) extensions, the other is reserving this extensions in the naming
> > (*.meta.xml). 
> 
> I'd go for *.meta.xml my reasoning is that we will also provide things 
> like *.source.xml and other such patterns. With the locationmap it is 
> not a problem that you are reserving extension, they can be changed on a 
> per site basis if necessary.
> 

Yeah, good point. I agree.

> > The *.prop would contain the view specific extra content dispatcher
> > (nuggets) that are now stored in the view. 
> 
> Sorry, I'm not familiar enough with views terminology yet. Can you give 
> me this in English, or even with a code example?
> 

Actually our favorite example: ;-)
<forrest:contract name="feeder">
    <forrest:properties contract="feeder">
      <forrest:property name="feeder" nugget="get.nugget.feeder">
        <url>/feeds/somefeed.xml</url>
      </forrest:property>
    </forrest:properties>
</forrest:contract>

The forrest:properties should go in a file for their own. that would
make: 
in *.fv:
<forrest:contract name="feeder"/>
    
and in *.prop.xml:
<forrest:properties contract="feeder">
 <forrest:property name="feeder" nugget="get.nugget.feeder">
   <url>/feeds/somefeed.xml</url>
 </forrest:property>
</forrest:properties>

Actually here you see that it is a kind of skinconf, but especially for
the one file. That is the reason why we need to harmonize the
skinconf/forrest:properties. Where I see the skinconf as
default.prop.xml. ;-)

Another thing that I noticed that each contract/properties should be
linked via unique id, to better reuse dynamic contracts in the view. 

> > What is now missing is the logic:views part, because IMO that part has
> > to stay in the view. The logic:view part is for the designer like the
> > whole view. logic:view is handling *only* presentation logic to the
> > view. 
> 
> Good point.
> 
> Ross


salu2
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


Re: logic filters in views (was Re: Roadmap)

Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
> On Thu, 2005-06-23 at 20:54 +0100, Ross Gardler wrote:
> 
>>Tim Williams wrote:
>>
>>>On 6/23/05, Diwaker Gupta <di...@gmail.com> wrote:
>>>
>>>
>>>>Now that the release is just around the corner (since the website is
>>>>already updated, I guess we're just waiting for the announcement,
>>>>perhaps we should jot down a priority list of new features for 0.8.
>>>>
>>>>Personally, I'd like to see the following happening:
>>>>...
> 
> 
>>>I'd add...
>>>o Metadata -- I'd personally like to see support for inline dublin
>>>core "meta" tags, custom metadata, and external [RDF-based] metacards.
>>
>>This is a definite need, I'm not sure it will make into 0.8 though. If 
>>someone is available to implement it for 0.8 then it goes in. I can 
>>imagine myself looking into this for 0.9 if it hasn't already been done.
> 
> 
> ...
> 
>>>o Perspectives/Logic:Views as described
>>>http://marc.theaimsgroup.com/?l=forrest-dev&m=111942914210799&w=2\
>>
>>I think we need more discussion on a design for this. I'd be more 
>>comfortable if this kind of information was in the document metadata 
>>rather than in the view. +1 to the concept though, just not sure how and 
>>when. It should certainly be in the issue tracker.
> 
> 
> lol
> 
> I reckon the whole design of views needs discussion (I will never stop
> on saying this). ;-)
> 
> Seriously, coming back to metadata: 
> I recommend to split the forrest:properties from the view. Ross was
> never really comfortable with their existence in the view and I agreed
> saying they are right now a later entry point into the processing
> pipeline (that I have in mind). 
> 
> I agree on an earlier mail from nicola (about metadata) and suggest:
> index.fv
> index.prop
> index.meta
> index.xml
> 
> or:
> index.fv.xml
> index.prop.xml
> index.meta.xml
> index.xml

Just to confirm, these are optional right? We have default files:

default.fv
default.prop
default.meta

and the above override the per file versions above.

It would be great to have per directory defaults too that could override 
the defaults, but be overridden by the files above.


> Actually I am unsure which one is better because one invents fancy (e.g.
> *.meta) extensions, the other is reserving this extensions in the naming
> (*.meta.xml). 

I'd go for *.meta.xml my reasoning is that we will also provide things 
like *.source.xml and other such patterns. With the locationmap it is 
not a problem that you are reserving extension, they can be changed on a 
per site basis if necessary.

> The *.prop would contain the view specific extra content dispatcher
> (nuggets) that are now stored in the view. 

Sorry, I'm not familiar enough with views terminology yet. Can you give 
me this in English, or even with a code example?

> What is now missing is the logic:views part, because IMO that part has
> to stay in the view. The logic:view part is for the designer like the
> whole view. logic:view is handling *only* presentation logic to the
> view. 

Good point.

Ross

logic filters in views (was Re: Roadmap)

Posted by Thorsten Scherler <th...@apache.org>.
On Thu, 2005-06-23 at 20:54 +0100, Ross Gardler wrote:
> Tim Williams wrote:
> > On 6/23/05, Diwaker Gupta <di...@gmail.com> wrote:
> > 
> >>Now that the release is just around the corner (since the website is
> >>already updated, I guess we're just waiting for the announcement,
> >>perhaps we should jot down a priority list of new features for 0.8.
> >>
> >>Personally, I'd like to see the following happening:
> >>...

> > I'd add...
> > o Metadata -- I'd personally like to see support for inline dublin
> > core "meta" tags, custom metadata, and external [RDF-based] metacards.
> 
> This is a definite need, I'm not sure it will make into 0.8 though. If 
> someone is available to implement it for 0.8 then it goes in. I can 
> imagine myself looking into this for 0.9 if it hasn't already been done.

...
> 
> > o Perspectives/Logic:Views as described
> > http://marc.theaimsgroup.com/?l=forrest-dev&m=111942914210799&w=2\
> 
> I think we need more discussion on a design for this. I'd be more 
> comfortable if this kind of information was in the document metadata 
> rather than in the view. +1 to the concept though, just not sure how and 
> when. It should certainly be in the issue tracker.

lol

I reckon the whole design of views needs discussion (I will never stop
on saying this). ;-)

Seriously, coming back to metadata: 
I recommend to split the forrest:properties from the view. Ross was
never really comfortable with their existence in the view and I agreed
saying they are right now a later entry point into the processing
pipeline (that I have in mind). 

I agree on an earlier mail from nicola (about metadata) and suggest:
index.fv
index.prop
index.meta
index.xml

or:
index.fv.xml
index.prop.xml
index.meta.xml
index.xml

Actually I am unsure which one is better because one invents fancy (e.g.
*.meta) extensions, the other is reserving this extensions in the naming
(*.meta.xml). 

The *.prop would contain the view specific extra content dispatcher
(nuggets) that are now stored in the view. 

What is now missing is the logic:views part, because IMO that part has
to stay in the view. The logic:view part is for the designer like the
whole view. logic:view is handling *only* presentation logic to the
view. 

Now one can argue that an earlier stage of forrest should do that but I
do not see this. I see that designer need to create designs that are
dependent on simple conditions to add (or not) contracts (and/or hooks)
to the view.

Views are following the dispatcher-view pattern which means that the
view dispatches all nuggets (business helper) and contracts (view
helper). logic:view is a filter which determines what to dispatch.

How to activate this logic in the view I agree that need discussion. ;-)

salu2
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


Re: Roadmap

Posted by Ross Gardler <rg...@apache.org>.
Tim Williams wrote:
> On 6/23/05, Diwaker Gupta <di...@gmail.com> wrote:
> 
>>Now that the release is just around the corner (since the website is
>>already updated, I guess we're just waiting for the announcement,
>>perhaps we should jot down a priority list of new features for 0.8.
>>
>>Personally, I'd like to see the following happening:
>>
>>o views -- polished, with atleast 2 supplied skins and a cleaned up
>>plugin structure (or going into the core, I'm not sure whats the plan)
>>
>>o Support for Google sitemap -- since this is a Google proposal, I'm
>>pretty sure that sites using Google sitemaps will get more visibility
>>than those not using it. So in general it would be a good idea. And
>>with Forrest, it should be pretty easy to generate the sitemap in
>>whatever format we want
>>
>>o XHTML2 -- the Forrest team should make sure that this transition is
>>as smooth as possible. So for instance, supply a simple script that
>>will convert existing document-v20 to XHTML2 automagically :)
>>
>>o So far the focus has been on improving the HTML output (since thats
>>the most visible). I know there has been some work into customizing
>>the PDF output, but I think both the PDF and Text output formats need
>>a bit more work to bring them upto speed.
> 
> 
> I'd add...
> o Metadata -- I'd personally like to see support for inline dublin
> core "meta" tags, custom metadata, and external [RDF-based] metacards.

This is a definite need, I'm not sure it will make into 0.8 though. If 
someone is available to implement it for 0.8 then it goes in. I can 
imagine myself looking into this for 0.9 if it hasn't already been done.

> o Locationmaps -- I guess this goes without saying...

+1

> o Perspectives/Logic:Views as described
> http://marc.theaimsgroup.com/?l=forrest-dev&m=111942914210799&w=2\

I think we need more discussion on a design for this. I'd be more 
comfortable if this kind of information was in the document metadata 
rather than in the view. +1 to the concept though, just not sure how and 
when. It should certainly be in the issue tracker.

Ross

Re: Roadmap

Posted by Tim Williams <wi...@gmail.com>.
On 6/23/05, Diwaker Gupta <di...@gmail.com> wrote:
> Now that the release is just around the corner (since the website is
> already updated, I guess we're just waiting for the announcement,
> perhaps we should jot down a priority list of new features for 0.8.
> 
> Personally, I'd like to see the following happening:
> 
> o views -- polished, with atleast 2 supplied skins and a cleaned up
> plugin structure (or going into the core, I'm not sure whats the plan)
> 
> o Support for Google sitemap -- since this is a Google proposal, I'm
> pretty sure that sites using Google sitemaps will get more visibility
> than those not using it. So in general it would be a good idea. And
> with Forrest, it should be pretty easy to generate the sitemap in
> whatever format we want
> 
> o XHTML2 -- the Forrest team should make sure that this transition is
> as smooth as possible. So for instance, supply a simple script that
> will convert existing document-v20 to XHTML2 automagically :)
> 
> o So far the focus has been on improving the HTML output (since thats
> the most visible). I know there has been some work into customizing
> the PDF output, but I think both the PDF and Text output formats need
> a bit more work to bring them upto speed.

I'd add...
o Metadata -- I'd personally like to see support for inline dublin
core "meta" tags, custom metadata, and external [RDF-based] metacards.

o Locationmaps -- I guess this goes without saying...

o Perspectives/Logic:Views as described
http://marc.theaimsgroup.com/?l=forrest-dev&m=111942914210799&w=2\

--tim

Re: Roadmap

Posted by Ross Gardler <rg...@apache.org>.
Diwaker Gupta wrote:
> Now that the release is just around the corner (since the website is
> already updated, I guess we're just waiting for the announcement,
> perhaps we should jot down a priority list of new features for 0.8.

Good idea. We use the issue tracker to manage our roadmap, so can 
someone please add these (once agreed) to the issue tracker (the XHTML2 
one is already there) and schedule them for 0.8.

> Personally, I'd like to see the following happening:
> 
> o views -- polished, with atleast 2 supplied skins and a cleaned up
> plugin structure (or going into the core, I'm not sure whats the plan)

+1

> o Support for Google sitemap -- since this is a Google proposal, I'm
> pretty sure that sites using Google sitemaps will get more visibility
> than those not using it. So in general it would be a good idea. And
> with Forrest, it should be pretty easy to generate the sitemap in
> whatever format we want

+1 (see http://marc.theaimsgroup.com/?t=111787145800002&r=1&w=2 )

> o XHTML2 -- the Forrest team should make sure that this transition is
> as smooth as possible. So for instance, supply a simple script that
> will convert existing document-v20 to XHTML2 automagically :)

I assume you mean the subset of XHTML2 as our internal format. +1 for that.

Note we don't need a script to do the conversions, we would just move 
support for XDocs into a plugin which has the necessary XSLT's

> o So far the focus has been on improving the HTML output (since thats
> the most visible). I know there has been some work into customizing
> the PDF output, but I think both the PDF and Text output formats need
> a bit more work to bring them upto speed.

These are both plugins so would not be on the Forrest roadmap. They now 
have an independent release cycle.

Having said that the PDF is generated from the FO which is currently 
part of the skins so this goes into views.

Ross