infoglue user conference autumn 2009 stockholm 2009-12-11

InfoGlue User Conference Autumn 2009

Stockholm2009-12-11

-2-© InfoGlue Community | 23-04-19

Agenda

Preview InfoGlue 3.0 part 1

Break with sandwich

Preview InfoGlue 3.0 part 2

Lunch

Feedback / discussion etc and info on remaining dev-process, timetable etc

Break if we need one

What’s new in the upcoming 2.9.8.x?


InfoGlue 3.0 practicalities

Will keep backward compability with 2.x installations– Any changes to data-model will be extensions or seemless transfers– No need to rewrite templates etc. – Only small changes to java-API:s

Will perhaps come with a change in license. – Proposal is to change to dual license: GPL v3 for Core and LGPL for deliver-

related parts. Technically it’s othewise difficult to keep templates etc you write for clients not be infected by GPL.

– Feedback here? Any thought or suggestions?

Support for IE6 is dropped completely now in the admin-tools. For sites it’s up to you as before.

Dropping support for Java 1.4, Tomcat 4, MySQL 4 probably.

The process is still open for minor changes and now is the time to influence


InfoGlue 3.0 part 1

Biggest drawbacks with InfoGlue 2.x

– Outdated GUI design / code which was hard to style and develop further

– Image-buttons in menues etc, hard to translate and style

– Inflexible in many situations – hard to work with several tools concurrently

– FRAMES:based which made GUI very inflexible

– Inflexible toolbar-system.

– Lacked some central features we never got around to

– Still to little focus on usability in many areas

– Not good on small screen or in zoom-mode or for persons with handicap


New GUI-framework

Tab-based, Liquid, Outlook-inspired GUI improves user efficiency and experience– Easier to work on several parts at once without loosing context– Maximize tabs to use whole workspace area

● No more need to open in full screen mode in new window● Zoom etc and you still see a lot of your content / workarea

– Better support of persons with disabilities– Classic mode will be supported for a while

New CSS-based toolbar system with flexible design-possibilities– More extendable and flexible. Makes use of vertical axis better.

Skins and translations– You can now write and upload your own skins (css / images) or translations

as a zip / textfile and use directly without any difficult deployment.– Great if you wish to make a High-contrast skin or perhaps you are just dying

to create the ultimate ”Hello-Kitty”-theme.


New GUI-framework continued…

Better, faster and more accessible/useful internal search system. Early but with very big potential.– Allways available and not limited to contents– Keep context when clicking on found items– Lucene-based

New features in tree-controller

– Drag/Drop for move– Context-menu in content and structure

● Many operations supported● New features also (sort pages and hide/show pages). ● QUESTION: is it important to publish change in order and or hide page in

navigation? There is potentially a huge performance difference in which solution we choose.

– Structure tree now has a favourites-area which contains popular component you can drag/drop to supporting slot on page.● Do you want to be able to close that area?



Reinvented mydesktop– Could be a great starting point for some users– More focus on my personal work

● My latest pages / contents● Expiring content / pages● Workflows as before● Shortcuts

– Great discussion point – what would you like?

Wastebasked finally almost done– Will support seamless delete / restore of repositories, contents and pages

for now.

New dialog system– Inline (no more popups where possible)– If possible now always a confirmation to all actions– Question: Need for power users to disable confirmation screens?



Better online help system planned and set up.– We need writers of documentation. Suggestion is to make the help site a

context-sensitive ”wiki” on InfoGlue.org where many can contribute.– Any thoughts on this?

Improved error screen– Built-in bug-report facility

Improved application settings– Better division of settings– Current / default value visible next to setting

New infrastructure for extentionpoints to enable plugging in new tools in the GUI is in the plans but not sure if it will be finished in first version.


New GUI-framework - editing view

Tab-based also – to minimize and separate text, categories, cover and assets better

Widget based content type attributes

New WYSIWYG (CKEditor 3.01)– Possible to choose between old and new editor systemwide


Other new features

News in NiceURI to support language parameter– Better for search engines and predictable behaviour as not dependent on

browser settings or user sessions– Before two users entering the same url could get different languages.–

Possibility to state several domains to a site a let the domain select which language it should default to. – Great for mirrored sites

Now the only time browser language is selected is if none of these new features are used. For backward compability reasons. Or should we allways resort to master language for site if nothing else stated?


Some misc improvements

A new Eclipse IDE plugin version is on it’s way. Better version control support.

Support for automatic switch between HTTPS/HTTP based on protection settings

Better support for self-registration / self-management if building community sites.

Better performance is some areas

Some security improvements (we need community input here).– Correct level and risk-levels


Timetable and process

We have set the features to be included (which you have seen)

80% is allready implemented and the remaining 20% are not difficult

Then a big testing, bugfixing process will start and hopefully stabilize the version in a month or so.

Our aim is to release a final version during Q1 (before I go on maternity leave hopefully)– Will be followed by a couple of minor releases when users begin finding

issues or bugs

Our recommendation is to wait a month or two with production servers after the initial release to avoid the biggest problems. Early adopters will be highly valued and it will not hurt to use it in development servers as long as you know the limitations. The good thing is that the templates will not differ much as the taglibs etc have not changed much.


Timetable and process cont…

A new developer bundle will be package and released for version 3

We will call for more help in the community. People writing code (the last 20% ), documenting, supporting, testing or marketing the platform is wanted.

Peter J has set up a new forum which we should use as much as possible.

In the meantime we will release one or two more 2.9.x version. Here are some features they have/will include.


What’s next

We need InfoGlue to be more lightweight in installation and setup

Code refactoring to clear out some old dependencies

Move to Maven / SVN

Build a larger developer community or change community model

infoglue user conference autumn 2009 stockholm 2009-12-11

Documents