You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Vik Tara <vi...@propco.co.uk> on 2009/07/03 12:53:36 UTC
Re: Blog Module
Hi All,
Have spent a bit more time looking at roller - it's very good!!
In my view a lenya integration would have to accommodate:
1. Authentication
Roller uses acegi for security. I have read some posts on the cocoon
mailing list that suggest a method for getting acegi working with cocoon.
Does anyone have any experience with this?
Essentially I am suggesting we would need to produce an additional
module that allows lenya users to authenticate using acegi.
2. Viewing / Editing / Publishing
It would make sense to add additional screens to the CMS area that allow
for these features.
I have taken a look at abdera and it looks promising. By creating a few
actions we can publish content to roller using ATOM.
Suggestions for the logic / flow of these screens would be helpful!
3. Styling
Roller uses it's own theme/template mechanism - so we would need to
think of how the module could create a template based on the users lenya
styling.
All comments appreciated!
Regards
Vik
Vik Tara wrote:
> Andreas Hartmann wrote:
>> Andreas Hartmann schrieb:
>>> Vik Tara schrieb:
>>>> I am planning to take a look at apache roller today - I have a
>>>> requirement to get a blog together for our own company website.
>>>>
>>>> In order to consider integration with Lenya could everyone put their
>>>> thoughts forward on this?
>> […]
>>
>>> Deep: Use Lenya as a facade
>>> ===========================
>>>
>>> * Access Roller as a web service (read+write)?
>> BTW, Apache Abdera (AtomPub implementation) contains a client library
>> which could be used on the Lenya side to connect to Roller (or any other
>> AtomPub-compliant blog system):
>>
>> http://abdera.apache.org/docs/api/org/apache/abdera/protocol/client/package-frame.html
>
> Yeah - I came across that - I would like to head in that direction I think.
>
> This would be a good test of what we discussed - integrating another
> apache project rather than competing with it and also benefiting from
> association with other projects.
>
>>
>> -- Andreas
>>
>>
>>> * Map Lenya users to Roller users? Single sign-on?
>>> * Use Lenya GUI to write entries + comments
>>>
>>>
>>> I could imagine that the first option is more efficient to get
>>> started. WDOT?
>>>
>>> -- Andreas
>>>
>>>
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Blog Module
Posted by Andreas Hartmann <an...@apache.org>.
Hi Vik,
Vik Tara schrieb:
>> On Fri, 03 Jul 2009 11:53:36 +0100, Vik Tara <vi...@propco.co.uk> wrote:
>> [[...]]
>>> 2. Viewing / Editing / Publishing
>>>
>>> It would make sense to add additional screens to the CMS area that allow
>>> for these features.
>>>
>>> I have taken a look at abdera and it looks promising. By creating a few
>>> actions we can publish content to roller using ATOM.
>>>
>>> Suggestions for the logic / flow of these screens would be helpful!
>> How do you imagine the end user usecase ? :
>>
>> - Post is editing in Lenya
>> - validation put post's content in Roller (but user don't see anything
>> about that)
>> - post reading is done via Lenya
>>
>> In fact, for user, blog posting on roller is like posting on Lenya, nothing
>> show him that's on roller. That is ?
>
> Yes - we would only need to show the user the actual blog post from
> roller. My view was that the lenya module would install roller in
> somewhere in the publications file system and access it from there if we
> needed to display pages.
would it be easy to accomplish this? Otherwise I'd just let the user
install Roller and just configure the URI in the Lenya application (see
my other mail for some thoughts).
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Blog Module
Posted by Vik Tara <vi...@propco.co.uk>.
Hi Florent,
Florent André wrote:
> Hi, thanks for this mail,
>
> I have some questions / comment :
>
> On Fri, 03 Jul 2009 11:53:36 +0100, Vik Tara <vi...@propco.co.uk> wrote:
>> Hi All,
>>
> [[...]]
>> 2. Viewing / Editing / Publishing
>>
>> It would make sense to add additional screens to the CMS area that allow
>> for these features.
>>
>> I have taken a look at abdera and it looks promising. By creating a few
>> actions we can publish content to roller using ATOM.
>>
>> Suggestions for the logic / flow of these screens would be helpful!
>
> How do you imagine the end user usecase ? :
>
> - Post is editing in Lenya
> - validation put post's content in Roller (but user don't see anything
> about that)
> - post reading is done via Lenya
>
> In fact, for user, blog posting on roller is like posting on Lenya, nothing
> show him that's on roller. That is ?
Yes - we would only need to show the user the actual blog post from
roller. My view was that the lenya module would install roller in
somewhere in the publications file system and access it from there if we
needed to display pages.
>
> And how is the process for people who post comment ?
They would post the comment directly on to the blog page - which would
be handled by roller.
>
>> 3. Styling
>>
>> Roller uses it's own theme/template mechanism - so we would need to
>> think of how the module could create a template based on the users lenya
>> styling.
>
> Can you send a pointer where the Roller template mechanism is explain ? (if
> you have that in your bag)
Here you go:
http://mirror.public-internet.co.uk/ftp/apache/roller/roller-4/v4.0.1/docs/roller-template-guide.pdf
>
> 4. Content repository
>
> How Roller stock the content ? Like Lenya (uuid, visioning, ...) or on
> another way ?
I have not figured that bit yet! It does need a database however (Apache
Derby?)
Does anyone have any reservations about the module having to install a
database?
>
> Do you think it will be possible to transform blog post into Lenya document
> or publish a Lenya document into blog's post ?
For sure - I think that's how this will all work.
You create content in lenya, through a pipeline we post it to roller
using actions / abdera client.
Keep the comments coming!
Vik
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Blog Module
Posted by Florent André <fl...@4sengines.com>.
Hi, thanks for this mail,
I have some questions / comment :
On Fri, 03 Jul 2009 11:53:36 +0100, Vik Tara <vi...@propco.co.uk> wrote:
> Hi All,
>
[[...]]
>
> 2. Viewing / Editing / Publishing
>
> It would make sense to add additional screens to the CMS area that allow
> for these features.
>
> I have taken a look at abdera and it looks promising. By creating a few
> actions we can publish content to roller using ATOM.
>
> Suggestions for the logic / flow of these screens would be helpful!
How do you imagine the end user usecase ? :
- Post is editing in Lenya
- validation put post's content in Roller (but user don't see anything
about that)
- post reading is done via Lenya
In fact, for user, blog posting on roller is like posting on Lenya, nothing
show him that's on roller. That is ?
And how is the process for people who post comment ?
>
> 3. Styling
>
> Roller uses it's own theme/template mechanism - so we would need to
> think of how the module could create a template based on the users lenya
> styling.
Can you send a pointer where the Roller template mechanism is explain ? (if
you have that in your bag)
4. Content repository
How Roller stock the content ? Like Lenya (uuid, visioning, ...) or on
another way ?
Do you think it will be possible to transform blog post into Lenya document
or publish a Lenya document into blog's post ?
Looking forward to see this cool module !
>
> All comments appreciated!
>
>
> Regards
>
>
>
> Vik
>
> Vik Tara wrote:
>> Andreas Hartmann wrote:
>>> Andreas Hartmann schrieb:
>>>> Vik Tara schrieb:
>>>>> I am planning to take a look at apache roller today - I have a
>>>>> requirement to get a blog together for our own company website.
>>>>>
>>>>> In order to consider integration with Lenya could everyone put their
>>>>> thoughts forward on this?
>>> […]
>>>
>>>> Deep: Use Lenya as a facade
>>>> ===========================
>>>>
>>>> * Access Roller as a web service (read+write)?
>>> BTW, Apache Abdera (AtomPub implementation) contains a client library
>>> which could be used on the Lenya side to connect to Roller (or any
other
>>> AtomPub-compliant blog system):
>>>
>>>
http://abdera.apache.org/docs/api/org/apache/abdera/protocol/client/package-frame.html
>>
>> Yeah - I came across that - I would like to head in that direction I
>> think.
>>
>> This would be a good test of what we discussed - integrating another
>> apache project rather than competing with it and also benefiting from
>> association with other projects.
>>
>>>
>>> -- Andreas
>>>
>>>
>>>> * Map Lenya users to Roller users? Single sign-on?
>>>> * Use Lenya GUI to write entries + comments
>>>>
>>>>
>>>> I could imagine that the first option is more efficient to get
>>>> started. WDOT?
>>>>
>>>> -- Andreas
>>>>
>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: dev-help@lenya.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Blog Module
Posted by Jann Forrer <ja...@id.uzh.ch>.
Hi Vik
> Have spent a bit more time looking at roller - it's very good!!
>
> In my view a lenya integration would have to accommodate:
>
> 1. Authentication
>
> Roller uses acegi for security. I have read some posts on the cocoon
> mailing list that suggest a method for getting acegi working with cocoon.
>
> Does anyone have any experience with this?
>
>
Not really but I did look at it during the work on the shibboleth
implementation. It looked very promising to me!
However to integrate it into lenya is probably not that easy.
BTW acegi security project is becoming Spring Security. See:
http://www.acegisecurity.org/
> Essentially I am suggesting we would need to produce an additional
> module that allows lenya users to authenticate using acegi.
>
>
That would be really nice!
> 2. Viewing / Editing / Publishing
>
> It would make sense to add additional screens to the CMS area that allow
> for these features.
>
> I have taken a look at abdera and it looks promising. By creating a few
> actions we can publish content to roller using ATOM.
>
> Suggestions for the logic / flow of these screens would be helpful!
>
> 3. Styling
>
> Roller uses it's own theme/template mechanism - so we would need to
> think of how the module could create a template based on the users lenya
> styling.
>
> All comments appreciated!
>
>
Jann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Blog Module
Posted by Vik Tara <vi...@propco.co.uk>.
Hi Andreas,
Andreas Hartmann wrote:
> Andreas Hartmann schrieb:
>> Hi Vik,
>>
>> Vik Tara schrieb:
>>> Have spent a bit more time looking at roller - it's very good!!
>>>
>>> In my view a lenya integration would have to accommodate:
>>
>> […]
>>
>>> 3. Styling
>>>
>>> Roller uses it's own theme/template mechanism - so we would need to
>>> think of how the module could create a template based on the users lenya
>>> styling.
>>
>> … or we just pull the RSS/Atom and feed it into a pipeline. The
>> pipeline + XSLT would be reusable for other feeds.
Your on the button as usual - that's a much neater solution than mine -
i'll go with your idea!
>>
>>
>> BTW, would it make sense to allow "mounting" a module at a particular
>> URL? E.g.
>>
>> /mypub/authoring/blog/** -> /modules/roller/{1}
>>
>> Of course that can be done in the publication sitemap, but maybe we
>> can provide a more generic mechanism?
+1
>>
>>
>> In this context: How do we tell the roller module which Roller
>> application it shall access? Maybe we could use some kind of generic
>> "module configuration document" which is used to mount a module at a
>> particular URL:
>
> I guess this wasn't entirely clear: The "module configuation document"
> would be a document in the Lenya content repository. It could be edited
> using the source editor, Firedocs etc.
>
> -- Andreas
>
>
>>
>> /mypub/authoring/blog.xml
>>
>> <?xml version="1.0"?>
>> <module id="org.apache.lenya.modules.roller">
>> <param name="blogUri" value="http://localhost:8080/roller/myblog"/>
>> </module>
>>
>>
>> In the easiest case, this could generate an Include statement:
>>
>> <i:include src="cocoon://modules/roller/?blogUri=…"/>
>>
>> To support multiple-page apps, we could maybe generate Include
>> statements for "virtual" child documents (which don't exist in the
>> site structure), using the same params as the module base document:
>>
>> <i:include src="cocoon://modules/roller/post123.html?blogUri=…"/>
>>
>>
I was thinking of this slightly differently - ie the module would
install roller as part of the build (using ANT) - so the module would be
'aware' of the install.
I see how that could be problematic however - I think your solution
proposes that we hook to an already installed roller?
>> Just some random thoughts …
>>
>> -- Andreas
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Blog Module
Posted by Andreas Hartmann <an...@apache.org>.
Andreas Hartmann schrieb:
> Hi Vik,
>
> Vik Tara schrieb:
>> Have spent a bit more time looking at roller - it's very good!!
>>
>> In my view a lenya integration would have to accommodate:
>
> […]
>
>> 3. Styling
>>
>> Roller uses it's own theme/template mechanism - so we would need to
>> think of how the module could create a template based on the users lenya
>> styling.
>
> … or we just pull the RSS/Atom and feed it into a pipeline. The pipeline
> + XSLT would be reusable for other feeds.
>
>
> BTW, would it make sense to allow "mounting" a module at a particular
> URL? E.g.
>
> /mypub/authoring/blog/** -> /modules/roller/{1}
>
> Of course that can be done in the publication sitemap, but maybe we can
> provide a more generic mechanism?
>
>
> In this context: How do we tell the roller module which Roller
> application it shall access? Maybe we could use some kind of generic
> "module configuration document" which is used to mount a module at a
> particular URL:
I guess this wasn't entirely clear: The "module configuation document"
would be a document in the Lenya content repository. It could be edited
using the source editor, Firedocs etc.
-- Andreas
>
> /mypub/authoring/blog.xml
>
> <?xml version="1.0"?>
> <module id="org.apache.lenya.modules.roller">
> <param name="blogUri" value="http://localhost:8080/roller/myblog"/>
> </module>
>
>
> In the easiest case, this could generate an Include statement:
>
> <i:include src="cocoon://modules/roller/?blogUri=…"/>
>
> To support multiple-page apps, we could maybe generate Include
> statements for "virtual" child documents (which don't exist in the site
> structure), using the same params as the module base document:
>
> <i:include src="cocoon://modules/roller/post123.html?blogUri=…"/>
>
>
> Just some random thoughts …
>
> -- Andreas
>
>
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Blog Module
Posted by Andreas Hartmann <an...@apache.org>.
Hi Vik,
Vik Tara schrieb:
> Have spent a bit more time looking at roller - it's very good!!
>
> In my view a lenya integration would have to accommodate:
[…]
> 3. Styling
>
> Roller uses it's own theme/template mechanism - so we would need to
> think of how the module could create a template based on the users lenya
> styling.
… or we just pull the RSS/Atom and feed it into a pipeline. The pipeline
+ XSLT would be reusable for other feeds.
BTW, would it make sense to allow "mounting" a module at a particular
URL? E.g.
/mypub/authoring/blog/** -> /modules/roller/{1}
Of course that can be done in the publication sitemap, but maybe we can
provide a more generic mechanism?
In this context: How do we tell the roller module which Roller
application it shall access? Maybe we could use some kind of generic
"module configuration document" which is used to mount a module at a
particular URL:
/mypub/authoring/blog.xml
<?xml version="1.0"?>
<module id="org.apache.lenya.modules.roller">
<param name="blogUri" value="http://localhost:8080/roller/myblog"/>
</module>
In the easiest case, this could generate an Include statement:
<i:include src="cocoon://modules/roller/?blogUri=…"/>
To support multiple-page apps, we could maybe generate Include
statements for "virtual" child documents (which don't exist in the site
structure), using the same params as the module base document:
<i:include src="cocoon://modules/roller/post123.html?blogUri=…"/>
Just some random thoughts …
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org