Re: ANNOUNCE: Bricolage 1.2.0
On Fri, 11 Jan 2002, Matt Sergeant wrote: > Any chance of supporting more template systems in the future, like TT and > XSLT? Adding more Burners (brictalk for templating system) is definitely something we're interested in. If you'd like to give it a try there's a brief set of instructions in the Bric::Util::Burner docs: http://bricolage.thepirtgroup.com/docs/Bric/Util/Burner.html Look for the "ADDING A NEW BURNER" section. For general information about the templating system, see: http://bricolage.thepirtgroup.com/documentation.html -sam
Re: ANNOUNCE: Bricolage 1.2.0
On Fri, 2002-01-11 at 11:39, Matt Sergeant wrote: > Looks neat! Thanks, Matt! > Any chance of supporting more template systems in the future, like TT and > XSLT? The templating architecture is managed via subclasses. So anyone who wants to add his/her favorite templating system is welcome to implement a new subclass. I encourage interested developers to join the bricolage-devel list on SourceForge. https://sourceforge.net/mail/?group_id=34789 Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: ANNOUNCE: Bricolage 1.2.0
On 11 Jan 2002, David Wheeler wrote: > On Fri, 2002-01-11 at 01:29, [EMAIL PROTECTED] wrote: > > > Do you provide a demo of Bricolage. Can I expect something similar to > > the Midgard Project on PHP? > > Unfortunately there is no demo of Bricolage at this time. But you can > start reading up on it and see some screenshots at > http://bricolage.thepirtgroup.com/. Looks neat! > I'm not familiar with Midgard, though it looks interesting. What > differentiates Bricolage from other OSS CMSs, however, is its robust > support for configurable workflows. Furthermore, its templates are > written in HTML::Mason or HTML::Template -- that is, Perl. So you have a > complete, robust programming language to work with. Any chance of supporting more template systems in the future, like TT and XSLT? -- <:->Get a smart net
Re: ANNOUNCE: Bricolage 1.2.0
On Fri, 2002-01-11 at 01:29, [EMAIL PROTECTED] wrote: > Do you provide a demo of Bricolage. Can I expect something similar to > the Midgard Project on PHP? Unfortunately there is no demo of Bricolage at this time. But you can start reading up on it and see some screenshots at http://bricolage.thepirtgroup.com/. I'm not familiar with Midgard, though it looks interesting. What differentiates Bricolage from other OSS CMSs, however, is its robust support for configurable workflows. Furthermore, its templates are written in HTML::Mason or HTML::Template -- that is, Perl. So you have a complete, robust programming language to work with. Thanks, David -- David Wheeler AIM: dwTheory Bricolage Maintainer ICQ: 15726394 [EMAIL PROTECTED] Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: ANNOUNCE: Bricolage 1.2.0
Basel, Freitag, 11. Januar 2002, 10:26:28 . *see original email below* Hello David > Bricolage is a full-featured, enterprise-class content management > system. It offers a browser-based interface for ease-of use, a > full-fledged templating system with complete programming language > support for flexibility, and many other features. It operates in an > Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its > repository. Do you provide a demo of Bricolage. Can I expect something similar to the Midgard Project on PHP? Best Regards Christian - [EMAIL PROTECTED] - . == beginn original == Date: Freitag, 11. Januar 2002, 04:06:23 Subject: ANNOUNCE: Bricolage 1.2.0 I'd like to announce the release of Bricolage 1.2.0. It will shortly be available for download from http://bricolage.sourceforge.net/. This release features several bug fixes and quite a few important new features. It uses HTML::Mason exlusively for its UI, and uses either HTML::Mason or HTML::Template for its templating architecture. Here's a brief description of Bricolage: Bricolage is a full-featured, enterprise-class content management system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. Here's a list of the changes from 1.0.2: VERSION 1.2.0 New Features * Added Context-sensitive, online help. [Sam] * Added separate interface for editing templates (via FTP). [Sam] * Added the ability to use HTML::Template Templates. [Sam] * Added ability for differnt Output Channels to function as different component roots for in Mason templates. This will allow for templates that can't be found in the current Output Channel to be searched for in other Output Channels. [David] * Added link to Event log to Find Story, Find Template, and Find Media screens. [David] * Added true previewing for media assets. Now, when you click their URIs to preview them, they will be distributed to the preview server(s) before redirecting the user to them, rather than just serving them up from where they live on the Bricolage file system. The latter can still be accessed under "Download" in the Media Asset profile. This will continue to be the preferred way to grab media files for editing and such, as it will not incur the overhead of distributing the media file. [David] * Allow only one template with a given name for a given category, element, burner and output channel. [Sam] * Added a Maintainer section to the About page. [David] * Updated About page to mimic the layout of the help pages. [David] Bug Fixes * Fixed a bug with local previews where a preview page could show up instead of the Bricoalge UI. Thanks to Sara for the spot. [David] * Fixed a bug where Mason component calls failed in previews when the PREVIEW_MASON directive was enabled. [David] * Changed default value for text area fields added via the form builder (i.e., in Contributor Type and Element profiles) to 0. The values 0 and "" always make the the new field unlimited in length. [David] * Fixed a couple of buttons to be proper case rather than upper case. [David] * Separated the filesystem destinations for assets burned for publication and for assets burned for previewing. This will prevent someone previewing and stomping all over a published version of an asset before the published version is distributed. [David] * Removed hard-coding of the local preview directory in httpd.conf and httpd-ssl.conf. Now using the values stored in PREVIEW_LOCAL, instead, to determine the proper directory. [David] * Added the DEF_MEDIA_TYPE directive. Bricolage will use the value in this directive to assign a Media Type to all file resources if they Bricolage can't figure it out from their file extentions. This fixes a bug where Bricolage would choke if it couldn't figure out the MediaType itself. [David] Enjoy! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED] === end original
ANNOUNCE: Bricolage 1.2.0
I'd like to announce the release of Bricolage 1.2.0. It will shortly be available for download from http://bricolage.sourceforge.net/. This release features several bug fixes and quite a few important new features. It uses HTML::Mason exlusively for its UI, and uses either HTML::Mason or HTML::Template for its templating architecture. Here's a brief description of Bricolage: Bricolage is a full-featured, enterprise-class content management system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. Here's a list of the changes from 1.0.2: VERSION 1.2.0 New Features * Added Context-sensitive, online help. [Sam] * Added separate interface for editing templates (via FTP). [Sam] * Added the ability to use HTML::Template Templates. [Sam] * Added ability for differnt Output Channels to function as different component roots for in Mason templates. This will allow for templates that can't be found in the current Output Channel to be searched for in other Output Channels. [David] * Added link to Event log to Find Story, Find Template, and Find Media screens. [David] * Added true previewing for media assets. Now, when you click their URIs to preview them, they will be distributed to the preview server(s) before redirecting the user to them, rather than just serving them up from where they live on the Bricolage file system. The latter can still be accessed under "Download" in the Media Asset profile. This will continue to be the preferred way to grab media files for editing and such, as it will not incur the overhead of distributing the media file. [David] * Allow only one template with a given name for a given category, element, burner and output channel. [Sam] * Added a Maintainer section to the About page. [David] * Updated About page to mimic the layout of the help pages. [David] Bug Fixes * Fixed a bug with local previews where a preview page could show up instead of the Bricoalge UI. Thanks to Sara for the spot. [David] * Fixed a bug where Mason component calls failed in previews when the PREVIEW_MASON directive was enabled. [David] * Changed default value for text area fields added via the form builder (i.e., in Contributor Type and Element profiles) to 0. The values 0 and "" always make the the new field unlimited in length. [David] * Fixed a couple of buttons to be proper case rather than upper case. [David] * Separated the filesystem destinations for assets burned for publication and for assets burned for previewing. This will prevent someone previewing and stomping all over a published version of an asset before the published version is distributed. [David] * Removed hard-coding of the local preview directory in httpd.conf and httpd-ssl.conf. Now using the values stored in PREVIEW_LOCAL, instead, to determine the proper directory. [David] * Added the DEF_MEDIA_TYPE directive. Bricolage will use the value in this directive to assign a Media Type to all file resources if they Bricolage can't figure it out from their file extentions. This fixes a bug where Bricolage would choke if it couldn't figure out the MediaType itself. [David] Enjoy! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
