Updates for Pier - Check if I have problems where these aren't Improve Pier ToDo and ToDo.

1. Add a wikipedia page - link from the seaside page
2. Research https://github.com/seasidest/seaside/wiki - Make sure things are up-to-date. Any recent changes to Margritte?
3. Why do PRCodeblocks not work in Pier as I assume? These look like:

[[[eval=true
PRStructure withAllSubclasses size printString
]]]

New features to add to Pier:

• Update the automated tasks to have better error handling
• for a blog, is it possible to list all unpublished child posts? - a report of Updates which have nil publish dates (a view may be more effective for this).
• Add DB persistence for truly huge wiki (and a way to test something like that)
• Chatbot:
  • http://pillarhub.pharocloud.com/hub/mikefilonov/ajaxupdateseaside
  • http://onsmalltalk.com/ajax-how-to-build-cascading-dialogs-in-seaside
  • Pier may be able to use willow for Ajax
• It may be useful to have an "unscheduled" category of the ToDo list, such as for haircuts and eye appt that require a call.

Improve the Workout App (and Weight Lifting):

• Check user input
• Update the documentation for this
• Links related:
  • Refactoring date and time - in examples replace crtab with cr; tab
  • Threads on Dates
  • Search for Comparing Dates in Pharo
• See if location information can help
• How should this react when an exercise outside the recommended exercises is done?
  • Current seems to remove the last recommended exercise - Seems smarter to insert the last sets of that exercise before the current recommendation
  • If you are just repeating the last exercise, should it stick with that, or depend on the number of sets?
• For mobile use at a gym with poor connection, it is beneficial to display only part of the total workout log

Pier Todo Usability Improvements:

• somehow I was able to make it un-scrollable by adding libraries
• Use the custom seaside debugger, join the mailing list
• new Seaside - Material Design Lite
• can it be changed into one of these - like this hosting (this may help, or this)
• improve search
• add Https for Pier
• Improve instructions on PierToDo
• daylight savings time - It really depends on the location of the server. May want to create a task so every Saturday night the scheduled tasks are re-created
• Display the completed tasks in batches - see Pier ToDo View
• Finish Mobile-view-of-pier
• check if better CSS can be made - minimize space
• When clicking on open in the changes for a complete task, it reports: Unable to open 'Complete' in the current context.
• Can tasks be shared better between different users?
• Ajax-ify - Seaside Tutorial, or compare it to a Zinc tutorial
• Is there a Pier bug tracker similar to https://pharo.fogbugz.com/?
• can I add a MindMap
• Check error handling - would this work better: [ 'http://cmidashboard:8080/' asUrl retrieveContents ] on: ZnHttpUnsuccessful , ZnMissingHost, ZnUnexpectedContentType, NameLookupFailure do: [ :ex | ex inspect ].

Need to post about:

• Update the broken link report so everything under a page can be searched (ie documentation)
• When creating a new task, the time should be midnight (add the ToDo time change)
• clicking Complete should have more feedback, like the button graying out or the item disappearing - maybe there's a JS button that would be better
• create a contact app - keep track of google searches, FB pictures, keeping in contact
• improve security for user generated content
• Update comparing dates to using asDate yyyymmdd = Date today (adjust for timeshift) yyyymmdd - minimize the insanity
• Usability:
  • Extend the timeout to at least 25 minutes - Updated under WALastAccessExpiryPolicy - found the entry under config/Pier -> Expiry Policy - See Seaside Timeout also
• Seaside logging (experimental)
• Try ChartJS for seaside

General Pier Improvements

• Pier runs on http, find how https could be used
• Pier size - problems with larger wikis (image persistency limit around 10k pages)
• Exporting the wiki to files - create a special visitor?
• Possible RSS replacement for Pier
• try storing in a database - maybe Mongodb (a warning), but checking objects may help
• improve the editor - maybe use quill (description)
• external web browser - can this work like a web scraper (a good one)
• add a proof reader
• comments - could require a quiz

Why Pier - It is important to own your content. The big problem with most information storage things (wiki, shared drive, sharepoint, oneNote) is that information isn't very good, it needs a refactoring tool:

• Refactor a wiki - Swiki Notes, what would a wiki refactoring browser look like?

It would be cool to offer a button, [Refactor] which would:

• Create links based on page titles, or contents
• Rename this page if many links to it have different text
• move text to other pages, or add text from other pages to this page
• Break up this page into several pages and create intellegent links between them

The button would need to allow one to preview the changes and accept them if they are suitable.

• Wordpress used for email attacks - need to prevent this from being possible with Pier

Long-term goals:

• work with web assembly

Report: