Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2009-09

Enhance Macro usage by making it easier to find

23 messages · 6 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Graeme Geldenhuys

Hi,

Before I add this as a feature request in Mantis, I thought I would discuss the idea first. Maybe others (and not just me) could also see the benefit of this.

Currently Lazarus supports various macros in path and filenames[1]. But to be able to use it, you need to first go look in the help to see what macros are available.

A popular example is [2] below...

Anyway, my thoughts were that maybe we can add a "insert macro" popup menu / button next to any EditBox where paths or filenames are entered - and where macros can be used. See the attached image, where a product named PINs use this idea. Now the user doesn't need to refer to help files are try and remember all available macros.

Your thoughts?

[1] http://wiki.lazarus.freepascal.org/IDE_Macros_in_paths_and_filenames

[2]
http://wiki.lazarus.freepascal.org/IDE_Window:_Compiler_Options#Unit_output_directory

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/ -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot.png Type: image/png Size: 3356 bytes Desc: not available URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20090911/6b3f20be/attachment.png>

Reply by email

Mattias Gärtner
to Graeme Geldenhuys

Zitat von Graeme Geldenhuys :

Show quoted text 19 lines
Hi, Before I add this as a feature request in Mantis, I thought I would discuss the idea first. Maybe others (and not just me) could also see the benefit of this. Currently Lazarus supports various macros in path and filenames[1]. But to be able to use it, you need to first go look in the help to see what macros are available. A popular example is [2] below... Anyway, my thoughts were that maybe we can add a "insert macro" popup menu / button next to any EditBox where paths or filenames are entered - and where macros can be used. See the attached image, where a product named PINs use this idea. Now the user doesn't need to refer to help files are try and remember all available macros. Your thoughts?

Thought 1:

Under Linux and Windows users are used to the right click popup menus of edit fields (for clipboard, input methods, special characters and accessibility). So maybe there it would be more appropriate to add a menu item.
Under OS X a right click popup menu is a bad idea.

Thought 2:

It would be nice to have completion boxes Ctrl+Space for all edit fields. They could list all macros and/or all files .... The problem is that the gtk intf does not yet support non modal on modal forms.

Mattias

Reply by email

Michael Van Canneyt
to Mattias Gärtner
Mattias G?rtner wrote 35 lines
Zitat von Graeme Geldenhuys : > Hi, > > Before I add this as a feature request in Mantis, I thought I would > discuss the idea first. Maybe others (and not just me) could also see > the benefit of this. > > Currently Lazarus supports various macros in path and filenames[1]. But > to be able to use it, you need to first go look in the help to see what > macros are available. > > A popular example is [2] below... > > Anyway, my thoughts were that maybe we can add a "insert macro" popup > menu / button next to any EditBox where paths or filenames are entered - > and where macros can be used. See the attached image, where a product > named PINs use this idea. Now the user doesn't need to refer to help > files are try and remember all available macros. > > Your thoughts? Thought 1: Under Linux and Windows users are used to the right click popup menus of edit fields (for clipboard, input methods, special characters and accessibility). So maybe there it would be more appropriate to add a menu item. Under OS X a right click popup menu is a bad idea. Thought 2: It would be nice to have completion boxes Ctrl+Space for all edit fields. They could list all macros and/or all files .... The problem is that the gtk intf does not yet support non modal on modal forms.

Why does this pose a problem ? I would think that you'd use a simple listbox for this ?

Michael.

Reply by email

Graeme Geldenhuys
to Mattias Gärtner: Zitat von Graeme Geldenhuys : Thought 1: Under Linux and Windows users are used to the…

Mattias G?rtner het geskryf:

Show quoted text 7 lines
Thought 1: Under Linux and Windows users are used to the right click popup menus of edit fields (for clipboard, input methods, special characters and accessibility). So maybe there it would be more appropriate to add a menu item. Under OS X a right click popup menu is a bad idea.

My first thought was a right click popup menu entry - but then thought no. That's exactly the reason why I thought of using a "insert macro" button. This should then apply to all platforms without stepping on anybody's toes.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

Reply by email

Mattias Gärtner
to Graeme Geldenhuys

Zitat von Graeme Geldenhuys :

Show quoted text 13 lines
Mattias G?rtner het geskryf: > Thought 1: > > Under Linux and Windows users are used to the right click popup menus > of edit fields (for clipboard, input methods, special characters and > accessibility). So maybe there it would be more appropriate to add a > menu item. > Under OS X a right click popup menu is a bad idea. My first thought was a right click popup menu entry - but then thought no. That's exactly the reason why I thought of using a "insert macro" button. This should then apply to all platforms without stepping on anybody's toes.

We need a possibility to merge system popup menu items anyway. We could first add the button and change it later when the "merging" is implemented.
And keep in mind, that not all macros can be used everywhere.

Mattias

Reply by email

Mattias Gärtner
to Michael Van Canneyt: Why does this pose a problem ? I would think that you'd use a simple listbox for this ?…

Zitat von Michael Van Canneyt :

Show quoted text 9 lines
On Fri, 11 Sep 2009, Mattias G?rtner wrote: [...] > It would be nice to have completion boxes Ctrl+Space for all edit > fields. They could list all macros and/or all files .... > The problem is that the gtk intf does not yet support non modal on > modal forms. Why does this pose a problem ? I would think that you'd use a simple listbox for this ?

Well. Yes, this is be possible, but it has some minor quirks:
- If the edit is on a small dialog the listbox is also very short.
- A listbox needs all items in advance for its scrollbar. This would be pretty slow if the completion box shows thousands of files/words.
- for the highlighting/formatting we need to custom paint. IMO a custom control is better suited.

Is there any volunteer to program a TCompletionBox?

Mattias

Reply by email

Graeme Geldenhuys
to Mattias Gärtner: Zitat von Graeme Geldenhuys : We need a possibility to merge system popup menu items…

Mattias G?rtner het geskryf:

We need a possibility to merge system popup menu items anyway. We could first add the button and change it later when the "merging" is implemented.

+1

And keep in mind, that not all macros can be used everywhere.

I know, and that's the difficult part. I don't know how macros are registered in the IDE, so I don't know how to quite handle this. Hard-coding the macro list in each dialog does not seem like the right option either.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

Reply by email

Mattias Gärtner
to Graeme Geldenhuys

Zitat von Graeme Geldenhuys :

Show quoted text 14 lines
Mattias G?rtner het geskryf: > > We need a possibility to merge system popup menu items anyway. > We could first add the button and change it later when the "merging" > is implemented. +1 > And keep in mind, that not all macros can be used everywhere. I know, and that's the difficult part. I don't know how macros are registered in the IDE, so I don't know how to quite handle this. Hard-coding the macro list in each dialog does not seem like the right option either.

First the right macro list must be fetched. There are three or four cases. And some macros are done via an event. These must be converted to registered macros.

But at the moment my todo list is quite long.

Mattias

Reply by email

Vincent Snijders
to Graeme Geldenhuys
Graeme Geldenhuys wrote 7 lines
Thanks for the info... Mattias G?rtner het geskryf: > But at the moment my todo list is quite long. Same here. I'll simply add it as a feature request - not to be forgotten.

I am not sure that the bug tracker is the most suitable place for such a thing. Most of the time such feature request end up buried in the "let's look at those issues when we have time" stack. It will probably even be forgotten when somebody actually finds time and implements it. And then it is still in the bug tracker as unresolved issue, while in fact it has been implemented already.

It does work correctly for SynEdit for example: we are lucky to have a maintainer who has time to add new features regularly. So feature requests for SynEdit can be assigned to him.

IMHO a better place for such feature requests without a clear owner (with a limited todo list) is: http://wiki.lazarus.freepascal.org/Feature_Ideas

Somebody who wants to contribute to Lazarus and doesn't know what to do, can find a feature more easily in the wiki than hidden between hundreds (almost 1000) other issues in the bug tracker.

Vincent

Reply by email

Martin
to Graeme Geldenhuys: Vincent Snijders het geskryf: OK, done that too, and added a reference to the Mantis…
Graeme Geldenhuys wrote 8 lines
Vincent Snijders het geskryf: > IMHO a better place for such feature requests without a clear owner (with a limited > todo list) is: http://wiki.lazarus.freepascal.org/Feature_Ideas > OK, done that too, and added a reference to the Mantis report.

From the mantis report / Subject: "Enhance Marco usage by making them easier to find"

Who is Marco? :)

Reply by email

Graeme Geldenhuys
to Vincent Snijders: What is the purpose of the Mantis report, except polluting the bug tracker, so that…

Vincent Snijders het geskryf:

What is the purpose of the Mantis report, except polluting the bug tracker, so that finding issues is harder?

The feature request was added to Mantis first - BEFORE you mentioned the wiki. Instead of duplicating my bad typing skills (and wasting my time), I just added a reference in the Wiki to the Mantis report for more details.

If you do not want Feature Requests in the Mantis tracker, then you must make it clear to *everybody*! Also delete the "Feature" option in the Mantis tracker.

Also make sure the wiki has the facts straight! The first line in that wiki page mentions that you can also add feature requests to Mantis! So who must I believe?

This is a perfect example of "fragmented documentation"! Users do not know where is what, or what is the "newest / latest" information. This goes hand-in-hand with my request a while back to finalize the help format for the Lazarus IDE and Lazarus LCL: fpdoc format, web forums, wiki, offline help etc...

Anyway, I also do NOT have access to delete my own postings in the Mantis tracker (bugs or feature requests) - so from my side there is very little else I can do.

And if you are still wondering why I keep bitching about not having offline help, or why I don't like editing wiki's much, read the following:

http://news.bbc.co.uk/2/hi/africa/8248056.stm
http://technology.iafrica.com/news/technology/1915560.htm

I'm pretty sure South Africa is not the only country in the world with shitty or ridiculously expensive (on avg. 500% more expensive than EU countries) Internet access.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

Reply by email

Vincent Snijders
to Graeme Geldenhuys
Graeme Geldenhuys wrote 9 lines
Vincent Snijders het geskryf: > What is the purpose of the Mantis report, except polluting the bug > tracker, so that finding issues is harder? The feature request was added to Mantis first - BEFORE you mentioned the wiki. Instead of duplicating my bad typing skills (and wasting my time), I just added a reference in the Wiki to the Mantis report for more details.

Yes, you were too fast or I was too slow.

If you do not want Feature Requests in the Mantis tracker, then you must make it clear to *everybody*! Also delete the "Feature" option in the Mantis tracker.

I only want feature requests that stand a reasonable chance to be implemented before version 3.0 (due after 2025).

Also make sure the wiki has the facts straight! The first line in that wiki page mentions that you can also add feature requests to Mantis! So who must I believe?

You can. But IMHO this one is a bad example of such a feature request. Good one, because you and Michael feel responsible for that and the issue can be assigned:
http://bugs.freepascal.org/view.php?id=12730
Good one, because Martin is extending synedits features: http://bugs.freepascal.org/view.php?id=13514

Show quoted text 7 lines
This is a perfect example of "fragmented documentation"! Users do not know where is what, or what is the "newest / latest" information. This goes hand-in-hand with my request a while back to finalize the help format for the Lazarus IDE and Lazarus LCL: fpdoc format, web forums, wiki, offline help etc...

Good idea. I will try to make the wiki off line in 0.9.30.

Anyway, I also do NOT have access to delete my own postings in the Mantis tracker (bugs or feature requests) - so from my side there is very little else I can do.

I fear I offend people, if I close this issue with "No change required", "Won't fix" (it is not true, patches are excepted). I don't see how I can resolve this issue, so I will keep it open, unless the reporter requests it to be closed.

Vincent

Reply by email

Graeme Geldenhuys
to Vincent Snijders

Vincent Snijders het geskryf:

I only want feature requests that stand a reasonable chance to be implemented before version 3.0 (due after 2025).

And who decides the fate of such feature requests? If you did not notice, I first posted the idea here in the mailing list to be discussed and get a feeling of what other developers think. I made it clear that I do not know how others feel about this feature, but that I thought it would be helpful. I did not want to "pollute" the Mantis tracker with features only I want.

Mattias and Michael commented, without explicitly saying: NO THIS IS RUBBISH! So based on their responses, I understood it that others also feel this could be beneficial, but none of use have the time to implement it right this minutes. Hence, the Feature Request in Mantis - so the idea is documented and not forgotten.

BTW: This is the first time I hear that Lazarus developers do NOT look at the Feature Request section in Mantis. It's news to me.

You can. But IMHO this one is a bad example of such a feature request.

In your opinion maybe. By like I said, who decides what is good or bad? At least I posted my idea in the mailing list - to be discussed. You might not have noticed, but I do this often before I report features requests or bugs in mantis.

I fear I offend people, if I close this issue with "No change required", "Won't fix" (it is not true, patches are excepted).

Why not simply allow the creator of the feature request or bug report to delete their own reports.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

Reply by email

Marco van de Voort
to Vincent Snijders: Yes, you were too fast or I was too slow. I only want feature requests that stand a…
Vincent Snijders wrote 7 lines
> This is a perfect example of "fragmented documentation"! Users do not > know where is what, or what is the "newest / latest" information. This > goes hand-in-hand with my request a while back to finalize the help > format for the Lazarus IDE and Lazarus LCL: fpdoc format, web forums, > wiki, offline help etc... > Good idea. I will try to make the wiki off line in 0.9.30.

Is there a way to regularly export from the wiki?

Reply by email

Marco van de Voort
to Vincent Snijders
Vincent Snijders wrote 8 lines
Marco van de Voort schreef: >> Good idea. I will try to make the wiki off line in 0.9.30. > > Is there a way to regularly export from the wiki? I think wikihelp can be used or adapted. http://wiki.lazarus.freepascal.org/Projects_using_Lazarus#WikiHelp http://lazarus-ccr.svn.sourceforge.net/viewvc/lazarus-ccr/applications/wikihelp/

I think it won't because SB called v.snijders installed something called "bad behaviour" :-)

Or at least his email address is in the http 403 error.

Reply by email

Vincent Snijders
to Marco van de Voort
Marco van de Voort wrote 13 lines
On Sat, Sep 12, 2009 at 11:25:20AM +0200, Vincent Snijders wrote: > Marco van de Voort schreef: >>> Good idea. I will try to make the wiki off line in 0.9.30. >> Is there a way to regularly export from the wiki? > I think wikihelp can be used or adapted. > http://wiki.lazarus.freepascal.org/Projects_using_Lazarus#WikiHelp > http://lazarus-ccr.svn.sourceforge.net/viewvc/lazarus-ccr/applications/wikihelp/ I think it won't because SB called v.snijders installed something called "bad behaviour" :-) Or at least his email address is in the http 403 error.

Then wikihelp must be tought not to behave badly.

Vincent

Reply by email

Vincent Snijders
to Graeme Geldenhuys: Vincent Snijders het geskryf: And who decides the fate of such feature requests? If you…

Even though it is Friday again, I will try to respond without getting too emotional.

Graeme Geldenhuys wrote 5 lines
Vincent Snijders het geskryf: > I only want feature requests that stand a reasonable chance to be > implemented before version 3.0 (due after 2025). And who decides the fate of such feature requests?

He who implements, decides. This is open source, you know ;-). And with all those distributed SCM systems, core developers stand no change impeding feature requests, if there is a developer who implements them. :-)

Show quoted text 5 lines
If you did not notice, I first posted the idea here in the mailing list to be discussed and get a feeling of what other developers think. I made it clear that I do not know how others feel about this feature, but that I thought it would be helpful.

I have no objection to a feature request, but a feature request without somebody who wants to implement is.

Show quoted text 7 lines
I did not want to "pollute" the Mantis tracker with features only I want. Mattias and Michael commented, without explicitly saying: NO THIS IS RUBBISH! So based on their responses, I understood it that others also feel this could be beneficial, but none of use have the time to implement it right this minutes.
Hence, the Feature Request in Mantis - so the idea is documented and not forgotten.

Still in Mantis it will be forgotten is my experience. Adding them to mantis has no additional value. So http://wiki.lazarus.freepascal.org/Feature_Ideas is as good.

BTW: This is the first time I hear that Lazarus developers do NOT look at the Feature Request section in Mantis. It's news to me.

I can only speak for myself and how I see it used. Other Lazarus developers have to tell what they do with feature requests in the wiki. Take for example "Using navigation keys in a form at design time" :
http://bugs.freepascal.org/view.php?id=1738. Yesterday Paul committed some changes to implement this feature. I asked if he had seen this issue in mantis, he said no, but a colleague of him wanted it to be implemented very much. He didn't even know about it. If I would not remember it, I bad it would be there for a year or more, until somebody noticed that this was implemented a long time ago.

Show quoted text 5 lines
> You can. But IMHO this one is a bad example of such a feature > request. In your opinion maybe. By like I said, who decides what is good or bad?

Note the difference: This discussion is about what is a good or bad feature request. It is about what is a good or bad place to document a feature request. With assignee -> bug tracker, without assignee: http://wiki.lazarus.freepascal.org/Feature_Ideas

Example: a good feature request for the bug tracker is: http://bugs.freepascal.org/view.php?id=14618
Dmitry is maintainer of this component and the issue can be assigned to him.

As a Lazarus developer who uses the bug tracker a lot and wants to keep it manageable, I may not decide about it, but I fancy the idea I can make suggestions about its usage.

At least I posted my idea in the mailing list - to be discussed. You might not have noticed, but I do this often before I report features requests or bugs in mantis.

That is good, keep doing so. I read all those emails. I am sorry I could not respond between 11:26, the first answer to your feature request and 12:36. At that time I hoped "I'll simply add it as a feature request" meant adding it in the wiki. I was simply too late.

Show quoted text 7 lines
> I fear I offend people, if I close this issue with "No change > required", "Won't fix" (it is not true, patches are excepted). Why not simply allow the creator of the feature request or bug report to delete their own reports.

I would be reluctant to that, maybe only for issues not yet resolved. It may cause valuable information to be lost. In svn log messages we often refer to issues in the bug tracker.

Vincent

Reply by email

Graeme Geldenhuys
to Vincent Snijders

Vincent Snijders het geskryf:

Even though it is Friday again, I will try to respond without getting too emotional.

:-) I'll be nice today, seeing that I'm on holiday all of next week. I already feel relaxed.

I have no objection to a feature request, but a feature request without somebody who wants to implement is.

OK, then we have different ideas of Mantis usage. In the future I'll mention ideas in the mailing list. If there are no clear takers I'll add it to the wiki. If it's something I have the ability of implementing, I'll add it to my personal todo list.

> Why not simply allow the creator of the feature request or bug > report to delete their own reports. I would be reluctant to that, maybe only for issues not yet resolved.

I meant issues that have not been resolved and not been assigned to anybody yet.

Have a nice day! ;-)

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

Reply by email