Hi Vera, I think code questions like this don't need to go to design, so I'm responding there...
> My understanding of the design considerations of Chandler is still poor, > so I would like to consult with you, guys, whether there is a > recommended location for this kind of module or package that will > conform with the chandler design and guidelines. In the long run, I'm hoping your report code can live entirely in a separate parcel, which you can package up independent of Chandler and publish to the Python Cheeseshop. But for now, it's not really possible to hook into the Quick entry area from a parcel, so your code makes the most sense as a patch. I think putting your module in parcels/osaf is an OK place for it, but I'm interested in other developers' opinions. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
