Module development and code questions

Just wondering if anyone has developed or started developing a shopping cart / catalog module. I'm new to drupal and just trying to wrap my head around the module development process. Before I get my hands dirty, I was wondering if there's anything comparable out there.

I quite like image.module. An excellent tool for creating collaborative galleries.

You can see the results at zeigeist.ca. Click on "photo gallery" in the Navigation links. You'll notice that import.module is the front page and has been hacked even more significantly. That's another story I don't want to get into.

Here's what I did:

• The big hack is: the image displayed in a node view is resized if it is larger (in either dimension) than a "resize" variable. The node-view image links to the original image and vice-versa. e.g., if I upload a 1024x768 image and the resize variable is set to 640, the image will be displayed in the node at 640x480 and will link to a page which displays the original image at it's full size. This full sized page links back to the node view.
• Preview seemed to be broken, so I fixed it. I also hacked it up a bit so that the preview looks more or less like it actually will in the gallery. (See first bullet.) The big difference is that in preview, the image displayed in the node links just to the temp image instead of to a page. There's no link back from the temp image, so navigation is a bit of a problem in preview. Can't think of a good way around this, so I'll leave it for now.
• Added submission guidelines variable so I could explain the navigation problem in preview. Also added a variable for the path to the resized images.
• I have personal galleries disabled, but I noticed that the link to personal galleries is still available from "view use information" when disabled, so I hacked it a bit so this links to all the photos a user has uploaded into the regular galleries. This doesn't work quite right, but I think it's a neat idea.
• I didn't like the lack of link borders around images, so I made them visible.

Hello lads/lasses,

Just to let you know that I'm currently modifying the archive.module to meet my custom requirements.

The user story involved is that of a business user extracting a time-span of nodes (eg this week's, this month's, x to y etc) and presenting it in a streamlined presentation (no boxes etc) which can then be saved and emailed out to people (and later automated of course with _cron! )

My first iteration will involve modifying archive_page to allow for more form-input, including the ability to hide the form itself. Something along the lines of:

http://neko.evolove.net/files/archive_form.gif

I'm also going to restrict the node types to stories only.

Let me know what you think!

Just a generic thought for the future, I'm reading the docco on module development, and while the hooks are fine I guess would a better solution be for all modules to extend a base "Module" class (abstract) that defines the interfacel.

Then perhaps you could variable variables to dynamically name classes to call methods, something like

instantiatedModuleName->getHead();
instantiatedModuleName->save(...);
instantiatedModuleName->getHelp();

Hi guys,

Just wondering if there is a Drupal architecture diagram(s) - I think some nice diagrams would help understanding how everything fits together.

I'm thinking class diagram, rendering pipeline (sequence diagram?) ER diagram for the database etc.

Always good to keep a systems documentation up to date

cheers,
neko

Hello,
I was about to start trying to develop an Events module when I found one already started. Now, there are a couple items that I'd like to ask about:

1. Is there any way to delete images?
2. Will this have a link to the Images Module, someday?
3. Are there any plans to add other type of events?

Let me explain better what I mean in #3. I'm working on a family website, and one of the goals in my list, is to be able to see and plan all kind of events on-line. So, what I meant about by other type of events, is, more fexibility on the dates.
Like:

Non-Recurrent:

Family Reunions - One specific date

Recurrent:

Birthdays - Once a year, always same date.

Anniversaries - Same as BDays

Vacation Planning - Range of dates

Family reunions - All sort of weird date math:

• Go see grandpa every month, on the 12th.


• Cousins outing, every other week, on Sat.


• Call mom, long distance, every 10 days.


• etc. etc.

I'll try to start looking to see if I can help with any of this, some dates are easy, some are not as easy. Besides, I'm totally new to Drupal, I've been only using it for 2 weeks.
Hey, 2 weeks and I already have my site up and running, and mostly translated!!



Thanks for reading!




PD: I tried using the -triple dash- delimiter, but didn't work