Re: [Tsheetx-developers] Who's actively working on the TSNG system?

[David T. <tom...@us...>]

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