Solid-ide (solside) is now on github


#21

Er, maybe. I haven’t fully investigated. Could well be something in my code that was erroneously targeted at the way NSS 4.x worked and should have been more general. Thanks for submitting an issue.


#22

So are you saying that I never should have been able to edit my home pages with Solid IDE? Not sure I understand the use of the word erroneously targeted, sounds like your saying that you added this feature by mistake.


#23

Given the current state of the specifications and servers, an app code developer is faced with trying to write code that matches a not-totally-fleshed out specification or writing to work with the current server. I always try to write to the spec and include the server specifics when I can. So all I am saying is that it may be that the new NSS has something broken with how it handles index.html in the root folder, or my code may not have been written to include all possibilities. The feature itself was not a mistake, the way I implemented may have been. I won’t know until I look further and I can’t look further right now because I am in the middle of a massive re-write of solid-file-client which will eventually bubble up to good things for Solid IDE.


#24

Great, thanks for the reply, there is always ```
curl --cookie “connect.sid=” --upload-file index.html https:///index.html


Or, ```
curl –cookie “connect.sid=<insert cookie value>” https:<your pod>.net/ -F data=”@/<your/file/index.html>”

#25

Yes, or

let fc = require('solid-file-client')
await fc.login()
fc.updateFile( URL, content, "text-turtle")

or (assuming solid-shell is installed)

sol upload targetURL sourceFile

#26

Great! Now I have to learn Solid-Shell also. Always on the cutting edge.


#27

That doesn’t work for me (I’m not using NSS by the way), but I may not understand - I don’t have an ‘edit button’, green or otherwise. I have ‘save edits’ (always greyed out) next to view.

I’m looking at the code which I think controls this but it is still mysterious to me:


#28

Yes, sorry, I am talking about the “save-edits” button. The code above says "if you are logged in and if you have Write permission for the resource you are examining, make the “save edits” button green and active, i.e. allow the resource to be edited and saved back to the server. So you have to first login (using Solid IDE options, not using the databrowser). Then go to a resource you have permission to edit and that button should be green. The problem @adventure is reporting is unrelated to that, it has to do with not being able to access the index.html of the root folder and AFAIK is unrelated to other resources. But I’d like to get to the bottom of your issue Mark, so keep hammering me with questions.


#29

Thanks Jeff, I think I can feel a mini-hack coming on! :wink:


#30

Sorry @jeffz


#31

Or you could try this little hack (works for me):

To enable editing change the following line to perms = { Read:true, Write:true, Control:true }


#32

Thanks, I will give it a shot when I get back to my office in a few minutes


#33

Thinking about it, the issue in my case is also logging in, but that may not affect you.


#34

I don’t think that @happybeing’s fix applies to @adventure’s problem. You two are talking about very different things. I investigated a bit on @adventure’s issue and it looks like the problem of not being able to edit the root index.html has to do with a change in how NSS responds to a GET request on the root folder - it now sends HTML instead of Turtle and since Solid-IDE expects Turtle, it fails. At least now we have something to work on.

Mike, I would encourage you to reframe “bs” as “the expected two steps forward and one step back of a project in its childhood” and “idiots!!!” as “dedicated and hard-working humans who are not perfect with the occasional idiot like @jeffz thrown in.”

And instead of thinking of yourself as an abused customer, think of yourself as a valuable contributor to the process who found a problem and reported it to people who could do something about it. That is not something to be frustrated about, it is a necessary part of the process. Thanks for your role in it.


#35

Ok, you make several good points, my temper gets the best of me sometimes and thanks to more level headed folks like yourself, I am able to see my mistakes more clearly, so I do apologize for my indiscretion, and removed the post.


#36

@happybeing I made the changes that you recommended however, Jeff was correct, it did not fix my problem.


#37

Frustration is understandable. I’m glad to see you back in the “we’re all in this together” spirit. The magnificent thing about this project is that its goal and its implementation depend on and promote collaboration and there’s a role for everyone.


#38

Ok, I have to take three steps forward to make up for that one for sure. This project has taught me some very valuable lessons, and I am humbled by it all.


#39

We all have much to learn and I’ve learned an enormous amount from hanging out in projects like this. Great outcome here, and incredibly well said Jeff, that was lovely to read, you are a bright star. I’m glad to be able to learn from you and Mike. As for ‘we all make mistakes’, really, even moi? :joy:

Back to the technical issue, we should have known it was the back end, life would be so much easier without the back end don’t you think? Hmm, if only there was a project to… :laughing:


#40

For some time I have relied upon Solid IDE and have wanted to customize it a bit, add a couple of features that I think would be helpful such as a help button, that would lead a person to how to videos, docs, pr’s, issues and things like that. i have also wanted to add some links to other resources. Discovering the Kitchen Sink feature was a great find because it broadens my horizons on the various uses and customizations I was previously unaware of. At any rate, @happybeing I agree that Jeff is a “Bright Star” and super talented individual, as is yourself and everyone else working on Solid!