[L2Ork-dev] GSoC'21 Proposal feedback

Gabriela Bittencourt gabrielabittencourt00 at gmail.com
Fri Apr 9 09:04:09 EDT 2021


Hello (and sorry for the delay),

On 04/04/2021 03:47, Jonathan Wilkes wrote:
> On Sat, Apr 3, 2021 at 8:03 PM Albert Graef <aggraef at gmail.com> wrote:
>> Ok, makes perfect sense. I just made some further suggestions in the document which will hopefully clarify those items.
> Also-- the same for `[expr]`, `[expr~]`, and `[fexpr]`. These are
> boxes are where users tend to type a lot of complicated business.
> Seeing it pop back up as an option could be a timesaver.
Now I understand what you mean in this part. I've just proposed an 
approach to object arguments in my 'project proposal', if you can have a 
look, I would appreciate it :)

I've added some comments "ADDED 04/09" in the parts of the project that 
I've added today.


- Gabriela

>
> -Jonathan
>
>> On Sun, Apr 4, 2021 at 12:39 AM Gabriela Bittencourt <gabrielabittencourt00 at gmail.com> wrote:
>>> I'm really talking about those messages (Ctrl+2).
>>>
>>> This was a suggestion of Jonathan in a previous e-mail discussion:
>>>
>>> "
>>>
>>> A few other ideas:
>>>
>>> * dealing with object arguments and message box content. I love the way DevTools will remember entire commands, even across instances. So perhaps a way to add previously entered box content
>>>
>>> "
>>>
>>> The idea was to expand the autocomplete to the messages also. I thought about storing the created messages in cache and as a new message is created a suggestion based on the previous ones is offered: enter to accept and tab to go to cycle through options. Differently of the objects drop-down, for the messages I pictured an inline autocomplete (as terminal tools usually are). Tell me if it's clearer and I can rewrite the proposal.
>>>
>>> About the objects arguments I'm not sure what to do with it: show argument type ?
>>>
>>> Thanks,
>>>
>>> Gabriela
>>>
>>> On 03/04/2021 23:36, Albert Graef wrote:
>>>
>>> Hi Gabriela
>>>
>>> Thanks for the proposal, looks good to me! I corrected two typos in-place, and I'm not sure what to make of these two items for the main weeks (this isn't really clear from the context to me, maybe I'm missing something obvious?):
>>>
>>> Create a search index with the previously created messages;
>>>
>>> Implement an inline autocomplete for messages (no dropdown window);
>>>
>>>
>>> Are you really talking about Pd messages there (those little flags, Ctrl+2)? If not, can you please elaborate?
>>>
>>> Thanks,
>>> Albert
>>>
>>>
>>> On Sat, Apr 3, 2021 at 11:11 PM Gabriela Bittencourt <gabrielabittencourt00 at gmail.com> wrote:
>>>> Hello mentors,
>>>>
>>>>
>>>> I've just shared my proposal project "Improving workflow with
>>>> autocomplete feature" - I've tried to keep it short (1 page).
>>>>
>>>> Could you please review it and let me know if it's clear enough?
>>>>
>>>> Also, as I structured the project myself, with Jonathan's suggestions,
>>>> if you have any concerns about the approach for each task, I will be
>>>> happy to hear.
>>>>
>>>>
>>>> Thank you very much,
>>>>
>>>> Gabriela Bittencourt
>>>>
>>>> _______________________________________________
>>>> L2Ork-dev mailing list
>>>> L2Ork-dev at disis.music.vt.edu
>>>> https://disis.music.vt.edu/listinfo/l2ork-dev
>>>
>>>
>>> --
>>> Dr. Albert Gr"af
>>> Computer Music Research Group, JGU Mainz, Germany
>>> Email: aggraef at gmail.com, web: https://agraef.github.io/
>>>
>>> _______________________________________________
>>> L2Ork-dev mailing list
>>> L2Ork-dev at disis.music.vt.edu
>>> https://disis.music.vt.edu/listinfo/l2ork-dev
>>
>>
>> --
>> Dr. Albert Gr"af
>> Computer Music Research Group, JGU Mainz, Germany
>> Email: aggraef at gmail.com, web: https://agraef.github.io/
>> _______________________________________________
>> L2Ork-dev mailing list
>> L2Ork-dev at disis.music.vt.edu
>> https://disis.music.vt.edu/listinfo/l2ork-dev
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev


More information about the L2Ork-dev mailing list