On Fri, 21 Sep 2012 15:51:50 -0300, sommeralex
wrote:
i know that the zone itself does not trigger events. the zone itself is
just a HTML content.
the question is, why zoneManager.update() is not enough. If i have zone
already defined in my java/tml class, why then is it not possible to
up
On Fri, 21 Sep 2012 14:59:50 -0300, sommeralex
wrote:
function updatePage(response){
var zoneManager = Tapestry.findZoneManagerForZone(zoneId);
zoneManager.updateFromURL(urlGetGroupsOnLocation);
}
but what i dont understand ist, why do i need an URL? why not
just zoneManager.update()?
> I use underscores in the page names rather than camel case
It's not a huge problem... but it's not a standard way of naming a java
class either. If it was bothering you, you could decorate the
ComponentEventLinkEncoder to convert CamelCase to camel-case.
--
View this message in context:
http:
Lance, I use underscores in the page names rather than camel case. I've never
had any issues doing it, just not sure if it's good practice.
Hi trsvax, I'm not completely sure I understand the idea behind your
suggestion? Could you possible provide a use case where this would come in
handy? Thanks
You might be interested in this
https://github.com/trsvax/Jacquard/blob/master/src/main/java/com/trsvax/jacquard/services/MultiStatePersistenceStrategyImpl.java
It enables @Persist to use url query parameters. It's possible to make it
the default persist strategy in which case things such as the
> I've always been told to use them
I wasn't saying don't use them... I was saying that I'd be surprised if a
search engine would use them any differently to whitespace.
Does this mean that you have page class names with underscores in them? Or
do you have a mechanism to tell tapestry to convert C
Thanks Thiago, I will look into that API. The site is actually starting to
grow a bit more rapidly now, so I think it's about time I start taking it a
bit more seriously and fix all the bugs. :) Now I just need to find more
time to mess with it :-/
--
View this message in context:
http://tapest
Interesting, I've always been told to use them in order to help search
engines to determine the URL content. As always Lance, Thank you for your
valuable input.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Query-Parameter-Suggestions-tp5716416p5716442.html
Sent from t
> I also noticed tapestry can't handle dashes like used-car-for-sale
I haven't noticed this. What does tapestry do?
> Do you know if search engines treat them equally?
I'd assume that search engines ignore them. Since google's ranking algorithm
is a well-kept secret, it's impossible to know.
--
On Fri, 21 Sep 2012 11:17:23 -0300, George Christman
wrote:
I also noticed tapestry can't handle dashes like used-car-for-sale,
instead I need to use underscores, used_car_for_sale.
Tapestry does handle dashes in query parameters and activation contexts,
just not in page names, as they s
I'm also taking into consideration bookmarked search results, emailing urls,
or saved search results. That would be the only reason I would want to store
those parameters in the url.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Query-Parameter-Suggestions-tp5716416p57
Thanks Lance for your suggestions. I'm very aware of non URL improvements
which are improvements I'll be working into the redesign, but currently just
focused on my URL structure.
I also noticed tapestry can't handle dashes like used-car-for-sale, instead
I need to use underscores, used_car_for_s
> would you just pass any sort/pager parameters in as a key/value pair too
Possibly not, think about what people will be googling for and make sure
that's in the URL.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Query-Parameter-Suggestions-tp5716416p5716436.html
Sent f
> we're currently doing the following:
www.cardaddy.com/carsearch/1/5/2/10/3/4
For maximum SEO, it's best to include keywords in the URL. That being said
there are many non-URL-related improvements you can make to a website to
improve SEO.
> I'm assuming for keyword searches I would just use "key
On Fri, 21 Sep 2012 05:54:27 -0300, rosecorp
wrote:
Thank you Ivan, that suggestion is very useful, I will try to refactor my
solutions this night. Thanks a lot!
Ivan suggested exactly the same solution as me, but with a better
explanation. Thanks Ivan! :)
--
Thiago H. de Paula Figueire
Hi Lance, your approach using key/value is the same approach were currently
using, however yours is much better since your using descriptive parameters
rather than just primary keys.
Although horrible for SEO, we're currently doing the following,
eg www.cardaddy.com/carsearch/1/5/2/10/3/4
I defi
Hello!
I have a javascript function,
function onGetLatLng(gLatLng){
if(gLatLng == null) {
alert("Sorry, we couldn't find this address.");
return false;
}
new Ajax.Request(urlGetGroupsOnLocation, { onSuccess: updatePage,
If you need to load all scripts when page is loaded just place @Import
annotation to your page java class. There is no way to make it dynamicly as
components placed in block are not rendered and as result doesn't add their
scripts to page. You need to specify all scripts explicitly.
Or you can try
Hi Thiago,
Maybe I wasn't clear in my first post. I will paraphrase my problem.
I am using tapestry5-jquery and there is a use case where I load page with 3
different options to choose which are event links and then I handle it in
java code to render particular block. The problem is that one of t
You need to contribute ComponentMessagesSource service:
@Contribute(ComponentMessagesSource.class)
public static void contributeComponentMessagesSource(
@Value("com/example/my-messages1") final Resource myMessage1,
@Value("com/example/my-messages2") final Resource myMessage2,
final OrderedConfig
Not sure if it's a good idea or not but you could provide a similar function
to request parameters using key/value pairs in activation context.
eg www.cardaddy.com/carsearch/make/porsche/model/911/colour/red
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Query-Parameter
As you suspected, query parameters don't score as high for SEO as activation
context parameters. Sometimes, query parameters are a necessary evil when
you have optional fields. Tapestry will treat "$N" as null if you want to
pass a null activation context parameter.
Perhaps if you provide an examp
On second thought, MessagesSource is part of the private API so shouldn't be
referenced by your code. Decorate ComponentMessagesSource [3] instead.
[3]
http://tapestry.apache.org/5.3.5/apidocs/org/apache/tapestry5/services/messages/ComponentMessagesSource.html
--
View this message in context:
1. To place components defined in java class on your template you should
use t:id attribute equal to field name(id attribute references clientId
logic). As you don't use this attribute in your code snippet you have 2
separate selects. One of this selects are defined within java class and
doesn't pr
Use a decorator [1] to decorate MessagesSource [2] and provide your own
implementation for getMessages()
[1] http://tapestry.apache.org/tapestry-ioc-decorators.html
[2]
http://tapestry.apache.org/5.3.5/apidocs/org/apache/tapestry5/internal/services/MessagesSource.html
--
View this message in co
25 matches
Mail list logo