Hi,

This module looks to be an empty page.. I was just about to start a very similar project but for Entites using the Entity API, not nodes. I was wondering, have you started this? Is there any code for this project? I'd love to take a look so I can try to integrate it with a project i've been working on: http://drupal.org/sandbox/tmsimont/1917664

thanks.

Comments

amolinari’s picture

amolinari commented

developed for 6.x, porting to 7.x in this days, need to integrate in a client's project before next tuesday, so some codes will be pushed in the next days: it's ok for you to wait some days? want to discuss project details?

amolinari’s picture

amolinari commented

developed for 6.x, porting to 7.x in this days, need to integrate in a client's project before next tuesday, so some codes will be pushed in the next days: it's ok for you to wait some days? want to discuss project details?

tmsimont’s picture

tmsimont commented

sure -- i might just start on a solution more specific to my needs.

does your module work with entities or just nodes?

amolinari’s picture

amolinari commented

yes right now it's supposed to use nodes, it's a d6 porting so on d6 the system used nodes: what are the benefit you think we'll have by using entities?

a RESERVABLE is a node (a service, a doctor, a printer etc.) that is supposed to have title, description etc so we think about keeping using nodes
a RESERVATION will contains the data about the reservation (date_from, date_to) and a reference to reservable object: maybe the reservation can be an entity because it's not needed to have a page or more visual detail like a reservable... but why not a node too? i'm not so good with entity api and didn't want to devel all crud operations (i suppose there aresome confortable api fo that, but i don't know), so I thought about using nodes :-)

suggestions?

tmsimont’s picture

tmsimont commented

I was thinking about having the reservation apply a status to a particular entity -- not so much that the reservation itself would be an entity.

So the from/to could be a configurable field that could be placed on any entity, and then the entity that is reserved would have a status of "reserved" which would prevent additional reservations.

What I need is a bit simpler.

I've described my use case as best that I can here: #1928656: "Obligated entity"