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

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

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
>>
>>
>