(I made this post to request adive and permission for the issue below, I have tried to email this to the mailing list but it is being bounced back. So maybe someone can give me a heads up to that as well )
Let me start off by explaining how we came to this. It has come to our attention that we wanted to build a Setup Wizard for pERP. So instead of merely building this for us I decided to build a generic Wizard application that other users of groupware could use. For now you simply make your wizard and send the parent Wizard application your steps which are classes developed for what you want to do in the step. The Wizard application would go through the step process by clicking on the steps that are shown in the sidebox.
This is where the problem arose. Lets say a person makes a wizard that has 30 steps. Well the sidebox would become very large. So to fix this problem I decided to build an auto-scroll function into the sidebox and set its max height. As you can imagine this could not be done without changing core files of egroupware.
After coding so far I have decided to poll this to the group. This is no simple task due to the awful Internet Exploder Browser we are all so fond of. So far I have narrowed this to a few files.
-
class.idots_framework.inc.php - The changes in the file are to determine divSideboxes are there and divSidebox entries are there, allowing a formula to estimate what the em size of the box would be. If it is bigger than the preference Sidebox Max Height that the user set in Preferences(which was also added into the code in another file) then we make the height of the sidebox the user setting. If not we would leave it alone. This was done in such away to make sure that the scrollbar acted the same way in all browsers.
-
slidereffects.js - This file was changed for one reason. Upon closing the sidebox the scrollbar would not disappear in IE. So in this file we turn of the auto-scroll function of the div when it is being hidden, and then back on, when it is being displayed.
3.navbar.tpl - The only changes here are to set the tpl variable in the correct div, and give it an ID that was not already there, for the purpose of accessing it in Javascript.
At this point there is one other step, onload of each page will need to check the browser capability to assure that the scrollbar behavse properly again. In doing so we will adjust the width of the divSideboxContainer so all is well. We would have to push the onload function where the sidebox gets created so that it would affect all applications from here on in.
I’m am basically looking for approval or any input on what you all think about this enhancement . Thank you for all your time.
Cheers
John Trudel
