iungo.org » FAQ


Frequently asked questions. You should really read it...

  • What does iungo mean?
    "iungo" is latin for "connecting something". iungo connects some generic Zope-products (AbracadabraObject, PropertyTools, OrderedObjectManager, Epoz) with only a few lines of code to build up a nice-and-easy-to-use-system. iungo also want to connect people with information.
  • Why should I use iungo? There are already Plone, Silva, CPS, ...
    iungo tries to keep simple things simple. Anyone who mastered the basics of Zope should be able to do nice things with iungo which are hard to achieve with more complex frameworks for beginners. iungo tries to ease up the life of users (a simple interface), designers (no constraints in designing layouts) and developers (just vanilla zope).
  • When should I avoid iungo?
    iungo doesn't support a complicated role-& rights-system. iungo is designed from the fact, that most websites or intranets are maintained by only a few trusted power-users anyway. If you need different rights within one iungo-repository, you should better go with another framework, but it is still possible, because iungo is built on a central controller which can handle different rights if you want to.
  • Which skills do I need to run iungo?
    You only need some basic experience with the Zope-Management-Interface (ZMI) for installation & administration. If you've already worked with the ZMI, you'll get used to iungo in a few minutes.
  • Which skills are needed to customize iungo?
    Everyone who has read the Zope-Book should be able to build up own systems with iungo. You only need the native API of Zope to make use of iungo-repositories.
  • Why is iungo distributed as .zexp-File and not as a file-system-based product?
    iungo connects already existing and well tested frameworks with just a few lines of code. This code can easily be maintained "through the web". iungo also tries to overcome a builtin zope-limitation: A single Zope-Instance can only keep with one version of a product. If you need different versions, you'll need to setup different Zopes. This is a maintainance-nightmare, so iungo provides the possibility to be used in different versions within one Zope-Instance. iungo is therefore very ISP-friendly...;)
  • How can I change the look of the iungo-desktop?
    All important properties can be reached via the root-folder of your iungo-instance. Read more...
  • Does iungo support nice URLs?
    The iungo-desktop links documents and images with a special parameter named "iungo", so moving a page doesn't destroy any links between pages or images. But you can reach each document via a nice url, too. iungo uses a redirect if it detects the special request-parameter to resolve the correct page to display.  This way you have the best of both worlds: You can insert links into your documents which won't break, but you can reach all content via the dynamic built navigation with nice urls.
  • How can I disable the Copy/Move-Buttons for anomyous users?
    The Copy/Move-buttons are bound to the Zope-permission "Copy or Move". In a default Zope-installation this permission is granted to anomyous users (don't ask me what's the rationale behind this). Enter the ZMI and turn this permission off for Anonymous. Then the buttons will not be displayed until logged in.


iungo is Copyright © 2007 by Maik Jablonski