Search options (Page 3 of 8)

While we're talking about profile changes, how about we re-do the time zone selection?

1. People from Newfoundland can't select their time zone, currently.

2. It doesn't take into account the differences between Daylight Savings Time and Standard Time ...

I realised this as I tried to modify it myself, to add cities to the list:

<select name="form[timezone]">
<option value="-12"<?php if ($user['timezone'] == -12) echo ' selected' ?>>UTC -12</option>
<option value="-11"<?php if ($user['timezone'] == -11) echo ' selected' ?>>UTC -11</option>
<option value="-10"<?php if ($user['timezone'] == -10) echo ' selected' ?>>UTC -10 Hawaii (Honolulu)</option>
<option value="-9"<?php if ($user['timezone'] == -9) echo ' selected' ?>>UTC -09 Alaska (Anchorage)</option>
<option value="-8"<?php if ($user['timezone'] == -8) echo ' selected' ?>>UTC -08 Pacific (Los Angeles, Vancouver)</option>
<option value="-7"<?php if ($user['timezone'] == -7) echo ' selected' ?>>UTC -07 Mountain (Denver, Calgary)</option>
<option value="-6"<?php if ($user['timezone'] == -6) echo ' selected' ?>>UTC -06 Central (Chicago, Regina)</option>
<option value="-5"<?php if ($user['timezone'] == -5) echo ' selected' ?>>UTC -05 Eastern (New York, Toronto)</option>
<option value="-4"<?php if ($user['timezone'] == -4) echo ' selected' ?>>UTC -04 Atlantic (Halifax)</option>
<option value="-3.5"<?php if ($user['timezone'] == -3) echo ' selected' ?>>UTC -03.5 ??? Newfoundland</option>
<option value="-2"<?php if ($user['timezone'] == -2) echo ' selected' ?>>UTC -02</option>
<option value="-1"<?php if ($user['timezone'] == -1) echo ' selected' ?>>UTC -01</option>
<option value="0"<?php if ($user['timezone'] == 0) echo ' selected' ?>>UTC/GMT (London)</option>
<option value="1"<?php if ($user['timezone'] == 1) echo ' selected' ?>>UTC +01 CET (Paris)</option>

I understand feeping creaturism and the second-system syndrome, but this isn't bloatware, but something that could strengthen PunBB's extensibility and make it more versitile. (It's not bells and whistles either, since PunBB was designed to be elegant, yet also to have modifications to improve it's functionality.)

Perhaps I'll try forking 1.1.2 and attempt to integrate both CSS/XHTML and some kind of mod system to see what the result could be. ;)

Well, the same excuse could have been said for Windows, after all, if an application overwrites a file or registry entry, or replaces a DLL with a newer version then there would be problems. But Windows has guidelines for creating programs, including using a separate folder for program files and naming conventions for software registry entries, plus improved DLL handling in Windows XP, so it gives freedom to use "installation" programs, instead of manual x-copy.

So we could create module guidelines that explain where and when to modify PunBB and include standardized conventions for naming and location. Then we can create installation PHP scripts for every modification and perhaps use another utility to automatically check for interoperatibility between modifications, with the modifications listed in another section.

Or we could go the Firefox/Mozilla route and support "Extensions" in PunBB, with an integrated method for installing PunBB extensions and more programmable access to PunBB, like being able to add your own code to various parts of PunBB without needed to edit the PunBB files themselves. Like calling the following to add a "Signatures" link to the admin page.

$PunBBex->AddToAdminMenu("Signatures","/extensions/signatures/signatures.php?section=admin");

Either way, it would be nice to extend PunBB with more support for Extensions. The difference between the two is that with the first, most of it is dependant on the mod's installation script and in the second, it's more dependant on the PunBB software. But the good parts with both is that suddenly, Firefox-like, PunBB can be fast and extensible for any user. Combined with a full CSS-based layout and I would say we've easily the best forum software out there, perfect for a version 2.0 ;)

Yes, that makes sense. In some ways what I mentioned about creating PunBB extension support would allow PunBB to include the modification's files, then let the modification change PunBB dynamically.

Please don't ignore the questions in my original post ... I am quite interested in how people create their modifications ? do they start from a newly extracted PunBB and open the files they need in Dreamweaver (or notepad, ultraedit)? Do they work on the HTML first, creating the look they want, then adding the functionality afterward? Do they write out the requirements, create planning documents? That's just part of the first question, please continue with the rest of the questions, if you feel like it.

Answering these questions may help us build the prefect PunBB modding solution that will benefit everyone, plus help encourage PHP newbies delve into the source code and perhaps make the entire mod creation process easier and faster for everyone.

For example the tool I mentioned in my first post. With these answers, I could try to design the tool's "workflows", the way I intend it to be used, with the way people actually create mods. There's no point in making something that people don't like using. Same with PunBB. Why standardize the readme.txt if people don't like using it? Or can we make it easier to produce them? In which case, how? This is a larger topic than you'd think at first glance ;)

Then lets focus on the mods. Let's make it easier to create mods. Let's make it easier to install mods. Let's make it easier to update mods for newer versions of PunBB. Let's make it easier to find mods. Please post your ideas here.

Rickard and I were talking about that, instead of having both users and groups in this "ACL"-type interface, he suggested just groups ... I agreed because as you said, "[you] can always create a group with 1 user". Interesting if we could incorporate both the EFAM permissions, modified to groups, with a new UI for both ;)

Eagerly awaits tomorrow! *grin*

Hello Marc.

I would say the reason is obvious: No one thought much about it ;)

The most logical way for humans who are used to reading up-to-down is to start from the top and work down though your source code, noting changes as you go. Perhaps a more adventurous developer would use a diff program and then reformat it by hand or with a script. The order is not standardized in any fashion, so it's up to the individual mod developer to decide.

I would, however, agree with your "reverse order" idea. Another idea would be to adjust the line numbers to where they would be when the person installing it gets to the line, so for example, with 10 new lines inserted above, the next change should have its line number offset by 10 lines. Of course, for each, it would simply place extra burden on a mod developer to change their script.

Perhaps it would be easier to tell people to start from the bottom and work their way up? ;)

Oh? Sure, then.

Edit: Never mind. Seems ... it works now. Before it gave an error about not being able to update the ... something. Database, possibly. I loaded modgen.cactuz.nu and logged in with that. I guess the problem was the URL, since using www.cactuz.nu seems to work.

Hmm cool. Yeah, that makes sense. I'll try experimenting with it and get back to you on that one.

You're welcome. (again!) Glad to see we solved both problems quickly ;)