[dani2mobile]

Hi ...

I had a python script that uses 'import calendar' and
a small piece of code to add appointments

		
new_entry = db.add_appointment()

new_entry.set_time(now+last,now+last+hour)

new_entry.content=goal

new_entry.location='Location:Facebook'

new_entry.commit()

Everything is working well and fine as python script the generated appointments are getting logged in calender.

But after converting into sis ... and successfully installing it on my N73 device .. I find that the app runs and exits before syncing my appointments with calender

I have tried the following options as capabilities

sudo ensymble_python2.5-0.25.py py2sis --appname="Dani" --shortcaption="go4it." -caps="NetworkServices+LocalServices+ReadUserData+WriteUserData+Location" --caption="My Application"--version=1.2.3 --verbose /home/irayan/py2sis/myapp.py

Please guide me ...

[aya42]

Originally Posted by dani2mobile

...
caps="NetworkServices+LocalServices+ReadUserData+WriteUserData+Location"
...

Well, you should only need the ReadUserData and WriteUserData caps to read and write the calendar data respectively.

As I understand it, the only valid caps for a self-signed SIS are: NetworkServices, LocalServices, ReadUserData, WriteUserData, and UserEnvironment. It's possible that the inclusion of the 'Location' cap is causing ensymble to fail in some way.

There should be a clue when you install the SIS on the devices, as it should pop-up a warning listing the capabilities you have requested when installing a self-signed SIS.

Try removing the 'Location' cap, and see if that helps. If not, make sure you include the output from ensymble in any followup post.

The other possibility is that your script is trying to import another script which you have not included in the SIS file.

[jethro.fn]

To get a better picture of where your stand-alone application halts, you can enclose the script in an exception harness. You'll get an exception dump if the program fails for some reason.

Originally Posted by dani2mobile

sudo ensymble_python2.5-0.25.py ...

Not an issue here, but "sudo" is not needed. Ensymble does not require root capability on UNIX/Linux.

[dani2mobile]

Hi..Thanks aya42 for replying, I tried porting the script again, into sis using ONLY the following capabilities

C:\Python25>python ensymble_python2.5-0.25.py py2sis --appname="Dani" --shortcaption="go4it." -caps="Net
workServices+ReadUserData+WriteUserData" --caption="My Application"--version=1.2.3 --verbose myapp.py

The following is the output of the ensymble

ensymble_python2.5-0.25.py: warning: no application version given, using 1.0.0
ensymble_python2.5-0.25.py: warning: no UID given, using auto-generated test UID 0xe305818a
ensymble_python2.5-0.25.py: warning: no certificate given, using insecure built-in one

Input file(s)     synCHRONUSoff.py
Output SIS file   synCHRONUSoff_v1_0_0.sis
UID               0xe305818a
Application name  Dani
Version           1.0.0
Language(s)       EN
Icon              <default>
Short caption(s)  go4it.
Long caption(s)   My Application--version=1.2.3
Install drive     <any>
Text file(s)      <none>
Certificate       <default>
Private key       <default>
Capabilities      0x0 (NONE)
Vendor name(s)    Ensymble
Autostart         No

Still, I face the same issue ... "The python script" runs perfectly and makes appropriate entries into calender ... but the sis file after getting perfectly installed exists before making entries to calender

@jethro.fn ... Thanks for replying, I still need to implement your suggestion and check ...

[aya42]

Originally Posted by dani2mobile

...
Capabilities      0x0 (NONE)
...

There's the clue.

Originally Posted by dani2mobile

... -caps="NetworkServices+ReadUserData+WriteUserData" ...

And there's the problem. Change "-caps" to "--caps".

[dani2mobile]

Thanks aya42 and others ... I now, have my app running perfectly!!! ... I wud like to have more information over removing the warning [due to self signed py2sis conversion] during the app installation.