Menu
▾
▴
tsheetx-developers
|
From: Scott M. <sco...@gm...> - 2011-02-10 16:04:55
|
Hey everyone, So, I've nearly dropped off the face of the earth over the past several months with regards to this project, but I'm recently back working on fixing the configuration table, which, in my opinion, is a horrible mess. My goal, once the new configuration table is working well, is to also create a similar structure that can be used for per user configuration items. In a day and a half, I've managed to get a large chunk of that work done. So, who is actively working on improving which parts of the system at the moment? Mark Wrightson, are you still working on improving the code base? Is anyone working on internationalization (ability to do translations to other languages)? -Scott |
|
From: Mark W. <ma...@rw...> - 2011-02-10 16:58:09
|
<!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 text="#000000" bgcolor="#ffffff">
Hi Scott, <br>
<br>
Myself and Peter have been very busy over the last couple of months
working on cleaning up the entire codebase, making it much more
Object Orientated cleaning up XHTML errors and css-ifying everything
to make it more skinnable and manageable. Please look at our
txsheet-2.0-demo to see what we have been upto. Unfortunately both
myself and Peter have been quite busy lately so nothing has changed
since about 10th Jan. There is still a fair bit to go on our side
before it would be classed as 'stable'.<br>
<br>
On my list of things to do are: <br>
a) update the way the menu is built changing the structure to be
more like: <a class="moz-txt-link-freetext" href="http://www.scm-uk.com">http://www.scm-uk.com</a><br>
b) improve the authorisation/authentication mechanisms to make it
more versatile but i need to recompile php with ldap before<br>
I can do this. ( can anyone help here)<br>
<br>
Since peter and I started back in Novemeber nothing has been changed
in the trunk as far as I know which as it stands makes it very
convenient for merging our changes once our changes have been
approved. So far we have left all database tables alone however we
have stopped using the html header, footer, etc from the config
files in favour of a template / theme style method.<br>
<br>
Peter has a nice list of all the changes we have made so maybe now
is the time to ask him to email it out to everyone?<br>
I should stress that while we have made quite a lot of changes in
our branch about 90+% of the codebase remains unchanged.<br>
It is mainly structural upgrades that we have been making.<br>
<br>
May I ask what changes you are planning to the config table and what
you mean by user configuration items?<br>
<br>
All the best<br>
Mark Wrightson<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 10/02/2011 16:04, Scott Miller wrote:
<blockquote
cite="mid:AANLkTimoVrL7-EJcDDdU=Hn2...@ma..."
type="cite">Hey everyone,<br>
<br>
So, I've nearly dropped off the face of the earth over the past
several months with regards to this project, but I'm recently back
working on fixing the configuration table, which, in my opinion,
is a horrible mess. My goal, once the new configuration table is
working well, is to also create a similar structure that can be
used for per user configuration items. In a day and a half, I've
managed to get a large chunk of that work done.<br>
<br>
So, who is actively working on improving which parts of the system
at the moment?<br>
<br>
Mark Wrightson, are you still working on improving the code base?<br>
Is anyone working on internationalization (ability to do
translations to other languages)?<br>
<br>
-Scott<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/intel-dev2devfeb">http://p.sf.net/sfu/intel-dev2devfeb</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-02-10 17:42:13
|
Good to hear about the HTML stuff in the database now being ignored, and moving to some sort of template system; I think that will be much nicer than having that stuff in the database. I would certainly be interested in reading what peter has... There are many suggested improvements that are impossible without having per user configuration options. Things like having each user able to create a default set of time entries per week, eventually allowing the user to set their own timezone (once we can store times as UTC). Once we have this ability a whole myriad of new possibilities are opened up to further improve the user experience. Peter Lazarus, are you still working on improving the "managment approval" area? -Scott On Thu, Feb 10, 2011 at 4:23 PM, Mark Wrightson <ma...@rw...>wrote: > Hi Scott, > > Myself and Peter have been very busy over the last couple of months working > on cleaning up the entire codebase, making it much more Object Orientated > cleaning up XHTML errors and css-ifying everything to make it more skinnable > and manageable. Please look at our txsheet-2.0-demo to see what we have > been upto. Unfortunately both myself and Peter have been quite busy lately > so nothing has changed since about 10th Jan. There is still a fair bit to > go on our side before it would be classed as 'stable'. > > On my list of things to do are: > a) update the way the menu is built changing the structure to be more like: > http://www.scm-uk.com > b) improve the authorisation/authentication mechanisms to make it more > versatile but i need to recompile php with ldap before > I can do this. ( can anyone help here) > > Since peter and I started back in Novemeber nothing has been changed in the > trunk as far as I know which as it stands makes it very convenient for > merging our changes once our changes have been approved. So far we have > left all database tables alone however we have stopped using the html > header, footer, etc from the config files in favour of a template / theme > style method. > > Peter has a nice list of all the changes we have made so maybe now is the > time to ask him to email it out to everyone? > I should stress that while we have made quite a lot of changes in our > branch about 90+% of the codebase remains unchanged. > It is mainly structural upgrades that we have been making. > > May I ask what changes you are planning to the config table and what you > mean by user configuration items? > > All the best > Mark Wrightson > > _____________________________________________ > > Mob: 07725 695178 > Email: ma...@rw... > > > On 10/02/2011 16:04, Scott Miller wrote: > > Hey everyone, > > So, I've nearly dropped off the face of the earth over the past several > months with regards to this project, but I'm recently back working on fixing > the configuration table, which, in my opinion, is a horrible mess. My goal, > once the new configuration table is working well, is to also create a > similar structure that can be used for per user configuration items. In a > day and a half, I've managed to get a large chunk of that work done. > > So, who is actively working on improving which parts of the system at the > moment? > > Mark Wrightson, are you still working on improving the code base? > Is anyone working on internationalization (ability to do translations to > other languages)? > > -Scott > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance.http://p.sf.net/sfu/intel-dev2devfeb > > > _______________________________________________ > Tsheetx-developers mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > > |
|
From: Scott M. <sco...@gm...> - 2011-02-10 18:00:42
|
Oh, sorry, I didn't answer what the new config stuff would look like:
rather than having each configuration item have it's own column in the
database, I'm making the table generic, so we can easily add whatever we
want to the configuration table. So it currently looks like this:
columns are: name | type | INT | FLOAT | TEXT
INT and FLOAT are their namesake types, name is varchar(35), type is an enum
('INT','FLOAT','TEXT') defaulting to text, and TEXT is of type MEDIUMTEXT
(which was done to make sure there was enough space for the HTML entities,
which with your work, would mean we could probably safely make that of type
TEXT instead)
An example select from the database looks like this:
mysql> select * from tstrunk_new_config where name not like "HTML%";
+------------------------+------+------+-------+------------------------------+
| name | type | INT | FLOAT |
TEXT |
+------------------------+------+------+-------+------------------------------+
| version | TEXT | NULL | NULL |
1.6.0 |
| locale | TEXT | NULL | NULL
| |
| timezone | TEXT | NULL | NULL |
US/Central |
| timeformat | INT | 12 | NULL |
NULL |
| weekstartday | INT | 1 | NULL |
NULL |
| startPage | TEXT | NULL | NULL |
monthly |
| project_items_per_page | INT | 20 | NULL |
NULL |
| task_items_per_page | INT | 20 | NULL |
NULL |
| simpleTimesheetLayout | TEXT | NULL | NULL | small work description
field |
| useLDAP | INT | 0 | NULL |
NULL |
| LDAPurl | TEXT | NULL | NULL |
ldap://watson:389 |
| LDAPBaseDN | TEXT | NULL | NULL |
dc=watson |
| LDAPUsernameAttribute | TEXT | NULL | NULL |
cn |
| LDAPSearchScope | TEXT | NULL | NULL |
base |
| LDAPFilter | TEXT | NULL | NULL
| |
| LDAPProtocolVersion | TEXT | NULL | NULL |
3 |
| LDAPBindUsername | TEXT | NULL | NULL
| |
| LDAPBindPassword | TEXT | NULL | NULL
| |
| LDAPReferrals | INT | 0 | NULL |
NULL |
| LDAPFallback | INT | 0 | NULL |
NULL |
+------------------------+------+------+-------+------------------------------+
Oh, you can also see above, I've replaced several of the old LDAP items with
an LDAPurl item instead...
-Scott
On Thu, Feb 10, 2011 at 5:42 PM, Scott Miller <sco...@gm...>wrote:
> Good to hear about the HTML stuff in the database now being ignored, and
> moving to some sort of template system; I think that will be much nicer than
> having that stuff in the database. I would certainly be interested in
> reading what peter has...
>
> There are many suggested improvements that are impossible without having
> per user configuration options. Things like having each user able to create
> a default set of time entries per week, eventually allowing the user to set
> their own timezone (once we can store times as UTC). Once we have this
> ability a whole myriad of new possibilities are opened up to further improve
> the user experience.
>
> Peter Lazarus, are you still working on improving the "managment approval"
> area?
>
> -Scott
>
>
> On Thu, Feb 10, 2011 at 4:23 PM, Mark Wrightson <ma...@rw...>wrote:
>
>> Hi Scott,
>>
>> Myself and Peter have been very busy over the last couple of months
>> working on cleaning up the entire codebase, making it much more Object
>> Orientated cleaning up XHTML errors and css-ifying everything to make it
>> more skinnable and manageable. Please look at our txsheet-2.0-demo to see
>> what we have been upto. Unfortunately both myself and Peter have been quite
>> busy lately so nothing has changed since about 10th Jan. There is still a
>> fair bit to go on our side before it would be classed as 'stable'.
>>
>> On my list of things to do are:
>> a) update the way the menu is built changing the structure to be more
>> like: http://www.scm-uk.com
>> b) improve the authorisation/authentication mechanisms to make it more
>> versatile but i need to recompile php with ldap before
>> I can do this. ( can anyone help here)
>>
>> Since peter and I started back in Novemeber nothing has been changed in
>> the trunk as far as I know which as it stands makes it very convenient for
>> merging our changes once our changes have been approved. So far we have
>> left all database tables alone however we have stopped using the html
>> header, footer, etc from the config files in favour of a template / theme
>> style method.
>>
>> Peter has a nice list of all the changes we have made so maybe now is the
>> time to ask him to email it out to everyone?
>> I should stress that while we have made quite a lot of changes in our
>> branch about 90+% of the codebase remains unchanged.
>> It is mainly structural upgrades that we have been making.
>>
>> May I ask what changes you are planning to the config table and what you
>> mean by user configuration items?
>>
>> All the best
>> Mark Wrightson
>>
>> _____________________________________________
>>
>> Mob: 07725 695178
>> Email: ma...@rw...
>>
>>
>> On 10/02/2011 16:04, Scott Miller wrote:
>>
>> Hey everyone,
>>
>> So, I've nearly dropped off the face of the earth over the past several
>> months with regards to this project, but I'm recently back working on fixing
>> the configuration table, which, in my opinion, is a horrible mess. My goal,
>> once the new configuration table is working well, is to also create a
>> similar structure that can be used for per user configuration items. In a
>> day and a half, I've managed to get a large chunk of that work done.
>>
>> So, who is actively working on improving which parts of the system at the
>> moment?
>>
>> Mark Wrightson, are you still working on improving the code base?
>> Is anyone working on internationalization (ability to do translations to
>> other languages)?
>>
>> -Scott
>>
>>
>> ------------------------------------------------------------------------------
>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>> Pinpoint memory and threading errors before they happen.
>> Find and fix more than 250 security defects in the development cycle.
>> Locate bottlenecks in serial and parallel code that limit performance.http://p.sf.net/sfu/intel-dev2devfeb
>>
>>
>> _______________________________________________
>> Tsheetx-developers mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>>
>>
>>
>> ------------------------------------------------------------------------------
>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>> Pinpoint memory and threading errors before they happen.
>> Find and fix more than 250 security defects in the development cycle.
>> Locate bottlenecks in serial and parallel code that limit performance.
>> http://p.sf.net/sfu/intel-dev2devfeb
>> _______________________________________________
>> Tsheetx-developers mailing list
>> Tsh...@li...
>> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>>
>>
>
|
|
From: David T. <tom...@us...> - 2011-02-13 12:56:44
|
Answers below: > Date: Fri, 11 Feb 2011 16:34:01 +0000 > From: ma...@rw... > To: tsh...@li... > Subject: Re: [Tsheetx-developers] Who's actively working on the TSNG system? > > Does anyone know what the timesheet.ng-2.x branch is? - if checked out it doesn't run > and there doesn't appear to be any information how to make it run (if indeed it would). This branch can now be junked. It is the work of Rob Searles (the guy who started this - and still pays for the domainname). He wanted to go more MVC-like and this was his start. I think the better starting point is now txsheet-2.0-demo. > > Scott, when you refer to the txsheet-2.0 branch which one do you mean? > timesheet.ng-2.x or txsheet-2.0-demo? > Its my bad for naming the branch in an unconventional way, it could be renamed? Renaming an existing branch is one simple command in SVN, but can cause a lot of confusion to people with working copies based on that branch. So I wouldn't recommend it, we can solve the confusion by removing the other branch. > > Myself and peter have currently tried to keep as much of the codebase intact as to > not introduce thousands of bugs while doing some restructuring. At least this way > we can get to a 'stable' point more quickly, get more developers involved to then > go nuts with the core parts of the txsheet codebase. :) > > One thing I have wondered is svn is great at propagating code changes but not db >changes. What is the best method to make changes to your db and then notify > developers that their db will need to be modified? An sql file can be written to > make the changes and stored in the sql folder but what about the notification bit? > - maybe an automated routine could be written? - start making more use of the > version number in the config table and started incrementing the minor version > number when a database tweak is required? Yes, it is a problem, but only for people with live data based on that developmental version (which is unusual). Simplest would be to start an "upgrade" script (see the examples in /install) and update the file every time you commit a change to the DB structure. That way when people update their working copies, they see a diff in that file to show them what DB structure changes have been made. I think using lots of minor version numbers is too much work. > Re: Can anyone claim responsibility for the changes? > To which part? - could you just run blame? > So far txsheet-2.0-demo has just been Peter and Mark (me) Blame just tells me who made the changes, I would like someone to take responsibility for them. Meaning - it is their baby, and they will keep on the work until it is merged into the ongoing work. Someone else's half-finished code is what I deal with at work, I am not so keen to do it in my spare time too. Cheers |
|
From: Mark W. <ma...@rw...> - 2011-02-13 16:57:00
|
txsheet-2.0-demo is currently my baby, and i'll continue with it until it is fit for merging. Saying that however, Peter has contributed quite a lot aswell and if anyone else is available to help please let me know! Mark _____________________________________________ Mob: 07725 695178 Email: ma...@rw... On 13/02/2011 12:56, David Thompson wrote: > Blame just tells me who made the changes, I would like someone to take > responsibility for them. Meaning - it is their baby, and they will > keep on the work until it is merged into the ongoing work. Someone > else's half-finished code is what I deal with at work, I am not so > keen to do it in my spare time too. |
|
From: Scott M. <Sco...@pr...> - 2011-02-14 16:08:34
|
My current work environment is a bit up in the air at the moment, so I can't promise a lot, but I would certainly like to help with the new version. After having the configuration stuff sit on my brain for the better part of a year, and then thinking about it in detail for a few minutes, I came to the realization that I could probably knock that out relatively quickly. The learning curve for the new system may keep me from being able to finish that stuff in 2.0 (yes, I mean the demo), but I'm certainly not ready to give up on that yet. -Scott -----Original Message----- From: Mark Wrightson [mailto:ma...@rw...] Sent: Sunday, February 13, 2011 10:57 AM To: tsh...@li... Subject: Re: [Tsheetx-developers] Who's actively working on the TSNG system? txsheet-2.0-demo is currently my baby, and i'll continue with it until it is fit for merging. Saying that however, Peter has contributed quite a lot aswell and if anyone else is available to help please let me know! Mark _____________________________________________ Mob: 07725 695178 Email: ma...@rw... On 13/02/2011 12:56, David Thompson wrote: > Blame just tells me who made the changes, I would like someone to take > responsibility for them. Meaning - it is their baby, and they will > keep on the work until it is merged into the ongoing work. Someone > else's half-finished code is what I deal with at work, I am not so > keen to do it in my spare time too. ------------------------------------------------------------------------ ------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Tsheetx-developers mailing list Tsh...@li... https://lists.sourceforge.net/lists/listinfo/tsheetx-developers |
|
From: Mark W. <ma...@rw...> - 2011-02-11 16:33:58
|
<!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 text="#000000" bgcolor="#ffffff">
Does anyone know what the timesheet.ng-2.x branch is? - if checked
out it doesn't run and there doesn't appear to be any information
how to make it run (if indeed it would).<br>
<br>
Scott, when you refer to the txsheet-2.0 branch which one do you
mean? timesheet.ng-2.x or txsheet-2.0-demo?<br>
Its my bad for naming the branch in an unconventional way, it could
be renamed?<br>
<br>
Myself and peter have currently tried to keep as much of the
codebase intact as to not introduce thousands of bugs while doing
some restructuring. At least this way we can get to a 'stable'
point more quickly, get more developers involved to then go nuts
with the core parts of the txsheet codebase. :)<br>
<br>
One thing I have wondered is svn is great at propagating code
changes but not db changes. What is the best method to make changes
to your db and then notify developers that their db will need to be
modified? An sql file can be written to make the changes and stored
in the sql folder but what about the notification bit? - maybe an
automated routine could be written? - start making more use of the
version number in the config table and started incrementing the
minor version number when a database tweak is required?<br>
<br>
Re: Can anyone claim responsibility for the changes?<br>
To which part? - could you just run blame?<br>
So far txsheet-2.0-demo has just been Peter and Mark (me)<br>
<br>
Cheers<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 11/02/2011 15:22, David Thompson wrote:
<blockquote cite="mid:BAY...@ph...l"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
Scott - I like your idea with the generic config table, but have
you considered defaults?<br>
Mark, Peter - I am impressed by your progress, well done, a rework
like this will give the "next gen" feel that we need. And don't
worry about rewriting 90% of the code, go ahead if necessary.<br>
<br>
I am not actively working on anything (well, related to TSNG I
mean), but I keep an eye on what is going on. There are a number
of branches where changes have been made that should really be
completed and merged into the trunk, or merged into txsheet-2.0
and further developed there. Can anyone claim responsibility for
the changes?<br>
<br>
Cheers<br>
tommo<br>
<br>
<hr id="stopSpelling">
Date: Fri, 11 Feb 2011 10:21:53 +1100<br>
From: <a class="moz-txt-link-abbreviated" href="mailto:pal...@gm...">pal...@gm...</a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:tsh...@li...">tsh...@li...</a><br>
Subject: [Tsheetx-developers] [SPAM] Re: Who's actively working on
the TSNG system?<br>
<br>
<meta name="Generator" content="Microsoft SafeHTML">
Scott,<br>
you asked if I have done more work on the 'management approval'
area. The answer is no. I have incorporated the management
approval process into branches/txsheet-2.0-demo but nothing
further has been added. I have spent most of my development time
on the changes made in conjunction with Mark.<br>
<br>
Peter<br>
<br>
On 11/02/11 05:00, Scott Miller wrote:
<blockquote
cite="mid:AAN...@ma...">Oh,
sorry, I didn't answer what the new config stuff would look
like: rather than having each configuration item have it's own
column in the database, I'm making the table generic, so we can
easily add whatever we want to the configuration table. So it
currently looks like this:<br>
<br>
columns are: name | type | INT | FLOAT | TEXT<br>
INT and FLOAT are their namesake types, name is varchar(35),
type is an enum ('INT','FLOAT','TEXT') defaulting to text, and
TEXT is of type MEDIUMTEXT (which was done to make sure there
was enough space for the HTML entities, which with your work,
would mean we could probably safely make that of type TEXT
instead)<br>
<br>
An example select from the database looks like this:<br>
<span style="font-family: courier new,monospace;">mysql>
select * from tstrunk_new_config where name not like "HTML%";</span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">+------------------------+------+------+-------+------------------------------+</span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">|
name | type | INT | FLOAT |
TEXT |</span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">+------------------------+------+------+-------+------------------------------+</span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">|
version | TEXT | NULL | NULL |
1.6.0 | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
locale | TEXT | NULL | NULL
| | </span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">|
timezone | TEXT | NULL | NULL |
US/Central | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
timeformat | INT | 12 | NULL |
NULL | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
weekstartday | INT | 1 | NULL |
NULL | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
startPage | TEXT | NULL | NULL |
monthly | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
project_items_per_page | INT | 20 | NULL |
NULL | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
task_items_per_page | INT | 20 | NULL |
NULL | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
simpleTimesheetLayout | TEXT | NULL | NULL | small work
description field | </span><br style="font-family: courier
new,monospace;">
<span style="font-family: courier new,monospace;">|
useLDAP | INT | 0 | NULL |
NULL | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPurl | TEXT | NULL | NULL | <a
moz-do-not-send="true" class="ecxmoz-txt-link-freetext"
target="_blank">ldap://watson:389</a> | </span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPBaseDN | TEXT | NULL | NULL |
dc=watson | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPUsernameAttribute | TEXT | NULL | NULL |
cn | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPSearchScope | TEXT | NULL | NULL |
base | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPFilter | TEXT | NULL | NULL
| | </span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPProtocolVersion | TEXT | NULL | NULL |
3 | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPBindUsername | TEXT | NULL | NULL
| | </span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPBindPassword | TEXT | NULL | NULL
| | </span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPReferrals | INT | 0 | NULL |
NULL | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">|
LDAPFallback | INT | 0 | NULL |
NULL | </span><br style="font-family:
courier new,monospace;">
<span style="font-family: courier new,monospace;">+------------------------+------+------+-------+------------------------------+</span><br>
<br>
Oh, you can also see above, I've replaced several of the old
LDAP items with an LDAPurl item instead...<br>
<br>
-Scott<br>
<br>
<div class="ecxgmail_quote">On Thu, Feb 10, 2011 at 5:42 PM,
Scott Miller <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sco...@gm...">sco...@gm...</a>></span>
wrote:<br>
<blockquote style="padding-left: 1ex;" class="ecxgmail_quote">Good
to hear about the HTML stuff in the database now being
ignored, and moving to some sort of template system; I think
that will be much nicer than having that stuff in the
database. I would certainly be interested in reading what
peter has...<br>
<br>
There are many suggested improvements that are impossible
without having per user configuration options. Things like
having each user able to create a default set of time
entries per week, eventually allowing the user to set their
own timezone (once we can store times as UTC). Once we have
this ability a whole myriad of new possibilities are opened
up to further improve the user experience.<br>
<br>
Peter Lazarus, are you still working on improving the
"managment approval" area?<br>
<font color="#888888"><br>
-Scott</font></blockquote>
</div>
<br>
</blockquote>
<br>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel
Studio XE: Pinpoint memory and threading errors before they
happen. Find and fix more than 250 security defects in the
development cycle. Locate bottlenecks in serial and parallel code
that limit performance. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/intel-dev2devfeb">http://p.sf.net/sfu/intel-dev2devfeb</a><br>
_______________________________________________ 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 wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/intel-dev2devfeb">http://p.sf.net/sfu/intel-dev2devfeb</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-02-11 16:42:43
|
>From a distant memory, I think the 2.x branch is a long ago abandoned work
by Rob Searles (the, or at least one of the, New Gen originating guys)...
-Scott
On Fri, Feb 11, 2011 at 4:34 PM, Mark Wrightson <ma...@rw...>wrote:
> Does anyone know what the timesheet.ng-2.x branch is? - if checked out it
> doesn't run and there doesn't appear to be any information how to make it
> run (if indeed it would).
>
> Scott, when you refer to the txsheet-2.0 branch which one do you mean?
> timesheet.ng-2.x or txsheet-2.0-demo?
> Its my bad for naming the branch in an unconventional way, it could be
> renamed?
>
> Myself and peter have currently tried to keep as much of the codebase
> intact as to not introduce thousands of bugs while doing some
> restructuring. At least this way we can get to a 'stable' point more
> quickly, get more developers involved to then go nuts with the core parts of
> the txsheet codebase. :)
>
> One thing I have wondered is svn is great at propagating code changes but
> not db changes. What is the best method to make changes to your db and then
> notify developers that their db will need to be modified? An sql file can
> be written to make the changes and stored in the sql folder but what about
> the notification bit? - maybe an automated routine could be written? - start
> making more use of the version number in the config table and started
> incrementing the minor version number when a database tweak is required?
>
> Re: Can anyone claim responsibility for the changes?
> To which part? - could you just run blame?
> So far txsheet-2.0-demo has just been Peter and Mark (me)
>
> Cheers
> Mark
>
> _____________________________________________
>
> Mob: 07725 695178
> Email: ma...@rw...
>
>
> On 11/02/2011 15:22, David Thompson wrote:
>
> Scott - I like your idea with the generic config table, but have you
> considered defaults?
> Mark, Peter - I am impressed by your progress, well done, a rework like
> this will give the "next gen" feel that we need. And don't worry about
> rewriting 90% of the code, go ahead if necessary.
>
> I am not actively working on anything (well, related to TSNG I mean), but I
> keep an eye on what is going on. There are a number of branches where
> changes have been made that should really be completed and merged into the
> trunk, or merged into txsheet-2.0 and further developed there. Can anyone
> claim responsibility for the changes?
>
> Cheers
> tommo
>
> ------------------------------
> Date: Fri, 11 Feb 2011 10:21:53 +1100
> From: pal...@gm...
> To: tsh...@li...
> Subject: [Tsheetx-developers] [SPAM] Re: Who's actively working on the TSNG
> system?
>
> Scott,
> you asked if I have done more work on the 'management approval' area. The
> answer is no. I have incorporated the management approval process into
> branches/txsheet-2.0-demo but nothing further has been added. I have spent
> most of my development time on the changes made in conjunction with Mark.
>
> Peter
>
> On 11/02/11 05:00, Scott Miller wrote:
>
> Oh, sorry, I didn't answer what the new config stuff would look like:
> rather than having each configuration item have it's own column in the
> database, I'm making the table generic, so we can easily add whatever we
> want to the configuration table. So it currently looks like this:
>
> columns are: name | type | INT | FLOAT | TEXT
> INT and FLOAT are their namesake types, name is varchar(35), type is an
> enum ('INT','FLOAT','TEXT') defaulting to text, and TEXT is of type
> MEDIUMTEXT (which was done to make sure there was enough space for the HTML
> entities, which with your work, would mean we could probably safely make
> that of type TEXT instead)
>
> An example select from the database looks like this:
> mysql> select * from tstrunk_new_config where name not like "HTML%";
>
> +------------------------+------+------+-------+------------------------------+
> | name | type | INT | FLOAT |
> TEXT |
>
> +------------------------+------+------+-------+------------------------------+
> | version | TEXT | NULL | NULL |
> 1.6.0 |
> | locale | TEXT | NULL | NULL
> | |
> | timezone | TEXT | NULL | NULL |
> US/Central |
> | timeformat | INT | 12 | NULL |
> NULL |
> | weekstartday | INT | 1 | NULL |
> NULL |
> | startPage | TEXT | NULL | NULL |
> monthly |
> | project_items_per_page | INT | 20 | NULL |
> NULL |
> | task_items_per_page | INT | 20 | NULL |
> NULL |
> | simpleTimesheetLayout | TEXT | NULL | NULL | small work description
> field |
> | useLDAP | INT | 0 | NULL |
> NULL |
> | LDAPurl | TEXT | NULL | NULL | ldap://watson:389
> |
> | LDAPBaseDN | TEXT | NULL | NULL |
> dc=watson |
> | LDAPUsernameAttribute | TEXT | NULL | NULL |
> cn |
> | LDAPSearchScope | TEXT | NULL | NULL |
> base |
> | LDAPFilter | TEXT | NULL | NULL
> | |
> | LDAPProtocolVersion | TEXT | NULL | NULL |
> 3 |
> | LDAPBindUsername | TEXT | NULL | NULL
> | |
> | LDAPBindPassword | TEXT | NULL | NULL
> | |
> | LDAPReferrals | INT | 0 | NULL |
> NULL |
> | LDAPFallback | INT | 0 | NULL |
> NULL |
>
> +------------------------+------+------+-------+------------------------------+
>
> Oh, you can also see above, I've replaced several of the old LDAP items
> with an LDAPurl item instead...
>
> -Scott
>
> On Thu, Feb 10, 2011 at 5:42 PM, Scott Miller <sco...@gm...>wrote:
>
> Good to hear about the HTML stuff in the database now being ignored, and
> moving to some sort of template system; I think that will be much nicer than
> having that stuff in the database. I would certainly be interested in
> reading what peter has...
>
> There are many suggested improvements that are impossible without having
> per user configuration options. Things like having each user able to create
> a default set of time entries per week, eventually allowing the user to set
> their own timezone (once we can store times as UTC). Once we have this
> ability a whole myriad of new possibilities are opened up to further improve
> the user experience.
>
> Peter Lazarus, are you still working on improving the "managment approval"
> area?
>
> -Scott
>
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen. Find and fix more
> than 250 security defects in the development cycle. Locate bottlenecks in
> serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________ Tsheetx-developers mailing
> list Tsh...@li...
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
>
>
> _______________________________________________
> Tsheetx-developers mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>
>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X