i think i could solve what i wanted to do.
generating dynamically the t:selects with their appropriate selectModels.
TML
${baseFeature.key}
JAVA
@Property
private final ValueEncoder encoder = new
ValueEncoder()
{
@Override
public String toClien
Sorry for the spam. If your an experience Tapestry consultant/contractor my
company is in need of some of your skills.
Please contact me directly (p.s. no principles please).
Chris
-
To unsubscribe, e-mail: users-unsubscr...@ta
Have the same Problem here with Tomcat 7.0.33 and Tapestry 5.3.6
Is it a tapestry problem or tomcat one? Any comments from devs?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tomcat-7-Parallel-Deployment-tp5715717p5719909.html
Sent from the Tapestry - User mailing list
Hello again,
I am still trying to implement my dynamic selectModel.
What i did so far is:
TML
JAVA
list: standardFeatureSelectModels is
//this method gets the groups features and generates for them the
selectModels
public List getStandardProfileFeatureSelectModelsForGroup(Group
group){
FYI, I found it necessary to add the following to my Layout component
@Import(stack="core")
Otherwise the bootstrap CSS was only included if I had a on my
page.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-5-4-alpha-2-css-overriding-tp5719856p5719906.html
Se
There are few T5.4-a2 components (that I seem to use) that pull in the
core stack which then imports the bootstrap.css. Alerts is one of
them, which I've Munky Patched not to. You're then free to import
whatever CSS you want in whatever order as per usual.
Another option (which I also do to keep t
If I was to take a guess, it would be the new usage of require.js in tapestry
5.4. Tapestry has defined a bootstrap module. You might need to define a
module which depends on the bootstrap module to guarantee that yours is
loaded after bootstrap.
As I said, this is a guess... I've not yet dug too
