hypercontent-developer

[Hypercontent-developer] Semi-formalized JA-SIG News and Announcement Policy

[Jim H. <jim...@do...>]

The JA-SIG Board of Directors has had inquiries from organizations
interested in posting news items related to JA-SIG and its projects. We
felt it was an appropriate time to produce a written policy statement to
make it clear to organizations that we welcome relevant announcements.
We also thought it was important to given them information on how to go
about submitting announcements.

The resulting policy and process is documented at the following location:
http://www.ja-sig.org/wiki/display/JSG/JA-SIG+News+and+Announcement+Policy

We will be adding links to this document in a number of relevant places
and sending a note out to jasig-announce but I first wanted to give the 
developers a "heads up." Our goal is to have this expedite the process 
of posting news, not impede it.

Let me know if you have any questions or concerns.

Thanks,
JimH

[Hypercontent-developer] HyperContent 2.0 now available

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

HyperContent 2.0 is now available for download from the HyperContent 
home page at

http://hypercontent.sourceforge.net

This release fixes 6 small bugs from the Release Candidate, and 
includes a new user activity report screen to make it easy to keep tabs 
on who's using the system.  Based on the stability and wide use of the 
system at Columbia, we are dropping all release modifiers and calling 
this simply "2.0" - yes, it is final.  Subsequent bug fixes and minor 
feature enhancements will be packaged as sub-releases, e.g. 2.0.1.

Along with the release, you'll notice three new links from the 
HyperContent home page that should be of great interest to the 
community

Help Site for 2.0
	- a new web site for HC2-specific documentation.  Still incomplete, 
but will be receiving much attention over the next couple of months.

Community Wiki
	- this is a place we can swap web site archives, to facilitate the 
sharing of web site implementation techniques, and share code add-ons 
like authentication modules.  Hosted on the JA-SIG Confluence server.

Bug and Issue Tracker
	- this has moved to the JA-SIG Jira server, and will be the new system 
of record for bug and issue tracking.  Got a bug?  Report it here!

-Alex

[Hypercontent-developer] HyperContent 2.0 Release Candidate now available

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

Hello all,	
	You can find a link for the new HyperContent 2.0 Release Candidate 
distribution from the HyperContent home page at

http://hypercontent.sourceforge.net

This release candidate contains a lot of bug fixes and enhancements 
driven by our first few weeks of production use here at Columbia.  We 
currently have about a dozen users using the system daily, and are 
training more every week.  Notable additions since the last beta 
release include image watermarking support, simpler filesystem 
configuration, highlighted search results and two new sample projects.  
For the full list of changes, visit

http://sourceforge.net/project/shownotes.php?release_id=367743

Cheers,
	Alex

[Hypercontent-developer] HyperContent 2.0b4 now available

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

Hello all,
	I have just posted a link to the fourth beta release of HC2 on the 
HyperContent home page.  This release contains a number of bug fixes 
based on our initial production migrations at Columbia, and adds 
support for recursive navigation/site-map generation for doctypes with 
** patterns.  But most importantly, it adds hooks for integration with 
CAS and uPortal.
	For CAS, a new class is required that actually goes with the CAS 
client; it provides a JAAS LoginModule implementation that sits on top 
of the existing CAS java client.  It may be a while before this class 
shows up in an official CAS client release, but if anyone is interested 
in getting this enabled, let me know and I can email the source.  
Andrew Petro has volunteered to post the source on the CAS wiki as 
well.  I will send detailed instructions to the list on how to 
integrate with CAS to the first person who asks ;-)
	For uPortal, a simple web-proxyable channel has been added that gives 
a user a list of their authorized projects; this looks just like the 
initial screen of HC 1.4, but the links open HC2 in a separate window.  
This dashboard can be reached at any valid URL on the HC2 server by 
adding the parameter "mode=dashboard-portlet" (e.g. 
"https://hypercontent.columbia.edu/index.html?mode=dashboard-portlet"). 
  With CAS and the CASConnectionContext in uPortal, you can achieve 
single sign-on between the portal, the proxied dashboard channel, and 
the direct HC2 session, for a seamless user experience.

	I will be on vacation the first two weeks of August, and while I will 
make some effort to catch up with email every couple of days, I won't 
be doing any development work.  The only remaining "must-haves" for a 
final release are search-reindexing and lock-clearing scripts, which 
are of quite limited scope and should be complete shortly after I 
return.  I expect to have a final 2.0 release by the end of August, but 
I would stress that we are running the b4 code in production and have 
already migrated a number of sites, so the system has already endured 
some trial by fire.

Cheers,
	Alex

[Hypercontent-developer] HyperContent 2.0b3 released

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

Hello all,
	I have just added the beta 3 release to the HyperContent home page.  
This release contains fixes for a variety of bugs raised on and off 
this list, and introduces the scheduling component, which offers you 
the ability to define calendar-based, fixed-interval or specific 
date-time schedules for workflow events.  This includes support for 
user-defined schedules; the new schedule script allows you to specify 
the appearance and expiration time for a file, or even for a version of 
a file.  The approvals script now sends out daily reminders for files 
requiring approval, and the publish script in the sample project is set 
up to publish on an hourly basis.  These are just examples to show you 
how it's done; it's expected that you would want to tweak the schedules 
and scripts for your own requirements in real use.
	This is the version we will be using going into our pilot production 
site migration over the next couple of weeks here at Columbia.  I 
encourage everyone who is actively checking out HC2 to upgrade to this 
beta, since some of the bug fixes are potentially critical.  I expect 
to release the final version of 2.0 in the next 2-6 weeks, once we have 
successfully migrated one or two projects in production and worked 
through any critical issues identified by our real users, and by all of 
you.

Cheers,
	Alex

[Hypercontent-developer] HyperContent 2.0 beta pre-announcement

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

Greetings,
	I thank you all for your patience with the HyperContent 2.0 
development of late.  I can assure you that the quiet on this list has 
not indicated a lack of development activity; the workflow engine and 
screens have come together, as have the bulk of the workflow scripts 
that will come with the release.  There is still some work to be done 
to enable localization throughout - all the workflow screens are 
littered with "keys" rather than labels for the moment, and scheduling 
of workflow activities (build, publish, zip ,etc) is not yet available. 
  However, the current code base is quite stable, and performing well.  
I will be working today on the release notes and light documentation to 
support a beta release, which will consist of the current CVS code plus 
a sample project.  I hope to approach final release status within 
another month, but I think this beta will represent a solid foundation 
for those eager to get started with version 2.  Migration of existing 
version 1.4 projects is quite simple, though groups and permissions 
have to be manually re-entered.  The beta will be of sufficient quality 
to develop new sites as well, with some excellent new features for 
developers, including support for ** patterns, improved dependency 
recognition, quick XSL previewing, image processing pipelines and more.

You can expect the beta announcement in the next couple of days.  I 
will be hosting a pre-conference seminar on HyperContent 2 at the 
upcoming JA-SIG conference in Baltimore, for those who would like a 
hands-on tour.  There are indications that the seminar may fill up, so 
register soon!

-Alex

[Hypercontent-developer] JUnit

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

Andrew,
	I'v been pondering your offer to contribute some JUnit testcases, and 
I think perhaps the most logical place to start would be with the 
IFileSystemManager API.  This is the persistence core of HyperContent, 
and it has quite a few implementations already; I think JUnit test 
cases would be helpful here especially because more implementations are 
likely, and because the behavior is fairly loosely defined at the 
moment for implementations that may not support a particular feature.  
For example, some may throw UnsupportedOperationExceptions if they 
don't support search indexing, but may just blindly return true to 
lock() if it is unsupported.  I will work on improving the 
documentation of the API to indicate the expectations that inform the 
current set of implementations; this could then form the basis of some 
test cases.

Let me know what your schedule looks like, when you might be able to 
spend some time on this.  Also, if you'd like developer CVS access just 
let me know your sourceforge ID.

Alex

[Hypercontent-developer] HyperContent 2 development update

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

Hello all,
	I wanted to give a status update on HyperContent 2 development.  The 
current CVS code was distributed as a preview release at the JA-SIG 
conference this last weekend, and the foundation is pretty solid:

- HTTP 1.1 web server with context-mapped projects and pipeline-driven 
content processing, as described in the last update
- Form handling framework for interactive screens (tied into pipelines 
for wiring GUIs to processors)
- Persistence layers on top of the basic filesystem API providing 
transactional characteristics and temp file management
- Persistent user history (recently viewed & saved, unsaved documents)
- DHTML GUI built on pipeline and form handling frameworks
- GUI enables search, edit, view, save and delete functionality, with 
browse by directory structure or browse-in-place using site navigation
- All editing functionality from version 1.4 available in edit modes
- Complete backwards compatibility with 1.x projects

The big missing piece is Workflow; I'll be posting in a few days with 
the candidates for workflow engine libraries after I weed out the 
nonstarters (many require EJB or RDBMS).  Other basic missing functions 
that need to be implemented before a final 2.0 release:

- groups configuration
- copy/move at GUI level (filesystem level is implemented)
- rebuild & optimize search index
- upload/download zip
- localization of velocity templates
- wire in user feedback throughout

Build and publish, as known in 1.x, will be batch activities within the 
new workflow engine, and will be able to be scheduled or set up as 
automatic actions when content is changed.  Manual workflow activities 
will include 'approve for publication' and 'request content update'. 
Please post other workflow scenarios!  My goal is to adopt a workflow 
engine which will allow extensible workflow construction, but I'd like 
to support a good set of basic activities out of the box.

The current estimated release date for 2.0 is March, allowing time for 
remaining development, testing and some documentation.   Andrew Petro 
of Yale has offered to help with development of JUnit tests, which will 
be very helpful in keeping the system stable moving forward.  Any other 
contributions would be most welcome; just reply to the list if you're 
interested in lending a hand with anything I've mentioned here.

Alex

[Hypercontent-developer] HyperContent 2 build script and info

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

Hello all,
	Though I have been somewhat preoccupied with our imminent portal 
rollout at Columbia, the HyperContent bits continue to trickle out . . 
. I have committed a simple ant script and a bare-bones content 
repository to the CVS, so if you checkout the hypercontent2 module you 
can now perform an "ant startup" and visit a simple hello world page at 
"http://localhost:8080/index.html".  While there is no content of 
interest in this project as yet, it provide a sufficient structural 
example for you to take an existing HyperContent 1.x project and port 
it into the HyperContent 2 server.  The porting steps are:

--------------------------

1. Register your project with the bootstrap project.  This is done by 
creating a directory under /repositories/bootstrap/projects, and 
creating a file called "filesystem.xml" within that directory.  This 
file should contain ONLY the repository element from your project 
definition, with one new attribute called "mount".  This indicates the 
mount path of this project on the server.  By default, the HyperContent 
servlet is mapped to the root context, so if you mount your project at 
"/my-project/"  the base url for your project would be 
"http://localhost:8080/my-project/".

2. Create a directory "config" in your project repository.  Put a copy 
of your project definition file at the location 
"/config/project-definition.xml".  The project definition resides 
within the project repository in HyperContent 2, so that the repository 
is self-describing, which will enable easier copying and moving of 
projects.

3. Create a file "/config/permissions.xml" in your project repository.  
For world read access, this will work:

<?xml version="1.0" encoding="UTF-8"?>
<permissions>
	<permission principal="group:anybody" activity="read" target="/"/>
</permissions>

You can also assign permissions to users, who are defined in the 
bootstrap project.  The pattern for adding users is to put them in a 
path like "/repositories/bootstrap/users/u/us/username.xml", where the 
last two directories correspond to the first and first two characters 
of the username.  See the demo user file for an example.  
Authentication is done via JAAS, so you can plug in another 
authentication mechanism.  The user files in the future will be 
primarily intended for storing user preferences.

4.  Run "ant startup", and visit your web site.  Note that directory 
listings and/or automatic index page mapping are not yet implemented, 
so you will have to enter the full  URL of a file.  Your web site 
should behave just as it would if you performed a build under 1.x, but 
now it is served dynamically.  The only catch is that options 
configured in the Build options editor are not currently supported - 
I'd like to get a feel for whether people use these options, as I am 
considering deprecating them.

--------------------------

What is going on under the hood?
	HyperContent 2 is acting as an HTTP 1.1 server; it is able to map 
incoming requests to rendering pipelines based on  your project 
definition; if the pipeline is not a simple pass-through, the rendering 
is cached to disk.  The dates of both the disk cache and the user's 
browser cache are compared with every request against a recursive 
dependency analyzer, so that content is immediately flagged out of date 
when any dependency is modified.  The maximum latency of last mod date 
changes is configureable in the hypercontent.properties file. 
HyperContent 2 also GZIPs content if the browser supports it, and 
caches the GZIP version to disk.  Disk caching is handled by Berkeley 
DB Java edition, which is based on the fast Java NIO in JDK 1.4, and 
which has a configureable memory cache for frequently accessed content. 
  Templates for not-found, not-authorized, auth-required and error 
screens are also provided in the bootstrap project, and can be 
overridden by any other project.
	Pipelines are matched on five components: base-directory (used to 
create virtual directories for presenting alternative forms of output, 
such as text-only), base path (repository path without file extension), 
file extension (used to define the content type of the pipeline 
output), permissions, and "mode", which is a special parameter.  Modes 
are used to define non-cacheable views of data, and are primarily 
intended for interactive components such as authoring tools.  These 
modal views will also NOT be able to be built and published in batch 
processes; they are intended only to come from the HyperContent server 
itself in real-time.
	Authoring tools are going to be developed as component modes.  For 
example, you might have a directory browser mode and a WYSIWYG mode, 
and you'll be able to present a page with both tools by creating a 
composite mode.  A simple way to do this is using a Velocity template 
which uses the include directive to load the URl of the page with 
different mode parameters.  These include requests are handled 
internally, without going back out over the network.
	A new form handling framework is also in development which will allow 
for the mapping of form inputs to unique keys which are bound to 
objects, so that multiple form-based tools can be composed into a 
single page and submitted via one form, without losing track of where 
each input goes.  This will also allow the determination of idempotency 
to the level of individual inputs, as a key->input mapping is invalid 
as soon as all references to the input backing object are let go by the 
authoring tool to which they belong.  A Mersenne-Twister based unique 
ID generator is used to guarantee uniqueness of these keys within a 
JVM; they are represented as 10 character strings built from a 62 
character set ([0-9][a-z][A-Z]), with up to 2^ 59 possible values.


What's next?
	The form handling framework will be developed in conjunction with the 
porting of one or more authoring tools from HyperContent 1.4 to 
establish proof of concept.      This should be done in the next few 
weeks. The biggest remaining challenge after that will be a new 
workflow-based publication engine which will allow more control over 
how batch-processing is done that was possible in v1, from automatic 
build and publish to a remote server on save, to several stages of 
approval or automated content validation components.  Once that code is 
built, a new project-definition grammar will be built from the ground 
up to make it easy to leverage more of the advanced features of 
HyperContent 2; backwards compatibility for 1.x project definition 
files will be maintained indefinitely, as that logic is cleanly broken 
out into a separate SAX ContentHandler.


Regards,
	Alex

Re: [Hypercontent-developer] HyperContent 2.0 status

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

Jack,
	I guess the level of integration will depend on the use cases to be 
satisfied.  If you'd like to allow people to manage topic maps, which 
could then be published to a web site, an editor would provide you the 
appropriate "space" within which to plug the appropriate engine and a 
GUI for manipulating the data.  This would assume that the ultimate 
persisted representation would be XML, which could then be transformed 
using XSL or another templating language, and would work well enough 
under 1.4.  If you envision a more dynamic interaction with a separate 
topic store, HyperContent 2.0 introduces a class hierarchy of 
FileAssets, which may represent some processing on top of whatever data 
exists in the repository file.  I use this to dynamically generate 
Navigation structures from template files, but it could also be used to 
dynamically build an XTM document from a separate store upon request 
(e.g. page render time).  If you'd like to present topic maps as a 
means of finding data in the repository, HyperContent 2.0 will 
definitely be a more appropriate environment, as the management 
environment in v1.x is monolithic, allowing plug-ins only at the level 
of editing particular files, not for navigating the system.  The use of 
modal views in 2.0 will allow for a much more customizable management 
experience.

Cheers,
	Alex

On Sep 2, 2004, at 1:50 PM, Jack Park wrote:

> Thanks, Alex.
>
> My thinking is that I have a need that goes beyond uPortal, so I
> thought I'd start with standalone HyperContent, meaning 2.0.
>
> I suppose there is some benefit, however, in starting with 1.4
>
> I'll look at it. Particularly, I'll try to come up to speed on the
> editors you mention. I suspect, however, that there are some
> requirements for a topic map engine, quite possibly TM4J, though TM4J
> would need to be integrated with the backside used in HyperContent. I
> have a few ideas of my own on knowledge datastores, and will need to
> think all this through in the context of HyperContent.
>
> Thanks
> Jack
>
> On Thu, 2 Sep 2004 13:31:23 -0400, Alex Vigdor <av...@co...> 
> wrote:
>> Jack,
>>         Depending exactly what you intend to do, I might recommend
>> implementing it in HyperContent 1.4.  Are you specifically interested
>> in generating a topic map for a web site to be managed in 
>> HyperContent?
>>   If so, you could accomplish that in the current release and fairly
>> painlessly migrate it into 2.0 down the road.  HyperContent supports
>> RDF metadata; you could implement topics in the Dublin Core Subject
>> field (no Java coding required), or you could develop a small editor 
>> to
>> manage a custom topic metadata grammar (some Java coding required, to 
>> a
>> well defined API which will unfortunately be changing a bit in v2).
>> Producing the topical map could then be implemented as a combination 
>> of
>> XML includes and XSL processing to group related materials together.
>> HyperContent's design allows you to implement quite complex, custom 
>> web
>> site features with little to no Java coding, once you grok the power 
>> of
>> XML includes combined with XSLT.  The XML Includes allow you to pull
>> all data and/or metadata out of your repository into a single XML
>> document for XSL processing.
>>
>> Alex
>>
>>
>>
>> On Sep 2, 2004, at 1:10 PM, Jack Park wrote:
>>
>>> Thanks Alex.
>>>
>>> I plan to look at the code in terms of adding a topic map as a
>>> navigational system to the architecture. It's pretty clear I'll need
>>> to ask a few questions along the way.
>>>
>>> The first one is: how soon a build.xml?
>>>
>>> Many thanks.
>>> Jack
>>>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Hypercontent-developer mailing list
> Hyp...@li...
> https://lists.sourceforge.net/lists/listinfo/hypercontent-developer
>

Re: [Hypercontent-developer] HyperContent 2.0 status

[Jack P. <jac...@gm...>]

Thanks, Alex.

My thinking is that I have a need that goes beyond uPortal, so I
thought I'd start with standalone HyperContent, meaning 2.0.

I suppose there is some benefit, however, in starting with 1.4

I'll look at it. Particularly, I'll try to come up to speed on the
editors you mention. I suspect, however, that there are some
requirements for a topic map engine, quite possibly TM4J, though TM4J
would need to be integrated with the backside used in HyperContent. I
have a few ideas of my own on knowledge datastores, and will need to
think all this through in the context of HyperContent.

Thanks
Jack

On Thu, 2 Sep 2004 13:31:23 -0400, Alex Vigdor <av...@co...> wrote:
> Jack,
>         Depending exactly what you intend to do, I might recommend
> implementing it in HyperContent 1.4.  Are you specifically interested
> in generating a topic map for a web site to be managed in HyperContent?
>   If so, you could accomplish that in the current release and fairly
> painlessly migrate it into 2.0 down the road.  HyperContent supports
> RDF metadata; you could implement topics in the Dublin Core Subject
> field (no Java coding required), or you could develop a small editor to
> manage a custom topic metadata grammar (some Java coding required, to a
> well defined API which will unfortunately be changing a bit in v2).
> Producing the topical map could then be implemented as a combination of
> XML includes and XSL processing to group related materials together.
> HyperContent's design allows you to implement quite complex, custom web
> site features with little to no Java coding, once you grok the power of
> XML includes combined with XSLT.  The XML Includes allow you to pull
> all data and/or metadata out of your repository into a single XML
> document for XSL processing.
> 
> Alex
> 
> 
> 
> On Sep 2, 2004, at 1:10 PM, Jack Park wrote:
> 
> > Thanks Alex.
> >
> > I plan to look at the code in terms of adding a topic map as a
> > navigational system to the architecture. It's pretty clear I'll need
> > to ask a few questions along the way.
> >
> > The first one is: how soon a build.xml?
> >
> > Many thanks.
> > Jack
> >

Re: [Hypercontent-developer] HyperContent 2.0 status

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

Jack,
	Depending exactly what you intend to do, I might recommend 
implementing it in HyperContent 1.4.  Are you specifically interested 
in generating a topic map for a web site to be managed in HyperContent? 
  If so, you could accomplish that in the current release and fairly 
painlessly migrate it into 2.0 down the road.  HyperContent supports 
RDF metadata; you could implement topics in the Dublin Core Subject 
field (no Java coding required), or you could develop a small editor to 
manage a custom topic metadata grammar (some Java coding required, to a 
well defined API which will unfortunately be changing a bit in v2).  
Producing the topical map could then be implemented as a combination of 
XML includes and XSL processing to group related materials together.  
HyperContent's design allows you to implement quite complex, custom web 
site features with little to no Java coding, once you grok the power of 
XML includes combined with XSLT.  The XML Includes allow you to pull 
all data and/or metadata out of your repository into a single XML 
document for XSL processing.

Alex

On Sep 2, 2004, at 1:10 PM, Jack Park wrote:

> Thanks Alex.
>
> I plan to look at the code in terms of adding a topic map as a
> navigational system to the architecture. It's pretty clear I'll need
> to ask a few questions along the way.
>
> The first one is: how soon a build.xml?
>
> Many thanks.
> Jack
>
> On Thu, 2 Sep 2004 12:52:37 -0400, Alex Vigdor <av...@co...> 
> wrote:
>> Hello all,
>>         I just wanted to provide a status update on the development of
>> HyperContent 2.0.  As of last night,  I have created a new CVS module
>> "hypercontent2" which contains the current code and library
>> dependencies for HyperContent 2.  This is very much a work in 
>> progress;
>> there are no build scripts currently, and I have not checked in any
>> project content to demonstrate the new server.
>>         The way to run HyperContent 2 is through a new class,
>> "org.hypercontent.HTTPServer", which uses Tomcat in embedded mode to
>> offer up the server.  HyperContent 2 is backwards compatible with
>> version 1.x projects, but the structure has changed: project 
>> definition
>> files now reside within the project repository, at
>> "/config/project-definition.xml", and another file
>> "/config/permissions.xml" is used to configure permissions.  I will
>> check in sample content in the near future.
>>
>> A quick overview of what is there already in the HyperContent 2.0 code
>> base:  a standalone web server using JAAS for authentication, which 
>> can
>> serve up static or processed data via "pipelines", and supports
>> advanced browser caching via the HTTP1.1 specification, including
>> support for If-Modified-Since and Etag headers, as well as the basic
>> Last-Modified, Content-Length and Content-Type headers.  Projects are
>> mapped to base paths within the servlet context, so that the URL of a
>> file looks something like
>> "http://www.server.edu/hypercontent-servlet/project-mapping/file-dir/
>> file.ext". Recursive dependency resolution has been implemented, so 
>> for
>> example a file which is transformed by an XSL stylesheet which imports
>> another XSL file will be properly recognized as out-of-date if the
>> imported XSL file is changed.  Disk caching has been implemented using
>> Berkeley DB Java Edition, so that dynamic processing of a page is only
>> performed once after server startup, until any dependency of that page
>> is modified. As of right now, HyperContent 2 can act as a dynamic web
>> server for any HyperContent 1.x project content. HyperContent 1.x 
>> style
>> batch processing has not yet been migrated over, but will be soon.
>>
>> HyperContent 2.0 is introducing a new type of view, which I've taken 
>> to
>> calling "modal".  Any form of content presentation that was supported
>> under HyperContent 1.x is considered a "static" view, such that it is
>> mapped to a plain URL, and is a candidate for batch processing and 
>> disk
>> caching.  Modal views of content will be mapped to a "mode" parameter
>> in addition to the basic URL, and will not be capable of being built 
>> in
>> a batch request or cached to disk - they are exclusively dynamic.  
>> This
>> type of view will be used for management and authoring tools.  I am
>> currently working on integrating the Velocity templating engine as an
>> alternative to XSLT, and with either templating language you will be
>> able to import other modal views, such that modal views can be
>> assembled as components and brought together in various combinations.
>> For example, a directory browser will be a single component that might
>> be reused in different contexts, such as a 1.x style management 
>> screen,
>> or in an "open file" dialog that might pop-up when you want to insert
>> an image in a WYSIWYG area.
>>
>> We're still a few weeks off from doing an alpha release, but the code
>> is now out there if anyone is interested in taking a peek.  I'll be
>> happy to help anyone with further details on the migration process, as
>> needed.
>>
>> Cheers,
>>         Alex
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by BEA Weblogic Workshop
>> FREE Java Enterprise J2EE developer tools!
>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>> _______________________________________________
>> Hypercontent-developer mailing list
>> Hyp...@li...
>> https://lists.sourceforge.net/lists/listinfo/hypercontent-developer
>>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Hypercontent-developer mailing list
> Hyp...@li...
> https://lists.sourceforge.net/lists/listinfo/hypercontent-developer
>

Re: [Hypercontent-developer] HyperContent 2.0 status

[Jack P. <jac...@gm...>]

Thanks Alex.

I plan to look at the code in terms of adding a topic map as a
navigational system to the architecture. It's pretty clear I'll need
to ask a few questions along the way.

The first one is: how soon a build.xml?

Many thanks.
Jack

On Thu, 2 Sep 2004 12:52:37 -0400, Alex Vigdor <av...@co...> wrote:
> Hello all,
>         I just wanted to provide a status update on the development of
> HyperContent 2.0.  As of last night,  I have created a new CVS module
> "hypercontent2" which contains the current code and library
> dependencies for HyperContent 2.  This is very much a work in progress;
> there are no build scripts currently, and I have not checked in any
> project content to demonstrate the new server.
>         The way to run HyperContent 2 is through a new class,
> "org.hypercontent.HTTPServer", which uses Tomcat in embedded mode to
> offer up the server.  HyperContent 2 is backwards compatible with
> version 1.x projects, but the structure has changed: project definition
> files now reside within the project repository, at
> "/config/project-definition.xml", and another file
> "/config/permissions.xml" is used to configure permissions.  I will
> check in sample content in the near future.
> 
> A quick overview of what is there already in the HyperContent 2.0 code
> base:  a standalone web server using JAAS for authentication, which can
> serve up static or processed data via "pipelines", and supports
> advanced browser caching via the HTTP1.1 specification, including
> support for If-Modified-Since and Etag headers, as well as the basic
> Last-Modified, Content-Length and Content-Type headers.  Projects are
> mapped to base paths within the servlet context, so that the URL of a
> file looks something like
> "http://www.server.edu/hypercontent-servlet/project-mapping/file-dir/
> file.ext". Recursive dependency resolution has been implemented, so for
> example a file which is transformed by an XSL stylesheet which imports
> another XSL file will be properly recognized as out-of-date if the
> imported XSL file is changed.  Disk caching has been implemented using
> Berkeley DB Java Edition, so that dynamic processing of a page is only
> performed once after server startup, until any dependency of that page
> is modified. As of right now, HyperContent 2 can act as a dynamic web
> server for any HyperContent 1.x project content. HyperContent 1.x style
> batch processing has not yet been migrated over, but will be soon.
> 
> HyperContent 2.0 is introducing a new type of view, which I've taken to
> calling "modal".  Any form of content presentation that was supported
> under HyperContent 1.x is considered a "static" view, such that it is
> mapped to a plain URL, and is a candidate for batch processing and disk
> caching.  Modal views of content will be mapped to a "mode" parameter
> in addition to the basic URL, and will not be capable of being built in
> a batch request or cached to disk - they are exclusively dynamic.  This
> type of view will be used for management and authoring tools.  I am
> currently working on integrating the Velocity templating engine as an
> alternative to XSLT, and with either templating language you will be
> able to import other modal views, such that modal views can be
> assembled as components and brought together in various combinations.
> For example, a directory browser will be a single component that might
> be reused in different contexts, such as a 1.x style management screen,
> or in an "open file" dialog that might pop-up when you want to insert
> an image in a WYSIWYG area.
> 
> We're still a few weeks off from doing an alpha release, but the code
> is now out there if anyone is interested in taking a peek.  I'll be
> happy to help anyone with further details on the migration process, as
> needed.
> 
> Cheers,
>         Alex
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Hypercontent-developer mailing list
> Hyp...@li...
> https://lists.sourceforge.net/lists/listinfo/hypercontent-developer
>

[Hypercontent-developer] HyperContent 2.0 status

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

Hello all,
	I just wanted to provide a status update on the development of  
HyperContent 2.0.  As of last night,  I have created a new CVS module  
"hypercontent2" which contains the current code and library  
dependencies for HyperContent 2.  This is very much a work in progress;  
there are no build scripts currently, and I have not checked in any  
project content to demonstrate the new server.
	The way to run HyperContent 2 is through a new class,  
"org.hypercontent.HTTPServer", which uses Tomcat in embedded mode to  
offer up the server.  HyperContent 2 is backwards compatible with  
version 1.x projects, but the structure has changed: project definition  
files now reside within the project repository, at  
"/config/project-definition.xml", and another file  
"/config/permissions.xml" is used to configure permissions.  I will  
check in sample content in the near future.

A quick overview of what is there already in the HyperContent 2.0 code  
base:  a standalone web server using JAAS for authentication, which can  
serve up static or processed data via "pipelines", and supports  
advanced browser caching via the HTTP1.1 specification, including  
support for If-Modified-Since and Etag headers, as well as the basic  
Last-Modified, Content-Length and Content-Type headers.  Projects are  
mapped to base paths within the servlet context, so that the URL of a  
file looks something like  
"http://www.server.edu/hypercontent-servlet/project-mapping/file-dir/ 
file.ext". Recursive dependency resolution has been implemented, so for  
example a file which is transformed by an XSL stylesheet which imports  
another XSL file will be properly recognized as out-of-date if the  
imported XSL file is changed.  Disk caching has been implemented using  
Berkeley DB Java Edition, so that dynamic processing of a page is only  
performed once after server startup, until any dependency of that page  
is modified. As of right now, HyperContent 2 can act as a dynamic web  
server for any HyperContent 1.x project content. HyperContent 1.x style  
batch processing has not yet been migrated over, but will be soon.

HyperContent 2.0 is introducing a new type of view, which I've taken to  
calling "modal".  Any form of content presentation that was supported  
under HyperContent 1.x is considered a "static" view, such that it is  
mapped to a plain URL, and is a candidate for batch processing and disk  
caching.  Modal views of content will be mapped to a "mode" parameter  
in addition to the basic URL, and will not be capable of being built in  
a batch request or cached to disk - they are exclusively dynamic.  This  
type of view will be used for management and authoring tools.  I am  
currently working on integrating the Velocity templating engine as an  
alternative to XSLT, and with either templating language you will be  
able to import other modal views, such that modal views can be  
assembled as components and brought together in various combinations.   
For example, a directory browser will be a single component that might  
be reused in different contexts, such as a 1.x style management screen,  
or in an "open file" dialog that might pop-up when you want to insert  
an image in a WYSIWYG area.

We're still a few weeks off from doing an alpha release, but the code  
is now out there if anyone is interested in taking a peek.  I'll be  
happy to help anyone with further details on the migration process, as  
needed.

Cheers,
	Alex

Re: [Hypercontent-developer] RDF url for news

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

Hi Dimitry,
	Because HyperContent currently sits inside uPortal, there is no way to 
link directly to a piece of content in a HyperContent repository.  
Version 2.0, which is in development right now, exposes every file in 
the repository and every view pipeline (e.g. XSL transformed data) via 
a standard URL.  For now, with version 1.4, our general approach is to 
publish the XML to a static file on a web server, and point uPortal to 
the appropriate URL on that web server. We do this with a number of 
types of content, including RSS and expandable lists of links.

Alex

On Aug 17, 2004, at 1:34 PM, Dmitry Y. Podkuiko wrote:

> Hello,
>
> I am running HyperContent 1.4 and I am wondering if there is any way 
> to get to the RDF url for the news that can be fed into the
> Oracle RSS portlet or any other portlet in uPortal, etc?
>
> Thanks,
>
> Dmitry
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Hypercontent-developer mailing list
> Hyp...@li...
> https://lists.sourceforge.net/lists/listinfo/hypercontent-developer
>

[Hypercontent-developer] RDF url for news

[Dmitry Y. P. <dpo...@mt...>]

Hello,

I am running HyperContent 1.4 and I am wondering if there is any way to get 
to the RDF url for the news that can be fed into the
Oracle RSS portlet or any other portlet in uPortal, etc?

Thanks,

Dmitry 

[Hypercontent-developer] development update

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

Hello all,
	This is a status update for those interested in following HyperContent 
development.  The current release is version 1.3, and version 1.3.1 has 
been tagged in the CVS.  It contains 4 bug fixes and one or two minor 
new features; I'm leaving on vacation for a week starting tomorrow, so 
I may not get it out before then, but you can feel free to download it 
with the 'rel_1_3_1' tag.
	The code in the CVS added post 1.3.1 is related to some new 
functionality which I'm hoping to bundle into version 1.4 in time for 
the JA-SIG June conference; it offers a whole new way of managing site 
navigation.  Up until now, site navigation has been constructed through 
a combination of XML includes and XSL logic for labeling, sorting and 
displaying.  If ad-hoc sorting is desired, the only way to do it until 
now has been to add a custom sort field to XML data and include that 
data at build time for XSL processing. To re-order objects could be 
laborious, as you have to edit each file whose position should change 
individually.   Adding a one-off link to a navigation area could 
involve creating or editing yet another file.
	The new functionality allows you to define navigation templates in an 
XML file, which will be dynamically resolved at build time into a tree 
of fully sorted and labeled navigation items.  These templates can be 
as simple as saying "put book chapters under book divisions under books 
and label and sort them all by title", but also accommodate one-off 
links, custom ordering and labeling, restricting the maximum number of 
displayed items, and more.  This functionality is already complete:  
the HyperContent web site has been converted to use it.  Using this 
mechanism allowed me to remove 25% of the overall XSL code, 20% of the 
project definition code,  order documentation chapters in one place 
rather than many, reduce build-time memory consumption by over 50% and 
speed up the build!
	What I'm currently working on to fit on top of this is a navigation 
editor, which will allow you to re-order items by simple drag and drop, 
click to edit labels and locations, and easily add or remove ad-hoc 
items from a navigation set.  The drag-and-drop DHTML magic is 
finished, which I expect was the hardest part, so I am optimistic about 
completing the work in time for the conference.

	As of right now, it looks like version 1.4 will be the end of the 1.x 
track; each release since 1.1 has added functionality within the 
initial architecture, only minimally extending the architecture to 
support new features as required.  This summer marks the beginning of 
development for version 2.0, which is going to entail a major 
architectural overhaul.  v2 is going to be a standalone server 
application; it will no longer sit inside of uPortal, but will be able 
to present management tools and content portlets to any portal via WSRP 
and UDDI, or directly to the user's browser with no intermediary.  v2 
will have an integrated content server, so that it can be used to 
deliver dynamic content as well as pushing static content like v1.x.  
This content server will be built on WebDAV, which will make it 
possible to edit repository content directly from the desktop.

Over the course of the summer I'll be posting more documentation about 
the v2 design, but the short of it is pretty much what you see above. 
If anyone is interested in contributing to the development, don't 
hesitate to respond!

Alex

[Hypercontent-developer] HyperContent 1.3 now available (was CuCMS)

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

HyperContent version 1.3 is now available for download from the 
HyperContent site at

http://hypercontent.sourceforge.net/downloads/index.html

HyperContent is a professional grade web content management system 
(formerly known as CuCMS) that enables content experts, designers, 
developers and administrators to collaborate effectively in the 
production of high quality web sites with consistent navigation and 
design. HyperContent recently received the endorsement of the JA-SIG as 
an effective solution for higher education web content management 
needs.

HyperContent 1.3 adds several exciting new features, including
     * Multilingual spell-checking with built-in dictionaries for 
American and British English, French and German
     * In-browser image cropping and resizing, and automatic conversion 
between GIF, JPG and PNG formats
     * SFTP support for secure content publishing
     * uPortal 2.2 support including dynamic locale selection
     * Image thumbnail support


Interested parties are encouraged to join the new HyperContent users 
mailing list now available at

http://sourceforge.net/mail/?group_id=101745


Further information about HyperContent can be found at

http://hypercontent.sourceforge.net

[Hypercontent-developer] test message 3 (ignore)

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

[Hypercontent-developer] test message (ignore)

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