The browser widget works on all platforms and should do so uniformly - any platform specific aspects will be marked in the dictionary as such in the usual way.
So there is no need to do anything different for android or iOS - it should 'just work'. Mark Mark Sent from my iPhone > On 20 Feb 2016, at 15:28, Sannyasin Brahmanathaswami <bra...@hindu.org> wrote: > > On February 20, 2016 at 2:40:56 AM, Trevor DeVore > (li...@mangomultimedia.com<mailto:li...@mangomultimedia.com>) wrote: > You have to switch to the browse tool to see the contents of the browser. > Did you try that? > > > oh... duh... yes, that works :-) > > @ james... thanks for the encouragement, it seems wise at this stage to push > to move on to 8...this project will take a few months, so getting in now is a > good thing. "Use the drop down menu... dictionary" > > Silly thing was opening with the top of the dictionary underneath the menubar > (I have a ticket in for the team to fix that...) > > after running manually "set the loc of stack "revDictionary" to the > screenloc... I found the two menus: API | Guide > > Nice that the browser widget is independent and stays on the card and is not > stack wide. > > Does it automatically create the mobile version of itself when deployed on > iOS or Android? Or do we need to fork and instantiate the mobile browser > using the mobile methods? > > I'm on my way with 8... > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
