One save is enough as I previously explained.
One save is enough as I previously explained.
Principal developer of Lianja, Recital and other products
Follow me on:
Twitter: http://twitter.com/lianjaInc
Facebook: http://www.facebook.com/LianjaInc
LinkedIn: http://www.linkedin.com/in/barrymavin
You edit the page not the section. It's full page edit. So you just issue the edit on a page using showDocument()
Principal developer of Lianja, Recital and other products
Follow me on:
Twitter: http://twitter.com/lianjaInc
Facebook: http://www.facebook.com/LianjaInc
LinkedIn: http://www.linkedin.com/in/barrymavin
I have made some changes in Beta11 that should resolve this. Try that later today and let me know.
I am assuming you resolved your issue with the app.init() delegate creating public variables?
Principal developer of Lianja, Recital and other products
Follow me on:
Twitter: http://twitter.com/lianjaInc
Facebook: http://www.facebook.com/LianjaInc
LinkedIn: http://www.linkedin.com/in/barrymavin
The "Full page edit App" included as an example shows this in operation. It is working fine. I suspect this issue is fixed in the next v1.1beta11 build. When I release betas they are a snapshot of development at that point. This is close to release so I need to make sure I have fixed this issue that you are experiencing calling delegates when operations are in progress. I have taken care of this scenario now.
Principal developer of Lianja, Recital and other products
Follow me on:
Twitter: http://twitter.com/lianjaInc
Facebook: http://www.facebook.com/LianjaInc
LinkedIn: http://www.linkedin.com/in/barrymavin
Hi Barry
Yes, the variables going out of scope works great now - thank you. INIT(), LOAD() and READY() are now all procs in a custom library.
INIT() defines the PUBLIC variables
LOAD() opens the database and tables
READY() sets the public variables to their values, read from the tables or hard coded
Not quite sure what you meant by "some legacy delegates". All our delegates call either procs in custom libraries or call the prgs created automatically by Lianja. Do we need to do anything else?
We are going to spread the sections over more pages as the pages have got too big.
Thanks for the heads up about Page edit.
I guess we should be issuing showdocument("page:PageName?action=editmode")
and then
showdocument("page:PageName?action=save").
Will try Beta 11 & report back.
Thanks for your prompt reply - much appreciated.
Cheers
SpringBox
Last edited by SpringBox; 2014-04-08 at 07:36.
Hi Barry
Have tried the full page edit in Beta 10 - edit now works great, but same issue with the save performance. In this app, we don't "save" from the UI, we always call "save" in code - normally when the user switches pages.
As soon as Beta 11 is up, will try that & let you know.
Thanks
SpringBox
Yes v1.1Beta11 is currently on its way.
FYI the App delegates was the only place where we were creating separate files -- which was wrong -- and it caused issues in the web/mobile so I changed it.
These now work in web/mobile when you have JavaScript App delegates. So the delegate handling is now consistent across App, Pages, Sections and FormItems. Thats why it was changed.
Principal developer of Lianja, Recital and other products
Follow me on:
Twitter: http://twitter.com/lianjaInc
Facebook: http://www.facebook.com/LianjaInc
LinkedIn: http://www.linkedin.com/in/barrymavin
Hi Barry
Beta 11 - what a difference !! Fast, slick & just as it should be - thank you
The Page edits / saves work perfectly & the whole app is much faster.
Cheers
SpringBox
Thats good. Close to release now.
Principal developer of Lianja, Recital and other products
Follow me on:
Twitter: http://twitter.com/lianjaInc
Facebook: http://www.facebook.com/LianjaInc
LinkedIn: http://www.linkedin.com/in/barrymavin
Bookmarks