Could this be interesting in Servoy Developer?

Having a big solution with many forms sometimes is hard to find the one you need. Maybe creating folders inside the active solutions could make that easier because we could group forms the way we would like.

How many of you think that creating folders inside the active solution tree could be useful?

+2

+1

Do you all know about the locator that you get by pressing Ctrl + Shift + L ?

Joas:
Do you all know about the locator that you get by pressing Ctrl + Shift + L ?

I do, and LOVE it. Major timesaver to find any Servoy object AND methods.
Also Ctrl-H is a HUGE benefit to find anything in ALL your code/forms.

Hope this helps.

Entering a * does not show anything in my environment, but entering a ? shows the whole string (in my case a relationship). Either I do not understand it correctly or the description in the header of the window is wrong.
How would I search for all relationships not starting with an underline?

Joas:
Do you all know about the locator that you get by pressing Ctrl + Shift + L ?

Servoy 5.2.9
Mac OS X 10.6.7

Regards,

It searches for resources that start with the string you typed.
So if you type “?a” it will find everything that has an “a” as it’s second character.
And if you type “blax” you get everything that contains “bla” and further to the right also “x”.

You are right that typing just “*” doesn’t find anything, while it should find everything. I’m not sure why that is, but to be honest: it also doesn’t make that much sense to locate everything. :)

The first list that you see is History, and only when you really start searching for something (and that is not * because that is even implied, the * is always there as the last char) something happens.

So just typing * is exactly the same as nothing, this is default eclipse search dialog behavior

I missed your question before

Robert Huber:
How would I search for all relationships not starting with an underline?

It is not possible to do a not-search.

However, I think this is not a good case to use the resource locator. The locator is best used to find and open one thing at a time.
If you want to see ALL relations not starting with an underline, you could better just look under relations in the solution explorer.

First of all thanks for all the above answers and explanations.

Joas:
I missed your question before

Robert Huber:
How would I search for all relationships not starting with an underline?

It is not possible to do a not-search.

However, I think this is not a good case to use the resource locator. The locator is best used to find and open one thing at a time.
If you want to see ALL relations not starting with an underline, you could better just look under relations in the solution explorer.

My requirement is to get the number of all database relationships. This excludes all starting with an underline, as in our convention “underline relationsships” are only for functional purposes and not existing in the database design (entity relationship model). The reason for counting the number of relationsships in Servoy is to make sure it’s the same number as in the datamodel - to make sure we there is none missing and none too much, i. e. one we forgot to delete in Servoy while changing the datamodel.
I did not find an easy way of counting the number or relationships in Servoy, though.

Regards,

count all the .rel files?
and maybe with a regxpression filter out the onces you don’t want to count?

This works fine, thanks for the tip!

jcompagner:
count all the .rel files?
and maybe with a regxpression filter out the onces you don’t want to count?

Or in a Servoy method use the solutionModel to get all relations and then filter the ones you want:

	var _relations = solutionModel.getRelations();
	_relations = _relations.filter(function (relation) { return /^_/.test(relation.name);});
	
	application.output(_relations.length);

Also very fine your tip, thanks Joas

Joas:
Or in a Servoy method use the solutionModel to get all relations and then filter the ones you want:

	var _relations = solutionModel.getRelations();
_relations = _relations.filter(function (relation) { return /^_/.test(relation.name);});

application.output(_relations.length);