Planning for the first release

Sorry for the late reply, I did most of the work here for a project, and I'll use it again on another project very soon, so I'm getting back to it. Thanks for the support, the module surely needs some love.

Particularly I'm now unsure about some design issues for it, and I need to think over. I would be glad if more people join in, if you have suggestions, concerns or criticism, it'll be a very good moment to post it.

I'll let this issue open as a brainstorm for the next steps.

@mboudey, I'm unsure about your suggestions. This module currently is tied to CCK as to manage fields, so any solution derived from that should be fairly easy to integrate. Webforms, on the other hand, would be a completely different purpose and workflow.

But assuming it would be useful to have BOTH. Then we need to isolate a kind of backend for handling the quoting. One of them would just send them like a submitted webform and the other would just store it as a node (with CCK fields). Does that answer your concern?

Though I have not tried this module yet, but I'd prefer that it could be tied with Ubercart on the product/service items, descriptions, price, contacts, etc. This will be much easier and making more sense for invoicing and payment.

In other words, I'm looking for a way to convert Estimates into invoices for payment in Ubercart.

guapunya, I first designed this module so that I didn't have to deal with a shop structure when all that was needed was an estimate (in the first use case, and estimate about services such as renting water trucks). It doesn't makes sense to me to tie it to UC, since if you're already going to use it, it provides everything it's needed without this module, AFAIK.

Even though we could really make a bridge here, I would do it as a submodule, and as an optional functionality, as I really think it's useful for many sites to have this module w/o setting up a shop structure (which would be an overkill and a lot of work).

Is there any info on how this should work with the 2 content types or is this not testable yet?

@andren, although there is no release yet, the code can be pulled and tested.

You can use whichever content types you wish. One should serve as the quote itself and may contain fields relative to the user, like contact details, location, etc. and the other should be a quoting item, which should contain quoting information only for the item, like quantity, etc.. Last, but not least, you should edit the content types that you want to be quotable and assign them to the quoting item.

I still didn't have time to invest in this project, but I think I'll dive on it in the next weeks, so comments, suggestions and bug reports are appreciated. Please open up new support issues as soon as you have trouble.

The project now has an alpha release. I'll leave this open for the next features I'd like to add:

- A block that displays the quote form for the node being viewed.
- Menu access denying access to quote/finish so that it can be a normal menu entry that will only show up when you quote some items.

There are also some minor bugs that generates warnings...

Also:

- Add option to redirect user after the quoting is finished.

Summary

Adding integration with views as new feature

Menu access for quote/finish and quote/clear

Updating