[ Thanks to LinuxNews.pl for this link.
]
“The power of the Kylix is its objectivity. With packet you
get lot of classes – labels, edition windows, listboxes,
comboboxes, buttons, tabels etc. – but you aren’t limited to them.
You can create your own components, modify existing or bring into
the project higher level classes – for example sheets, which can
inherit further.”
“Non-visual components don’t seem to be some kind of revolution
– technically they are just classes. But without Kylix, programmer
has to remember how initiate object from given class, with which
parameters given method can be called, and what are possibily
interactions with the other objects – now you can build your
application as simple as your child plays with the puzzles.”
“Work in group? No problem. Your partner working on an
application chooses componets he needs, almost the same way which
your wife do the shopping. One dialog box and one color palette,
please. Thank you.
Complete
Story
Web Webster
Web Webster has more than 20 years of writing and editorial experience in the tech sector. He’s written and edited news, demand generation, user-focused, and thought leadership content for business software solutions, consumer tech, and Linux Today, he edits and writes for a portfolio of tech industry news and analysis websites including webopedia.com, and DatabaseJournal.com.