[Nafetz]

Hi,

I'm using Eclipse with Aptana Plugin and Emulator with VirtualBox on my Windows 7 machine.
I would really like to use my notebook with Lubuntu for developing now and then. But my Linux knowledge is too low, to get the HP SDK installed completely (don't know which version of VirtualBox should be installed and from which sources).

As I read some of you are using common text editors for developing apps. Do you have comfortable ways to debug your code out of the text editors? Or are you using the emulator with VirtualBox, too?

Best regards,

Stefan

[Grabber5.0]

Can you clarify what you mean by "debug your code" ? It sounds like you mean interactively. I haven't done any interactive debugging outside of what bits of Enyo work in Chrome debugger. For everything else, it's log statements in the emulator or on-device.

[MAMISHO]

If you want to debug on webOs emulator you can try this Beckism.com: Remotely debugging WebOS apps with weinre. It was really easy at first for me. I tested on MacOs Successefully. But Lastly is not working for me.

[Nafetz]

Can you clarify what you mean by "debug your code" ?

I was hoping to have a possibility to check values of my variables without having to enter dozens of Mojo.Log.info into my code. Breakpoints would be fantastic :sigh:

I haven't done any interactive debugging outside of what bits of Enyo work in Chrome debugger

Using chrome is a good idea. I watched https://youtu.be/yvpT9cz06sA again and had to find out that there isn't a palm-inspector any more.
Besides I had to use

ssh -p 5522 -L 5581:localhost:8080 -oKexAlgorithms=+diffie-hellman-group1-sha1 root@localhost

instead of

ssh -p 5522 -L 5581:localhost:8080 root@localhost

and finally calling http://localhost:5581/Apps/ in Chrome led to an error which I could solve with the help of maemo-Forum
But there are still many errors so the app looks very different than on the emulator. And it seems like apps with separate sqlite databases don't work at all.

I hate giving up, but after several hours of fighting to make this work it seems like frustration is winning :-(

When frustration has gone I might give Ares Debugger another try, but I did not understand how this is working exactly the last time.

[Herrie]

I was hoping to have a possibility to check values of my variables without having to enter dozens of Mojo.Log.info into my code. Breakpoints would be fantastic :sigh:


Using chrome is a good idea. I watched again and had to find out that there isn't a palm-inspector any more.
Besides I had to use
[CODE]ssh -p 5522 -L 5581:localhost:8080 -oKexAlgorithms=+diffie-hellman-group1-sha1 root@localhost
instead of
[CODE]ssh -p 5522 -L 5581:localhost:8080 root@localhost
and finally calling http://localhost:5581/Apps/ in Chrome led to an error which I could solve with the help of maemo-Forum
But there are still many errors so the app looks very different than on the emulator. And it seems like apps with separate sqlite databases don't work at all.

I hate giving up, but after several hours of fighting to make this work it seems like frustration is winning :-(

When frustration has gone I might give Ares Debugger another try, but I did not understand how this is working exactly the last time.

Some of the webkit specific stuff (border image related) from Enyo 1.0 got properly fixed in Chrome 51+ and breaks the look of the apps. You would have to update your Enyo 1.0 framework & app so it keeps displaying properly. We recently had to do this in LuneOS. I guess if you're using Mojo it might be the same problem. See https://github.com/webOS-ports/enyo-...4331745a4cf885 for how we fixed it in LuneOS for newer Chrome/Chromium versions.


-- Sent from my TouchPad using Communities

[Nafetz]

Hi,

thanks for all help. After another (useless) hours of researching I found several hints that I might be much too late for debugging in Mojo.
Is it really true that all debugging features that can be seen in the Youtube video are already gone with the realease of webOS 2 in 2011?
I did some research to prove this: In Frank Zammettis Book "Practical Palm Pre webOS projects" are some screenshots of debugging configurations with Eclipse. Today I had a look into the file Eclipse\plugins\com.palm.pdt.debug.ui_2.0.0.201106022334\plugin.xml (installed in June 2011) and found out that all debugging commands are commented out.
Even in the SDK the call of palm-emulator --help offers no -debug-option any more. So maybe even the command-line debugging is impossible.

I'm giving up and do not waist any minute longer to find a way to debug my apps. Instead I will continue to run them a hundred times until I have found all bugs...
As long as my devices are still running I will be "happy" this way

[MAMISHO]

Hello. Today I had a little bit of time to test some features of LuneTube And I had to setup my develop environment again. I admit, http://beckism.com/2011/04/remote-debug-webos/ is not updated. So I going to give you the steps that I followed to setup weinre and you'll can debugging apps on desktop Web browser like a Chrome/safari.

At first you need to install NodeJS. I got v6.9.1
Then install weinre from npm repository.
sudo npm -g install weinre

After that, you should to add the script in your index or debug.html . It must seems to this.

<!DOCTYPE html>
<html>
	<head>
		<script src="http://localhost:8080/target/target-script-min.jsjsjs&$quot$;&$gt$;&$lt$;/$script$&$gt$;
..
..

Then in a console type this.

weinre --boundHost -all-

the in your browser go to

http://localhost:8080
http://localhost:8080/client/#anonymous

By default weinre listen to in localhost:8080, but if you want to debug from webOS's emulator you should be sure that weinre is accessible from external target. In any mobile device or computer try to acces to server weinre, for example, in my case weinre is running in 192.168.1.45:8080 (Localhost:8080) if you see the weinre page, run your app in emulator and you will see the app on chrome console. Its helpfully because you will be able to see all objects like PalmSystem, deviceInfo and of course your variables with console.log(enyo.$.app.$.stuff);

Remember, the script that must be first tag after open <head>

<script src="http://<id where weinre is runing>:8080/target/target-script-min.jsjsjs &$quot$; &$gt$; &$lt$; / $script$&$gt$;

[Nafetz]

Thank you very much for your help.
I believe it is too hard for me. I have problems to understand all commands and returned messages in Lubuntu...
I think I have installed NodeJS and I think I have installed weinre but I get the message that there isn't a node file or folder in /usr/bin/env. That's correct because /usr/bin/env is a file on my system. No chance to have a file or folder inside of it.

After that, you should to add the script in your index or debug.html

I can have a debug.html file? In Mojo or is this Enyo?

<script src="http://localhost:8080/target/target-script-min.j.s

And where do I find target and what is "target-min-script.j.s"?

But before trying to answer a lot of questions that I have: Will I have the chance at all to debug Mojo-Apps with external sqlite-databases in it?
I already had the command "ssh -p 5522 -L 5581:localhost:8080 root@localhost" that is noted on Beckism.com but ended in many of my apps not running in Chrome the way I tried some postings above. So I fear that could happen again - after spending a lot of time trying to understand this

Maybe it's better for me giving up and using command-line debugging? (I tested it meanwhile like shown in the Youtube video - not very comfortable but at least it really worked)

(sorry for being so difficult...)

[MAMISHO]

Hi and so sorry to reply late. (I was on holidays).

Firstly, the tutorial is to debug Enyo APPS and I only tested on Enyo but I imagine That it's possible to test Mojo APPS because "target-script-min. j s " is served from weinre and connect Java or NodeJS to web Browser. In my case It was not necessary run ssh -p 5522 -L 5581:localhost:8080 root@localhost.

Can you access to localhost:8080 ?.

Remember, if you run app from your device you should to change "localhost:8080" by your "<ip where weinre is running:8080/target......>"

The command to test on command lines Its here. I Used to use palm-log to see the results from console.log but you can get more complex commands.

Commands showed on video

https://es.slideshare.net/fpatton/le...g-palm-dev-day

Tips and information about system params. (PalmSystem used to be usefull )

webappmanager: PalmSystem Class Reference

How to rotate the emulator? [Archive] - webOS Nation Forums

[Nafetz]

Hi MAMISHO,

thank you very much for your patience and help. I really appreciate this.
Sorry, I didn't have had time the last weeks for further experiments and this might continue some weeks.
But I will give it another try next year