[Lazarus] Only VCL-compatible components in LCL

[Kostas Michalopoulos]

I've always found CCR to be a hacky and hard to use solution, starting from
the requirement to use SVN or Git.

IMO the best solution would be to have a real package manager that can
access repositories (with a default one provided by the lazarus devs that
should replace the CCR and provide everything in it) from inside Lazarus
that can download and install packages. Opening a project file that relies
on a package should scan the repositories to see if it is available and ask
the user to download it. The user should not need to do anything more than
selecting Yes or No there and to install new packages should be done from
the Add / Remove packages window that is already there. Basically what
Netbeans and Eclipse are already doing for many years now (especially
Eclipse).

Personally i have a bunch of Lazarus projects at my site that many of my
own programs use. Right now one has to track and download each requirement
separately - look at this wiki page
<http://runtimelegend.com/rep/rtworld/wiki?name=Build+and+Prepare+Runtime+World>
as an example (it used to be longer before multithreadprocslaz became part
of Lazarus itself). One needs to download, build and install four separate
packages manually. I could instead provide a repository that can be added
in the package manager (and even referenced from my program's project file
to be added automatically so the user wont even have to add it manually!)
and have Lazarus download and install the required packages.

As things are right now, if something is not part of Lazarus it is a great
pain to use it exactly because of all those extra steps required. Other
languages and environments have already solved that long time ago and i
think Lazarus should also do the same. Using a library should be as pain
free as possible and ATM in Lazarus it is hard - with the exception of
Windows, it is even harder than C and C++ since in Linux all popular
distributions include thousands of ready to use libraries which are
available with a single `apt-get` (or the distro's equivalent).


On Fri, Dec 12, 2014 at 8:19 AM, Hans-Peter Diettrich <DrDiettrich2 at gmx.de>
wrote:
>
>
> Am 11.12.2014 um 14:29 schrieb Dmitry Boyarintsev:
>
>  On Thu, Dec 11, 2014 at 1:11 AM, Hans-Peter Diettrich <
> DrDiettrich2 at gmx.de> wrote:
>
>> As I understand that: The components in the LCL should be available with
>> all supported widgetsets. An implementation for only one widgetset is not
>> worth of adding it to the LCL, because it would burden the LCL maintainers
>> with the implementation for all other widgetsets.
>>
>
>  On the other hand, it pretty much blocks anyone else to add components
> to LCL.
> Because an author has to introduce a solution for all (or most?)
> widgetsets by LCL.
>  With more widgetsets introduced to LCL, it might be next to impossible
> for some developers.
>
> Why not leave it to the LCL maintainers, which controls should be added to
> the LCL, and which not? Provide them good reasons for doing so...
>
> DoDi
>
> --
> _______________________________________________
> Lazarus mailing list
> Lazarus at lists.lazarus.freepascal.org
> http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20141212/107ec0b2/attachment-0003.html>