TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Layout of Select criteria where Between used in the filter
At the moment if you are using between in a filter with ask the user the from and to fields use up two separate lines. This might look neater if the appeared on the same line and would make the screen a bit more user friendly.
User Experience

Philipp (Augusta)
Date Created
9/29/2016 12:09:03 PM
Date Updated
10/5/2016 3:37:16 AM
New Idea
Promoted By
Philipp (Augusta)
cooper collier  9/29/2016 12:36:01 PM
I bet you could use the new style sheet to customize this for your situation

Philipp Matuschka (MMB) 9/30/2016 2:50:56 AM
Good suggestion, but given that CSS would generally be outside my skillset and that this enhancement comes with a health warning, I think I'll pass.
cooper collier  9/30/2016 10:56:25 AM
After reading your comment, I was thinking, "yeah, but it would be simple!" So I took a few minutes and gave it a try. Then I took some more time. the simple turned into 2 hours.

I am forced to apologize for commenting without testing first! This is not something that can be changed using CSS. I will not presume to answer for the TeamDesk guys, they are spectacular programmers. But, after carefully looking at the layout, I think implementing your idea would require a major rewrite.

However, I would like to comment on your last sentence.

I understand the "CSS... omg.. run..." feeling! I was the same not so long ago. I kept meaning to learn it, but it every time I looked at a tutorial online it was daunting and confusing. "classes use dot, while ID using #, {} one place, not another etc"

The fact is the tutorials make it much more complicated than it really is. They are trying to teach you engine mechanics, when all you want to do is press the peddle and wiggle the wheel back and forth! (never mind brakes, too complicated :> )

Example: I always hated the title in TeamDesk. It is much to big, It takes up 10% of my screen Now the" fix" is simple.

Open a text editor, put this line in it.

#td-apptitle{line-height: 20px; font-size: 15px}

save it as dbstyles.css.
Upload to resources section.
Get out of "setup" and refresh your screen.

TRY it. I guarantee you will not hurt anything, It simply makes the text smaller.
Try adding ;color:red inside the {}

go to these pages, see what else you can do with the text. Anything you put inside the {} will only affect the title! GO FOR IT.

If you are able to build databases in TeamDesk. I can easily teach you (or anyone) enough CSS to make basic formatting changes in about 30 min.

As far as the HEALTH WARNING.
There are things you can do in css that would be a "little bad". You can move or hide columns or buttons. There is the real risk you will make things ugly. But, I cannot imagine any way you could damage your database.

The real warning is, future TD changes may affect your custom styling! The worse that is going to happen is some things may return to 'default" . I have made some extensive css styles in TD. If TD changes something and my css style stops working, I am fully aware that it is 100% my problem. In other words. "Don't go crying to them"

Before you style something, calculate the odds of it changing.
(I know this does not mean much without knowing css)
*if you style the ID (ie Name) it is unlikely it will change.
*If you style basic HTML elements higher chance of change.

In the example above, we change the ID #td-apptitle . The odds of TD ever changing the title are close to zero.

On the opposite extreme, I recently did some major changes to a form. Screen shot here. This form has a slightly higher chance of being affected by future change.

Philipp Matuschka (MMB) 10/5/2016 3:37:16 AM
@Cooper, thanks for the huge amount of time you invested in this. I am under deadline pressure at the moment, so it may be a few weeks before I get to try some of your CSS suggestions.

Having said that my philosophy in 10 years of using TD/DBFlex has been to stick as closely as I possibly can to what is offered "as standard". This minimizes both risk and compatibility issues. I find that the guys are great at what they do, very responsive on any show stopper issues and pretty good on more "nice to have" issues.

@Staff, back to the original suggestion raised, it wouls till be nice if this could be looked at at some stage.
Back to Search Results