Blog
All Blog Posts | Next Post | Previous PostWhere do you want ... TMS to go in 2010 ?
Tuesday, December 8, 2009
The end of 2009 is approaching rapidly. Almost time to make up the balance of 2009 and to make plans for the new year. 2010 looks to be an exciting year full of challenges as well.Perhaps the most eagerly anticipated product will be Delphi Project X. We look forward to explore new opportunities with Project X. Another big step looks to be IntraWeb XI and we're watching the new developments closely to ensure existing and new components will use the framework as good as possible. Meanwhile, Microsoft is adding ever more exciting features to Silverlight. In 2009, we released our first product for Silverlight, the TMS Silverlight Planner and we look forward to continue to add features to this component as well as work on other Silverlight controls. Around the corner is also a new version of Visual Studio. Our team has been working harder than ever on our VCL components as always. We've released several new VCL components and many major updates to existing VCL products. This will be no different in the coming year 2010. Also, documentation overall is high on the list of priorities. A big effort is underway and we hope to reveal the results in the first half of 2010.
To align our efforts and hard work in the best possible way with your wishes & needs, this is also an excellent period to listen carefully to your feedback. Some questions we have for you:
- What components are you missing ?
- What extensions to existing components do you need ?
- What technologies should we focus on ?
- What can we improve or add on our website to make things easier, faster, better for you ?
- What can we improve in the way our components are distributed ?
- What can we do better for help files, FAQs, sample apps, developer guides ?
- What can be improved in the way we provide support ?
- Anything else we can do to provide you with a better experience and to provide you with the solutions,service & products you need ?
We look forward to all your feedback. You can post your comments, questions, wishes here or you can also contact us directly by email via the newsgroups. Let's make 2010 a great and fruitful year!
Bruno Fierens
This blog post has received 25 comments.
Gemmell Lachlan
1: I think it would be great to have an extended FormStyler component in which you can configure and save your own named styles.
2: I think the documentation needs to be a little more detailed.
3: How about adding a Forum to the site.
4: I think your support is excellent and give you 11/10 for that :)
O''Connor Chris
My Customers have asked, when my Software could support these really cool features.
Speck Thomas
Andreas Firnau
Regards,
RIchard Ulrich
Ulrich Richard
Your components look very good, but I think robustness is very poor with some component. I had to remove all the SmoothListBox from my interface because they were unstable. I had many problems at each version increment with it. For example, incorrect destroy order, followed in an version update by some call to a refresh method after the inherited destroy called in the destructor, followed by some strange crashes hard to reproduce with this component, followed by removing the component to get some stability...
Moreover if a couple of smooth components (like smooth buttons, edit box, etc) are put on a smooth panel, the interface becomes very sluggish and unresponsive, that makes the smooth panel almost useless for me. The support told me that the solution is to avoid this kind of use..
Also, the code still have compilation warning, that I think is not acceptable in commercial code.
After all this I only use the AdvStringGrid, the only component I didn''t have problem with until now, but the code quality is still suspicious with a lot of commented code, ultra long methods with nested sub-methods and incoherent programming, naming and spacing style.
I like the look and the wide choice of components in your suite, but I think I will have to stop using them if stability and quality is not getting better. I use them in industrial application and I cannot afford to get such kind of problems.
Regards,
Simon Alex Berube
Berube Simon Alex
Van Landeghem Hugues
#2 - better custom framing options for edit controls (border style,etc) check out what woll2woll gives the ability to do. changing borders/which borders, etc depending on focused or not, etc.
#2 - a smooth rich text editor (basically full editor) like woll2woll''s but more visually customizable to match the rest of the program interface.
Messerschmidt Michael
#2 Better extensibility of the components. More protected instead of private methods, more protected access to private fields and better "hooking" possibilities. With regard to "hooking": it is very hard to derive specialized components from yours. Many events are triggered throughout various method implementations and are therefore difficult to "hook into". Currently often the only option is to duplicate code... It would be a lot easier if events were always triggered in their own protected "DoEvent" methods.
#3 A good rich text editor that can read and save rtf, html and perhaps even ms-word. With style support so that style changes to a text don''t require someone to change each and every occurence of a particular style use.
Venema Marjan
Kieninger Günter
I found couple of bugs in the AdvStringGrid concerning a Combobox as Inplace Editing Control and Cursor Navigation when there are Fixed Cells in the grid (I have to tell you in detail later). There is always something to improve in the existing controls, so please keep maintaining your top components.
You could as well enhance the syntax highlighting capabilities of your AdvMemo components. Currently it is only possible to choose from a set of languages. I would be very nice if you could add ways to customize the styling. I''d like to define keywords to be highlighted always, independent from delimiters that surround the keyword.
Thanks!
Korte Christian
Documentation and Help needs lots of work to be usable.
Pohjonen Pentti
Again, as above, would like a component that allows opening and saving of ms-word .doc, and rtf formats.
Lastly I have FastReports and FastCube, but do wish there was a TMS equivalent of FastReports, and more in the charts to approach the breadth and flexibility of Steemas Teechart Pro.
Robert Edgar
All that hectoring aside, what do the writers expect those comments to produce? A sudden rush to fix the bugs because Bruno hasn"t shown any interest in fixing them? That"s farcial. Bruno"s fixing them as fast as he can. He sees the end of the tunnel coming and wants direction on where next to go.
Documentation. That"s a good idea. The rest of the moaning? A waste of everybody"s time.
Mugford Gary
Thanks
Martin Lawrence
Martin Lawrence
Pucino Francesco
Maybe an ExporttoPDF in the same component?
Component for showing events in an "Iphone-bubble" style (or Skype-like style) would be cool.
Documentation could improve, but I''m very happy with the support team!
I wish you a Happy new year!
Malinovszky Laszlo
Aignesberger Martin
It has always struck me kind of strange that a nice product like TMS Component etc. has such crappy documentation.
My wishlist for Xmas might also include:
o SourceCode System Integration (SCC connection).
o License handling component (like LockBox from TurboPower).
o A barcode component.
Finally I want to take this opportunity to send to every user of Delphi the very best holiday wishes.
Per Danielsson
The only big thing on my wish list would be a commitment or comment on cross platform features of the next Delphi release.
Searancke Martin
I started using Delphi about 15 years ago, but now I''m tired of the poor evolution of Delphi, and I have switched to iPhone dev with XCode. Very exiting !! really love it.
So why not porting some comps to iPhone.
For instance there is no Excell export on iPhone, so why not making a Flexcell for iPhone (Without PDF, PDF already exists).
Also there not a lot of comps in iPhone, why not adding some new ones ?
Best holidays wishes to all.
Da Silva Armindo
Please ensure that all units compile without producing hints and warnings.
I compile all my projects using the source of the components I have, never using pre-compiled dcu''s. I also have a zero tolerance policy for hints and warnings: all projects must compile cleanly.
TMS components perform very poorly in this regard, as many TMS Component units produce hints and/or warnings. Doesn''t look very professional, and is a nuisance and a hindrance to my own QA efforts.
The hints and warnings produced by TMS code prevent me from enforcing the zero tolerance policy in my automated builds. It would be very hard if not impossible to make exceptions for TMS units. And amending the sources myself is not an option either, as I would have to do this again and again for every update you publish...
Venema Marjan
Venema Marjan
And if Bruno can improve TMS Component Software in a couple of key areas - to make me a millionare, tax free of course. Isn''t it nice that my needs are small ?
Merry Christmas all !!!
HO HO HO !!!
Barone Mike
All Blog Posts | Next Post | Previous Post
Happy new year!
Cavalcanti Herculis