[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.newcomer] Re: GUI builder for new projects

On 4/14/2009 1:36 PM, ns_dkerber@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
In my application, I'm somewhat resource limited, especially RAM, and
it's an industrial data collection application.  So most of the time
nobody ever looks at it unless we need to do some troubleshooting (a
couple times per year typically, and some haven't been touched in 3 or 4
years).  Therefore, looking the same across platforms is a non-issue, as
is "native" look-and-feel, while memory use could be an issue (I really
need to avoid disk swapping in normal operation).  We can add more RAM
to new machines if needed, but would prefer not to, and can't
realistically add ram to machines that are already in the field when
deploy new software.

Because it is using native widgets most of the time, I'd say that SWT is "lighter" than Swing. Long ago I accumulated several years of experience developing Swing apps and I can tell you, at least back then, they were anything but lightweight.
SWT, if used stand-alone without the Eclipse/RCP platform, is probably not going to add much to your memory requirements. If it were me I'd do some little prototype app and see how it behaves on your target machines. Either VEP or WindowBuilder (free trial, remember) can help throw together such a prototype; but as someone else mentioned it might be faster to learn and hand-code a prototype. I depends on what kind of learner you are...


Hope this helps,
Eric