Re: [Hypercontent-users] to_hypercontent_project

[Alex V. <av...@co...>]

On Aug 16, 2004, at 12:04 PM, Ingmars Rubenis wrote:

> Hello!
>
> We have some questions about hypercontent.
> 1)Is it possible to build and publish the data not at this moment, but
> after a view days and or hours? For example not to push build, but
> choose after
> how many days to build and publish the result of xml and xsl
> transformation. Where can we find the lines to change or may be You
> can help to do it?

Scheduled building and publishing is a planned feature for a future 
release of HyperContent, but is not currently possible. If you are 
curious how building and publishing is achieved at the code level, look 
at the command classes BuildNode and PublishNode. This should give you 
an idea of the data elements that would need to be persisted in order 
to store a build or publish command for future execution.

>
> 2) How we can join to Hypercontent CVS. We have some ideas to
> contribute specially to PHP. We would like try to integrate some
> windows (textarea block) for adding php dynamic part and may be jsp.
> What do You think?
>
> 3) Also we are intersted to help to develop Hypercontent 2.0 version.

You can access the CVS from the hypercontent web site.  I think PHP or 
JSP support is a very good idea, and would make a lot of sense in the 
HyperContent 2.0 architecture, as it will act as a standalone web 
server.  If you would like to contribute, you should begin by reviewing 
the design document for HyperContent 2.0 (attached). This lays out the 
basic priorities established for version 2.0, and you can provide 
feedback or suggestions.  From there, if you are interested in 
developing components, for example to support PHP, we can discuss how 
that can best be plugged into the 2.0 architecture on the developer's 
list, and you can submit code on the developer's list as well.  You can 
get CVS commit access once you become regular contributors.

The development code base for HyperContent 2.0 is not yet in the 
SourceForge CVS, but will be in the near future once some housekeeping 
is complete.  Once it is, I can help you understand the appropriate 
APIs to use to plug in functionality.

Alex