Jim Coltz Calendar

[lvasic]

Fantastic! like usual. Excellent stuff.

[iRadiate]

Working on a fully dynamic - xbasic free build, just the Viewbox and SQL and templates, all management configurable client-side on the way in - just thought I'd share, their will be some JavaScript but at this time there is none. So if you have a wish list now the time to let me know if you are interested, decided to build my own as I can have unlimited view and developer can just add what they want - and no List control or Grid involved - flies along. Tiny 250k published UX. Slots are easily defined, per user, per entity etc. I'm also adding to my Hybrid User Management Console. - nothing but Vb's.

I remember going to see Cat Stevens at a concert and he said he loved the Beatles music but he struggled to play it - so he wrote his own songs - nothing to learn.. Sounds good to me,
Pete

https://www.screencast.com/t/7gEoF8YECJ

ps. I loved Jim's Calendar and him, wonderful man and product, but need Mobile interaction - good work Jim, thanks, served me well.

Pete

Very nice Pete ... as always

[peteconway]

Thanks - Pete

[peteconway]

Having fun
https://www.screencast.com/t/Z73vft6Fw

[peteconway]

Really fast..
https://www.screencast.com/t/Z73vft6Fw

[peteconway]

If you wan't xbasic to interpret a state variable as something other than a char (C) type and another then try this.

debug(1)
function setArgumentValueAsC as c (e as p)
dim argumentName as c = e._state.argumentName
dim argumentValue as N = convert_type(e._state.argumentValue,"C")
e.arguments.set(argumentName,argumentValue)
end function
function setArgumentValueAsN as c (e as p)
dim argumentName as c = e._state.argumentName
dim argumentValue as N = convert_type(e._state.argumentValue,"N")
e.arguments.set(argumentName,argumentValue)
end function
function setArgumentValueAsL as c (e as p)
debug(1)
dim argumentNameL as c = e._state.argumentName
dim argumentValue as L = convert_type(e._state.argumentValue,"L")
e.arguments.set(argumentName,argumentValue)
end function
function setArgumentValueAsD as c (e as p)
debug(1)
dim argumentName as c = e._state.argumentName
dim argumentValue as D = convert_type(e._state.argumentValue,"D")
e.arguments.set(argumentName,argumentValue)
end function
function setArgumentValueAsT as c (e as p)
debug(1)
dim argumentName as c = e._state.argumentName
dim argumentValue as T = convert_type(e._state.argumentValue,"T")
e.arguments.set(argumentName,argumentValue)
end function

or dynmic
function setArgumentValueAsD as c (e as p)
debug(1)
dim argumentName as c = e._state.argumentName
dim argumentValue as e._state.typeValue = convert_type(e._state.argumentValue, e._state.typeValue)
e.arguments.set(argumentName,argumentValue)
end function

where typeValue = C or N or L or D or T

etc.

Pete

[CharlesParker]

thanks pete, are you saying you found a work around to jims calendar or are you commenting in another context? Seems like it's the way AA is setting the state vars that is now causing the issues

[peteconway]

I just recall somewhere - someone pointed to the change in state vars - maybe be the issue, If it is - this could be a remedy. I'm writing my own calendar control in the Viewbox, I'm no longer actively using Jims.

Cheers
Pete


correction on the dynamic set argument

client-side

{dialog.object}.stateInfo['argumentName'] = 'Argument name to set' ;
{dialog.object}.stateInfo['argumentValue'] = 'Value of the Argument' ;
{dialog.object}.stateInfo['argumentType'] = 'N' // C or N or L or D or T etc.

{dialog.object}.runAction('setArgumentValue'); calls the function.


server-side

function setArgumentValue as c (e as p)
debug(1)
dim argumentName as c = e._state.argumentName
dim argumentValue as e._state.argumentType = convert_type(e._state.argumentValue, e._state.argumentType)
e.arguments.set(argumentName,argumentValue)
end function

[Jim Coltz]

For those interested the fix for the deletes from the UX in my calendar follows:

You will need to edit your jqcal_datafeed.a5w page to look like this:

<%a5
'this page is used to handle the data requests from the calendar
'all vars not dimmed on this page passed in from calendar
''updated 10/27/2022 to fix issue with AA no longer putting state variables where they belong.
if eval_valid("request.variables") then 'look for the request object from the POST
    dim r as p = request
    '_debug(1)
    if variable_exists("r.Variables._state.table")= .f. then
        if variable_exists("r.Variables._stateInfoJSON")then
            r.Variables._state = json_parse(r.Variables._stateInfoJson)
        end if
    end if
    ?jqcal_response(r)
else
    ?"Error, request variable not available"
end if
%>​

Note that the latest version of AA 8368_5659, which is what this fix is based on, adds a <!DOCTYPE html> to the top of the page when you open it in the editor (go figure). This needs to be removed for it work.
The added code is checking for the r.Variables._state.table variable that used to be there before AA decided to mess up the handling of state variables when using a url with their ajax callback or if using jQuery's ajax callback (which is what I used in my calendar code). If the variable is missing we then look for the new r.Variables._stateInfoJson variable and if we find it we parse it back into the r.Variables._state variable where it belongs. I tested this in the base 4.541 Jqcalendar app as well as in my own application and this seems to have fixed the problem.

Again, just make sure you remove any extra stuff that AA wants to automatically insert into your page. And don't forget to publish the edited page.

[peteconway]

Hi Jim - thanks that's awesome - I'm going to keep working on my viewbox build as it suits tablet and mobile controls in AA - I decided not to go beyond build 8099 as I don't really need anything else.
Pete

[CharlesParker]

I knew Jim would come through because well he's basically awesome...anyways - Pete, definitely keep on working on what your doing, seems like your on the right path. I am sure AA made code changes in the best interest of their product I don't fault them for it - in fact I find it pretty sweet that Jim was able to dive in and correct it so that what he built can still work effectively! Good job Jim!

[peteconway]

Cheers

[iRadiate]

The fix doesn't seem to work for me and causes a fault when loading the calendar data:

JQCalDatafeed.jpg


I did remove the <!DOCTYPE html> as suggested. I am on build 8245-5650 not build 8368-5659 which Jim is using. Is the fix build specific?

Thanks

[Jim Coltz]

The error indicates that something "non-whitespace character" is being returned by the jqcal_datafeed.a5w page. If you remove my new code does the error go away? This shouldn't be build specific, shouldn't being the key word. I've tested this in build 8000, which is what I was sticking with as that build did not have the problem.

If you capture what is returned in the POST command (using debug tools in the browser) you can run that through one of the online JSON validators and see where the issue is. In particular, look for something at the end, which in your case, from the screen shot of the message, is an extra ? mark. Check your page for the extra character

[iRadiate]

Ah, my fault ... I had a '?' at the end of the code. Working now, thanks Jim!