Aren't parsed again themselves? Why again? It seems globals are not parsed at all!
Is there any reason why you did not wanted to parse it?
I think parsing the globals is a necessary thing (or at least to make it available optionally).
And I don't think, that there are any disadvantage of parsing the globals. Are there?
Just imagine the situation of the Body starting & closing globals.
Let we create a 2 column table in the body:
- In the first column we want to place (include) a menu from test.html
- In the second column we place the Forum itself
Imagine how easy would it be to do it, if we have global parsing, and how could we solve it without it.
GForum is fully dynamic, so using SSI tags are not posible in cgi output. Body tags are useful so we must keep them. Finally, if we don't do parsing of globals, we are not able to include any menu file in the left table column.
Adding parsing of globals, I think is an easy task. The question is, if GT wants to implement it, or not?
I suggest to implement global parsing, and make parsing of globals OPTIONAL, so the user can decide if he needs this feature or not.
This way the feature is available, but if somebody doesn't want to use it, the user turns off parsing option and will not feel any speed decrease. It is that easy.
I think it would be a fair solution. But that's only my opinion.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
Is there any reason why you did not wanted to parse it?
I think parsing the globals is a necessary thing (or at least to make it available optionally).
And I don't think, that there are any disadvantage of parsing the globals. Are there?
Just imagine the situation of the Body starting & closing globals.
Let we create a 2 column table in the body:
- In the first column we want to place (include) a menu from test.html
- In the second column we place the Forum itself
Imagine how easy would it be to do it, if we have global parsing, and how could we solve it without it.
GForum is fully dynamic, so using SSI tags are not posible in cgi output. Body tags are useful so we must keep them. Finally, if we don't do parsing of globals, we are not able to include any menu file in the left table column.
Adding parsing of globals, I think is an easy task. The question is, if GT wants to implement it, or not?
I suggest to implement global parsing, and make parsing of globals OPTIONAL, so the user can decide if he needs this feature or not.
This way the feature is available, but if somebody doesn't want to use it, the user turns off parsing option and will not feel any speed decrease. It is that easy.
I think it would be a fair solution. But that's only my opinion.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
