GerhardV

Theme: Dusk (ext-theme-uni_dusk)

Theme: Topaz (ext-theme-uni_topaz)

Most of them are ready. I don't really want to charge anything for them but I thought that maybe they can contribute towards my UniGUI subscription renewal...so I am still contemplating...thinking of making them available for free and allow donations by those who feel like it. For custom request I would have to charge though as it does take a bit of time to build. Currently the following are complete: Emerald, Dusk, Office-Blue, Office-Green and Topaz Work in Progress: Bootstrap, Crisp-Condensed Planned: Dark theme I will post some screen shots in the mean time.

Will see if I can create one based on a smaller version.

I like that Delphi Developer!

This was still based on the previous ExtJS version 4.2. Will recreate this for 6.5 soon.

Thank you Nelson.

Almost ready...busy with testing

Toolbars... Font is Roboto Condensed.

New themes based on Office 365...and with a smaller font etc.

Yes you can. Just add the following to Servermodule => CustomFiles: files/css/MyCustomCSSFile.css

As I said - "You can right click on the checkbox label in Chrome and select "Inspect element". Then you would be able to see in the developer panel what the actual CSS selector is for the checkbox label and not the check." Doing the above ... you can inspect the composition of the element. Typically for check boxes and radio buttons it is composed of a label and an image / FontAwsome meaning two CSS selectors, one for each. See the image for details...what you are looking for is in the class attribute.

You can right click on the checkbox label in Chrome and select "Inspect element". Then you would be able to see in the developer panel what the actual CSS selector is for the checkbox label and not the check. For the Triton theme for example: .x-form-cb-label-default { margin-top: 6px; font: 400 13px/17px Fira Sans Condensed, sans-serif; color: #404040; } In your CustomCSS if you just want the font size to be different you only need to have the following then: .x-form-cb-label-default { font: 400 13px/17px Open Sans, sans-serif; } You don't always have to include !important - have to use it very wisely as you force an overriding. https://css-tricks.com/when-using-important-is-the-right-choice/

Here is a screenshot where the height is 36px. Also attach is the CSS file where I have added the selector to make the adjustments, blocked of with comments. NOTE: I have not fully tested this to see if it influence any other selectors. Also please remember that with a new version install it will override this file so you would need to break it out into it's own file. I will later on create a theme based on a "slimmer" version. Regards, G uni-xtheme-uni_emerald.css

You can override the corresponding CSS selector by adding it to the "uni-xtheme-uni_emerald.css" file. I will see if I can add the appropriate selectors to the file for easy changing without affecting the font sizes and padding. What height did you have in mind? Currently it is at 44px.

Build 1449 includes a new visual theme called Emerald. Below are a few screenshots of what it looks like: If you don't want the rounded corners then you can change the border-radius for buttons and tabs in "uni-xtheme-uni_emerald.css" file. I have also added CSS selectors for bgv-btn-theme and bgv-btn-flat, which are custom buttons which you can add by adding the following to the ClientEvents / UniEvents function beforeInit(sender, config) { config.cls="bgv-btn-theme"; } function beforeInit(sender, config) { config.cls=("bgv-btn-flat bgv-btn-flat-round"); }

Thank you for the notion Farshad. Guys please, this is NOT a thread to compare UniGUI against the still developing TMS Webcore, it was mentioned as an example only. What I can say is that their is a definite improvement in UniGUI with Sencha V6.5.3.

First of all let it be noted - I really enjoy working with UniGUI, understand that Farshad is flying solo (one man doing the job) and appreciate the effort. BUT - we really cannot wait days for Farshad to reply to messages or email for support or direction. We all have projects to complete, others even have solutions or suggestions for UniGUI but because we do not have the full source code our hands are tied and we are totally depended on Farshad. So these are the options as I see it: Release the full source code and have the UniGUI community contributing - off course with all the relevant non-disclosures (NDA’s) in place. FMSoft to employ more people (developers), which will be able to help with development, field the questions and handle technical support with regards to the architecture. Open source the project – obviously financial implications...or maybe get Embarcadero involved? Call it a day and move on - TMS WebCore is looking promising and have a support team behind them. Please see this as constructive criticism. I truly believe that we can accelerate the development (success) of UniGUI with more hands on deck! Regards, Gerhard

+1

Farshad have you given this any thought? Or can you perhaps share the source for TMainMenu?

Farshad is it possible to add a Scale property to TuniMainMenu just like TUniButton's Scale property where one can specify it so that the menu buttons are bbsSmall, bbsMedium or bbsLarge? And then also be able to specify the height of the toolbar? Thank you.

Seems we don't have the source code for uniMainMenu.pas. Farshad can we perhaps make it more flexible and add a height property to TUniMainMenu which uniGUI can then use to set the element.style height property and the x-box-inner correspondingly? As well as a property for the button scale (small, medium and large).

Thanks Farshad. The only annoying thing is TMainMenu. The buttons are very small and it seems like the height is hard coded as the element.style property {height: 32px} is set, probably in code. Difficult to change as it seems .x-box-inner is also set at a fixed height of 20px.

Farshad, I am looking at the Triton theme, which I quite like as a base to work from, but I have noticed that the you override the font it actually distributes with (Open Sans) with Tahoma 12. It means all button related components like main menus for example only has that font even if you make the size of the button bigger to trigger medium and large fonts. I want the font to be driven by CSS. The Main Menu buttons look in particular very small. I also notice that you downsize the edit boxes for Triton and the Calendar looks quite different from the standard theme. I know I can edit uni-xtheme-triton.css and removed those which then uses the actual fonts but I am not sure what effect that will have that I am not aware of. I would expect it to take the theme as is and looks identical. Any explanation for this? Thanks. BTW I have added the following to uni-xtheme-triton.css to center the triggers: .x-form-trigger { vertical-align: middle; } P.S. If you can also see my question on this post: http://forums.unigui.com/index.php?/topic/10239-custom-theme-selection-at-design-time/

Yes I did. I think you might have mis-understood me. I can see the triton.modified theme but I cannot see one that I have added myself by just making a copy of that one and named it something else. "I have only noticed the file "uni-xtheme-triton.modified.css" in the "C:\dev\FMSoft\Framework\uniGUI\uni-1.0.2.1444\css" folder." ... meaning there are no other references to it. So I was wondering how Farshad is building that dropdown selection list of available themes.