> The first issue I found is that the setup dialog for fppkg doesn't look
> for a fppkg executable, it expects the install directory where is fpc
> supposed to be installed, I guess in order to use that for locating the
> right fppkg executable. I expect this to work as is only on released
Because 'it works'. At least, on my machine. ;)
:)
The only way to catch all problems in the wild, is to release it into
the wild. I think it's viable to use trunk for that.
Did you try to fix it?
Indeed.
Does the initial-setup dialog show you the option to create a new fppkg
On Fri, 15 Mar 2019 13:55:28 -0600
"Jesus Reyes A. via lazarus" wrote:
>[...]
> and BTW although not for MVC but, can fppkg-lazarus integration be
> removed until it just works? I would like not to see the config
> lazarus IDE dialog to open on every launch just because fppkg is not
> setup
En Mon, 11 Mar 2019 07:01:33 -0600, Michael Van Canneyt via lazarus
escribió:
On Mon, 11 Mar 2019, Kostas Michalopoulos via lazarus wrote:
On Fri, Mar 8, 2019 at 12:55 PM Juha Manninen via lazarus
wrote:
Everybody wants to include their custom components in LCL. Why?
Most likely
On 08/03/2019 09:10, Juha Manninen via lazarus wrote:
On Thu, Mar 7, 2019 at 3:09 PM zeljko via lazarus
wrote:
Not as default TFontDialog. Maybe as TLazFontDialog or similar.
+1
AlexeyT, what is wrong in having a separate component for those who need it?
If the current native dialogs have
On Mon, 11 Mar 2019, Martin Frb via lazarus wrote:
On 11/03/2019 14:01, Michael Van Canneyt via lazarus wrote:
IMO Lazarus should provide a decent selection that allows someone to
do most
common tasks without needing to install something extra.
(what this "decent selection" is, is up for
On 11/03/2019 14:01, Michael Van Canneyt via lazarus wrote:
IMO Lazarus should provide a decent selection that allows someone to
do most
common tasks without needing to install something extra.
(what this "decent selection" is, is up for debate, of course)
Well, that and where does the
On Mon, 11 Mar 2019, Kostas Michalopoulos via lazarus wrote:
On Fri, Mar 8, 2019 at 12:55 PM Juha Manninen via lazarus
wrote:
Everybody wants to include their custom components in LCL. Why?
Most likely because it is much easier to have a single "batteries
included" installer that provides
On Fri, Mar 8, 2019 at 12:55 PM Juha Manninen via lazarus
wrote:
> Everybody wants to include their custom components in LCL. Why?
Most likely because it is much easier to have a single "batteries
included" installer that provides everything you need out of the box
now and much more likely to be
Okay, will do so. About lcl patch, we ll talk later.
On 08.03.2019 14:54, Juha Manninen via lazarus wrote:
Everybody wants to include their custom components in LCL. Why? The
Online Package Manager is designed exactly for easy access to external
components. Let's use it please!
--
Regards,
On Fri, Mar 8, 2019 at 1:01 PM Alexey via lazarus
wrote:
> Juha, I wanted to hook new dialog (ok, separate component) into TFontDialog.
I also feel a separate dialog, TLazFontDialog or whatever, is better.
It should be put into a package and then provided through OPM.
I think you should create a
Completely new form.
> Do you want to embed a component into the native dialog, or to
> create a complete custom drawn font dialog?
>
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus
On Fri, 8 Mar 2019 14:01:06 +0300
Alexey via lazarus wrote:
> Juha, I wanted to hook new dialog (ok, separate component) into
> TFontDialog. Can I make a patch to allow such a hook? It must be very
> small diff which don’t bloat the lcl.
Do you want to embed a component into the native dialog,
Juha, I wanted to hook new dialog (ok, separate component) into TFontDialog.
Can I make a patch to allow such a hook? It must be very small diff which don’t
bloat the lcl.
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
On Thu, Mar 7, 2019 at 3:09 PM zeljko via lazarus
wrote:
> Not as default TFontDialog. Maybe as TLazFontDialog or similar.
+1
AlexeyT, what is wrong in having a separate component for those who need it?
If the current native dialogs have bugs (Carbon etc.) they should be
fixed obviously. That
Am 07.03.2019 um 14:12 schrieb AlexeyT via lazarus:
Here's my GH repo with dialog which almost 100% mimics GTK2
FontDialog. https://github.com/alexey-t/atfontdialog
On Windows the font dialog also allows to select the color which is
missing here.
An issue: the dialog is resizable, but the
On 07/03/2019 13:09, zeljko via lazarus wrote:
On 03/06/2019 07:54 PM, AlexeyT via lazarus wrote:
I have an idea to make LCL based TFontDialog- which will be LCL form,
which can be called by TFontDialog.Execute (if Boolean variable in
LCL is set). Why make it?
I haven't checked recently, but
On 07/03/2019 13:12, AlexeyT via lazarus wrote:
> Default must be native OS dialog. I suggest to use my dialog when
> boolean option in LCL (will be added) true.
The replies so far are not surprising at all. LCL prides itself staying
with "native components". Granted I find that has many
On 07/03/2019 18:14, Alexey via lazarus wrote:
Please no? What do other developers think, also no (lcl option for universal
dialog not wanted)?
AT
IMHO, it should be a separate component. So no code will be pulled into
the user app, if it is not used.
While certainly useful, it is not
Please no? What do other developers think, also no (lcl option for universal
dialog not wanted)?
AT
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus
On Thu, Mar 7, 2019 at 2:12 PM AlexeyT via lazarus
wrote:
> Default must be native OS dialog. I suggest to use my dialog when
> boolean option in LCL (will be added) true.
Please no!
--
Bart
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
Default must be native OS dialog. I suggest to use my dialog when
boolean option in LCL (will be added) true. Here's my GH repo with
dialog which almost 100% mimics GTK2 FontDialog.
https://github.com/alexey-t/atfontdialog
It even increases preview height for big sizes >20.
On 07.03.2019
On 03/06/2019 07:54 PM, AlexeyT via lazarus wrote:
I have an idea to make LCL based TFontDialog- which will be LCL form,
which can be called by TFontDialog.Execute (if Boolean variable in LCL
is set). Why make it?
- we can make all best features of FontDlgs from all WSes
- we can make
I have an idea to make LCL based TFontDialog- which will be LCL form,
which can be called by TFontDialog.Execute (if Boolean variable in LCL
is set). Why make it?
- we can make all best features of FontDlgs from all WSes
- we can make additional events- e,g, OnSelectFont (called when used
24 matches
Mail list logo
