Proposed Standard Region numbering

[jhollin1138]

It seems that more and more people are grabbing one region from a skin and adding it to their skin.  Only to have to spend some time solving region conflicts.

I was wondering what you all thought about setting up some standard Region numbering, with the lowest region number being designated as the main control region.  Standard numbering should help eliminate region conflicts, assuming we all follow them.

This is what I was thinking:

Region 0: Main Header Control Region (Date and Main Controls).
Region 1-9: Reserved for Header Sub-Regions
----------
Region 10: Main Weather Region
Region 11-19: Reserved for Weather Sub-Regions
----------
Region 20: Main RSS Region
Region 21-29: Reserved for RSS Sub-Regions
----------
Region 30: Main Time Region
Region 31-39: Reserved for Time Sub-Regions
----------
Region 40: Main System Information Region
Region 41-49: Reserved for System Information Sub-Regions
----------
Region 50: Main Launcher Region
Region 51-59: Reserved for Launcher Sub-Regions
----------
Region 60: Main POOM Region
Region 61-69: Reserved for POOM Sub-Regions
----------
Region 70+: Available for future use

I think I got them all.

[MadTxn]

I think that's a great idea.  Also, it would help to have a listing of regions at the top of the file in a comment, as well as descriptions before each region, like

Code Select Expand


//////////////////////////////////////////////////////////////////////////////
// Region: 0
// Page: 0
// Content: Date & Options
// Parent region:
// Subregions:
// Update regions:
// Pages: 1
// Dimensions: 240 x 20
// Vars:
//////////////////////////////////////////////////////////////////////////////


I've shafted myself many a time with conflicts.

Edit:  I just saw this post from fishboy...

...I tried changing my regions to 20 and 21, but apparently TodayPlus does not like region numbers > 20.  Will look for another region number to use and then repost the file.

[fishboy]

Standardization would be a good idea.  To support your numbering conventions, however, it looks like TodayPlus would need to be modified to handle region IDs greater than 19 (which shouldn't be a big task I believe).  

Awhile back, I asked srs if ID numbers could be replaced with text instead (i.e. launcher0, launcher1, rss0, rss1, etc.).  This would add more description to the region and also make it easier to cut and paste modules. At the time he said it would require some effort to make this change and so it was not implemented.  However, recent forum discussions lead me to believe that he may be reconsidering this change (as you know, he is always one step ahead of us  ).

[jhollin1138]

Standardization would be a good idea.  To support your numbering conventions, however, it looks like TodayPlus would need to be modified to handle region IDs greater than 19 (which shouldn't be a big task I believe).

I wasn't aware that there was a limitation.  It would be great if srs could eliminate, or expand, the restriction.

Awhile back, I asked srs if ID numbers could be replaced with text instead (i.e. launcher0, launcher1, rss0, rss1, etc.).  This would add more description to the region and also make it easier to cut and paste modules. At the time he said it would require some effort to make this change and so it was not implemented.  However, recent forum discussions lead me to believe that he may be reconsidering this change (as you know, he is always one step ahead of us  ).

You got that right.  It seems to be his typical response that he already has it in the works.