I'm not sure i'm asking this the right way.
I've been pouring through the API manual and i'm finally getting the hang of writing my own complex module (although i've never written a simple one yet ;-))..
My module will require two new tables that store event and venue data. The module will then relate (JOIN) the data and display it as needed.
I'm confused about a few things:
1) Does my data need to be designed as a NODE? What i mean is must my module ONLY extend type node by creating a new node type "events" and "venues" and then using node hooks and tables with nids behind the scenes?
OR
2) can i just ditch the whole node paradigm and create my own tables without nids but basic primary keys?
I believe views and panels are NOT nodes. So i DO NOT THINK CONTENT THAT IS DISPLAYED IN DRUPAL HAS TO BE OF TYPE (EXTENDED) NODE (but i'm not sure)?
I think one can create whatever table one wants and access it however one wants (whether nodes or custom tables) as long as hook_menu and hook_block are (MUST be) provided in order to output and make the content available on the page - right??
Another way of asking this might be:
1) What do i GAIN by extending my new data types as a node (that i can't foresee right now)?
2) What do i LOSE by NOT extending my new data types as a node (that i can't foresee right now)?
thanks in advance for any and all input regarding this