[IPython-dev] Editor widget and data persistence

[Brian Granger]

I agree with @takluyver that in this particular case a widget is
probably the wrong answer. I think that the `%%writefile` magic of the
upcoming text editor page is a much better solution...

Cheers,

Brian

On Wed, Oct 22, 2014 at 4:56 PM, Adam Hughes <hughesadam87 at gmail.com> wrote:
> If you have a notebook that calls the GUI, you can launch it in a second
> notebook just using the %run magic as well.  IE, if you had:
>
> mywidget.ipynb
>
> Then you can launch it in a separate notebook with:
>
> %run mywidget.ipynb
>
> On Wed, Oct 22, 2014 at 3:42 PM, Pablo Winant <pablo.winant at gmail.com>
> wrote:
>>
>> Thank you Thomas.
>>
>> On Wed, Oct 22, 2014 at 12:28 PM, Thomas Kluyver <takowl at gmail.com> wrote:
>>>
>>> Hi Pablo,
>>> IPython.html.nbextensions.> I wonder if it is possible to save the state
>>> of these widgets when saving the notebook
>>>
>>> Currently, no. We're working on ways to do that, but it turns out to be
>>> more complicated than it seems.
>>>
>>> > More specifically, I'd like to use the text editor widget to edit a
>>> > text file that comes with a notebook
>>>
>>> It's possible to do this with widgets, but I don't think it's the best
>>> fit for the problem. It sounds like what you want is the %%writefile cell
>>> magic. Just make a code cell containing the text you want, with %%writefile
>>> filename.txt at the top. When you run it, it will save that content to the
>>> file.
>>>
>>
>> Actually my usecase is trying to provide users with an easy interface to
>> edit the content of simple structure that is also serializable as a
>> JSON/YAML file. I would be happy if I could find way to store information
>> produced by the code in the notebook and then read it back. Maybe, there is
>> a way to edit cell of notebook metadata from the notebook itself ?
>>
>>
>>>
>>> We are also planning to put a text editor component inside the notebook
>>> server, but that's not quite ready yet.
>>>
>>> > the IPython widgets are becoming one of the very few alternatives for
>>> > python web-guis
>>>
>>> Yes, and this is a much larger scope than the widget architecture was
>>> really designed for. We're trying to work out how to handle this.
>>
>>
>> I can smell some big architectural work here... Good luck with that !
>>
>> Pablo
>>
>>
>>>
>>>
>>> Thanks,
>>> Thomas
>>>
>>> On 22 October 2014 07:58, Pablo Winant <pablo.winant at gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> The new widgets are absolutely wonderful !
>>>>
>>>> I wonder if it is possible to save the state of these widgets when
>>>> saving the notebook. More specifically, I'd like to use the text editor
>>>> widget to edit a text file that comes with a notebook. That would kill two
>>>> birds with one stone for me: avoid the need to ship a separate file with the
>>>> notebook (btw, is there already a canonical way to do that ?), and be able
>>>> to edit it from within the notebook. Are there plans in this direction ? Any
>>>> idea about how I could implement that ?
>>>>
>>>> A somewhat related question: the IPython widgets are becoming one of the
>>>> very few alternatives for python web-guis. Do you think it would be possible
>>>> to use it for a relatively simple application and hide the notebook from
>>>> user's sight so that it looks like an independent application ?
>>>>
>>>> Best,
>>>>
>>>> Pablo
>>>>
>>>> _______________________________________________
>>>> IPython-dev mailing list
>>>> IPython-dev at scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> IPython-dev mailing list
>>> IPython-dev at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>>
>>
>>
>> _______________________________________________
>> IPython-dev mailing list
>> IPython-dev at scipy.org
>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>
>
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>



-- 
Brian E. Granger
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger at calpoly.edu and ellisonbg at gmail.com