[Hypercontent-users] Re: hypercontent help for XHTML editing

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

Hi Vangel,
	I have embedded my responses below, and I am copying the =20
hypercontent-users list as I think your questions may be relevant to =20
others.

On Apr 2, 2006, at 5:07 PM, Vangel V. Ajanovski wrote:

> Hello Alex,
>
> I found your email in a presentation from JASIG conference about =20
> Hypercontent 2.0
>
> I need some info about two things in Hypercontent that I'm not able =20=

> to achieve because of lack of examples in the documentation I was =20
> able to find. Could you help we some explanations?
>
> Your presentation on JA-SIG Winter Conference Dec. 05 states that =20
> it's possible to use network mounted drives and that it can be used =20=

> to feed XHTML documents for uPortal.
>
> So I have two problems with those two things.
>
> 1. I don't really understand how should I configure a filesystem =20
> for publishing to a network mount in Windows 2003.
>
> The web server is on another computer that is also running Windows =20
> 2003 and I want the content to be published to that computer. I =20
> already tried by installing cygwin and openssh daemon on the other =20
> server and I'm using SFTP to transfer the files, but I don't like =20
> it. I would like to use some native windows mechanism and the user =20
> that is publishing the changes of the files to be able to input his =20=

> login and password for the network share to which the files will be =20=

> transfered. Is it possible and how?

There are currently only two filesystem implementations that can take =20=

a username & password at runtime: FTP and SFTP.  If you would like to =20=

tie in a native Windows server protocol like SMB, there will need to =20
be some existing Java client library (e.g. JCIFS) which you can use =20
as the provider; you would write a thin wrapper around this client =20
that subclasses RemoteFileSystemImpl, like both the FTP and SFTP =20
implementations.  Subclassing RemoteFileSystemImpl simplifies the =20
filesystem API and takes care of caching directory listings and some =20
synchronization issues, though you'll see some further =20
synchronization in both the FTP and SFTP code.  Ultimately the goal =20
is to provide an implementation of IFileSystemManager  which can be =20
mapped to a key in /source/properties/FileSystemConfig.xml.  You can =20
then use this key to populate the "type" attribute of the "filesystem-=20=

def" element under a "build", "publish" or "mount" tag in a project =20
definition, or under the "repository" tag in a project declaration =20
file (/projects/*/filesystem.xml).

All the Filesystem code is under the package "/org/hypercontent/=20
filesystem" and its subpackage "impl".

Our normal pattern of using file servers gives the HyperContent =20
application complete read/write access to relevant areas on an NFS or =20=

SMB server which is already mounted, and restricts access within =20
those areas using HyperContent's own authorization mechanisms.  This =20
way the user does not have to log in again once they are logged into =20
HyperContent, and HyperContent doesn't have to know anything about =20
the file server technology: it just gets to the files through the =20
normal Java IO APIs.


> 2.  I have trouble with XHTML document editing.
>
> I am managing a simple web site that merely provides XHTML files =20
> for WebProxy channels in uPortal. I imported this site as a ZIP =20
> file into hypercontent and I want to edit the files. If when I =20
> click edit the file is opened as plain text everything will be ok. =20
> But, if for example I open it in WYSIWYG editor, all x/html header =20
> tags will be removed.
>
> So the document that was for example:
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> "http://www.w3.org/1999/xhtml">
>      OPEN DAY !!!! =D0=9E=D0=A2=D0=92=D0=9E=D0=A0=D0=95=D0=9D =D0=94=D0=95=
=D0=9D !!!! OPEN DAY !!!! =20
> =D0=9E=D0=A2=D0=92=D0=9E=D0=A0=D0=95=D0=9D =D0=94=D0=95=D0=9D
>
>
> will become
>        OPEN DAY !!!! =D0=9E=D0=A2=D0=92=D0=9E=D0=A0=D0=95=D0=9D =D0=94=D0=
=95=D0=9D !!!! OPEN DAY !!!! =20
> =D0=9E=D0=A2=D0=92=D0=9E=D0=A0=D0=95=D0=9D =D0=94=D0=95=D0=9D
>
>
> This is very strange behaviour. Obviously TinyMCE doesn't recognize =20=

> my XHTML files.
> Do you have any idea what should I do?

You can adjust the TinyMCE settings for .html documents in the file /=20
screens/modal-html.vm in the bootstrap repository.  For example, you =20
might try adding plugins:"fullpage" to the config.  The full TinyMCE =20
configuration reference is available at

http://tinymce.moxiecode.com/tinymce/docs/reference_configuration.html

Another option is to edit the files in XML and run them through a =20
simple XSL transformation that adds the doctype.

Cheers,
	Alex=