Zope-Announce December 2002

zope-announce@zope.dev

17 participants
24 discussions

Seeking Expressions of Support
by Steve Holden 18 Dec '02

18 Dec '02

This is my last word on this subject until after Christmas. It's also about as close as I'll ever get to spamming -- apologies to those of you who receive multiple copies of this mail. Please send it on to any individual or list with an interest in Python and related topics. For PyCon DC 2003 to be a success it needs people to get involved. Then Python will finally have low-cost conferences. So take a look at the following link, then don't mail me -- visit the Python Wiki PyCon page and express your support (or not, as the case may be): http://pydish.holdenweb.com/pycon/threat.html Happy holidays ----------------------------------------------------------------------- Steve Holden http://www.holdenweb.com/ Python Web Programming http://pydish.holdenweb.com/pwp/ Bring your musical instrument to PyCon! http://www.python.org/pycon/ -----------------------------------------------------------------------

1 0

Strip-o-Gram 1.3 Released!
by Chris Withers 17 Dec '02

17 Dec '02

Strip-o-Gram is an HTML Conversion Library that can convert HTML to Plain Text and strip specified tags and Javascript from HTML. See http://www.zope.org/Members/chrisw/StripOGram for more details. This release includes several bug fixes and some new features and will allow the methods to be used from Zope's Script (Python)'s once http://collector.zope.org/Zope/685 has been resolved. cheers, Chris

1 0

PyCon DC 2003: Extension of Submission Deadline
by Guido van Rossum on behalf of Steve Holden 17 Dec '02

17 Dec '02

The deadline for submissions to PyCon DC 2003 appears to have been too tight for many authors. While some promised submissions have arrived, several have not even though the original deadline of 15 December has passed. Rather than exclude promising papers the organizing committee has decided to extend the deadline for submissions. Accordingly, the new schedule for proposals is as follows: Submission Deadline: January 15, 2003 Notification of Acceptance: January 31, 2003 Final Versions Due: March 10, 2003 Conference Dates: March 26-28, 2003 [unchanged] Authors who have already submitted abstracts are invited to resubmit if they feel that the original deadline had an adverse effect on the quality of their submissions. Please make any appropriate media, mailing lists and newsgroups aware of this announcement. Enquiries should be sent in the first instance to pycondc-2003(a)python.org. Information about PyCon DC 2003 is available at the following URLs: www.python.org/pycon www.python.org/cgi-bin/moinmoin/PyCon The latter URL, a Wiki page, can also be used to communicate with the conference organizers. This is *your* conference: tell us what *you* want to see in it. regards ----------------------------------------------------------------------- Steve Holden http://www.holdenweb.com/ Python Web Programming http://pydish.holdenweb.com/pwp/ Bring your musical instrument to PyCon! http://www.python.org/pycon/ -----------------------------------------------------------------------

1 0

NeoPortal Content Pak 0.9a has been released.
by Wankyu Choi 15 Dec '02

15 Dec '02

I'm pleased to announce that NeoPortal Content Pak 0.9a has been released. NeoPortal Content Pak is a collection of CMFPlone content types. It's dependent on Plone but I wouldn't call it Plone product since I don't fully follow the Plone developing guides. You can download NeoPortal Content Pak from http://www.zoper.net/Downloads. NeoPortal Content consists of three different types: Primitive, Container and Element types. Primitive Types Primitive NeoPortal Content Types are basic content types you'd find in an ordinary CMF site. Container Types Container types can **contain** Element types. Only a defined set of NeoPortal Elements can be added to a NeoPortal Container. NeoPortal Containers give NeoPortal Elements sequenceable id's at the time of their addition. Any given id's via Elements' contructor methods are ignored unless the 'no_id_check' argument is set to true when calling '_setObject'. NeoPortal Containers can re-number its Elements' id's if needed. Element Types Only NeoPortal Containers can contain NeoPortal Element Types and Element types are container-dependent: for example, only an Advanced Container type can contain Advanced Element types. Members Types Ordinary portal members can add the following NeoPortal Content Types. Primitive Types - NeoPortal Document : behaves just like CMF's Document with additional NeoPortal features - NeoPortal News Item : behaves just like CMF's News Item with additional NeoPortal features - NeoPortal Link : behaves just like CMF's Link with additional NeoPortal features; can open new window - NeoPortal File : behaves just like CMF's File with additional NeoPortal features - NeoPortal Image : behaves just like CMF's Image with additional NeoPortal features; can edit image-specific attributes ( border, align, scale, hspace, vspace, css_class, etc ) - NeoPortal Media : NeoPortal Link + Content-type-aware icons - NeoPortal External File : NeoPortal File + Filesystem storage - NeoPortal Folder : PloneFolder with addtional NeoPortal features Container Types - NeoPortal Article : NeoPortal Folder + Article features; as of 0.9a, all NeoPortal Element types are addable only to this container type Element Types - NeoPortal Page Element : NeoPortal Document + Element features - NeoPortal Form Element : NeoPortal Document + Element features - NeoPortal Table Element : NeoPortal Document + Element features - NeoPortal Link Element : NeoPortal Link + Element features - NeoPortal Media Element : NeoPortal Media + Element features - NeoPortal File Element : NeoPortal File + Element features - NeoPortal Image Element : NeoPortal Image + Element features - NeoPortal External File Element : NeoPortal External File + Element features Note that, as of version 0.9a, NeoPortal Form Element and NeoPortal Table Element behave exactly like NeoPortal Page Element. I have created these types for future versions of NeoPortal Content Pak so that I can easily extract HTML forms and tables from a document. It is highly recommended users of NeoPortal Content Types use NeoPortal Form Element/NeoPortal Table Element when adding HTML form or table tags instead of directly inserting them into a Page Element. Manager Types Only managers or anyone with 'ManagePortal' permissions can add the following NeoPortal Content Types. Primitive Types - NeoPortal Advanced Document : NeoPortal Document + advanced features - NeoPortal Advanced News Item : NeoPortal News Item + advanced features - NeoPortal Advanced Link : NeoPortal Link + advanced features; can use Javascript - NeoPortal Advanced File : NeoPortal File + advanced features - NeoPortal Advanced Image : NeoPortal Image + advanced features - NeoPortal Advanced Media : NeoPortal Media + advanced features; can open - NeoPortal Advanced External File : NeoPortal External File + advanced features - NeoPortal Advanced Folder : NeoPortal Folder + advanced features Container Types - NeoPortal Advanced Article : NeoPortal Article + advanced features; as of 0.9a, all NeoPortal Advanced Element types are addable only to this container type Element Types - NeoPortal Advanced Page Element : NeoPortal Page Element + NeoPortal Advanced Document - NeoPortal Advanced Form Element : NeoPortal Form Element + NeoPortal Advanced Document - NeoPortal Advanced Table Element : NeoPortal Table Element + NeoPortal Advanced Document - NeoPortal Advanced Link Element : NeoPortal Link Element + NeoPortal Advanced Link - NeoPortal Advanced Media Element : NeoPortal Media Element + NeoPortal Advanced Media - NeoPortal Advanced File Element : NeoPortal File Element + NeoPortal Advanced File - NeoPortal Advanced Image Element : NeoPortal Image Element + NeoPortal Advanced Image - NeoPortal Advanced External File Element : NeoPortal External File Element + NeoPortal Advanced External File Common Features for All NeoPortal Content Types As of version 0.9a, NeoPortal Content Types come with the following common features. Content Caching Document-like types can cache rendered content. These types have two common properties: 'text' and 'cooked_text'. The 'text' property holds the raw content while the 'cooked_text' property contains the rendered content. You SHOULD never get 'text' and 'cooked_text' properties directly. You must let NeoPortal Content Objects examine their values first. NeoPortal Content Types define the following methods to get and set their content: - getRawNeoPortalContent() : return raw content ( self.text ) - setRawNeoPortalContent( self , text='' ): set text - getRenderedNeoPortalContent() : return cooked_text ( some NP objects re-render their raw content depending on REQUEST ) Content Renderers ( Cookers ) A NeoPortal renderable content class ( document-like classes ) define the '_cookContent' method which is used to pre-cook content. The 'Format' Dublin Core element defines the behavior of the '_cookeContent' method: 'structured-text', for example, causes the content to be rendered into Structured Text. **Embeddable** NeoPortal Content Types also define a private method called '_renderEmbeddedObjects'. The method searches the content trying to find embedding markers ( note! I said markers, not objects, only references are stored in the content ) and render them by applying their 'call_view' skins to the embedded object. NeoPortal content embedding works like OLE. Inline commenting capability common to all document-ish NeoPortal Content Objects is one good example of how NeoPortal content embedding works. Another method 'iconizeNeoPortalContent' is available to all NeoPortal content classes that inherit the 'NeoPortalIconizableContent' mix-in class. As its name implies, **NeoPortal Iconizable Content** turn simple text notations into graphic icons, emoticons, for example:: ':-)' becomes a smiling icon ( :-) ) when rendered. Content cookers can be easily created. Only your imagination is the limit. A NeoPortal Content Object, when being saved, refers to the '_np_renderers' Class property to get its list of renderers. For example:: _np_renderers = ['_insertInlineCommentFormMarker', '_cookContent', \ '_renderInlineComments', '_renderEmbeddedObjects', \ 'iconizeNeoPortalContent'] The above is the default list of NeoPortal Content ( NP_Content.py ). The '_getNeoPortalContentRenderers' method should be used to get this property. Simply call '_updateNeoPortalContent' method and these renderers will be called in the defined order. If you want to skip a specific renderer you may directly call the '_renderNeoPortalContent' method with the new list of renders:: _renderNeoPortalContent( content=None, renderers=None, **kw ) The '_renderNeoPortalContent' method pushes the content ( self.getRawNeoPortalContent() is called when the 'content' argument is None ) through the list of the defined renders and return the rendered content. The '_updateNeoPortalContent' method internall calls the '_renderNeoPortalContent' to set the cooked_text value:: self.cooked_text = self._renderNeoPortalContent() Note the '_renderNeoPortalContent' method's '**kw' arguments. All renderers may define their own set of arguements. For instance, '_renderInlineComments' method defined in 'NeoPortalInlineCommentableContent' class accepts 'view_comment' argument which is used to filter out inline comments based on the argument's value: 0 for removing all comments or a certain creator's name to view only his comments:: _renderInlineComments( content, creator=None, REQUEST=None, **kw ) Object Embedding Document-like types can embed other objects. Embedded objects are rendered automatically in embedding object's view. Any changes in embedded objects are automatically updated in embedding object's view. Even inline comments can embed and render other objects; NeoPortal object embedding follows the rules of acquisition. Embeddable objects must provide a view named 'call_view'. For instance. NeoPortal Document comes with a call_view template 'call_doc.pt', which returns only the rendered content without any HTML or site headers. Embedding syntax is pretty simple: - __(id)__ # two underscores + opening '(' + the id of the object to embed +closing ')' + two underscores - __(image_1)__ # embeds an object whose id is 'image_1' Requested objects get rendered with their 'call_view' templates or replaced with the following error messages. - __(REQUESTED_OBJECT_DOES_NOT_SUPPORT_EMBEDDING: image_1)__ # not NeoPortal Content Type objects - __(CANNOT_EMBED_UNAUTHORIZED_OBJECT_IN_THIS_CONTEXT: image_1)__ # pure authorization errors - __(CANNOT_CROSS_EMBED: page_1)__ # page_1 alread embeded the current object; might fall into an infinite loop - __(NOT_AUTHRIZED_TO_EMBED_REQUESTED_OBJECT_IN_THIS_CONTEXT: image_1)__ # not owner of the object and it's not published - __(REQUESTED_OBJECT_DOES_NOT_SUPPORT_EMBEDDING_NO_CALL_VIEW: image_1)__ # NeoPortal Content Type objects but no call views found - __(REQUESTED_OBJECT_NOT_FOUND: image_1)__ # not found These error messages are only saved in the rendered ( cached ) content of the object. When embedded objects become available and you re-edit the embedding object, their call views will get rendered into the embedding object's cached content storage: 'cooked_text'. NeoBoard Articles also inherit from the NeoPortalEmbeddableContent class: an article can embed its attachments, for example, to render their 'call views' anywhere in the article body. Inline Commenting Document-like types are inline-commentable. Backtalk like inline comments can be added and users can view only selected commentor's comments ( works like MS-Word's annotations ) or can choose to view or not to view all the comments on the fly. When a user chooese not to view comments or to view only a certain person's commments, NeoPortal Content Objects re-render their content instead of resorting to their content caching machinery. IP-based Spam Blocking Document-like types are spam-blockable. IP-based spam blocking prevents duplicate postings in a given interval from the same IP address. One can't comment on an article twice in less than 10 seconds, for example, to prevent DOS-like malicious duplicate postings. IP-based Daily Access Log IP-based access logs are saved in a special container inside a NeoPortal Content Object and the container is purgeable by a given interval. Logs are viewable via 'log' object tab. Content Rating All NeoPortal Content Types are ratable. The max and min rating values can be changed via the 'np_options' object tab. Only one rating value can be stored from a single IP address: that is, one can't rate the same content twice but can change his/her rating value by rating the content again with a different value. New Discussion Tool NeoBoard gets instantiated instead of the stock CMF discussion container when discussion gets activated for a NeoPortal Content Object. Users can enjoy all the bells and whistles NeoBoard comes with. When discussion is enabled, an object tab labeled 'discussion' appears and clicking the tab leads to the NeoBoard instance. A list of articles also appear at the bottom of the object's view if one or more articles found. Note that NeoPortal Element Types cannot have their own discussion boards. They make use of their container's discussion board. ( It seemed awful lot of waste for every element to have its own NeoBoard instance. One board for a container should suffice. ) All options can be toggled on and off via 'np_options' object tab Common Features for NeoPortal Advanced Content Types As of version 0.9a, NeoPortal Advanced Content Types come with the following common features. DTML Handling Document-like types can render DTML tags in a given context. dtmlDescription Method All NeoPortal Advanced Content Types defines a method 'dtmlDescription' that returns the 'description' attribute value after rendering any DTML tags found in it. Advanced Features for Container Types NeoPortal Containers give NeoPortal Elements sequenceable id's at the time of their addition. Any given id's via Elements' contructor methods are ignored unless the 'no_id_check' argument is set to true when calling '_setObject'. In addition, NeoPortal Containers can re-number its Elements' id's if needed and navigation menus are automatically set up in a container view. We can make use of this automatic-ordering feature of a NeoPortal Container to make a photo album in a few seconds, for example: just add any number of NeoPortal Images into a NeoPortal Article. That's your photo album. NeoPortal External Files can be created in a batch inside a NeoPortal Container. For instance, a member can upload a set of image files to a directory under authorized file bases and import them as NeoPortal External Files. One can even add all the files found in subdirectories. NeoPortal External File Security You can set authorized file bases inside a file called 'file_bases.props' that resides in the 'data' directory under the NeoPortal Library package directory:: NeoPortalLibrary/ /data/file_bases.props # filepath bases - multiple bases allowed # unused bases may be commented out # zero base means you'll allow any directory depending on Zope user's file permissions #/home/ZopeHome/archives for unix/linux #\\ZopeHime for windows For example, if you set '/home/ZopeHome/archives' as the only authorized file base inside this file, members cannot set file paths of their NeoPortal External Files above this file base:: authorized file path: /home/Zopehome/archives/cool_images.zip unauthorized file path: /home/cool_images.zip NeoPortal Tools As of version 0.9a, NeoPortal Content Pak comes with thre distinct NeoPortal Tools: NeoPortal External Access Tool, NeoPortal Discussion Tool and NeoPortal Properties Tool. NeoPortal External Access Tool NeoPortal External Access Tool makes it possible to access worlds outside of Zope: filesystem, RDBMS, for example. As of version 0.9a, only filesystem can be accessed via NeoPortal External Files. NeoPortal Discussion Tool NeoPortal Discussion Tool allows NeoPortal Content Types to have NeoBoard instances as discussion container instead of CMF's stock discussion items container. NeoBoard instance gets instantiated when an owner/manager of an instance turns on the 'Allow Content Discussion' option. NeoPortal Properties Tool NeoPortal Properties Tool allows for site-wide configuration of NeoPortal Content Type options. Inidividual instances may override this site-wide configuration by setting their own values. Setting Content Type Options Zope's acquisition rules also apply to NeoPortal Content Types: an instance can set its properties individually or acquire them from its parent by context. Site-wide configuration is possible with the NeoPortal Properties Tool. Automatic Upgrade Old NeoPortal Content Pak instances can detect updated NeoPortal classes when you install a newer version of NeoPortal Content Pak. Upgrading from previous versions of products has never been easier: a click-and-go upgrade. i18n NeoPortal Content Pak has been built with i18n in mind since day one. See the 'i18n.txt' in the NeoPortal Library package directory for more info on how to activate the i18n machinery. Note that all internal messages NeoPortal Content Pak spews out go into a 'neoportal' domain message catalog. You should have a message catalog with 'neoportal' domain for this to work. Known Bugs If you embed references to other objects when **creating** document-like content, do not change the name (id) of the content object. NeoPortal Embedding System renders the references in the 'current' context, which gets changed when you rename the context. It's a minor issue and easily correctible by re-saving (re-editing) the content. It's not a bug, but NeoPortal News Items won't show up in your recent news box slot. If you want them to appear in the box, edit the 'news.pt' Plone skin:: results1 python:container.portal_catalog(meta_type='News Item', \ sort_on='created', sort_order='reverse',review_state='published'); results2 python:container.portal_catalog(meta_type='NeoPortal News Item', \ sort_on='created', sort_order='reverse',review_state='published'); results3 python:container.portal_catalog(meta_type='NeoPortal Advanced News Item', \ sort_on='created', sort_order='reverse',review_state='published'); results python: results1 + results2 + results3; --------------------------------------------------------------- To the dedicated staff at NeoQuest, language is not a problem to be dealt with, but an art waiting to be performed. --------------------------------------------------------------- Wankyou Choi CEO/President NeoQuest Communications, Inc. 3rd Floor, HMC Bldg., 730-14, Yoksam-dong, Kangnam-gu Seoul, Korea Tel: 82-2 - 501 - 7124 Fax: 82-2-501-7058 Corporate Home: http://www.neoqst.com Personal Home: http://www.zoper.net, http://www.neoboard.net e-mail: wankyu(a)neoqst.com ---------------------------------------------------------------

1 0

NeoPortal Library 0.9a has been released
by Wankyu Choi 15 Dec '02

15 Dec '02

I'm pleased to announce that NeoPortal Library 0.9a has been released. NeoPortal Library is an ever-growing collection of modules on which I'm planning to build a number of Zope/CMF/Plone products. You can download NeoPortal Library from http://www.zoper.net/Downloads In itself, NeoPortal Library won't be visible through ZMI. The modules in the library are supposed to be used only by my personal products. The ultimate goal of NeoPortal Library and the products that uses it is help create a sophisticated portal site powered by Zope/CMF/Plone. NeoPortal Library is, and will be, required by the following Products being actively developed by me: - NeoBoard : a threaded message board - NeoPortal Content Pak : a set of advanced content types used in a CMF/Plone site You must install this library to use NeoBoard or NeoPortal Content Pak. These products are also downloadable from http://www.zoper.net/Downloads. Sincerely, Wankyu Choi --------------------------------------------------------------- To the dedicated staff at NeoQuest, language is not a problem to be dealt with, but an art waiting to be performed. --------------------------------------------------------------- Wankyou Choi CEO/President NeoQuest Communications, Inc. 3rd Floor, HMC Bldg., 730-14, Yoksam-dong, Kangnam-gu Seoul, Korea Tel: 82-2 - 501 - 7124 Fax: 82-2-501-7058 Corporate Home: http://www.neoqst.com Personal Home: http://www.zoper.net, http://www.neoboard.net e-mail: wankyu(a)neoqst.com ---------------------------------------------------------------

1 0

NeoBoard 1.1b has been released
by Wankyu Choi 15 Dec '02

15 Dec '02

I'm pleased to announce that NeoBoard 1.1b has been released. For info on upgrading from previous versions, please read UPGRADE.txt. Especially users of 1.03 version MUST follow the exact upgrade steps specified in the document. >From NeoBoard 1.1b on, NeoPortal Library is required. If you want to use NeoBoard 1.1b in a CMFPone site. Please upgrade to Plone Beta3. What is NeoBoard? NeoBoard is a threaded message board product. NeoBoard is unique in that it can be used either as a standalone Zope product or as a CMF product or even as a CMF Plone product. It retains the same **Plonish** look and feel with or without Plone. Demo You can test out NeoBoard at the Boards Section of the <a href="http://www.neoboard.net/Boards">NeoBoard.net</a> site. Download You can download NeoBoard at the Download Section of the <a href="http://www.neoboard.net/Downloads">NeoBoard.net</a> site. NeoBoard Features NeoBoard bases most of its core features on NeoPortal Library. Bare Zope and CMF/Plone Support ( new since 1.1a ) NeoBoard can be used either as a standalone Zope product or as a CMF or Plone product. NeoBoard retains the same look and feel no matter where you install it. CMF-like Skins ( new since 1.1a ) NeoBoard's skins work exactly the same as CMF's. NeoBoard's skin system is modeled after CMF. If a skin works with CMF, it'll work with NeoBoard. Plone is not a must for NeoBoard to work, but NeoBoard borrowed much from Plone's skins. With or without Plone, NeoBoard looks Plone-ish. Collapsible Views ( new since 1.1b ) NeoBoard's article list can be collapsed or expanded. When the list is in the collapsed view, articles with replies will show *the number of replies* after their titles. When the list is in the expaneded view, articles with inline comments will show *the number of comments* after their titles. Sortable Views ( new since 1.1a ) NeoBoard's articles can be sorted on a number of properties: creation date (default), category, the number of accesses, and the number of ratings. Click on a corresponding table header and you'll get a sorted list on that property. Clicking the same header again will give you a reverse-sorted list on that property. Minimal Article Workflow Support ( new since 1.0b ) NeoBoard Articles should be approved for public viewing. The auto-approval option can be turned on if approving articles ( or moderating them ) seems cumbersome. NeoBoard managers can disapprove ( retract ) articles at any time. Publishing ( new since 1.0b ) NeoBoard can be published or retracted. You can even set a date on which to publish an NeoBoard instance. Simple Local Roles ( new since 1.0b ) The owner of a NeoBoard instance can delegate his/her manager role to other normal users via NeoBoard Managers form. NeoBoard managers are **NOT** Zope managers. Their roles are restricted to maintaining the given NeoBoard instance. Article Categories ( new since 1.0b ) NeoBoard Mangaers can define article categories under which to group NeoBoard Articles. These categories don't have anything to do with Zope Catalogs. One can view only those articles that fall under a selected category. Flexible Authentication Schemes ( new since 1.0b ) NeoBoard can either use ACL authentication or its own password-based per-article authentication scheme depending on the 'use_acl_auth' option value. When using ACL authentication, NeoBoard causes a login popup menu to appear by raising the 'Unauthorized' error when a unauthenticated user tries to access restricted resources such as an article posting form. When not using ACL authentication, NeoBoard presents username/password fields for posting/modifying/deleting articles or comments. Anonymous Posting ( new since 1.1b ) NeoBoard managers can choose to allow anonymous users to post articles/comments even when ACL user authentication is in use. Batch Actions ( new since 1.0b ) NeoBoard managers can copy, move, delete, approve, disapprove articles in a batch. Cataloging ( new since 1.0b ) NeoBoard articles and their attachments are all catalog-aware. One can search NeoBoard articles on any combinations of the following fields: - Title - Body - Username - Email - Attachment ( title, description, filename combined) Note that NeoBoard's search capability relies on ZCatalog, which, in turn, is dependent upon the underlying splitters. If your language lacks a splitter, you're out of luck. Don't come complaining about searching not working unless you're **DAMN** sure you have a right splitter. I, myself, can't search my own NeoBoards since there's no Korean splitter yet:-( Some day... I might develop one;-) Content Caching ( new since 1.1b ) NeoBoard Articles can cache rendered content. NeoBoard Articles have two common properties: 'text' and 'cooked_text'. The 'text' property holds the raw content while the 'cooked_text' property contains the rendered content. Content Iconization ( new since 1.1b ) NeoBoard Articles inherit the 'NeoPortalIconizableContent' mix-in class from NeoPortal Library. As its name implies, **NeoPortal Iconizable Content** turn simple text notations into graphic icons, emoticons, for example:: ':-)' becomes a smiling icon ( :-) ) when rendered. Object Embedding ( new since 1.1b ) NeoBoard Articles can embed other objects. Embedded objects are rendered automatically in embedding object's view. Any changes in embedded objects are automatically updated in embedding object's view. Even inline comments can embed and render other objects; NeoPortal object embedding follows the rules of acquisition. Embeddable objects must provide a view named 'call_view'. For instance. NeoPortal Article Attachment comes with a call_view template 'neoboard_article_attachment_call_view.pt', which returns only the rendered content without any HTML or site headers. Embedding syntax is pretty simple: - __(id)__ # two underscores + opening '(' + the id of the object to embed +closing ')' + two underscores - __(image_1)__ # embeds an object whose id is 'image_1' Requested objects get rendered with their 'call_view' templates or replaced with the following error messages. - __(REQUESTED_OBJECT_DOES_NOT_SUPPORT_EMBEDDING: image_1)__ # not NeoPortal Content Type objects - __(CANNOT_EMBED_UNAUTHORIZED_OBJECT_IN_THIS_CONTEXT: image_1)__ # pure authorization errors - __(CANNOT_CROSS_EMBED: page_1)__ # page_1 alread embeded the current object; might fall into an infinite loop - __(NOT_AUTHRIZED_TO_EMBED_REQUESTED_OBJECT_IN_THIS_CONTEXT: image_1)__ # not owner of the object and it's not published - __(REQUESTED_OBJECT_DOES_NOT_SUPPORT_EMBEDDING_NO_CALL_VIEW: image_1)__ # NeoPortal Content Type objects but no call views found - __(REQUESTED_OBJECT_NOT_FOUND: image_1)__ # not found These error messages are only saved in the rendered ( cached ) content of the object. When embedded objects become available and you re-edit the embedding object, their call views will get rendered into the embedding object's cached content storage: 'cooked_text'. An article can embed its attachments, for example, to render their 'call views' anywhere in the article body. Inline Commenting ( new since 1.1a ) NeoBoard Articles are inline-commentable. Backtalk like inline comments can be added and users can view only selected commentor's comments ( works like MS-Word's annotations ) or can choose to view or not to view all the comments on the fly. When a user chooese not to view comments or to view only a certain person's commments, NeoBoard Articles re-render their content instead of resorting to their content caching machinery. Note that articles with inline comments cannot be deleted by their posters. If a creator of an article attempts to delete an embedded inline comment, it'll still appear as a comment that lost its context ( neoboard_lost_article_comment_view.pt ). The above restriction doesn't apply when a NeoBoard manager deletes articles. IP-based Spam Blocking ( new since 1.1b ) NeoBoard Articles are spam-blockable. IP-based spam blocking prevents duplicate postings in a given interval from the same IP address. One can't comment on an article twice in less than 10 seconds, for example, to prevent DOS-like malicious duplicate postings. IP-based Daily Access Log ( new since 1.1b ) IP-based access logs are saved in a special container inside NeoBoard Articles and the container is purgeable by a given interval. Logs are viewable via 'log' button in an article view. Content Rating ( new since 1.1b ) NeoBoard Articles are ratable. The max and min rating values can be changed via the configuration menu. Only one rating value can be stored from a single IP address: that is, one can't rate the same content twice but can change his/her rating value by rating the content again with a different value. DTML Handling ( new since 1.0b ) NeoBoard Articles can render DTML tags in a given context if 'DTML' is chosen for a renderable format. Moving or Copying Articles Between Multiple NeoBoards ( new since 1.0b ) NeoBoard managers can copy or move NeoBoard Articles between two NeoBoard instances. Two restrictions apply: - Both instances must be using the same authentication scheme - Both instances must be using the same attachment storage type ( attachment wrapper ) Unlimited Number of Attachments ( new since 1.0b ) NeoBoard Articles can have an unlimited number of attachments either as stock Zope Files or NeoPortal External Files. If the size of attachments is of concern, you can opt for NeoPortal External Files as attachment wrapper. Attachments are content-type-aware, which means, they'll display icons corresponding to their content types. Note the following when you choose to use the filesystem for attachment storage: 1. NeoPortal External Files are just wrappers for actual files on the filesystem. When you copy or move articles, their attached files on the filesystem get also copied or moved to proper locations. However, if you delete articles with attachments, their linked files on the filesystem are **not** deleted but renamed to filename+**._temp**. You should manually delete these remnants. ( For those who're curious why... You can't distinguish when Zope is copying/moving or deleting these files. In any case, Zope first **DELETES** these files. If it's a copy or move operation, NeoBoard can smartly figure that out. But deleting is a whole lot different matter. ) 2. If you copy your NeoBoard instance, its archive path gets also renamed. Before **RENAMING** the copied NeoBoard instance, go to the manger optioins menu and rename the archive path first. That's the only chance you got. NeoBoard doesn't allow you to change its archive path with one or more articles in it. NeoPortal External File Attachment Security ( new since 1.1b ) You can set authorized file bases inside a file called 'file_bases.props' that resides in the 'data' directory under the NeoPortal Library package directory:: NeoPortalLibrary/ /data/file_bases.props # filepath bases - multiple bases allowed # unused bases may be commented out # zero base means you'll allow any directory depending # on Zope user's file permissions #/home/ZopeHome/archives for unix/linux #\\ZopeHime for windows For example, if you set '/home/ZopeHome/archives' as the only authorized file base inside this file, users with permissions to add NeoBoard/CMFNeoBoard instances cannot set their archive paths above this file base:: authorized archive path: /home/Zopehome/archives/my_dir unauthorized archive path: /home/archives Automatic Upgrade ( new since 1.1b ) Old NeoBoard instances can detect updated NeoBoard classes when you install a newer version of NeoBoard. Upgrading from previous versions of products has never been easier: a click-and-go upgrade. i18n ( new since 1.1a ) NeoBoard supports i18n of its messages. See the 'i18n.txt' in the NeoPortal Library package directory for more info on how to activate the i18n machinery. Note that all internal messages NeoBoard spews out go into a 'neoportal' domain message catalog. You should have a message catalog with 'neoportal' domain for this to work. Known Bugs When exporting/importing a NeoBoard instance, all articles lose their creation date values. There's a workaround: first set the export flag using the manager menu before you export an instance. Then when you finished importing that instance, revisit the manager menu and follow the instruction NeoBoard presents; the imported NeoBoard instance will refuse to work until you do that. Sincerely, Wankyu Choi --------------------------------------------------------------- To the dedicated staff at NeoQuest, language is not a problem to be dealt with, but an art waiting to be performed. --------------------------------------------------------------- Wankyou Choi CEO/President NeoQuest Communications, Inc. 3rd Floor, HMC Bldg., 730-14, Yoksam-dong, Kangnam-gu Seoul, Korea Tel: 82-2 - 501 - 7124 Fax: 82-2-501-7058 Corporate Home: http://www.neoqst.com Personal Home: http://www.neoboard.net e-mail: wankyu(a)neoqst.com ---------------------------------------------------------------

1 0

A Boy and His Catalog: Taming ZCatalog for 2.6.1 and Beyond
by Casey Duncan 13 Dec '02

13 Dec '02

A recreational journey into the land of code optimization and other fun misadventures. As a bonus, learn how to make your ZCatalog searches the envy of all your peers: http://www.zope.org/Members/Caseman/ZCatalog_for_2.6.1 Enjoy. -Casey PS: Happy holidays!

1 0

Zope 2.6.1 Beta 1 Released
by Matthew T. Kromer 12 Dec '02

12 Dec '02

Zope 2.6.1 Beta 1 Released Created by zopematt <http://www.zope.org/Members/zopematt>on 2002/12/12. ZOPE 2.6.1 Beta 1 Released Zope 2.6.1b1 represents a development step in the next Zope release formed with a large number of community contributions. You may download Zope 2.6.1b1 from Zope.org: http://www.zope.org/Products/Zope/2.6.1b1/ Users of the Zope source release should note that Python 2.1.3 is now the required platform. Python 2.1.3 includes a fix to an issue that could cause crashes in Zope. Particular features of interest in Zope 2.6.1b1: * Catlog changes to speed sorting and lower memory consumption * ZODB Deadlock avoidance, fixed store order * Fixes for the rfc822 timezone / locale bugs in Zope 2.6.0 * Fixes for collector issues 597, 640, 646, 650, 651, 671, 694, 699, 703 For more information on what is new in this release, see the CHANGES.txt and HISTORY.txt files for the release: * http://www.zope.org/Products/Zope/2.6.1b1/CHANGES.txt * http://www.zope.org/Products/Zope/2.6.1b1/HISTORY.txt For more information on the available Zope releases, guidance for selecting the right distribution and installation instructions, please see: http://www.zope.org/Documentation/Misc/InstallingZope.html

1 0

IssueTrackerProduct-0.4.8a
by Peter Bengtsson 09 Dec '02

09 Dec '02

Glad to say I've managed to organise my IssueTracker product a bit. Many new features and bug fixes have only been in CVS and even the CVS has been a bit messy with a faulty version lying there for weeks. Now I've zipped a recent version for your pleasure. Check it out on http://www.zope.org/Members/peterbe/IssueTrackerProduct I still urge people to use the CVS version on SourceForge. Can you please submit any bugs to my SourceForge page at http://sourceforge.net/projects/issuetracker/ Peter NOTE!! When installing the latest version, make sure to Completely Re-deploy Standards so that you get the latest Send2Friends_script object.

1 0

Zwiki 0.13.1 released
by Simon Michael 07 Dec '02

07 Dec '02

A "bugfix-plus" release, for IssueNo0385 (missing permissions). Changes * finish the switch to modern security declarations, fixing IssueNo0385 and hopefully not breaking much else. * also send mailouts on page deletion and renaming Download: http://zwiki.org/releases/ZWiki-0.13.1.tgz or http://zope.org/Members/simon/ZWiki/ZWiki-0.13.1.tgz Regards, -Simon

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Zope-Announce December 2002