Hi, works well. I completed a task and it auto hide which is fine. I guess a red [ x ] to allow deleting a completed task would be nice too. Anyway nicely done Noel~!
Some apps suggest “default” pods which are generally; [user].solid.community, [user].solidtest.space, and [user].inrupt.net, but i think it’s more a convenience.
Typing the location is fine as our browsers often remember the form inputs second time round. (on this app that seems disabled - a security feature perhaps). Logging out and entering another Pod cleared the workspace, and returning to the first Pod recovered the workspace fine here as well.
Yeah, I still have to add a lot of features, that is one of them :D.
Actually I removed it on purpose (the solid-auth-client library already does that using the modal login). I don’t like the fact that some platforms are given more visibility. Although I can agree that it can be easier for users, so I’ll keep that in mind for the future to find a better approach.
I haven’t done anything special for that, it’s just that being a JS application I’m not using a “name” attribute for the form input. Maybe it’d be a good idea to have one so that it remembers previous inputs as you mention.
Great app, @NoelDeMartin, very nice work! I think starting with the Schema types, as you have is good - likely to be widely recognized. As you add more features, you’ll need to look at more specific ontologies likes calendars and events.
A key pattern with Solid-based RWW apps is that the WebID-Profile doc of an authenticated User Identity should inform said app about about Data Storage location. Here are some WebID-Profile doc relations that are currently associated with this pattern, via my WebID-Profile doc:
As far as I understand, as long as you login with a solid account (instead of using the offline mode), tasks will be stored on your pod, right? My understanding of “pod” is the solid server. For example, one account in solid.community.
This is something I don’t know about and I think it may be related with what @pheyvaer was talking about. I’ll look into it and if I’ve got some doubts I’ll let you know. Thanks for the links
Yes, this works fine. When creating a workspace, it shows my storage https://angelo-v.solid.community and then I can choose a name for it. I can then find the data at https://angelo-v.solid.community/<name>/
Can you elaborate what’s the benefit of doing that?
About the storage, I still have to read a couple of links that have been posted on this thread to learn what storages are. Once I know them, I’ll see how to approach your suggestion :).
Shouldn’t that be seen with the name already? Unless you have the same name in different servers (which I guess is common).
The problem I see with placing the link on the name as it’s implemented now, is that it is displayed on the navigation drawer at all times. And I’m not sure if I’d want to add a link in there just for this reason. Maybe what I can do is include it on a “settings” panel or others that I plan to include at some point. Basically I agree that this information should be accessible somewhere within the app, but I’m not sure if the navigation drawer is the most appropriate place.
Thanks for your feedback, I’ll think about it and let you know once I’ve added this :).
@NoelDeMartin great job on this app! If you’re still interested in exploring other ontologies, my team works with the Common Core Ontology. I know that we have some detailed task-related terms. If you’re interested in giving them a try, I think we could add some additional features to your app (like due dates etc). Let me know if you wanna give it a shot, we’re happy to help.
That’d be great! I’ve actually been working for a while in a dev branch adding new features, and finding ontologies is still one of the main pain points. I’ll add descriptions (already implemented) and due dates to the next version, and I wouldn’t mind changing the ontologies because there won’t be a 1.0 stable version yet.
