eZ Community » Forums » Suggestions » Roadmap for 4.4. Any Ideas?
expandshrink

Roadmap for 4.4. Any Ideas?

Roadmap for 4.4. Any Ideas?

Tuesday 23 February 2010 8:19:52 pm - 41 replies

With 4.3 pretty close to its stabilization deadline, it's time to start the drums rolling for the roadmap that will lead to the next version. Much in the same vein as the open discussion that took place on this forum about the improved admin interface for 4.3, I think the community can contribute in shaping the greatest version-to-be ever.

My own ideas wishes: make 4.4 a developer's best friend - keep improving the new interface introduced in 4.3, but focus on simplifying the developer's job.

  • move the webshop completely out of the kernel into a new extension - a leaner, meaner base install is a boon
  • move all code for displaying/editing templates and the RAD page out of the kernel AND start developing it with: a rad wizard for every feature commonly found in extensions: datatypes, fetch functions, functions, workflow events, cronjobs, etc... merge code from ezgeshi for syntax hilite and from ezcodesniffer for compliance checking
  • set up a proper dependency management framework for extensions
  • allow extensions to install/deinstall tables and data when enabled/disabled
  • improve the interface used for creating and installing packages, making more apparent the distinction from downloaded packages and packages locally created; allowing to create new version of local packages; allowing to pick remote package repos via gui
  • rebase the ez package format on pecl

Thursday 25 February 2010 12:08:56 pm

Maybe we should be running a competition: Make an override ezwebin in projects.ez.no which is fully backwards compatible, but which uses a simpler DOM and smaller stylesheets. Smallest file size wins.

Of course a new design wouldn't go astray either, but i think backwards compatibility and upgradability are paramount.

We should be aiming at one named wrapper for each template, in most cases any more is just indulgence.

Thursday 25 February 2010 9:11:32 pm

I think there could be a new forum (or similar way) of knowing “How to’s” that will lead us to know simple and complex tasks.

There are so many features in ez that trying to understand all is impossible so when a new challenge is faced in a new project that involves an ez site you end up with a headache just searching and joining all pieces of information together (and sometimes we end up with a not so good solution at all)

It will help the newbies and older users to know the possibilities that ez could add to their projects and ease the information flow of discovering things that we could do that goes beyond our current knowledge, it could help newbies to get ideas on how ez can solve problems and thus compare the advantages and disadvantages of ez with other open source CMS’s.

A topic in a forum (or else) of “How to’s” could have links to extensions, new projects arising, pieces of code… and if moderated have their own roadmap to follow and contribution by the audience.

I did my own howtos as I went. Does seem like a waste for others to build their own howtos instead of building on a foundation.

Nicolas already pointed out that any further discussion re newbie help logically fits in a different thread..

http://share.ez.no/forums/general...ng-time-required-to-grasp-ez-publish

Cheers!

Friday 26 February 2010 1:45:37 pm

A few ideas:

  • REST / SOAP endpoints for integration with external systems (CRUD operations on content objects). There are a few extensions on this matter, but it would be nice if we had supported way of doing it
  • Drag / drop of objects in administration interface. It would be great if we could drag nodes from sub items block to content tree.
  • policies on attributes : +1
  • workflow improvment (more triggers) +1

Friday 26 February 2010 4:46:42 pm

Good good ideas !

I add a big personal wish :

* Drag / drop datatypes re-ordering in class/edit view, that would immediatly refresh the content attribute priority id field's value

Modified on Friday 26 February 2010 4:47:10 pm by Ronan Guilloux

Friday 26 February 2010 6:45:26 pm

Spend more time on bringing the community patches into the core.

Nothing else so far.

Sunday 14 March 2010 9:30:52 am

Yes, I second Björns demand (Spend more time on bringing the community patches into the core.) and

#015700: eZ Flow ignores locations

http://issues.ez.no/IssueView.php?Id=15700

This is ugly for the reuse of content for different sites with one online editorial department but different sites or for different channels. Since it is stored in the database this should be easy to implement.

Edit: Only style.

Modified on Tuesday 16 March 2010 8:30:55 am by Ekkehard Dörre

Sunday 14 March 2010 12:09:57 pm

#015700: eZ Flow ignores locations

http://issues.ez.no/IssueView.php?Id=15700

This is ugly for the reuse of content for different sites with one online editorial department but different sites or for different channels. Since it is stored in the database this should be easy to implement.

How exactly would you like to see that fixed ? How should the location be chosen ? Some UI when it gets chosen and has several location ? A "closest" location detector depending on the location of the currently edited frontpage ? Some INI configuration ?

Monday 15 March 2010 8:03:33 pm

#015700: eZ Flow ignores locations

http://issues.ez.no/IssueView.php?Id=15700

This is ugly for the reuse of content for different sites with one online editorial department but different sites or for different channels. Since it is stored in the database this should be easy to implement.

How exactly would you like to see that fixed ? How should the location be chosen ? Some UI when it gets chosen and has several location ? A "closest" location detector depending on the location of the currently edited frontpage ? Some INI configuration ?

The issue reported is simple enough:

make sure objects with multiple locations can be added with the location from the result of the content/browse operation ... which could be a secondary location

Tuesday 16 March 2010 9:30:56 am

Yes,

  • portal 1 with eZ Flow frontpage
  • - news for 1
  • - - Article 1.1
  • - - Article 1.2 main node NodeID 345
  • - news for both
  • portal 2 eZ Flow frontpage
  • - news for 2
  • - - Article 2.1
  • - - Article 1.2 second node NodeID 456

You browse in portal 1 for - news for 1 - - Article 1.2 main node and ObjectID and NodeID 345 is stored.

You browse in portal 2 for - news for 2 - - Article 1.2 main node and ObjectID and NodeID 456 is stored.

Result: You'll have clean URLs:

http://www.example.com/news_for_1/Article_1_2

http://www.other_example.com/news_for_2/Article_1_2

Thanks and greetings

Wednesday 17 March 2010 3:34:58 pm

Policies on attributes : +1

Voting for policies on attribute level !
This is a MUST have !

Wednesday 24 March 2010 3:23:11 pm

Hi,

So here is my Christmas wishes list:

- to have an alternative to XML Block as rich-text solution. It is frustrating to be so limited with the current Online Editor because of the constrainsts of ezxmltext .
Andre did already a great work to prepare this new version of the Online Editor. But still, it remains not possible for a user to select the color of a text, or to apply many style changes in the same paragraph. In fact, it could be very nice to be able to provide to our end users an editor interface as easy to use as the one they can use anywhere else.
There might be a lot of good reasons to keep XML Block (features, existing data, ...) but maybe either adding a new datatype or an attribute ("strict"blunk.gif Emoticon to the ezxmltext could be a way to propose an alternative for people looking for more flexible online editing solution

- easy way to update classes between dev and prod environment (when adding / updating / removing attributes)

- homogeneous way of overriding css, design, templates, settings... (so that there is a clear order of extension that we can safely use when building customizable multi-site installation)

- +1 for a dedicated shop extension

- +1 policies on attributes

Thanks for all the great work that you are doing to provide us with a very powerful tool.

Hakim

Wednesday 24 March 2010 4:15:39 pm

- to have an alternative to XML Block as rich-text solution. It is frustrating to be so limited with the current Online Editor because of the constrainsts of ezxmltext .

Hakim,

I am rather think that ezxmltext is one of the main advantage of eZ Publish ! For example in Drupal rich text stores directly HTML and you have no control on how the content is display on different media. It is a great lack for cross media publishing ! eZ Publish override systems will allow you to have for example an other way of displaying media on another siteaccess (let's say a mobile one) !

Cheers blunk.gif Emoticon

Wednesday 24 March 2010 4:59:32 pm

Hi Matthieu,

>>For example in Drupal rich text stores directly HTML and you have no control on how the content is display on different media

I do understand this concern, although in my case it is more theorical than practical (since I never get to build another site access for another media - mobile, ...)

I was proposing to have an alternative, not to replace the XML Block (which may be useful for some use case as you stated).

I may be wrong, but I guess that there are probably more eZ sites that are delivered to only one media rather than to many. If so, it would then make sense to provide flexibility for these sites.

Hakim

Wednesday 24 March 2010 5:15:29 pm

I do understand this concern, although in my case it is more theorical than practical (since I never get to build another site access for another media - mobile, ...)

I was proposing to have an alternative, not to replace the XML Block (which may be useful for some use case as you stated).

I may be wrong, but I guess that there are probably more eZ sites that are delivered to only one media rather than to many. If so, it would then make sense to provide flexibility for these sites.

Ok, but I think there is lots of other arguments in favor of ezxml. For example, browsing the content tree and inserting any object as embed (with a dedicated template for embeded). Not sur you can do that with Drupal happy.gif Emoticon

But I understand that your talking about an alternative but I don"t really see the need ... (It reminds me that you can add a color picker in ezoe you should see ezoe.ini but I'm not sure)

Wednesday 24 March 2010 10:37:24 pm

I would like 4.4 to have better documentation and tutorials for beginners. Charts, visualizations, A3 posters, screenrecordings of procedures etc.

 

A thing I like with EZ is the simple way to make new inputclasses. Its very easy to get new information into EZ. I would also like a similar way to get information out of EZ or at least some better explanations.

Saturday 24 April 2010 12:27:45 pm

@original post: "allow extensions to install/deinstall tables and data when enabled/disabled"

This is getting closer in 4.3 already: the correct file for the new db tables is share/db_schema.dba. Once it is there, 1-enable the extension, then 2-go to system/update check/db consistency page. You will get a sql script suggesting to add the new tables

@Ivo: "export to csv functions for objects, collections,shop,..."

The closest is probably the convert-any-template-object-to-php-array tpl operator in ggxmlview, see: http://projects.ez.no/ggxmlview/news/ggxmlview_0_2_released

@Mohamed: "Creating a dedicated (section/ tab / subtree) for custom settings and utility content objects in eZ Pulbish Admin interface"

The more I think of it, the more I am convinced we should use the design subtree for this. An available subtree of content, almost empty. Objects in there are not visible by default. You just need to: 1-assign create permissions for some content classes in the design section, 2-make this subtree visible by overriding the template used to display the left column in the design tab

@Nicolas: "more native workflows"

feel free to join the ezworkflowcollection effort

@Igor: "REST / SOAP endpoints for integration with external systems"

take a look at ezwebservicesapi. A step in the right direction, I think

Thursday 29 April 2010 5:34:01 pm

For the love of all that's holy, PLEASE consider adding a unified upgrade path. Having to run a billion PHP and SQL scripts from, say, 4.0.0 to 4.3 is presently very, very error prone.

A single "Click to Upgrade" button, ala Wordpress, would be much safer and less time-consuming.

Monday 12 July 2010 8:52:59 pm

Gaetano, regarding the share/db_schema.dba that is now (eZ Publish 4.3 and higher) recognized by eZ Publish inside extensions, is there a way to generate that easily from an existing eZ Publish database, for just a certain predefined set of tables - the one belonging to the extension.

./bin/php/ezsqldumpschema.php currently does not seem to have an option to specify the tables to dump. Is there another script usable for this, or could ezsqldumpschema.php be enhanced so it accepts a list of tables? Such a feature would certainly help developers to get their extensions that still contain a .sql schema file up to date, and hopefully opens up the road for more cross-database compatible extensions.

Monday 12 July 2010 8:55:18 pm

Seems like I was looking in the right direction, as there is an enhancement request already: http://issues.ez.no/IssueView.php?Id=15450. Unfortunately it hasn't been touched for a couple of months.

Monday 10 January 2011 11:36:57 am

Policies for attributes is really missing. ^^
Thanks to think about for futur releases...

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from