Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 12 total
Thread Application.Font ?
Fri, Jul 8 2016 3:57 PMPermanent Link

Trinione

Tim:
Would it be possible to implement say a Application.Font property which allows for all application surface, forms and other components to have the Font properties set this way?

Or, some sort of way to easily set to an application wide font?
Fri, Jul 8 2016 6:15 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com


<< Would it be possible to implement say a Application.Font property which allows for all application surface, forms and other components to have the Font properties set this way? >>

That's getting back to the Delphi-like ParentFont architecture, which was specifically removed in EWB 2.x because it's a giant pain for very little reward (it doesn't mesh well with DOM inheritance when EWB has to also keep track of the fonts being used).

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Jul 8 2016 7:16 PMPermanent Link

Boris B

Are interfaces layered?  if so, is there or could there be a base application interface that gets applied before any more specific ones?  Sort of like setting a style on <BODY>...
Sat, Jul 9 2016 11:42 AMPermanent Link

Trinione

<< That's getting back to the Delphi-like ParentFont architecture, which was specifically removed in EWB 2.x because it's a giant pain for very little reward (it doesn't mesh well with DOM inheritance when EWB has to also keep track of the fonts being used). >>

Ah! Ok. Understood.

Idea! What about a 'Default Font' drop-down selection setting in the 'Environment Settings | Project Options' tab?

NOTE: Now that I think about it - If this is too must a task, I can write a helper app to make the changes in the .wbf file. It is time consuming and repetitive to do it manually.
Mon, Jul 11 2016 4:21 AMPermanent Link

Matthew Jones

Trinione wrote:

> It is time consuming and repetitive to do it manually.

What are you actually trying to achieve here? Why are you not just
changing the interface definitions and fixing it everywhere like that?

If you want to do it at run-time, it is not hard to traverse the whole
UI looking for components of various types and adjusting their values.
I did this on one application to allow for a large or small font size
(desktop/mobile).

--

Matthew Jones
Mon, Jul 11 2016 8:32 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Boris,

<< Are interfaces layered?  if so, is there or could there be a base application interface that gets applied before any more specific ones?  Sort of like setting a style on <BODY>... >>

No, interfaces are not layered.

Tim Young
Elevate Software
www.elevatesoft.com
Mon, Jul 11 2016 1:30 PMPermanent Link

Trinione

"Matthew Jones" wrote:

Trinione wrote:

> It is time consuming and repetitive to do it manually.

<< What are you actually trying to achieve here? Why are you not just
changing the interface definitions and fixing it everywhere like that? >>

As this is an integral part of the system and resulting UI, I avoid changing the interface definitions as this would most likely lead to issues in the future as EWB evolves. When I need to I create new interfaces/components.

<< If you want to do it at run-time, it is not hard to traverse the whole
UI looking for components of various types and adjusting their values.
I did this on one application to allow for a large or small font size
(desktop/mobile). >>

Yes, I currently do this as well.

My suggestion was intended to provide a way to make it a part of EWB, so that this extra processing at run-time would not be necessary, and less time spent manually setting each component font name. Traversing the UI and changing the fonts may affect alignment and spacing - whereas having it lined up at Design Time is advantageous.

--

Matthew Jones
Mon, Jul 11 2016 4:57 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com


<< As this is an integral part of the system and resulting UI, I avoid changing the interface definitions as this would most likely lead to issues in the future as EWB evolves. When I need to I create new  interfaces/components. >>

The interfaces included with EWB are *designed* to be customized.  Modifying them using the control interface editor  is how I go about creating new control interface sets.

Tim Young
Elevate Software
www.elevatesoft.com
Mon, Jul 11 2016 5:35 PMPermanent Link

Trinione

Tim Young [Elevate Software] wrote:


<< As this is an integral part of the system and resulting UI, I avoid changing the interface definitions as this would most likely lead to issues in the future as EWB evolves. When I need to I create new  interfaces/components. >>

<< The interfaces included with EWB are *designed* to be customized.  Modifying them using the control interface editor  is how I go about creating new control interface sets. >>

Tim :
Am I misunderstanding something? My thinking is that when I change a standard EWB component's via the Interface file and I install a future update, say EWB 2.05, and that comes with possibly new features and changes to the component which would override my changes and I may have a bunch of things to keep track of and also potential bug/issue points of my own making.

In this case, for example, if I change the TLable Interface file to Font Name = 'Roboto', when I install say EWB 2.05 and that has Font Name = 'Segio UI', then I would have to make the changes again to the file? This example is simple, but I would need to keep track of every single change I make and do it over again with each release.

I understand and appreciate the flexibility of EWB, and am just wondering if I got that right?
Tue, Jul 12 2016 4:17 AMPermanent Link

Matthew Jones

Trinione wrote:

> but I would need to keep track of every single change I make and do
> it over again with each release.

I had the same concerns, but experience shows that it is not half as
big as you might think. The changes are minimal to existing things, and
insignificant. Standard diff tools will show you this - grab a copy of
the 2.04 interfaces now, and compare to the 2.05 one due soon.

--

Matthew Jones
Page 1 of 2Next Page
Jump to Page:  1 2
Image