Menu
▾
▴
tsheetx-developers — Timesheet Next Gen - Developer's mailing list
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
(4) |
May
(3) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(10) |
Jun
(1) |
Jul
(3) |
Aug
(19) |
Sep
(52) |
Oct
(5) |
Nov
(15) |
Dec
|
| 2011 |
Jan
|
Feb
(65) |
Mar
(53) |
Apr
(55) |
May
(37) |
Jun
|
Jul
(1) |
Aug
(17) |
Sep
(28) |
Oct
(7) |
Nov
|
Dec
|
| 2012 |
Jan
(3) |
Feb
|
Mar
(2) |
Apr
|
May
(4) |
Jun
(3) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2014 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Isabelle V. <ver...@fr...> - 2011-05-06 13:45:29
|
Hello, I have no problem with PHP Version 5.3.0. Sorry ;) Isabelle. |
|
From: Mark W. <ma...@rw...> - 2011-05-06 11:17:48
|
I am running PHP V5.3.2 and I now get jLogin, jLogout with the correct case. :) _____________________________________________ Mob: 07725 695178 Email: ma...@rw... On 06/05/2011 05:05, Peter Lazarus wrote: > Isabelle, > I wonder what version of php your server is using. If it is earlier than > 5.3.0, you would not experience any problem. From memory, Scott has php > version 4.something. > > My version of php is 5.3.6 and I did have a problem with language, no > language strings were displayed. > Peter > > On 05/05/2011 04:18 PM, Isabelle Vergely wrote: >> Hi all, >> >> I am surprised because I have no problem with the language switch. >> I applied what said Scott in a message sent to the list >> (2011-03-30 15:53), see: >> http://sourceforge.net/mailarchive/message.php?msg_id=27283175 >> >> To test the language, in the file: include/jclasses/factory.php >> change the line (#74): >> $locale = "en-GB"; >> For me, having $locale = "en-GB" or $locale = "fr-FR", it's OK >> to display strings respectively in English or French. >> >> I haven't test the last modification made be Peter yesterday. >> I will look to this soon. >> >> Isabelle. >> >> ------------------------------------------------------------------------------ >> WhatsUp Gold - Download Free Network Management Software >> The most intuitive, comprehensive, and cost-effective network >> management toolset available today. Delivers lowest initial >> acquisition cost and overall TCO of any competing solution. >> http://p.sf.net/sfu/whatsupgold-sd >> _______________________________________________ >> Tsheetx-developers mailing list >> Tsh...@li... >> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers >> > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > |
|
From: Peter L. <pal...@gm...> - 2011-05-06 04:05:09
|
Isabelle, I wonder what version of php your server is using. If it is earlier than 5.3.0, you would not experience any problem. From memory, Scott has php version 4.something. My version of php is 5.3.6 and I did have a problem with language, no language strings were displayed. Peter On 05/05/2011 04:18 PM, Isabelle Vergely wrote: > Hi all, > > I am surprised because I have no problem with the language switch. > I applied what said Scott in a message sent to the list > (2011-03-30 15:53), see: > http://sourceforge.net/mailarchive/message.php?msg_id=27283175 > > To test the language, in the file: include/jclasses/factory.php > change the line (#74): > $locale = "en-GB"; > For me, having $locale = "en-GB" or $locale = "fr-FR", it's OK > to display strings respectively in English or French. > > I haven't test the last modification made be Peter yesterday. > I will look to this soon. > > Isabelle. > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > |
|
From: Isabelle V. <ver...@fr...> - 2011-05-05 06:18:30
|
Hi all, I am surprised because I have no problem with the language switch. I applied what said Scott in a message sent to the list (2011-03-30 15:53), see: http://sourceforge.net/mailarchive/message.php?msg_id=27283175 To test the language, in the file: include/jclasses/factory.php change the line (#74): $locale = "en-GB"; For me, having $locale = "en-GB" or $locale = "fr-FR", it's OK to display strings respectively in English or French. I haven't test the last modification made be Peter yesterday. I will look to this soon. Isabelle. |
|
From: Peter L. <pal...@gm...> - 2011-05-05 04:56:20
|
I should also add that this problem was found, tested and resolved on PHP Version 5.3.6. So earlier PHP versions may not have experienced this issue. Peter On 05/05/2011 02:15 PM, Peter Lazarus wrote: > Dear All, > None of the language strings were being read in from the language ini > file. Instead, all strings were being displayed in all CAPITALS, which > is the action taken if a string is not found in the language translation > file. > > language.php version 314 fixes this problem. You should now see strings > in upper and lower case, prepended with "j". I have tested this out only > with en-GB.ini. > > Why this bug occurred I am not sure. Starting at line 452 of > language.php, I have commented out the php version tests, and have run > with just the function @parse_ini_file instead of the previously used > function @parse_ini_string. Perhaps the str_replace function (line 454) > messed up the contents of $strings so that it could not be properly > parsed with @parse_ini_string. > > Peter > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > |
|
From: Peter L. <pal...@gm...> - 2011-05-05 04:15:12
|
Dear All, None of the language strings were being read in from the language ini file. Instead, all strings were being displayed in all CAPITALS, which is the action taken if a string is not found in the language translation file. language.php version 314 fixes this problem. You should now see strings in upper and lower case, prepended with "j". I have tested this out only with en-GB.ini. Why this bug occurred I am not sure. Starting at line 452 of language.php, I have commented out the php version tests, and have run with just the function @parse_ini_file instead of the previously used function @parse_ini_string. Perhaps the str_replace function (line 454) messed up the contents of $strings so that it could not be properly parsed with @parse_ini_string. Peter |
|
From: Mark W. <ma...@rw...> - 2011-05-04 18:52:08
|
Hi Peter,
I get j*** everything. It isn't just you :)
I haven't looked at the internationalisation code whatsoever so don't
have any idea why it isn't currently working
Sorry!
Mark
_____________________________________________
Mob: 07725 695178
Email: ma...@rw...
On 04/05/2011 10:50, Peter Lazarus wrote:
> Hi Mark,
> do you see any of these internationalisation strings on your system
> being displayed correctly? If so, whatever problem is occurring on my
> system must be local to my system only.
> Peter
>
> -------- Original Message --------
> Subject: Re: [Tsheetx-developers] New Text Strings
> Date: Tue, 3 May 2011 09:49:01 -0500
> From: Scott Miller <sco...@gm...>
> To: pal...@gm...
> CC: Isabelle Vergely <ver...@fr...>,
> tsh...@li...
>
>
>
> Hey Peter,
>
> If the string does not exist in the translation files, it simply
> prints out the string that the JText stuff was called with. So, in
> your example, the translation for CLIENT doesn't exist, so that is why
> it comes out as jCLIENT. As soon as it is defined, it should be
> printed in non-all caps.
>
> On another note, I'm in the midst of an employment change, so, I'm
> afraid I will not have the time I've had in the past to work on this
> product. I still want to be involved, but the amount of time I have
> to actually work on the code will probably be severely limited, at
> least in the near future. Getting to this employment change has also
> greatly limited my time over the past few weeks (in fact, I don't
> think I've done anything of note over these past few weeks).
>
> -Scott
>
> On Mon, May 2, 2011 at 8:50 PM, Peter Lazarus <pal...@gm...
> <mailto:pal...@gm...>> wrote:
>
> Hi Isabelle,
> I am in the process of making changes to the supervisor form. Also
> adding internationalisation. A couple of questions:
> 1. There are some text strings on that form that are not in the
> en-GB.ini file. So I should add them to both the en-GB.ini and
> fr-FR.ini
> files. If I send you a note re what's been added, then you can
> alter the
> french translation, ok?
>
> And this question to all developers. Maybe I have missed something
> previously.
> 2. The call to JText::_('CLIENT') for example returns jCLIENT. Why
> doesn't it return the translated string "Client", or "jClient"
> where the
> "j" confirms the string has been internationalised?
> Peter
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> <mailto:Tsh...@li...>
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>
>
>
|
|
From: Peter L. <pal...@gm...> - 2011-05-04 09:49:12
|
Thanks Scott,
That is how I guessed it would work. So there maybe there is a bug in
the language code, or some path error, or maybe a location specification
error on my system. Most or all of the strings are currently defined in
the en-GB.ini file, but none appear in any form in the web pages. I'll
take a look and see if I can figure out what is not working.
Good luck with your change of jobs.
Peter
On 05/04/2011 12:49 AM, Scott Miller wrote:
> Hey Peter,
>
> If the string does not exist in the translation files, it simply
> prints out the string that the JText stuff was called with. So, in
> your example, the translation for CLIENT doesn't exist, so that is why
> it comes out as jCLIENT. As soon as it is defined, it should be
> printed in non-all caps.
>
> On another note, I'm in the midst of an employment change, so, I'm
> afraid I will not have the time I've had in the past to work on this
> product. I still want to be involved, but the amount of time I have
> to actually work on the code will probably be severely limited, at
> least in the near future. Getting to this employment change has also
> greatly limited my time over the past few weeks (in fact, I don't
> think I've done anything of note over these past few weeks).
>
> -Scott
>
> On Mon, May 2, 2011 at 8:50 PM, Peter Lazarus <pal...@gm...
> <mailto:pal...@gm...>> wrote:
>
> Hi Isabelle,
> I am in the process of making changes to the supervisor form. Also
> adding internationalisation. A couple of questions:
> 1. There are some text strings on that form that are not in the
> en-GB.ini file. So I should add them to both the en-GB.ini and
> fr-FR.ini
> files. If I send you a note re what's been added, then you can
> alter the
> french translation, ok?
>
> And this question to all developers. Maybe I have missed something
> previously.
> 2. The call to JText::_('CLIENT') for example returns jCLIENT. Why
> doesn't it return the translated string "Client", or "jClient"
> where the
> "j" confirms the string has been internationalised?
> Peter
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> <mailto:Tsh...@li...>
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>
>
|
|
From: Scott M. <sco...@gm...> - 2011-05-03 14:49:10
|
Hey Peter,
If the string does not exist in the translation files, it simply prints out
the string that the JText stuff was called with. So, in your example, the
translation for CLIENT doesn't exist, so that is why it comes out as
jCLIENT. As soon as it is defined, it should be printed in non-all caps.
On another note, I'm in the midst of an employment change, so, I'm afraid I
will not have the time I've had in the past to work on this product. I
still want to be involved, but the amount of time I have to actually work on
the code will probably be severely limited, at least in the near future.
Getting to this employment change has also greatly limited my time over the
past few weeks (in fact, I don't think I've done anything of note over these
past few weeks).
-Scott
On Mon, May 2, 2011 at 8:50 PM, Peter Lazarus <pal...@gm...> wrote:
> Hi Isabelle,
> I am in the process of making changes to the supervisor form. Also
> adding internationalisation. A couple of questions:
> 1. There are some text strings on that form that are not in the
> en-GB.ini file. So I should add them to both the en-GB.ini and fr-FR.ini
> files. If I send you a note re what's been added, then you can alter the
> french translation, ok?
>
> And this question to all developers. Maybe I have missed something
> previously.
> 2. The call to JText::_('CLIENT') for example returns jCLIENT. Why
> doesn't it return the translated string "Client", or "jClient" where the
> "j" confirms the string has been internationalised?
> Peter
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>
|
|
From: Isabelle V. <ver...@fr...> - 2011-05-03 08:22:11
|
Hello Peter,
Last week, I made several changes for internationalisation (see revisions
311 to 313): navcal, submit, some report and 'user_rates' pages and
languages files (en-GB.ini, fr-FR.ini).
For language files, I added several text strings and re-organised strings:
; Menu items
; General items
; Date, time, timesheet, hours management
; Clients management
; Projects management
; Rates
; Reports
; Tasks management
; Users, login management
; Clock management
; Project and task status options
; Absences management
...
You can modify the last version of en-GB.ini file in txsheet-2.0-demo
repository and I will update the French file.
Have you solved the bug I noticed: when I select the 'supervisors' item
menu, it returns:
Can't perform query: field 'supervisor' unknown in where clause.
I am not working on the tsheetx 2.0 database structure;)
The translation of the supervisor form will be easier if you give the
new version of this form.
Have a nice day.
Isabelle.
----- Mail Original -----
De: "Peter Lazarus" <pal...@gm...>
À: "Isabelle Vergely" <ver...@fr...>
Cc: tsh...@li...
Envoyé: Mardi 3 Mai 2011 03h50:28 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: New Text Strings
Hi Isabelle,
I am in the process of making changes to the supervisor form. Also
adding internationalisation. A couple of questions:
1. There are some text strings on that form that are not in the
en-GB.ini file. So I should add them to both the en-GB.ini and fr-FR.ini
files. If I send you a note re what's been added, then you can alter the
french translation, ok?
And this question to all developers. Maybe I have missed something
previously.
2. The call to JText::_('CLIENT') for example returns jCLIENT. Why
doesn't it return the translated string "Client", or "jClient" where the
"j" confirms the string has been internationalised?
Peter
|
|
From: Peter L. <pal...@gm...> - 2011-05-03 01:51:16
|
Hi Isabelle,
I am in the process of making changes to the supervisor form. Also
adding internationalisation. A couple of questions:
1. There are some text strings on that form that are not in the
en-GB.ini file. So I should add them to both the en-GB.ini and fr-FR.ini
files. If I send you a note re what's been added, then you can alter the
french translation, ok?
And this question to all developers. Maybe I have missed something
previously.
2. The call to JText::_('CLIENT') for example returns jCLIENT. Why
doesn't it return the translated string "Client", or "jClient" where the
"j" confirms the string has been internationalised?
Peter
|
|
From: Scott M. <sco...@gm...> - 2011-04-21 14:57:50
|
Ah, brilliant, user configurable option to use a picker, or just type it in. Heck, we could eventually even offer different time picker options even, along side the ability to apply different skinning styles :-) (This is meant as a tongue in cheek comment, but I would welcome this AFTER the system works again AND is proven solid several releases from now) I really need to work on the configuration area again... -Scott On Thu, Apr 21, 2011 at 9:45 AM, Mark Wrightson <ma...@rw...>wrote: > This is ok with me so long as the interface doesn't become confusing / > appear to have no common style. > If configuration is required then the config utility must also be 'world > class'. > > I just saw the time entry protoplasm thing and thought it looked very > clean and tidy. It could be a config option > to enable / disable it. The protoplasm time thing does allow for > keyboard style entry as well as clicking. > > It would be a big improvement to the current drop down menus on the > clocking popups. Saying this, i think > I may have lost the time entry bit to the clocking box..... Yep I did, > please svn update. The clocking popup on daily.php > would definitely benefit from protoplasm on the time entry. > > Mark > > _____________________________________________ > > Mob: 07725 695178 > Email: ma...@rw... > > > On 21/04/2011 10:15, David Thompson wrote: > > I think time and date entering are central to the application, so they > must be world class. > > > > But this will always be subjective, so maybe offering only one method is > the wrong way to go? > > > > Maybe we should offer every possible way we can find, to cover everyone's > tastes? > > > > Cheers > > > >> Date: Thu, 21 Apr 2011 09:10:10 +1000 > >> From: pal...@gm... > >> To: tsh...@li... > >> Subject: Re: [Tsheetx-developers] A beautiful time picker > >> > >> Dear All, > >> If you want to make use of the time picker, then I might as well convert > >> the date picker to the same group of code > >> (http://jongsma.org/software/protoplasm/control/datepicker). But I > would > >> also want that date picker to be the one and only date method in the > >> product. > >> > >> Any consensus on this? > >> > >> Peter > >> On 04/20/2011 08:19 PM, Mark Wrightson wrote: > >>> Hi Scott, > >>> > >>> This may be just the thing for your new daily page for the time > >>> selection part: > >>> > >>> http://jongsma.org/software/protoplasm/control/timepicker > >>> > >>> > >>> Mark > >>> > > > ------------------------------------------------------------------------------ > > Benefiting from Server Virtualization: Beyond Initial Workload > > Consolidation -- Increasing the use of server virtualization is a top > > priority.Virtualization can reduce costs, simplify management, and > improve > > application availability and disaster protection. Learn more about > boosting > > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > > _______________________________________________ > > Tsheetx-developers mailing list > > Tsh...@li... > > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > > > > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > |
|
From: Mark W. <ma...@rw...> - 2011-04-21 09:57:19
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
I have just discovered a new OOP technique that I had never heard
about before.<br>
Well i've been writing embedded C recently and found that you could
have static variables within a function.<br>
Thus that particular variable maintains state in each subsequent
call of the same function whilst keeping local scope instead of
class level scope / global scope.<br>
<br>
Now it turns out this is also possible in PHP so I thought I would
share it with everyone in case they find a good use for it. An
example is shown below:<br>
<br>
<div class="example-contents">
<div class="phpcode"><code><span style="color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 187);"><?php<br>
</span><span style="color: rgb(0, 119, 0);">function </span><span
style="color: rgb(0, 0, 187);">test</span><span
style="color: rgb(0, 119, 0);">()<br>
{<br>
static </span><span style="color: rgb(0, 0, 187);">$a </span><span
style="color: rgb(0, 119, 0);">= </span><span
style="color: rgb(0, 0, 187);">0</span><span style="color:
rgb(0, 119, 0);">;<br>
echo </span><span style="color: rgb(0, 0, 187);">$a</span><span
style="color: rgb(0, 119, 0);">;<br>
</span><span style="color: rgb(0, 0, 187);">$a</span><span
style="color: rgb(0, 119, 0);">++;<br>
}<br>
</span><span style="color: rgb(0, 0, 187);">test();<br>
test();<br>
test();<br>
?><br>
<br>
Information found here:
<a class="moz-txt-link-freetext" href="http://php.net/manual/en/language.variables.scope.php">http://php.net/manual/en/language.variables.scope.php</a><br>
<br>
Cheers!<br>
Mark</span></span></code><br>
</div>
</div>
<pre class="moz-signature" cols="72">--
_____________________________________________
Mob: 07725 695178
Email: <a class="moz-txt-link-abbreviated" href="mailto:ma...@rw...">ma...@rw...</a></pre>
</body>
</html>
|
|
From: Mark W. <ma...@rw...> - 2011-04-21 09:46:03
|
This is ok with me so long as the interface doesn't become confusing / appear to have no common style. If configuration is required then the config utility must also be 'world class'. I just saw the time entry protoplasm thing and thought it looked very clean and tidy. It could be a config option to enable / disable it. The protoplasm time thing does allow for keyboard style entry as well as clicking. It would be a big improvement to the current drop down menus on the clocking popups. Saying this, i think I may have lost the time entry bit to the clocking box..... Yep I did, please svn update. The clocking popup on daily.php would definitely benefit from protoplasm on the time entry. Mark _____________________________________________ Mob: 07725 695178 Email: ma...@rw... On 21/04/2011 10:15, David Thompson wrote: > I think time and date entering are central to the application, so they must be world class. > > But this will always be subjective, so maybe offering only one method is the wrong way to go? > > Maybe we should offer every possible way we can find, to cover everyone's tastes? > > Cheers > >> Date: Thu, 21 Apr 2011 09:10:10 +1000 >> From: pal...@gm... >> To: tsh...@li... >> Subject: Re: [Tsheetx-developers] A beautiful time picker >> >> Dear All, >> If you want to make use of the time picker, then I might as well convert >> the date picker to the same group of code >> (http://jongsma.org/software/protoplasm/control/datepicker). But I would >> also want that date picker to be the one and only date method in the >> product. >> >> Any consensus on this? >> >> Peter >> On 04/20/2011 08:19 PM, Mark Wrightson wrote: >>> Hi Scott, >>> >>> This may be just the thing for your new daily page for the time >>> selection part: >>> >>> http://jongsma.org/software/protoplasm/control/timepicker >>> >>> >>> Mark >>> > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > |
|
From: David T. <tom...@us...> - 2011-04-21 09:15:19
|
I think time and date entering are central to the application, so they must be world class. But this will always be subjective, so maybe offering only one method is the wrong way to go? Maybe we should offer every possible way we can find, to cover everyone's tastes? Cheers > Date: Thu, 21 Apr 2011 09:10:10 +1000 > From: pal...@gm... > To: tsh...@li... > Subject: Re: [Tsheetx-developers] A beautiful time picker > > Dear All, > If you want to make use of the time picker, then I might as well convert > the date picker to the same group of code > (http://jongsma.org/software/protoplasm/control/datepicker). But I would > also want that date picker to be the one and only date method in the > product. > > Any consensus on this? > > Peter > On 04/20/2011 08:19 PM, Mark Wrightson wrote: > > Hi Scott, > > > > This may be just the thing for your new daily page for the time > > selection part: > > > > http://jongsma.org/software/protoplasm/control/timepicker > > > > > > Mark > > |
|
From: Isabelle V. <ver...@fr...> - 2011-04-21 05:59:06
|
Hello, I have noticed that HTML messages are not well displayed on the mailing list and that they are not "scrubbed" but empty in the digests. It's better to send our messages to the mailing list as plain text content-type. Isabelle. |
|
From: Scott M. <sco...@gm...> - 2011-04-21 01:11:43
|
I'm not totally convinced that we want a time picker, but I'm not exactly against the idea either. The demo page I visited looked pretty large, I'm assuming that is adjustable? I have been too busy with actual work last few days, I haven't had a chance to see the updates to the date picker, but I'm looking forward to checking it out. -Scott On Wed, Apr 20, 2011 at 6:10 PM, Peter Lazarus <pal...@gm...> wrote: > Dear All, > If you want to make use of the time picker, then I might as well convert > the date picker to the same group of code > (http://jongsma.org/software/protoplasm/control/datepicker). But I would > also want that date picker to be the one and only date method in the > product. > > Any consensus on this? > > Peter > On 04/20/2011 08:19 PM, Mark Wrightson wrote: > > Hi Scott, > > > > This may be just the thing for your new daily page for the time > > selection part: > > > > http://jongsma.org/software/protoplasm/control/timepicker > > > > > > Mark > > > > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > |
|
From: Mark W. <ma...@rw...> - 2011-04-20 10:19:27
|
Hi Scott, This may be just the thing for your new daily page for the time selection part: http://jongsma.org/software/protoplasm/control/timepicker Mark -- _____________________________________________ Mob: 07725 695178 Email: ma...@rw... |
|
From: Mark W. <ma...@rw...> - 2011-04-20 10:02:39
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Peter, <br>
<br>
Good work on the datepicker. It is much much tidier now!<br>
<br>
There is several ways we can achieve internationalisation in
javascript. Your DateFormatSymbols sounds like the best option.<br>
<br>
Option 2: use the client_proj_task_javascript.class.php method to
generate the dynamic elements of the javascript. (n.b. SVN Update
before you look.)<br>
<br>
Option 3: a different version for each one as Isabelle suggests.<br>
<br>
Option 4: or... could a internationalisation javascript system be
implemented just like it has been done in php?<br>
<br>
<br>
Mark<br>
<pre class="moz-signature" cols="72">_____________________________________________
Mob: 07725 695178
Email: <a class="moz-txt-link-abbreviated" href="mailto:ma...@rw...">ma...@rw...</a></pre>
<br>
On 20/04/2011 10:07, Peter Lazarus wrote:
<blockquote cite="mid:4DA...@gm..." type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
Hi Isabelle,<br>
thanks for your comments. I have added a piece of text before the
calendar icon.<br>
<br>
Regarding the locale business, there is a java function which will
do this, but so far I haven't got it to work The class<span
class="f12b"><code><font color="#7f0055"><strong>
"DateFormatSymbols"</strong></font></code></span> gets the
months in the locale format. At this stage I am resisting changing
everything to the protoplasm datepicker code.<br>
<br>
Peter<br>
<br>
On 04/20/2011 05:03 PM, Isabelle Vergely wrote:
<blockquote
cite="mid:206...@sp..."
type="cite">
<pre wrap="">Hello Peter,
I like this new display of the java date picker in simple.php.
For internationalisation, the removal the date entry field
(input box) is a good idea.
Before the icon cal.gif, it would be useful to have a
string like JText::_('SELECT_OTHER_WEEK').
For internationalisation of the calendar, we can imagine
locale js files e.g. en_GB.js, fr_FR.js, es_ES.js with
the days and the months with the appropriate language.
To make the link between a java date picker and the
right locale js file, what do you think about these tools:
- <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://jongsma.org/software/protoplasm/control/datepicker?page=datepicker">http://jongsma.org/software/protoplasm/control/datepicker?page=datepicker</a>
- <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://docs.jquery.com/UI/Datepicker">http://docs.jquery.com/UI/Datepicker</a>
Cheers.
Isabelle.
</pre>
</blockquote>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/vmware-sfdev2dev">http://p.sf.net/sfu/vmware-sfdev2dev</a></pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Tsheetx-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tsh...@li...">Tsh...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/tsheetx-developers">https://lists.sourceforge.net/lists/listinfo/tsheetx-developers</a>
</pre>
</blockquote>
</body>
</html>
|
|
From: Isabelle V. <ver...@fr...> - 2011-04-20 07:03:52
|
Hello Peter,
I like this new display of the java date picker in simple.php.
For internationalisation, the removal the date entry field
(input box) is a good idea.
Before the icon cal.gif, it would be useful to have a
string like JText::_('SELECT_OTHER_WEEK').
For internationalisation of the calendar, we can imagine
locale js files e.g. en_GB.js, fr_FR.js, es_ES.js with
the days and the months with the appropriate language.
To make the link between a java date picker and the
right locale js file, what do you think about these tools:
- http://jongsma.org/software/protoplasm/control/datepicker?page=datepicker
- http://docs.jquery.com/UI/Datepicker
Cheers.
Isabelle.
|
|
From: Mark W. <ma...@rw...> - 2011-04-19 12:25:07
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear All, <br>
<br>
Since I started on the tsng project several months ago my aims have
been to:<br>
<br>
1) Convert the project to OO<br>
2) Improve the code structure<br>
3) Remove some of the code that involves a degree magic through the
use of includes and passing variables between these includes moving
to a class based structure<br>
4) Improve the error handling, error reporting, and debugging
capabilities<br>
5) Create a new framework that aids devleopment and makes the
project maintainable.<br>
<br>
To review:<br>
1) Much of the code is now functioning in the OO framework but quite
a lot of work is still required. Once the code 'works' as it once
did, we can move onto stage 2: restructuring the code that handles
the db queries and generating the tables / content. As it currently
stands I haven't really done anything to the actual application
level code.<br>
<br>
2) This is coming on slowly. The templating system has reduced the
quantity of code in each of the page files. When everything 'works'
again, stage 2 can commence which will make everything more readable
and understandable.<br>
<br>
3) Many pages included a file i.e. the navcal stuff that required
certain variables are set in the parent file so that navcal receives
the correct information. This is very bad programming practice as
there is no traceability and things either work or they don't. It
takes a lot of work to realise the coupling between the two files.
Therefore navcal is now class based and the required variables are
passed in through constructors and/or function calls. Readability
& Maintainability = 1 vs Magic = 0.<br>
<br>
4) The error handling whilst still in its infancy, has the
capability to speed up looking for errors in code. i.e. the error
screens display snippets of source code. Great for debugging. Also
the Debug class flags can be extremely useful. A good example is if
you click submit that then calls a *_action page, if you enable
Debug::$location then the _action page won't automatically redirect
back to where you originally came from allowing you to see any debug
statements related to that particular submission.<br>
<br>
5) Lots of good work is currently going on i.e.
Internationalisation, new Config, new Daily etc and all of this is
using the new framework i've spent quite a long time working on.
The other thing that is lacking in the project is comments.
Comments allow other developers to gauge an understanding before
reading code. It's not a perfect, example but look at
config.factory.class.php as it has quite a few comments before
functions, and inline. In comparison, just look at how poor the
commenting in common.class.php is? Using Javadoc style commenting
before functions and classes allows IDE's like eclipse to give you
snippets of documentation when you need it most. The eclipse auto
completion tools and javadoc popups are extremely useful when you
need to establish what variables need passing to a function.<br>
<br>
<br>
The common theme in everything I have done so far is to improve the
structure, readability and maintainability of the code in the
project. As I work on completing #1 I am changing a large number of
files simultaneously - see my last commit that updated 72 files! <br>
<br>
I have to say that I am slightly bemused as to why Scott has even
brought the if else problem up. I can't say whether I have or
haven't changed the structure of an already existing if else
statement to leave a carriage return between the } and the else.
But I more than likely have as I am working on changing so many
files. I will watch out next time i'm doing any work on tsng as I
can't say I intentionally change the ifelse structure. Many of the
changes I make in the OO change involve a degree of find/replace and
copy/paste.<br>
<br>
In my opinion this is more tidy and readable:<br>
<br>
if($i==1){<br>
echo 'i is one';<br>
echo '<br />';<br>
}<br>
else if($i==2){<br>
echo 'i is two';<br>
echo '<br />';<br>
}<br>
//inline comment<br>
else{<br>
echo 'i is not one or two';<br>
echo '<br />';<br>
}<br>
<br>
The alternative:<br>
<br>
if($i==1){<br>
echo 'i is one';<br>
echo '<br />';<br>
}else if($i==2){<br>
echo 'i is two';<br>
echo '<br />';<br>
}else{<br>
echo 'i is not one or two';<br>
echo '<br />';<br>
}<br>
<br>
The ifs and elses are all aligned with each other so when you are
glancing through code quickly the different cases can be seen very
quickly and easily. By having just a } on a line gives an amount of
separation that allows you to see the next if case. This format
also allows inline comments before an elseif/else statement.
Looking at Scotts preferred cuddled method, the next elseif case is
disguised in the rest of the code as there are no whitespace gaps
between the end of the first if case and the start of the second
making it more difficult to read. This is exacerbated when you have
large amounts of code in your if statement and / or long lines of
code at the beginning or end of each if case.<br>
<br>
In another example would you ever do this?:<br>
<br>
function($foo){<br>
echo "variable: ".$foo;<br>
}function($bar){<br>
echo "variable: ".$bar;<br>
}<br>
<br>
The answer is probably no. You would expect:<br>
<br>
<br>
function($foo){<br>
echo "variable: ".$foo;<br>
}<br>
<br>
function($bar){<br>
echo "variable: ".$bar;<br>
}<br>
<br>
What we should actually have is:<br>
<br>
/**<br>
* this is a description<br>
* @params String $foo - a random string<br>
*/<br>
function($foo){<br>
echo "variable: ".$foo;<br>
}<br>
<br>
/**<br>
* this is another description<br>
* @params String $bar - another random string<br>
*/<br>
function($bar){<br>
echo "variable: ".$bar;<br>
}<br>
<br>
Going back to the if elseif scenario, why bother to cramp the code
up making it more difficult to scan through? I've always followed
the coding standards rule of "do one thing and only one thing on
each line". Therefore I end an if case on one line and start the
elseif statement on the next line.<br>
<br>
<blockquote>Quote:18/04/2011 18:09GMT from Scott<br>
I do think that, in general, when working on an open source
project, new people should attempt to abide by whatever existing
style already exists, so long as that style is relatively sensible
and consistent.<br>
</blockquote>
I don't particularly buy into the statement above. That is akin to
saying I was here before you so therefore I am right. I am guessing
by the fact that we now have 4+ people working in the 2.0 branch
that the changes that I have been working on have been accepted by
the project. I therefore feel that the greater meaning to your
comment is slightly belittling. Before I started there wasn't a
huge amount of development being done. Now it appears that my work
has spurred more people to get back into development and the commit
rate of the project is significantly higher. TSNG is going through
a style change from functional PHP programming to OO PHP Programming
and with that comes a new style of code structure etc. Peter
acknowledged (16/04/2011 08:09GMT) that my preferred if else layout
improves the readability of the code, and that is what i'm trying to
achieve - more readability and better structure.<br>
<br>
<blockquote>Quote:14/04/2011 15:57GMT from Scott<br>
I realize change is sometimes disconcerting, so, play with it as
we develop it, and I think you'll see you're perhaps just trying
to cling to something that is familiar to you now.<br>
</blockquote>
Change as you rightly said Scott, is something that should be
embraced. Improvements can only be made if things change and I
think you are clinging onto an old style of practice for the sake of
change. White space is a good thing!<br>
<br>
<blockquote>Quote:18/04/2011 10:10 from David<br>
<pre>At some point early in the project I did apply a style to tidy up contributions from various people,
but as new people an contributions come then things change
(Entropy requires no maintenance. -- Markoff Chaney).</pre>
<pre>The best rule of thumb is:
keep functional changes separate from formatting/style changes. So Scott, put your pet peeves away at
the moment while the new code is written. I have seen projects where developers religiously
reformatted to their personal style on every commit, and you "can't see the wood for the trees".</pre>
</blockquote>
David does make a good point and i would like to add that i'm not
just reformatting code, i'm making changes to make tsng actually
work in the new framework.<br>
<br>
Regards<br>
Mark
<pre class="moz-signature" cols="72">_____________________________________________
Mob: 07725 695178
Email: <a class="moz-txt-link-abbreviated" href="mailto:ma...@rw...">ma...@rw...</a></pre>
<br>
On 18/04/2011 18:09, Scott Miller wrote:
<blockquote
cite="mid:BANLkTin=sbN...@ma..."
type="cite">Breaking your hand, that sucks, wishing you a speedy
recovery.<br>
<br>
Yeah, I see the point about Mantis.<br>
<br>
Codestyle: I'm not upset about the "cuddled / uncuddled elses",
but my first instinct is to go fix them all, and I realize that'
not what I should be spending my time doing. So I was hoping that
if Mark was amicable toward keeping elses cuddled, he would simply
stop uncuddling the elses. I do think that, in general, when
working on an open source project, new people should attempt to
abide by whatever existing style already exists, so long as that
style is relatively sensible and consistent.<br>
<br>
-Scott<br>
<br>
<div class="gmail_quote">On Mon, Apr 18, 2011 at 9:10 AM, David
Thompson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:tom...@us...">tom...@us...</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;"> Hi people.<br>
<br>
I have been quiet recently mostly due to work, but I also had
the misfortune a week ago to break my hand. But I have been
following what's been going on.<br>
<br>
So firstly, I want to say that I think it's great what
momentum and progress you have achieved on 2.0 so far. In the
past we have never had much more than two people on anything
at any one time. Thanks to everyone! I just wish I had more
time to help.<br>
<br>
I want to respond on a couple of points.<br>
<br>
Regarding Mantis: I agree with Mark - use it to record long
term TODOs, for immediate work on getting 2.0 stable and fully
featured the mailing list is best. But this is a good
reminder, try to prioritise and push things that can wait onto
Mantis, that way we will get 2.0 out quicker.<br>
<br>
Regarding codestyle: Somehow I'm honoured that you would
consider that I should decide, but you know that you can't win
on that one. At some point early in the project I did apply a
style to tidy up contributions from various people, but as new
people an contributions come then things change (Entropy
requires no maintenance. -- Markoff Chaney).<br>
<br>
The best rule of thumb is: keep functional changes separate
from formatting/style changes. So Scott, put your pet peeves
away at the moment while the new code is written. I have seen
projects where developers religiously reformatted to their
personal style on every commit, and you "can't see the wood
for the trees".<br>
<br>
So if you edit a file and it uses tabs then use tabs too, or
if it "cuddles elses" then do that too. But adapt on a
per-file basis. That way the other team members will better
see (and hopefully appreciate more) your contributions.<br>
<br>
I hope some of this makes sense (maybe I should cut down on
the painkillers...) <br>
<br>
Cheers<br>
------------------------------------------------------------------------------<br>
Benefiting from Server Virtualization: Beyond Initial Workload<br>
Consolidation -- Increasing the use of server virtualization
is a top<br>
priority.Virtualization can reduce costs, simplify management,
and improve<br>
application availability and disaster protection. Learn more
about boosting<br>
the value of server virtualization. <a moz-do-not-send="true"
href="http://p.sf.net/sfu/vmware-sfdev2dev" target="_blank">http://p.sf.net/sfu/vmware-sfdev2dev</a><br>
_______________________________________________<br>
Tsheetx-developers mailing list<br>
<a moz-do-not-send="true"
href="mailto:Tsh...@li...">Tsh...@li...</a><br>
<a moz-do-not-send="true"
href="https://lists.sourceforge.net/lists/listinfo/tsheetx-developers"
target="_blank">https://lists.sourceforge.net/lists/listinfo/tsheetx-developers</a><br>
<br>
</blockquote>
</div>
<br>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/vmware-sfdev2dev">http://p.sf.net/sfu/vmware-sfdev2dev</a></pre>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Tsheetx-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tsh...@li...">Tsh...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/tsheetx-developers">https://lists.sourceforge.net/lists/listinfo/tsheetx-developers</a>
</pre>
</blockquote>
</body>
</html>
|
|
From: Scott M. <sco...@gm...> - 2011-04-18 17:10:06
|
Breaking your hand, that sucks, wishing you a speedy recovery. Yeah, I see the point about Mantis. Codestyle: I'm not upset about the "cuddled / uncuddled elses", but my first instinct is to go fix them all, and I realize that' not what I should be spending my time doing. So I was hoping that if Mark was amicable toward keeping elses cuddled, he would simply stop uncuddling the elses. I do think that, in general, when working on an open source project, new people should attempt to abide by whatever existing style already exists, so long as that style is relatively sensible and consistent. -Scott On Mon, Apr 18, 2011 at 9:10 AM, David Thompson < tom...@us...> wrote: > Hi people. > > I have been quiet recently mostly due to work, but I also had the > misfortune a week ago to break my hand. But I have been following what's > been going on. > > So firstly, I want to say that I think it's great what momentum and > progress you have achieved on 2.0 so far. In the past we have never had much > more than two people on anything at any one time. Thanks to everyone! I just > wish I had more time to help. > > I want to respond on a couple of points. > > Regarding Mantis: I agree with Mark - use it to record long term TODOs, for > immediate work on getting 2.0 stable and fully featured the mailing list is > best. But this is a good reminder, try to prioritise and push things that > can wait onto Mantis, that way we will get 2.0 out quicker. > > Regarding codestyle: Somehow I'm honoured that you would consider that I > should decide, but you know that you can't win on that one. At some point > early in the project I did apply a style to tidy up contributions from > various people, but as new people an contributions come then things change > (Entropy requires no maintenance. -- Markoff Chaney). > > The best rule of thumb is: keep functional changes separate from > formatting/style changes. So Scott, put your pet peeves away at the moment > while the new code is written. I have seen projects where developers > religiously reformatted to their personal style on every commit, and you > "can't see the wood for the trees". > > So if you edit a file and it uses tabs then use tabs too, or if it "cuddles > elses" then do that too. But adapt on a per-file basis. That way the other > team members will better see (and hopefully appreciate more) your > contributions. > > I hope some of this makes sense (maybe I should cut down on the > painkillers...) > > Cheers > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > > |
|
From: David T. <tom...@us...> - 2011-04-18 09:10:26
|
Hi people.I have been quiet recently mostly due to work, but I also had the misfortune a week ago to break my hand. But I have been following what's been going on.So firstly, I want to say that I think it's great what momentum and progress you have achieved on 2.0 so far. In the past we have never had much more than two people on anything at any one time. Thanks to everyone! I just wish I had more time to help.I want to respond on a couple of points.Regarding Mantis: I agree with Mark - use it to record long term TODOs, for immediate work on getting 2.0 stable and fully featured the mailing list is best. But this is a good reminder, try to prioritise and push things that can wait onto Mantis, that way we will get 2.0 out quicker.Regarding codestyle: Somehow I'm honoured that you would consider that I should decide, but you know that you can't win on that one. At some point early in the project I did apply a style to tidy up contributions from various people, but as new people an contributions come then things change (Entropy requires no maintenance. -- Markoff Chaney).The best rule of thumb is: keep functional changes separate from formatting/style changes. So Scott, put your pet peeves away at the moment while the new code is written. I have seen projects where developers religiously reformatted to their personal style on every commit, and you "can't see the wood for the trees".So if you edit a file and it uses tabs then use tabs too, or if it "cuddles elses" then do that too. But adapt on a per-file basis. That way the other team members will better see (and hopefully appreciate more) your contributions. I hope some of this makes sense (maybe I should cut down on the painkillers...) Cheers |
|
From: Scott M. <sco...@gm...> - 2011-04-15 23:10:01
|
I've made some improvements on the newdaily page |
|
From: Mark W. <ma...@rw...> - 2011-04-15 21:51:45
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I think we should really start making more use of mantis. Mantis is
a fantastic tool and its functionality is designed to aid project
development i.e. roadmaps. If items are added to mantis then they
cannot be forgotten about. Yes the mailing list is archived but i
bet noone ever goes searching through the mailing list for forgotten
ideas, whereas if it was added as a new feature on mantis, assigned
to a member and given a target version such that it appears on the
roadmap, everyone then has a comprehensive todo list to get the next
version out of the door.<br>
<br>
Mark<br>
<pre class="moz-signature" cols="72">_____________________________________________
Mob: 07725 695178
Email: <a class="moz-txt-link-abbreviated" href="mailto:ma...@rw...">ma...@rw...</a></pre>
<br>
On 15/04/2011 22:39, Scott Miller wrote:
<blockquote
cite="mid:BANLkTi=8=P2r...@ma..."
type="cite">Absolutely, take the time you need to finish your
school project, this will still be here after that.<br>
<br>
I would agree that session objects seem to be the thing we should
be using to keep track of these items. Since there's no real
"bug" yet, and I've been pondering it off and on for months, and
it's now in the mail list archives, I don't think we'll forget,
there's really no need to add this to mantis at this time...<br>
<br>
-Scott<br>
<br>
<div class="gmail_quote">On Fri, Apr 15, 2011 at 9:10 PM, Mark
Wrightson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ma...@rw...">ma...@rw...</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> Hi Scott, <br>
<br>
I was thinking a little bit about this yesterday as I spent
a substantial amount of time fixing the $post variables. As
it currently stands, the $post variable is now in the
gbl.class.php and is accessed via gbl::getPost() and
gbl::setPost(). Please let me know if a particular page
doesn't work as it should. <br>
<br>
If you want to maintain state between page refreshes then
the best way to achieve this is through the use of the
$_SESSION object or serialised classes embedded in the
$_SESSION object. I will update this at somepoint but at
the moment I am still trying to work my way through the
codebase to make things just work. The move to the OO
format is a huge undertaking and it is not really my top
priority at the moment as I have a project dissertation that
needs my attention for the next couple of months. Scott
could you add this item into mantis and assign it to me?<br>
<br>
Cheers<br>
Mark<br>
<pre cols="72">_____________________________________________
Mob: <a moz-do-not-send="true" href="tel:07725%20695178" value="+17725695178" target="_blank">07725 695178</a>
Email: <a moz-do-not-send="true" href="mailto:ma...@rw..." target="_blank">ma...@rw...</a></pre>
<div>
<div class="h5"> <br>
On 15/04/2011 21:04, Scott Miller wrote:
<blockquote type="cite">In the previous versions of
TSNG, I'd attempted to better keep track of what
"context" the user was in. I'd accomplished this by
making use of a variable I'd called $post, and used
that whenever forms were submitted. This was much
better than it was previously, but it was not flawless
by any stretch of the imagination.<br>
<br>
So, to help make sure everyone understands what I'm
talking about, allow me to expound on what the word
"context" means herein. Context is sort of the "state
of mind" the user is in when trying to accomplish
something. As a normal user, if I go back in time to
look at something lets say in the weekly form, and
then decide I want to look at that with a different
form, say the monthly form, in previous versions, by
switching forms, the application totally forgot the
user had gone back in time, and presented the current
month again. By keeping track of context, the user is
now presented with the month the user had gone back to
look at. This is one very basic and important item of
context that I think we need to keep track of, what
date is the user currently interested in?<br>
<br>
Another example is if I'm now an administrator, and a
user has some problem with their previously entered
time, I can "become" the user by changing the "context
user" and from there, I can act as if I was the user
and I can even modify the user's time entries if I
need to do so. (Note: this option is only available to
the "administrator" accounts, and to guard against
unscrupulous managers, who might be tempted to
fraudulently modify an underling's times, never make a
manager an administrator. It is quite amazing in a
tiny office how often we as administrators had to
legitimately help fix someone's time entries).<br>
<br>
So far we have <br>
<ul>
<li>Context</li>
<ul>
<li>user id</li>
<li>date user is interested in</li>
</ul>
</ul>
We can add other items; if we're looking at a report
and we are interested in a range of dates for a
report, we need to keep track of the beginning and
ending date of interest. With new options just
created, another item might be if we want page areas
shown or hidden.<br>
<br>
So, with all this, my main question to the group is
how do we effectively keep track of all this potential
context? With Mark as the OO guy, I'm hoping you have
some good ideas for helping us keep track of it all,
and I'm hoping that option is better than the hugely
long set of post variables currently passed back and
forth. This is particularly important when we move to
using the java pop up calendar for navigation...<br>
<br>
-Scott<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</blockquote>
</body>
</html>
|
29 messages has been excluded from this view by a project administrator.
