BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Resizing Components & resolution independance
Goto page 1, 2, 3  Next
 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Thirdparty Tools (General)
View previous topic :: View next topic  
Author Message
Luke Grews
Guest





PostPosted: Mon May 09, 2005 3:40 pm    Post subject: Resizing Components & resolution independance Reply with quote



Hi All

I am looking for some advice on how to make our app resolution independant.
Can anyone recommend VCL resizing components and which are the best?
Further, how is this issue solved in the industry generally?

Any suggestions and ideas greatly appreciated.

Thanks
Luke


Back to top
Paul Dolen
Guest





PostPosted: Mon May 09, 2005 7:00 pm    Post subject: Re: Resizing Components & resolution independance Reply with quote



Quote:
I am looking for some advice on how to make our app resolution independant.
Can anyone recommend VCL resizing components and which are the best?
Further, how is this issue solved in the industry generally?

There are indeed some components for this. I used a few times a
product that was called PerfectSize, but the vendor went away. But,
in general, well, I think most people feel it best to not use those
things. Most people use anchors and components that will fill a
panel, like grids. On the app that I used PerfectSize on, it was a
app that was a data entry application, with screens with lots of
fields on them. For that kind of app, a resizing component could make
sense. But I think for most, it doesn't.

Back to top
Alan Questell
Guest





PostPosted: Mon May 09, 2005 7:27 pm    Post subject: Re: Resizing Components & resolution independance Reply with quote



There's one available in the JVLC components.

"Luke Grews" <duel (AT) telkomsa (DOT) net> wrote

Quote:
Hi All

I am looking for some advice on how to make our app resolution
independant.
Can anyone recommend VCL resizing components and which are the best?
Further, how is this issue solved in the industry generally?

Any suggestions and ideas greatly appreciated.

Thanks
Luke





Back to top
Crazy Horse's crazier lit
Guest





PostPosted: Mon May 09, 2005 9:20 pm    Post subject: Re: Resizing Components & resolution independance Reply with quote

"Alan Questell" <alanq (AT) pinehurst (DOT) net> wrote

Quote:
There's one available in the JVLC components.

If anybody tries this component and has success, please let me know. I'll
install the rest of the JVCL, in that case (I have part, but not all of it
installed, at least I see no such component) on the following JVCL tabs: JV
Non-Visual; JV Persistence; JV Buttons; JV Edits; JV Bars, Panels, JV
Labels; JV Visual; JV Images, Animators.

--

Download Blackbird Crow Raven's book
"STILL CASTING SHADOWS: Two American Families 1620-2006"
(.exe and Delphi source): http://cc.borland.com/ccweb.exe/listing?id=23106



Back to top
Mark G. Zeringue
Guest





PostPosted: Mon May 09, 2005 9:58 pm    Post subject: Re: Resizing Components & resolution independance Reply with quote

"Luke Grews" <duel (AT) telkomsa (DOT) net> wrote

Quote:
Hi All

I am looking for some advice on how to make our app resolution
independant.
Can anyone recommend VCL resizing components and which are the best?
Further, how is this issue solved in the industry generally?

Try TElasticForm, I used it to replace GTSizer since they do not seem
interested in upgrading to Delphi2005 and it was the only component I used
without source. TElasticForm has worked well and they provide source.
http://home.flash.net/~qsystems/

Mark



Back to top
Pete Muller
Guest





PostPosted: Mon May 09, 2005 10:01 pm    Post subject: Re: Resizing Components & resolution independance Reply with quote


DevEx's ExpressLayout Control (
http://www.devexpress.com/Products/VCL/ExLayoutControl ) is brilliant
:)


Pete.
Back to top
Alan Questell
Guest





PostPosted: Mon May 09, 2005 10:37 pm    Post subject: Re: Resizing Components & resolution independance Reply with quote

It works fine except it does not have an option to adjust the font size
based on form resizing. It resizes all controls however.

It's called JvFormAutosize and its on the "Jv Application, Forms" tab.

"Crazy Horse's crazier little brother" <cshannon (AT) d4sw (DOT) com> wrote

Quote:
"Alan Questell" <alanq (AT) pinehurst (DOT) net> wrote in message
news:427fb99e (AT) newsgroups (DOT) borland.com...
There's one available in the JVLC components.

If anybody tries this component and has success, please let me know. I'll
install the rest of the JVCL, in that case (I have part, but not all of it
installed, at least I see no such component) on the following JVCL tabs:
JV
Non-Visual; JV Persistence; JV Buttons; JV Edits; JV Bars, Panels, JV
Labels; JV Visual; JV Images, Animators.

--

Download Blackbird Crow Raven's book
"STILL CASTING SHADOWS: Two American Families 1620-2006"
(.exe and Delphi source): http://cc.borland.com/ccweb.exe/listing?id=23106





Back to top
Ben Crain
Guest





PostPosted: Tue May 10, 2005 12:18 am    Post subject: Re: Resizing Components & resolution independance Reply with quote

Pete Muller wrote:
Quote:
DevEx's ExpressLayout Control (
http://www.devexpress.com/Products/VCL/ExLayoutControl ) is brilliant
:)


Pete.
As I understand it, ExpressLayout does not deliver resolution

independence. In fact, I asked them (devexpress) about that explicitly,
and they replied that it was not intended to deliver resolution
independence, which was not a very good idea anyway. That is, trying to
achieve resolution independence is not worth the effort, and any such
effort is bound to fall short on some kind of app/control. At least
that's my interpretation of their response. If I'm missing something
please let me know.

I did try ExpressLayout, and would take issue with the assessment that
it's brilliant. It probably is, as a technical achievement. But I
found the learning curve ridiculously steep, and even after I got a grip
on the basics, I still found it quite tedious. My own personal solution
to this problem is, IMHO, easier to implement than ExpressLayout (if you
take account of the learning effort), delivers equal results (at least
for what I do), and offers some degree of resolution independence. My
solution:
Position everything -- everything! -- in code. Set all size properties
(size of controls, fonts sizes, etc), in code. This sounds like a lot
of work, and it can be at the outset, but, once you get everything set
up, making changes, even big ones, can be quite easy, often requiring
changes in only 1, or a few, lines of code.
To do that requires creating a number of variables to hold the values
that establish the positioning of everything. But not all that many:
even on a busy form, I typically need only about 20-30 such variables,
plus a small number of font settings, Height and Width settings for
controls, etc. Then I can achieve resolution independence by simply
changing these variables/settings depending on the user's screen
resolution. In principle that could be done for all screen resolutions,
but that would indeed be a lot of work, since you would have to run the
app at each different resolution and decide what the variable values
should be for that resolution to achieve the overall appearance you
want. But, to the extend you want to do that, the result is better than
simple resolution independence: you get exactly the appearance you
want, customized at each resolution. However, that's not, in my
opinion, worth doing at all resolutions. I do it for just 2: the
lowest I permit (800x600 -- I prohibit the app from running at the old
640x480, or whatever it was), and the next one up (1024x768 on my
monitor). That's good enough. Anyone using higher resolutions will see
my app (and everything on it) as smaller than I designed it. They will,
however, see everything positioned on the form -- relative to the form's
size and to everthing else on the form -- exactly as I intend it to
appear. If they want to see it bigger or smaller, they can change their
own screen resolution. No need for me to force on them a constant
absolute size at which everything will always appear.
As far as I've been able to check, major commercial apps don't try to
deliver resolution independence. Look at Delphi itself: if I run the
IDE at higher resolutions, everything on the IDE gets smaller and
smaller: no resolution independence there.

my 2 cents,
Ben Crain

Back to top
Jim McKay
Guest





PostPosted: Tue May 10, 2005 3:38 am    Post subject: Re: Resizing Components & resolution independance Reply with quote

Ben Crain said...

(...)

Quote:
My solution:
Position everything -- everything! -- in code. Set all size properties
(size of controls, fonts sizes, etc), in code. This sounds like a lot of
work, and it can be at the outset, but, once you get everything set up,
making changes, even big ones, can be quite easy, often requiring changes
in only 1, or a few, lines of code.

I do same thing. I built a persistence mechanism with
StorageLib (http://www.deepsoftware.ru/rsllib/index.html) into
one of my form classes to handle this. Works fine, and not
so much work at all.

--
Regards:
Jim McKay

"My theory of evolution is that Darwin was adopted."
-- Steven Wright

Posted with XanaNews: Ver: 1.17.4.1

Back to top
k_c_400@yahoo.com
Guest





PostPosted: Tue May 10, 2005 7:09 am    Post subject: Re: Resizing Components & resolution independance Reply with quote


Luke Grews wrote:
Quote:
Hi All

I am looking for some advice on how to make our app resolution
independant.
Can anyone recommend VCL resizing components and which are the best?
Further, how is this issue solved in the industry generally?

Any suggestions and ideas greatly appreciated.

Thanks
Luke

Try EasySize - do a google search on the "delphi easysize.zip" will
yield enough download information. Source include, freeware, work
reasonable well. Not perfect - won't work if a visible component is
created during the run time.

Be careful on the JVCL FormAutoSize component, a bit of component's
original size & position information will be lost after each resize,
i.e., change the form size a few times in a row, the components' size
and placement may not be what you want.


Back to top
Crazy Horse's crazier lit
Guest





PostPosted: Tue May 10, 2005 2:01 pm    Post subject: Re: Resizing Components & resolution independance Reply with quote

"Alan Questell" <alanq (AT) pinehurst (DOT) net> wrote

Quote:
It works fine except it does not have an option to adjust the font size
based on form resizing. It resizes all controls however.

Font (re)sizing seems pretty important to me; I cre8 apps for various people
here, and they all have their own individual resolution and dpi/font sizes.
TElasticForm looks interesting, and it's only $35 for the no-source version.

In fact, this is an important enough issue that I think it should come in
the (Delphi) box. Maybe one of the interns can walk around the bldg, and
look under the sofa cushions for a spare million or so, and license the best
component of this type.

--

Download Blackbird Crow Raven's book
"STILL CASTING SHADOWS: Two American Families 1620-2006"
(.exe and Delphi source): http://cc.borland.com/ccweb.exe/listing?id=23106



Back to top
Paul Dolen
Guest





PostPosted: Tue May 10, 2005 2:15 pm    Post subject: Re: Resizing Components & resolution independance Reply with quote

Quote:
lowest I permit (800x600 -- I prohibit the app from running at the old
640x480, or whatever it was), and the next one up (1024x768 on my
monitor)

Interesting way to go. Just a possible suggestion/comment. A popular
resolution is 1280 x 1024. But it is a 5:4 aspect ratio, while most
popular resolutions (such as the ones you listed) are 4:3. So, it
might (possibly) be worth adding that to your list of
configured/tested resolutions.

Back to top
JED
Guest





PostPosted: Wed May 11, 2005 3:13 am    Post subject: Re: Resizing Components & resolution independance Reply with quote

Crazy Horse's crazier little brother wrote:

Quote:
In fact, this is an important enough issue that I think it should
come in the (Delphi) box. Maybe one of the interns can walk around
the bldg, and look under the sofa cushions for a spare million or so,
and license the best component of this type.

I would hate to use an application that scaled in the way is mentioned
in this thread.

I'd put my hand out for the spare million though <g>

--
www.jed-software.com

Back to top
Craig
Guest





PostPosted: Wed May 11, 2005 3:17 am    Post subject: Re: Resizing Components & resolution independance Reply with quote



Quote:

I would hate to use an application that scaled in the way is mentioned
in this thread.


I wasn't going to say anything, but I also hate these 'scalable' apps. To me
it translates to an immediate uninstall.

Craig, www.h3k.biz



Back to top
Chris Morgan
Guest





PostPosted: Wed May 11, 2005 9:45 am    Post subject: Re: Resizing Components & resolution independance Reply with quote

Quote:
I wasn't going to say anything, but I also hate these 'scalable'
apps. To me
it translates to an immediate uninstall.

I agree.
If you have your screen set to a high resolution, it means you want to
see more information, or more applications at once, rather than just
a scaled-up version of a 640x480 form (or whatever).

My approach when developing is to just anchor or align everything and
check
the form is not too big for whatever minimum screen resolution you
specify,
and that it looks OK with both small and large fonts.

Cheers,

Chris



Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Thirdparty Tools (General) All times are GMT
Goto page 1, 2, 3  Next
Page 1 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.