Formatting Portals and Tab Panels

One technique I’d like to carry over from FMP is enabling the user to click on an item in a scrollable list and have a related action happen.

In FMP a field can be turned into a button, but in Servoy, so far as I’ve been able to discover, the field must be replaced by a label. That label can be given a dataprovider so that it behaves (more or less) like a field and can be turned into a button.

However, in doing so, the label for the field column is lost. Sorting still happens when clicking the column header, but there’s no visual cue for the user, nothing to identify the significance of the apparent field. The visual appearance of these labels are also somewhat different the genuine fields on either side.

This phenomenon is true for both portals and tab panels. Am I missing something?

Partial answer to my own question. If the label is “Named” instead of designated in the “Text” property, it will present in the column header. Fields use the “Text” property for this function.

Have yet to figure out how to make labels give the same visual appearance as fields. Fields have a graduated fill, labels have nothing. Unsure where this is set.

Morley:
Fields have a graduated fill

This is depending on your look and feel, mainly setting the border the same as a field will do the trick

Jan Blok:

Morley:
Fields have a graduated fill

This is depending on your look and feel, mainly setting the border the same as a field will do the trick

The documentation on look and feel I’ve seen so far is extremely terse. I’ve been hoping that when the docs for 2.1 come out there might be something more in this area.

LAFS, like beans, are in no way something Servoy can and should document I imho. This is the responsibility of the makers like it is my responsibility to explain how and what to use my plugins.

So I guess the only thing you can do is search the forum about what has been said about the subject and even better go out and use the lafs and see what suits you best.

IT2BE:
LAFS, like beans, are in no way something Servoy can and should document I imho. This is the responsibility of the makers like it is my responsibility to explain how and what to use my plugins.

So I guess the only thing you can do is search the forum about what has been said about the subject and even better go out and use the lafs and see what suits you best.

Sorry, but I know nothing about LAFS beyond the generality they have something to do with the look and feel of the visuals of a solution.

Where the heck did the LAFS that come pre-installed with Servoy come from? Who wrote them? How does Servoy interact with them? Can they be modified? In what environment? How do these things work?

I’ve just re-read the single page in the docs. Says there’s two pre-installed and that there are four “themes”, whatever those are. That’s what I mean by “terse”. Likely very clear to those who already know what a LAF and “themes” are, but utterly Greek to newcomers such as myself. I’m NOT asking for a flame war, just looking to learn.

When I posted my original puzzlement I had no idea who wrote, who has responsibility for LAFS. Since they’re pre-installed in Servoy I had no concept that they are independent of Servoy. Nothing in Servoy’s docs to suggest they’re independent, no reference to their source or where to get support for them, no URLs. Nothing. Failing any info to the contrary I assumed they’re written by the Servoy team.

I’m blown away by Servoy as a product and also by the support I’m getting. Drives FMP right out of the water. However, that said, Servoy and Servoy docs aren’t perfect. Confusions turn up. My observations are to the immediate issue at hand, not a sweeping dismissal, not in the least. That way lie flames.

In general I find Servoy docs to be accurate but incredibly terse. They make sense if you already know more or less what they’re talking about but coming in cold turkey they can be baffling.

IMHO, the Servoy team have everything to be proud of, especially the support. Servoy is already superb and it’s constantly getting better. That’s the most important point.

Morley:
When I posted my original puzzlement I had no idea who wrote, who has responsibility for LAFS

LAFS(also called skins) are very common concept on windows XP and Java, as far as I know even apple has two (aqua and brushedmetal)
Java LAFS can be downloaded from the internet put in to the lafs subdir. and be choosen (after servoy start) in the preference tab

Jan Blok:

Morley:
When I posted my original puzzlement I had no idea who wrote, who has responsibility for LAFS

LAFS(also called skins) are very common concept on windows XP and Java, as far as I know even apple has two (aqua and brushedmetal)
Java LAFS can be downloaded from the internet put in to the lafs subdir. and be choosen (after servoy start) in the preference tab

A bunch of followup questions:

If I alter the appearance of a text label maskerading as a button (the entry point of this thread) will this necessarily alter ALL buttons throughout? In other words can I be selective or is this a global situation?

If I want to just slightly tinker with some fine point of appearance does this require building my own LAFS?

Within Servoy can I give my users a popup of available LAFS on a preference screen for them to choose from?

This is stuff I’ve heard about but have never investigated.

Morley:
When I posted my original puzzlement I had no idea who wrote, who has responsibility for LAFS. Since they’re pre-installed in Servoy I had no concept that they are independent of Servoy. Nothing in Servoy’s docs to suggest they’re independent, no reference to their source or where to get support for them, no URLs. Nothing. Failing any info to the contrary I assumed they’re written by the Servoy team.

I’m blown away by Servoy as a product and also by the support I’m getting. Drives FMP right out of the water. However, that said, Servoy and Servoy docs aren’t perfect. Confusions turn up. My observations are to the immediate issue at hand, not a sweeping dismissal, not in the least. That way lie flames.

In general I find Servoy docs to be accurate but incredibly terse. They make sense if you already know more or less what they’re talking about but coming in cold turkey they can be baffling.

IMHO, the Servoy team have everything to be proud of, especially the support. Servoy is already superb and it’s constantly getting better. That’s the most important point.

Morley,

The Servoy 2.1 documentations should be available in the next few days
both for purchase from the Servoy Store in book form as well as in
downloadable pdf format.

We will post an announcement when the books are available and when
the documentation pdfs have been updated.

The new 2.1 version of the Servoy Developer Edition User’s Guide has an
expanded chapter on Servoy styles - including more description, detail
and references for the sections on LAFs, skins and Servoy CSS styles.

This same information is already available in the Servoy 2.1 online
Help Navigator:

  1. Choose Help>Help or press F1.

  2. The Servoy Help Navigator for Servoy 2.1 is “lazy loading” - meaning
    that Help is not installed as part of the Servoy 2.1 installation.

  3. To install Help, follow step 1 and choose “Download” in the Install
    option dialog.

  4. Be patient since the documentation download is fairly large and may
    take a bit of time. You will see a progress bar in the lower right of your
    Servoy window, showing the progress of the download.

  5. Once Help has been downloaded (you only need to download one
    time), choose Help>Help or press F1 to open the Help Navigator.

  6. Make sure you have the “Content” tab open and double click on the
    Styles chapter. You should see a section called "Look And Feels (or LAFs).

You might also want to read more about Servoy CSS styles. If you assign
a style definition or style class definition to an element, the properties of
that style definition or style class definition will take precedence over the
attributes of the default LAF.


Marc Norman
Servoy

Hey, this is very good news indeed. The docs are moving forward at a very quick clip. Excellent work, appreciation in advance.