<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi Walter, Utkarsh is using the datastore class so that is what he is doing already. Tony <div class="moz-cite-prefix">On 05/18/2016 12:06 AM, Walter Bender wrote: </div> <blockquote cite="mid:CADf7C8tBeN1k7CkBOCXcPY6_eZ_NAjEtY+0ScB8TrU_DBjTGTw@mail.gmail.com" type="cite"> <div dir="ltr"> <div class="gmail_extra"> <div class="gmail_quote">On Tue, May 17, 2016 at 4:44 PM, Ütkarsh Tiwari <<a moz-do-not-send="true" href="mailto:iamutkarshtiwari@gmail.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:iamutkarshtiwari@gmail.com">iamutkarshtiwari@gmail.com</a></a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I need to overwrite(delete) the existing object with a new object in the Journal. </blockquote> <div> </div> <div>Can you explain your use case a bit more? Why is it not adequate to just modify the existing object? What is achieved by replacing it? </div> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Thanks, Utkarsh Tiwari <div class="HOEnZb"> <div class="h5"> On 5/18/16, Sam Parkinson <<a moz-do-not-send="true" href="mailto:sam.parkinson3@gmail.com"><a class="moz-txt-link-abbreviated" href="mailto:sam.parkinson3@gmail.com">sam.parkinson3@gmail.com</a></a>> wrote: > If you make an activity, all of the journal interaction is handled by > the Journal. Maybe that would help you in this instance? > > On Wed, May 18, 2016 at 5:02 AM, Ütkarsh Tiwari > <<a moz-do-not-send="true" href="mailto:iamutkarshtiwari@gmail.com">iamutkarshtiwari@gmail.com</a>> wrote: >> Hi, >> How can we overwrite(contents) a specific object in Journal? >> >> Thanks, >> Utkarsh >> >> On 5/18/16, Ütkarsh Tiwari <<a moz-do-not-send="true" href="mailto:iamutkarshtiwari@gmail.com"><a class="moz-txt-link-abbreviated" href="mailto:iamutkarshtiwari@gmail.com">iamutkarshtiwari@gmail.com</a></a>> wrote: >>> Hi Tony, >>> In case if the user chooses to overwrite the >>> contents(code) of the existing project(already saved in Journal), >>> would you like to overwrite that Journal object or create a new >>> object(overwritten- this might create duplicate names)? >>> >>> Thanks, >>> Utkarsh Tiwari >>> >>> On 5/17/16, Walter Bender <<a moz-do-not-send="true" href="mailto:walter.bender@gmail.com"><a class="moz-txt-link-abbreviated" href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a></a>> wrote: >>>> I believe it defaults to ~/Documents (outside of sugar-build). >>>> >>>> -walter >>>> >>>> On Tue, May 17, 2016 at 10:48 AM, Ütkarsh Tiwari >>>> <<a moz-do-not-send="true" href="mailto:iamutkarshtiwari@gmail.com">iamutkarshtiwari@gmail.com</a> >>>>> wrote: >>>> >>>>> Hi, >>>>> What is the location of the 'Journal/Documents' folder inside >>>>> sugar-build? >>>>> >>>>> Thanks, >>>>> Utkarsh Tiwari >>>>> >>>>> On 5/15/16, Tony Anderson <<a moz-do-not-send="true" href="mailto:tony_anderson@usa.net"><a class="moz-txt-link-abbreviated" href="mailto:tony_anderson@usa.net">tony_anderson@usa.net</a></a>> wrote: >>>>> > Hi, Utkarsh >>>>> > >>>>> > I gave this version a trial. I think the integration is >>>>> complete. The >>>>> > next problems are left over from Richa Sehgal's work from last >>>>> year. >>>>> > >>>>> > I wasn't able to look at the feature page - I think Bernie >>>>> Innocenti >>>>> > is >>>>> > working on the server and it is down for a while. >>>>> > >>>>> > What we are trying to do goes beyond the jsfiddle on the >>>>> internet. It >>>>> > provides a way to enter html or css or javascript and test the >>>>> outcome >>>>> > when the >>>>> > code is processed by the browser. What I would like is that the >>>>> user >>>>> > can >>>>> > create an html file using an editor and then show that file on >>>>> with >>>>> > the >>>>> > fiddler. >>>>> > >>>>> > So, if I open the fiddler and enter <h1>Hello World</h1> , then >>>>> 'run' >>>>> > will display that in the right side panel. (And that works). >>>>> Now I >>>>> > save >>>>> > the file giving it a >>>>> > project name. e.g. helloworld. This is saved in the Journal. >>>>> When you >>>>> > look at the Journal, there are two entries. One shows the >>>>> Browse icon >>>>> > and the other a text page icon. This is normal - one represents >>>>> the >>>>> > journal object for the browse activity and the other object has >>>>> the >>>>> > saved html: helloworld.html. >>>>> > >>>>> > You can copy the helloworld.html file to the Documents folder >>>>> (hover >>>>> > over the text icon and select copy to Documents). Using >>>>> Terminal, you >>>>> > will see the file in the Documents folder is named >>>>> > helloworld.html.zip. >>>>> > This is correct (it should be a zip file) but the name should be >>>>> > helloworld.zip. In the Terminal you will see the expanded file >>>>> is >>>>> > helloworld.html. >>>>> > >>>>> > There are two problems: >>>>> > >>>>> > 1. When the file is zipped, it should be in a 'project' >>>>> directory >>>>> > with the name of the project. So helloworld/helloworld.html. >>>>> When >>>>> > unzipped, there should be a helloworld directory in Documents >>>>> and in >>>>> > it >>>>> > should be the helloworld.html file. >>>>> > 2. The html file needs a <title>helloworld</title>. Browse >>>>> > apparently uses the whole file as the title when one is not >>>>> given. >>>>> > Note: >>>>> > the title appears as the name of the tab. >>>>> > >>>>> > Having saved helloworld with project name helloworld, I was >>>>> able to >>>>> > open >>>>> > it (but only when fiddler is enabled - which is probably ok). It >>>>> > displayed correctly. However, if I show source I get the source >>>>> html >>>>> > for >>>>> > Richa Sehgal's fiddler page not the source of the >>>>> helloworld.html. >>>>> > >>>>> > Using Terminal, I did a less on the text of helloworld.html. It >>>>> is one >>>>> > line (normal for html which doesn't recognize newlines). There >>>>> is a >>>>> > package called BeautifulSoup which is included in the Sugar >>>>> image (it >>>>> > is >>>>> > outdated - should be bs4 but no problem). Anyway, you can find >>>>> the >>>>> > BeautifulSoup documentation on line. What you can do is use the >>>>> > prettyprint feature to save the html file so that it is more >>>>> useful >>>>> > for >>>>> > editiing. >>>>> > >>>>> > Note: the reason for the zip file is that an html file can >>>>> refer to an >>>>> > img (<img src='some.png'>Some</img>). This is a relative url and >>>>> > refers >>>>> > to a file in the same directory as the html file. By zipping >>>>> the html >>>>> > and media files together, it will work correctly when uploaded >>>>> to the >>>>> > school server, for example. This also supports having a main >>>>> page with >>>>> > links to other html files in the same directory (<a >>>>> > href='page1.html'>Page 1</a>). >>>>> > >>>>> > This is great progress and now we have the opportunity to make >>>>> sure >>>>> > that >>>>> > the feature works in various use cases. >>>>> > >>>>> > Tony >>>>> > >>>>> > On 05/14/2016 10:08 PM, Ütkarsh Tiwari wrote: >>>>> >> Hi, >>>>> >> I have fixed the .xo file. Now on clicking the 'Run' will >>>>> open a >>>>> >> new tab with blank fiddle screen and will insert the user code >>>>> inside >>>>> >> the blank skeleton in index.html. I have attached the new .xo >>>>> below. >>>>> >> >>>>> >> Note- "web-console.html" file contains the html code of the >>>>> >> JS-fiddler >>>>> >> designed by Ms. Richa Sehgal. We need not touch it. User code >>>>> is >>>>> >> saved >>>>> >> in the index.html file. >>>>> >> >>>>> >> I have also created a feature page - >>>>> >> <a moz-do-not-send="true" href="https://wiki.sugarlabs.org/go/0.110/Feature_List/JS_Fiddler" rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="https://wiki.sugarlabs.org/go/0.110/Feature_List/JS_Fiddler">https://wiki.sugarlabs.org/go/0.110/Feature_List/JS_Fiddler</a></a> >>>>> >> >>>>> >> Thanks, >>>>> >> Utkarsh Tiwari >>>>> > >>>>> > >>>>> _______________________________________________ >>>>> Sugar-devel mailing list >>>>> <a moz-do-not-send="true" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> >>>>> <a moz-do-not-send="true" href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> >>>>> >>>> >>>> >>>> >>>> -- >>>> Walter Bender >>>> Sugar Labs >>>> <a moz-do-not-send="true" href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a> >>>> <<a moz-do-not-send="true" href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a>> >>>> >>> >> _______________________________________________ >> Sugar-devel mailing list >> <a moz-do-not-send="true" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> >> <a moz-do-not-send="true" href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > _______________________________________________ Sugar-devel mailing list <a moz-do-not-send="true" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a moz-do-not-send="true" href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </div> </div> </blockquote> </div> <div> </div> -- <div class="gmail_signature"> <div dir="ltr"> <div>Walter Bender Sugar Labs</div> <div><a moz-do-not-send="true" href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a> </div> </div> </div> </div> </div> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ Sugar-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </pre> </blockquote> </body> </html>