A key place for feature requests is http://delphi.uservoice.com/forums/4432-general, but a further discussion area can do no har. Better than into Off topic threads :-)
A key place for feature requests is http://delphi.uservoice.com/forums/4432-general, but a further discussion area can do no har. Better than into Off topic threads :-)
http://delphi.uservoice.com/forums/4432-general
http://delphi.uservoice.com/forums/4432-general
Great post. Feedback like this is useful, but an internal strategy which doesn't necessarily aim to satisfy the latest fad, is also important. Features on demand can be expensive.
ReplyDeleteIf it is one thing I would like to see - it is more service releases that start to chew into the rather long list of outstanding issues.
#1 on the list: The out of memory in the IDE for XE3
I agree Lars. And the debugger which holds onto a handle to the EXE which is being debugged, which requires you to exit the IDE and restart it just to be able to build the EXE or debug again.
ReplyDeleteSure, it is not that we'll implement everything suggested. But listening to proposals and ideas is good, and given limited resources, when you have to pick either one or another features for next version, it is nice to see some numbers (like those in QC or user voice).
ReplyDeleteThe strategy is key but that's one taks to come up with one. The current can be explained as "Delphi Everywhere": desktop, tables, phones.
But some of the details are still open...
-Marco Cantu
Delphi Product Manager
@Lars Are you compiling multiple projects in a project group when you get the out of memory error, or does it happen while you compile a single project?
ReplyDeleteAndreas Hausladen - It can come from a single project compile, after I've built the project group, or from another project group build. If I compile the same project over and over throughout the day, it may also happen.
ReplyDeleteDoing a "Clean" for all projects will drop a lot of the memory, but it seems that it builds up quite quickly again.
It is strange though, because it is not entirely predictable (or rather, I am not - since I probably don't to the same thing all the time).
One word: Android.
ReplyDeleteBTW, happy to be part of this community.
Datasnap Deployment for Linux. IMO very important - not just for me, but also the product. I know Marco CantĆ¹ thinks the same, but just wanted to post it here as a reminder.
ReplyDelete