Thread: [Hypercontent-users] Xinha
Brought to you by:
alexvigdor
From: Carl B. <C.P...@hu...> - 2005-03-21 15:43:02
|
Hi Alex Would you suggest using Xinha (http://xinha.gogo.co.nz/cgi-bin/trac.cgi) instead of htmlArea? and if so how easy is will be be to switch ? Cheers Carl -- ************************************ Carl Barrow Web Developer e-Services The University of Hull Cottingham Road Hull HU6 7RX Ext. 6838 ************************************ |
From: Alex V. <av...@co...> - 2005-03-21 16:25:18
|
Hi Carl, I would caution against trying to switch WYSIWYG editors in HyperContent 1.4; I had to customize HTMLArea fairly extensively so that relative links and image paths would work correctly. You could certainly do it, but it will be more of a headache than you might think. We have talked here at Columbia about evaluating our options for a new editor for version 2.0, which should not require such customizations as HyperContent 2 is more transparent to the browser (since it responds like a regular web server). There's quite a few alternatives out there, so I think a competitive evaluation is due. Htmlarea,com now sports a list of open source WYSIWYG editors - we should definitely put Xinha on the list, and I would certainly appreciate your involvement in evaluating some of the alternatives. The baseline functionality is pretty common across tools, but features like table editing are perhaps more divergent in their implementations. What types of requirements would you have for a new WYSIWYG? Alex On Mar 21, 2005, at 10:48 AM, Carl Barrow wrote: > Hi Alex > > Would you suggest using Xinha > (http://xinha.gogo.co.nz/cgi-bin/trac.cgi) instead of htmlArea? and > if so how easy is will be be to switch ? > > Cheers > Carl > > -- > ************************************ > > Carl Barrow > Web Developer > e-Services > The University of Hull > Cottingham Road > Hull > HU6 7RX > Ext. 6838 > ************************************ > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Hypercontent-users mailing list > Hyp...@li... > https://lists.sourceforge.net/lists/listinfo/hypercontent-users |
From: Carl B. <C.P...@hu...> - 2005-03-22 13:37:52
|
Hi Alex I’ll stick with HTMLArea for now, I don’t want to create unnecessary work . It makes sense to wait until version 2, at which point I’d be glad to be involved in any evaluation process. Off the top of my head, our main requirements for a new WYSIWYG would be: Top Level The editor controls to be configurable so we can decide what the user sees. Plug-in Free, although I understand this might be a trade off for more flexibility. Cross Platform and Cross Browser compatibility. Low Level Tables support HTML Clean up to remove custom font and colour tags. I can work on a more detailed list. When do you expect version 2 to be ready for testing? I’m very interested to take a look. Thanks Carl Alex Vigdor wrote: > Hi Carl, > I would caution against trying to switch WYSIWYG editors in > HyperContent 1.4; I had to customize HTMLArea fairly extensively so > that relative links and image paths would work correctly. You could > certainly do it, but it will be more of a headache than you might > think. We have talked here at Columbia about evaluating our options > for a new editor for version 2.0, which should not require such > customizations as HyperContent 2 is more transparent to the browser > (since it responds like a regular web server). There's quite a few > alternatives out there, so I think a competitive evaluation is due. > Htmlarea,com now sports a list of open source WYSIWYG editors - we > should definitely put Xinha on the list, and I would certainly > appreciate your involvement in evaluating some of the alternatives. > The baseline functionality is pretty common across tools, but features > like table editing are perhaps more divergent in their > implementations. What types of requirements would you have for a new > WYSIWYG? > > Alex > > On Mar 21, 2005, at 10:48 AM, Carl Barrow wrote: > >> Hi Alex >> >> Would you suggest using Xinha >> (http://xinha.gogo.co.nz/cgi-bin/trac.cgi) instead of htmlArea? and >> if so how easy is will be be to switch ? >> >> Cheers >> Carl >> >> -- >> ************************************ >> >> Carl Barrow >> Web Developer >> e-Services >> The University of Hull >> Cottingham Road >> Hull >> HU6 7RX >> Ext. 6838 >> ************************************ >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Hypercontent-users mailing list >> Hyp...@li... >> https://lists.sourceforge.net/lists/listinfo/hypercontent-users > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Hypercontent-users mailing list > Hyp...@li... > https://lists.sourceforge.net/lists/listinfo/hypercontent-users -- ************************************ Carl Barrow Web Developer e-Services The University of Hull Cottingham Road Hull HU6 7RX Ext. 6838 ************************************ |
From: Alex V. <av...@co...> - 2005-03-22 15:12:43
|
Hi Carl, Version 2 is getting very close. I have a couple basic = workflows=20 working, request for approval and page monitoring, with email=20 notification and a flexible configuration file format. I need to=20 integrate build and publish as commands in the new workflow system,=20 bring the zip file i/o function over, and I think we'll be ready for=20 beta. Before the final release I'd like to do the evaluation and=20 integration of a new WYSIWYG, make some other changes to the XML=20 editor, and introduce a new configuration file format that makes it=20 easier to leverage some of the new features. And then . . . maybe a=20 vacation! Alex On Mar 22, 2005, at 5:28 AM, Carl Barrow wrote: > Hi Alex > > I=92ll stick with HTMLArea for now, I don=92t want to create = unnecessary=20 > work . It makes sense to wait until version 2, at which point I=92d be=20= > glad to be involved in any evaluation process. > > Off the top of my head, our main requirements for a new WYSIWYG would=20= > be: > > *Top Level > *The editor controls to be configurable so we can decide what the user=20= > sees. > Plug-in Free, although I understand this might be a trade off for more=20= > flexibility. > Cross Platform and Cross Browser compatibility. > > *Low Level* > Tables support > HTML Clean up to remove custom font and colour tags. > > I can work on a more detailed list. > > When do you expect version 2 to be ready for testing? I=92m very=20 > interested to take a look. > > Thanks > > Carl > > > > Alex Vigdor wrote: > >> Hi Carl, >> I would caution against trying to switch WYSIWYG editors in=20 >> HyperContent 1.4; I had to customize HTMLArea fairly extensively so=20= >> that relative links and image paths would work correctly. You could=20= >> certainly do it, but it will be more of a headache than you might=20 >> think. We have talked here at Columbia about evaluating our options=20= >> for a new editor for version 2.0, which should not require such=20 >> customizations as HyperContent 2 is more transparent to the browser=20= >> (since it responds like a regular web server). There's quite a few=20 >> alternatives out there, so I think a competitive evaluation is due.=20= >> Htmlarea,com now sports a list of open source WYSIWYG editors - we=20 >> should definitely put Xinha on the list, and I would certainly=20 >> appreciate your involvement in evaluating some of the alternatives.=20= >> The baseline functionality is pretty common across tools, but=20 >> features like table editing are perhaps more divergent in their=20 >> implementations. What types of requirements would you have for a new=20= >> WYSIWYG? >> >> Alex >> >> On Mar 21, 2005, at 10:48 AM, Carl Barrow wrote: >> >>> Hi Alex >>> >>> Would you suggest using Xinha=20 >>> (http://xinha.gogo.co.nz/cgi-bin/trac.cgi) instead of htmlArea? and=20= >>> if so how easy is will be be to switch ? >>> >>> Cheers >>> Carl >>> >>> --=20 >>> ************************************ >>> >>> Carl Barrow >>> Web Developer >>> e-Services >>> The University of Hull >>> Cottingham Road >>> Hull >>> HU6 7RX >>> Ext. 6838 >>> ************************************ >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real=20 >>> users. >>> Discover which products truly live up to the hype. Start reading = now. >>> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick >>> _______________________________________________ >>> Hypercontent-users mailing list >>> Hyp...@li... >>> https://lists.sourceforge.net/lists/listinfo/hypercontent-users >> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real=20 >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick >> _______________________________________________ >> Hypercontent-users mailing list >> Hyp...@li... >> https://lists.sourceforge.net/lists/listinfo/hypercontent-users > > > --=20 > ************************************ > > Carl Barrow > Web Developer > e-Services > The University of Hull > Cottingham Road > Hull > HU6 7RX > Ext. 6838 > ************************************ |