[allura:tickets] #8196 Save content before form submission

[Dave Brondsema]

- **status**: review --> in-progress
- **Comment**:

* invalidInputName could still use a comment explaining that it is to recognize 
antispam random names
* might as well remove the `autosave: true` from simplemde config if its not 
doing anything
* on a nested reply:
* to use a saved value, you have to click the "reply" button again.  So its 
not obvious immediately that your content has been saved (under that particular 
post), but not sure if we want to automatically expand it
* When you do start to restore a reply, you have to click into the editor 
for the text to show up.  Bug report 
https://github.com/sparksuite/simplemde-markdown-editor/issues/344 has a 
workaround, also mixed info there about whether an upgrade would fix it.
* the saved value doesn't get cleared after a successful submit



---

** [tickets:#8196] Save content before form submission**

**Status:** in-progress
**Milestone:** unreleased
**Created:** Wed Mar 14, 2018 06:28 PM UTC by Kenton Taylor
**Last Updated:** Fri Mar 23, 2018 07:12 PM UTC
**Owner:** Kenton Taylor


It would be helpful to save form content before submitting, in case the 
Antispam spinner/honeypot rejects it, or you get logged out. And obvious 
restore the content when viewing the form again.

Use localStorage? Clear it after a successful submit? And/or after an hour? 
Also need to deal with spinner field names properly.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed 
to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.

Re: [GSoC] To start contributing to Apache Allura

[Deshani Geethika]

Hi Dave,

Thank you for your valuable feedback. I've updated the proposal accordingly
and uploaded the final version

Regards!

On Tue, Mar 27, 2018 at 3:40 AM, Dave Brondsema  wrote:

> Comments inline:
>
> On 3/26/18 9:04 AM, Deshani Geethika wrote:
> > Hi All,
> >
> > I have few questions to be clarified about Personal Dashboard.
> >
> > Currently, when a user is logged in, neighborhoods are shown in the
> landing
> > page. We have few options here.
> >
> >1. Replace that Neighborhood page with the Personal Dashboard page.
> Then
> >we can give a link for Neighborhood page (Like the link for “Account”)
> >2. Neighborhood page will remain as it is and provide a link for
> >“Dashboard”. (Like the link for “Account”)
> >3. Merge these two pages. That means include neighborhoods in Personal
> >Dashboard
> >
>
> Yeah the current landing page with neighborhoods is not super great right
> now
> anyway.  Tickets 7308 and 2601 are related to that and maybe could be a
> stretch
> goal if your proposal were accepted and there was extra time.
>
> Anyway, for this.  I think separate pages would good.  One idea would be
> to show
> the personal dashboard if logged in, and the neighborhood page if not
> logged in.
>  Maybe have separate URLs like /dashboard and /index so you can still
> access
> both when logged in and "/" would redirect.
>
> >
> > According to the project description
> > , when
> > implementing the Personal Dashboard we can use a pluggable structure as
> in
> > User Profile. Therefore, I have included the personal_dashboard directory
> > in Allura/allura/ext/personal_dashboard path. Furthermore, the whole
> folder
> > and file structure can be depicted as below.
> >
> >
> >
> > Is it alright to reside the personal_dashboard directory in above path or
> > else do we have any other better option? Also, please let me know whether
> > this file and folder structure is alright.
>
> Yes, modeling things after the user profile pluggable structure is good.
> This
> path is a good one.
>
>
> >
> > Moreover, I have included the whole design in my GSoC proposal and I have
> > uploaded my drafted GSoC proposal to Apache Software Foundations via
> > official GSoC site . Let me know
> any
> > suggestions for the design and also for the proposal. Please find the
> link
> > for the proposal below.
> >
> > Proposal :
> >
> > https://docs.google.com/document/d/1clWKSJ8-
> ektpVaEgiJyoM34ievwkyCnD4uORMCT0eM8/edit?usp=sharing
> >
>
> I've made just one minor suggestion on the proposal so far.  Overall it is
> pretty good.  The most important things are: showing a detailed plan,
> breaking
> it down into small steps in the timeline, and being able to fully commit
> to all
> the time during the summer.  Those are covered pretty well.  If you do
> have any
> exams or vacation time, please include that in your commitment section.
>
> I'll add more comments if I think of more constructive feedback.
>
>
> > Regards!
> >
> > On Fri, Mar 23, 2018 at 10:07 PM, Deshani Geethika <
> > deshanigeeth...@gmail.com> wrote:
> >
> >> Hi Dave,
> >>
> >> I have drafted the GSoC proposal and would like to get feedback from
> you.
> >>
> >> Please review it from here:​
> >>  GSoC Proposal
> >>  ektpVaEgiJyoM34ievwkyCnD4uORMCT0eM8/edit?usp=drive_web>
> >> ​
> >> Regards!
> >>
> >> On Thu, Mar 22, 2018 at 9:14 PM, Dave Brondsema 
> >> wrote:
> >>
> >>> I've commented on the merge request.
> >>>
> >>> The personal dashboard project would be a great.
> >>> https://community.apache.org/gsoc.html has some information about what
> >>> makes a
> >>> good application.  I would recommend you write up a draft of your
> >>> proposal ideas
> >>> and share it either here on the Allura dev mailing list for public
> >>> feedback, or
> >>> to me privately if you prefer.  Getting feedback on your proposal is
> >>> allowed and
> >>> helpful.
> >>>
> >>>
> >>> On 3/21/18 2:02 PM, Deshani Geethika wrote:
>  Hi Dave,
> 
>  Thank you for reviewing my merge request :) I’ve refracted the code
> and
>  added the test coverage as described. Please review it and let me know
> >>> any
>  suggestions. Merge request can be found in [1]
> 
>  Meanwhile, I would like to start working on a GSoC project as I’ve got
> >>> some
>  decent exposure to Allura code-base now. When going through the
> projects
>  list, I’ve found out the project *[COMDEV-254] Allura - personal
> >>> dashboard*
>  [2] fits my interests.
> 
>  But, if there is any high prioritized project other than this, I would
>  equally interested in accepting it as well. I’m looking forward to
> know
>  further information in order to apply for Allura GSoC projects.
> 
>  [1] https://forge-allura.apache.org/p/allura/git/merge-requests/248/