Ace_Armstrong wrote:
Okay....I understand how to get the right format from PHP. What I don't get is where in the piCal code to make the change to that format.

peterr wrote:
If I understand the problem, as you had '/spacer.gif' highlighted, that is your concern.

Because the td/cell code for that is within a row which is within a table defined as 640 px wide, that is why it appears as 640 wide. In fact, _that_ table is within another table of 640 px wide.

I didn't install the common directory, because with XOOPS 2.2.x, all that code is already defined in a standard XOOPS path, ....... found that out after stumbling upon some piCal code.

Ace_Armstrong wrote:
the actual problem is the way there are several lines that specify the width of the table and the width of the various cells to be 640 and 630. This is nowhere within my theme, and none of the other modules create this table. In fact, piCal didn't do it until I upgraded to 0.84. That table simply doesn't appear anywhere within the code, unless it's in the parts that are written in Japanese.

peterr wrote:
Hmm, ... it seems most XOOPS modules display the centre content outside of the control structure sourced from the theme.html code. Here is some generated code from a forum display

[snip]

however the table positioning is aligned perfectly, whereas piCal is not. For example, the forums module code uses a percentage width for the table, rather than pixels:
[snip]

... so no doubt the piCal module should do the same, use percentages for the table widths.

HTH

Ace_Armstrong wrote:
Right. Which is the problem. I can't find where in the code it's specifying the pixel width so I can change it to percentages (or at least a smaller pixel width). My main objective at this point is to find that portion of the code so I can make the edits, but like I said: I can't find it anywhere, and I've been through the code line by line.

Ace_Armstrong wrote:
I can't find any reference to "640" or "630" anywhere in the code. I have gone through literally every file in the module and every file in the "common" directory.

peterr wrote:
1. I downloaded Gubed PHP Debugger, which certainly seems to be a good tool, set breakpoints, and step through code, but of course, the PHP code needs to be on a 'local' server, an IP on your LAN somewhere.

2. You could try using
PHPXref, which is a very good cross-ref utility, it is open source, and to see a demo of how it works, there is a site that has all the osCommerce source code, as a demo for PHPXref, see http://www.oscdox.com/crossx/nav.html?index.html

I have loaded that locally in the past, takes up a bit of space, because it creates a load of html pages, but it is a very handy tool for finding out where functions and variables are used.

3. The only suggestion I can make to find out _where_ to change the code, is to walk down a path I _may_ take. With the use of Gubed, I'm chewing on loading something like 'phpdev', which is a bundled Apache, PHP, Mysql,etc, and run it on an old Win95b box I have, then I start up the web server locally, run XOOPS, and then look at using Gubed to debug piCal.

peterr wrote:
Quote:

Ace_Armstrong wrote:
I can't find any reference to "640" or "630" anywhere in the code. I have gone through literally every file in the module and every file in the "common" directory.

Have a look at the db, the table name is "xoops_tplsource", and there are several occurances of '640' there. If I look in the corresponding table called "xoops_tplfile", the template files that have those values (in the db) are:

* pical_print.html
* pical_event_list.html

Sometimes the template row in the db is not the same as the template sitting in a path on the server.

Ace_Armstrong wrote:
I have no idea how to do any of that. I'm a design guy, not a programmer.