Re: Win32 Needs



maybe even get down to the basic set of components that was shipped
with Delphi 1

Not bad at all. I suggest stripping plus improving-fixing those kept.

Also, it used to be easy to automate component installation in the IDE.
IIRC, all you had to do was to update the registry "Known Packages"
key. Now, with Delphi 2006, I am not sure, but it seems you have to
update some "Package Cache" key - which is not an easy task.
Practically, after I use some command line based tool to compile all
packages I need, to make sure they install properly, I have to reopen
every one of the design packages in the IDE and "install", practically
half of my automation process is useless.

So, I think package installation should be revisited and made easier in
every aspect.


***

Other nice-to-have stuff:

- Unicode
- Win64
- optimizations
- VCL more thread-safe, if possible
- Help is not that bad, but the ol' good Delphi help was better and
faster and I could use a MSDN library if I needed what used to be
"Windows SDK" help.

- Better multithreading:
- I'd like TThread class in a separate unit

- I'd also like to have a global list of threads where threads are
registered upon construction and unregistered on destruction. Than this
list would have a method GetCurrentThread: TThread, so one can retrieve
the thread that is currently running (I can give some examples how that
can be usefull)

- fix the CheckSynchronize method (QC 22267) I practically have my
own thread class and I use my own CheckSynchronize version which uses a
threadsafe FIFO list for the synchronization requests. Pretty simple
and effective.

- There was a very clear purpose for existance of ThreadCount in
Classes unit. That reason is gone from Delphi 6 or 7. What's the
purpose of AddThread/RemoveThread (same unit), where is needed this
private variable ThreadCount, what's it for? Some code cleanup wouldn't
hurt.


regards,

Lucian
.



Relevant Pages

  • December update and Vista - unable to run/debug
    ... I installed the december update of Delphi 2007 yesterday. ... When I came back two hours after starting the installation, ... screen was black (screen saver?) and it wouldn't respond to a key or ... Starting the project outside the IDE works fine, ...
    (borland.public.delphi.non-technical)
  • Re: D7 in the path
    ... it isn't really necessary to have Delphi in your path. ... in the path PERMANENTLY during installation. ... Competent answer I was hoping for would be ... New IDE needs this information because ...
    (borland.public.delphi.non-technical)
  • Re: ANN: DelphiSpeedUp 2.3
    ... Some FastSys tweaks to improve speed in runtime packages ... The IDE is terminated faster by pressing CTRL when closing the ... Delphi 7 users start InstallDelphiSpeedUp7.exe ... Simply press the "Uninstall" ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: File types and locations
    ... > not needed unless the EXE is deployed using separate runtime packages. ... Are the DCU files ... which the Delphi installation adds to PATH ... > exception is encountered while running under the IDE? ...
    (borland.public.delphi.language.objectpascal)
  • Re: Delphi strategy against Lazarus
    ... You can queue up the packages so that the IDE recompiles only once. ... other benefits of Lazarus Packages are far greater. ... always be things Delphi does way A and Lazarus way B. ...
    (borland.public.delphi.non-technical)