How It Works
SeedCodeComplete2.HowItWorks History
Hide minor edits - Show changes to output
Changed lines 1-2 from:
!! So with no relationship between the calendar and the events table, how exactly does this work?
to:
!! So with such a simple relationship between the calendar and the events table, how exactly does this work?
Changed lines 7-8 from:
-> '''1.''' Scripts find the relevant day/week/month records and loop through those, writing them to a global variable. While this sounds slow, it is crazy fast. More scripts then look at this variable and make a couple more variables out of it so it is easier for other scripts read: variables like $$sc_ArrayContent.
to:
-> '''1.''' When the calendar draws, scripts find the relevant day/week/month records and loop through those, writing them to a global variable. While this sounds slow, it is crazy fast; this is the kind of thing FileMaker is best at. More scripts then look at this variable and make a couple more variables out of it so it is easier for other scripts read: variables like $$sc_ArrayContent.
Changed line 13 from:
The idea here is that no matter how many "cells" we have to draw, the calendar only fetches data from FileMaker Server once, making this '''much''' faster than calendars based on multiple portals.
to:
The idea here is that no matter how many "cells" we have to draw, the calendar only fetches data from FileMaker Server once, making this '''much''' faster than calendars based on multiple portals or filtered portals.
Changed lines 7-10 from:
-> '''1.''' Scripts find the relevant day/week/month records and loop through those, writing them to a global variable. While this sounds slow, this is crazy fast. More scripts then look at this variable and make a couple more variables out of it so it is easier to read, variables like $$sc_ArrayContent.
-> '''2.''' The calendar layout shows portal rows from the CalendarRows table to draw the day/week/month grid.
-> '''2.''' The calendar layout shows portal rows from the CalendarRows table to draw the day/week/month grid.
to:
-> '''1.''' Scripts find the relevant day/week/month records and loop through those, writing them to a global variable. While this sounds slow, it is crazy fast. More scripts then look at this variable and make a couple more variables out of it so it is easier for other scripts read: variables like $$sc_ArrayContent.
-> '''2.''' The calendar layout then shows portal rows from the CalendarRows table to draw the day/week/month grid.
-> '''2.''' The calendar layout then shows portal rows from the CalendarRows table to draw the day/week/month grid.
Changed line 13 from:
The idea here is that no matter how many "cells" we have to draw, the calendar only fetches data from FileMaker Server once.
to:
The idea here is that no matter how many "cells" we have to draw, the calendar only fetches data from FileMaker Server once, making this '''much''' faster than calendars based on multiple portals.
Changed lines 7-12 from:
'''1.''' Scripts find the relevant day/week/month records and loop through those, writing them to a global variable. While this sounds slow, this is crazy fast. More scripts then look at this variable and make a couple more variables out of it so it is easier to read, variables like $$sc_ArrayContent.
'''2.''' The calendar layout shows portal rows from the CalendarRows table to draw the day/week/month grid.
'''3.''' Finally, calcs in the CalendarRows table look at our global variables for any events on that day and display the relevant content.
'''2.''' The calendar layout shows portal rows from the CalendarRows table to draw the day/week/month grid.
'''3.''' Finally, calcs in the CalendarRows table look at our global variables for any events on that day and display the relevant content.
to:
-> '''1.''' Scripts find the relevant day/week/month records and loop through those, writing them to a global variable. While this sounds slow, this is crazy fast. More scripts then look at this variable and make a couple more variables out of it so it is easier to read, variables like $$sc_ArrayContent.
-> '''2.''' The calendar layout shows portal rows from the CalendarRows table to draw the day/week/month grid.
-> '''3.''' Finally, calcs in the CalendarRows table look at our global variables for any events on that day and display the relevant content.
-> '''2.''' The calendar layout shows portal rows from the CalendarRows table to draw the day/week/month grid.
-> '''3.''' Finally, calcs in the CalendarRows table look at our global variables for any events on that day and display the relevant content.
Changed lines 5-6 from:
%center% %width=450px% http://www.seedcode.com/rootimages/stikipad/nextcal/howitworks.png
to:
%center% %width=500px% http://www.seedcode.com/rootimages/stikipad/nextcal/howitworks.png
Changed lines 5-6 from:
%center% %width=350px% http://www.seedcode.com/rootimages/stikipad/nextcal/howitworks.png
to:
%center% %width=450px% http://www.seedcode.com/rootimages/stikipad/nextcal/howitworks.png
Changed lines 5-6 from:
%center% http://www.seedcode.com/rootimages/stikipad/nextcal/howitworks.png
to:
%center% %width=350px% http://www.seedcode.com/rootimages/stikipad/nextcal/howitworks.png
Added lines 1-13:
!! So with no relationship between the calendar and the events table, how exactly does this work?
Check out the following chart...
%center% http://www.seedcode.com/rootimages/stikipad/nextcal/howitworks.png
'''1.''' Scripts find the relevant day/week/month records and loop through those, writing them to a global variable. While this sounds slow, this is crazy fast. More scripts then look at this variable and make a couple more variables out of it so it is easier to read, variables like $$sc_ArrayContent.
'''2.''' The calendar layout shows portal rows from the CalendarRows table to draw the day/week/month grid.
'''3.''' Finally, calcs in the CalendarRows table look at our global variables for any events on that day and display the relevant content.
The idea here is that no matter how many "cells" we have to draw, the calendar only fetches data from FileMaker Server once.
Check out the following chart...
%center% http://www.seedcode.com/rootimages/stikipad/nextcal/howitworks.png
'''1.''' Scripts find the relevant day/week/month records and loop through those, writing them to a global variable. While this sounds slow, this is crazy fast. More scripts then look at this variable and make a couple more variables out of it so it is easier to read, variables like $$sc_ArrayContent.
'''2.''' The calendar layout shows portal rows from the CalendarRows table to draw the day/week/month grid.
'''3.''' Finally, calcs in the CalendarRows table look at our global variables for any events on that day and display the relevant content.
The idea here is that no matter how many "cells" we have to draw, the calendar only fetches data from FileMaker Server once.
