I suggest to revert the CCK features in DRUPAL-5.

1) Without this feature it's much easier to do straight upgrades to D6 and D7. See #373871: port Chessboard Renderer to D6
2) The feature has not been in any release, so no real harm done.
3) The project should make sure not to duplicate functionality from the Chess project.

I suggest to:
1) revert the CCK feature.
2) release another 5.x
3) straight port to 6 and release.
4) straight port to 7.
5) position this module in relation to the Chess project. Personally I think it would be good to focus on rendering stuff only (render API elements, theme_functions and display formatters). This project might turn into a rendering API to be used by other projects, who knows.

Feedback much appreciated.

Comments

eric_a’s picture

eric_a commented

Imagine a render API element type chessboard_position with properties like #notation_type, #notation, #pre_render, #diagram, #theme. This kind of stuff would make Chessboard Renderer do all kinds of rendering magic.

I'd submit D7 patches for this kind of stuff and do backports to 6 and 5 once we have straight ports to 6 and 7.

(The CCK-stuff can eventually be added back as a seperate module, so it becomes much easier to maintain the project.)

eric_a’s picture

eric_a commented
Title: Focus on being a rendering API » Focus on formatting and rendering

More accurate title. Accept a field (native chessboard type and possibly others one day), then format, render, theme. Providing database storage is probably better left to other projects (Chess for one), since providing a pluggable system for formatters, templates, and filters for different types is a big enough field in itself.

eric_a’s picture

eric_a commented
Title: Focus on formatting and rendering » Focus on API improvement and interfacing with Chess. Stick with 5.x-1.0 end-user feature set for now.
Category: task » feature

Actually, there is probably no real need to do a (full) CCK revert in DRUPAL-5 to get a D6 version of Chesboard Renderer going. That would be the same end-user feature set as Chesboard Renderer 5.x-1.0

I still think that it would be great if Chessboard Renderer would start providing theme functions/templates and element building functions first. This would allow for interfacing with the Chess project.

I'll start a new issue for the theming request.

eric_a’s picture

eric_a commented

See #765582: Add theming layer to Chessboard Renderer

eric_a’s picture

eric_a commented
Title: Focus on API improvement and interfacing with Chess. Stick with 5.x-1.0 end-user feature set for now. » Let Chessboard Renderer provide services to chess projects that provide game play and storage
Status: Active » Postponed

It is probably a good idea to postpone this to the moment when there is active development and concrete progress.
At that time getting the Chess project maintainers and community involved seems like the way to go.

eric_a’s picture

eric_a commented
Version: 6.x-1.x-dev » 7.x-2.x-dev
eric_a’s picture

eric_a commented
Issue summary: View changes
Status: Postponed » Fixed

We've got a Piece Placement Data Definition, a Data Type, templates and a render element type.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.