-
New Commercial Services Section
We have now opened a commercial services section here on the forum for registered users. If you have a Fabrik project that you wish to have someone work on for you, post it under Help Wanted. If you are an application developer and wish to earn some money helping others, post your details under Fabrik Application Developers.
Both of these are unmoderated. It will be up to both parties to work out the details and come to an agreement.
-
Joomla 5.1
For running J!5.1 you must https://fabrikar.com/forums/index.php?wiki/update-from-github/ or include the new file manually https://fabrikar.com/forums/index.php?threads/joomla-5-1-and-fabrik-cannot-find-files-error.54473/post-285151 See also Announcements
"Use as table row CSS class"
- Thread starter sergio
- Start date
- Status
cheesegrits
Support Gopher
I added that as a paid feature (someone wanted it badly enough to pay a few bucks for it). Basically, it just adds whatever the element value is (well, the value rendered on the table for the element) as a CSS class for either the whole row, or the individual cell. It replaces any spaces with underscore, and converts to lower case.
Lets say you have an invoicing system, with a dropdown for "Paid", "Invoiced", "Yet To Bill" (or whatever). You could have any "Yet To Bill" lines in the table show up in some other background color by adding the class yet_to_bill to the form CSS, with whatever styling you want. Or you could add all three options as classes, and style each type of line differently.
It's not super useful for everyone, but I'm sure some folk will find a use for it.
-- hugh
Lets say you have an invoicing system, with a dropdown for "Paid", "Invoiced", "Yet To Bill" (or whatever). You could have any "Yet To Bill" lines in the table show up in some other background color by adding the class yet_to_bill to the form CSS, with whatever styling you want. Or you could add all three options as classes, and style each type of line differently.
It's not super useful for everyone, but I'm sure some folk will find a use for it.
-- hugh
Hi,
I'm the guy who requested this feature, and this is how I used it:
It's a sign in/out board that is used to locate people and see what they're up to. The user fills in their status, schedule, return date/time, etc. Depending on the status they select, the row is colored and styled differently.
I'm the guy who requested this feature, and this is how I used it:
It's a sign in/out board that is used to locate people and see what they're up to. The user fills in their status, schedule, return date/time, etc. Depending on the status they select, the row is colored and styled differently.
Attachments
To get this to work properly in IE6 I had to replace the PHP that generates the table row class to put a hyphen instead of a space between the template class and the class generated by the table data:
I configured my template to highlight the row in a different color when hovered over with the mouse:
Cheers,
-n8
Code:
<tr class="oddrow<?php echo $c . '-' . implode(' ',$row_classes);?>">I configured my template to highlight the row in a different color when hovered over with the mouse:
Code:
<tr class="upoddrow<?php echo $c . '-' . implode(' ',$row_classes);?>" onMouseOver="this.className='dnoddrow<?php echo $c . '-' . implode(' ',$row_classes);?>'" onMouseOut="this.className='upoddrow<?php echo $c . '-' . implode(' ',$row_classes);?>'">Cheers,
-n8
cheesegrits
Support Gopher
One of the many, many (many many many many) (many) reasons I haven't run IE6 since the day FireFox came out!
I can just about live with IE8 now it has an (almost) (semi) decent debugger.
FYI, I'm under orders from Rob to move the actual logic out of the templates and into view.html.php. So pretty soon those templates will change, so they just use a simple variable name, rather than building the style array and exploding the array in situ.
I might even put some browser detection code in it, and do that IE6 fix.
-- hugh
I can just about live with IE8 now it has an (almost) (semi) decent debugger.
FYI, I'm under orders from Rob to move the actual logic out of the templates and into view.html.php. So pretty soon those templates will change, so they just use a simple variable name, rather than building the style array and exploding the array in situ.
I might even put some browser detection code in it, and do that IE6 fix.
-- hugh
Believe me, I'd love to stop support for IE6, but then I'd have to kill 35% of the people who visit my sites...
I think it would be cool to move the code out of the templates, might even be cool if you could preview the class name in the admin pages to make for easier template building....
I wonder if anyone else has started using this feature yet. I like it a lot, tho it does complicate the CSS, especially in my case with different declarations for onMouseOver, onMouseOut, etc... But it sure does look purdy!
Cheerio,
-n8
cheesegrits
Support Gopher
I like it as well. Neat little feature.
Main problem of course is only being able to use elements which are visible on the table row.
We're pretty sure we can work round this, though. We'll probably put the same feature in 2.0, but with a workaround so you can use any row data, regardless of visibility or access levels. Mainly because it will also help construct 'detail links', being able to use placeholders for non-visible elements. At the moment, you can point the details link to (say) profile.php&user={foo.userid}, but of course that means the userid element has to be visible.
In 2.0, you can specify a different 'detail link' for each element on the row. Which is a very useful feature - so you can (say) point one cell to a profile page with userid, and another to an email form with {email}. It'll be even more useful if you aren't restricted to visible data.
-- hugh
Main problem of course is only being able to use elements which are visible on the table row.
We're pretty sure we can work round this, though. We'll probably put the same feature in 2.0, but with a workaround so you can use any row data, regardless of visibility or access levels. Mainly because it will also help construct 'detail links', being able to use placeholders for non-visible elements. At the moment, you can point the details link to (say) profile.php&user={foo.userid}, but of course that means the userid element has to be visible.
In 2.0, you can specify a different 'detail link' for each element on the row. Which is a very useful feature - so you can (say) point one cell to a profile page with userid, and another to an email form with {email}. It'll be even more useful if you aren't restricted to visible data.
-- hugh
- Status