Drag drop on i-Phone
Locked
 
|
Hi All,
i have seaside application writing with GLASS:
Seaside 2.8g1-dkh.624 and
Scriptaculous.g-dkh243.
Into PC browser all work well.
I have test the application into i-phone
browser.
I found that the drag drop d'ont work on
it.
Anyone have idea about this problem ?
Any pointers would be greatly appreciated! Thanks! Dario _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
> I found that the drag drop d'ont work on it.
> > Anyone have idea about this problem ? Check the Apple Documentation on Safari Mobile: http://developer.apple.com/safari/ Safari on the iPhone (as well as other WebKit based browsers on other mobile devices) use a slightly different set of events than traditional desktop web browsers. Typically mouse-move events do not exist on such devices, because there is no such thing as a single mouse pointer position. You probably need to use a special library that supports drag and drop based on touch events. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by dtrussardi@tiscali.it
On Sat, Nov 21, 2009 at 3:35 AM, Dario Trussardi <[hidden email]> wrote:
Dario, you should be able to do one of the following: 1) re-target your browser to use one of the Safari Mobile browsers using Safari Desktop Develop -> User Agent -> Mobile Safari 3.1.2 - iPhone 2) Using the iPhone Simulator Good luck, -Conrad _______________________________________________ _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Hello everybody,
I maintain a small blog that I manage using a Perl-Program I wrote. I've been learning smalltalk for a (short) while and decided it would be a neat idea to put what I've learnt about seaside to good use. So I wrote a little program that would accept user comments and display them on the blog. Unfortunately I've been unsuccessful to finding out something about URL parameters and how to use them. What I would like to do is something like this: http://localhost:8080/seaside/comment?blogdate=20091122&_s=TbwWTAII8zTnnVL3&_k=QgJ6CzsF Also, I might want to add a URL parameter myself when actually posting the form. How does one do that? Is there any online literature available on this topic? Google wasn't being friendly ;-) Best regards, Ole._______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Hi Ole,
to extract parameters from URL, you have to make your own WAApplication subclass, where override 'handleRequest: aRequest'. Something like this: handleRequest: aRequest | blogdate | blogdate := aRequest at: 'blogdate'. ^ super handleRequest: aRequest If you want to add parameters to URL, you should override 'updateUrl: anUrl' in your component. So it could looks like: updateUrl: anUrl super updateUrl: anUrl. aUrl addToPath: 'my-great-parameter'. This works in Seaside 2.8. It can be different in Seaside 3.0. Cheers, Martin On 22.11.2009, at 8:30, Ole Voß wrote: > Hello everybody, > > I maintain a small blog that I manage using a Perl-Program I wrote. > I've been learning smalltalk for a (short) while and decided it > would be a neat idea to put what I've learnt about seaside to good > use. So I wrote a little program that would accept user comments and > display them on the blog. Unfortunately I've been unsuccessful to > finding out something about URL parameters and how to use them. What > I would like to do is something like this: > http://localhost:8080/seaside/comment?blogdate=20091122&_s=TbwWTAII8zTnnVL3&_k=QgJ6CzsF > > Also, I might want to add a URL parameter myself when actually > posting the form. How does one do that? Is there any online > literature available on this topic? Google wasn't being friendly ;-) > > Best regards, > > Ole._______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
> to extract parameters from URL, you have to make your own
> WAApplication subclass, where override 'handleRequest: aRequest'. Something > like this: > > handleRequest: aRequest > | blogdate | > blogdate := aRequest at: 'blogdate'. > ^ super handleRequest: aRequest Subclassing WAApplication is discouraged and normally not necessary (Seaside 2.6 and earlier required that). Simply override #initialRequest: in your root component. Have a look at WABrowser and the other components that override #initialRequest: and #updateRoot: to see some examples. This works exactly the same in Seaside 2.8 and 3.0. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
On Sun, Nov 22, 2009 at 1:54 AM, Lukas Renggli <[hidden email]> wrote:
>> to extract parameters from URL, you have to make your own >> WAApplication subclass, where override 'handleRequest: aRequest'. Something >> like this: >> >> handleRequest: aRequest >> | blogdate | >> blogdate := aRequest at: 'blogdate'. >> ^ super handleRequest: aRequest > > Subclassing WAApplication is discouraged and normally not necessary > (Seaside 2.6 and earlier required that). Simply override > #initialRequest: in your root component. > > Have a look at WABrowser and the other components that override > #initialRequest: and #updateRoot: to see some examples. This works > exactly the same in Seaside 2.8 and 3.0. His example included a session key in the URL. If that session key is valid, #initialRequest: would not be called since it is not the first request to the session. In Seaside 2.8 you can use "self session currentRequest"; in Seaside 3.0 "self requestContext request". Julian _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Thank you everybody, that helped a lot!
Ole On Nov 23, 2009, at 10:47 PM, Julian Fitzell wrote: > On Sun, Nov 22, 2009 at 1:54 AM, Lukas Renggli <[hidden email]> wrote: >>> to extract parameters from URL, you have to make your own >>> WAApplication subclass, where override 'handleRequest: aRequest'. Something >>> like this: >>> >>> handleRequest: aRequest >>> | blogdate | >>> blogdate := aRequest at: 'blogdate'. >>> ^ super handleRequest: aRequest >> >> Subclassing WAApplication is discouraged and normally not necessary >> (Seaside 2.6 and earlier required that). Simply override >> #initialRequest: in your root component. >> >> Have a look at WABrowser and the other components that override >> #initialRequest: and #updateRoot: to see some examples. This works >> exactly the same in Seaside 2.8 and 3.0. > > His example included a session key in the URL. If that session key is > valid, #initialRequest: would not be called since it is not the first > request to the session. In Seaside 2.8 you can use "self session > currentRequest"; in Seaside 3.0 "self requestContext request". > > Julian > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
«
Return to Seaside General
|
1 view|%1 views
| Free forum by Nabble | Edit this page |