6 ms·

I'm really excited about the interactive widgets. I've been curious about the idea of creating a spreadsheet widget to provide excel-like functionality in Jypyt

by calebm 12y ago

I'm really excited about the interactive widgets. I've been curious about the idea of creating a spreadsheet widget to provide excel-like functionality in Jypyter.

jasongrout 12y ago
Cool! You can see some of the widgets people have been doing at https://github.com/ipython/ipython/wiki/widgets https://github.com/ipython/ipython/wiki/widgets. If you come up with something, let us know and add your widget there.
carreau 12y ago
You mean like that : https://www.youtube.com/watch?v=_JZFSFR6Yeo https://www.youtube.com/watch?v=_JZFSFR6Yeo ? (link to code in youtube description)
- calebm 12y ago
  Yes, something like this but more full-featured.
scoutoss 12y ago
You might also be interested in https://github.com/quantopian/qgrid https://github.com/quantopian/qgrid, which renders pandas DataFrames interactively with SlickGrid (https://github.com/mleibman/SlickGrid https://github.com/mleibman/SlickGrid)
brudgers 12y ago
The thing about Excel is there are many 50~80% use case implementations. But none with all 30 years of Microsoft's spreadsheet experience baked in. The long tail use cases are where Excel excels, and in spreadsheets there are a lot of snowflake use cases.
- baldfat 12y ago
  The biggest thing about "Excel" and spreadsheets is the work you do is not reproducible and it is the main reason why you should program all your work. What people do with macros and spreadsheets is very dangerous and unless it is documented it has too much human error capability.
  - brudgers 12y ago
    The business case for using Excel overwhelms engineering best practices up to somewhere around five or six sigmas. The big ball of mud software architecture is good enough to make money. Anyway explaining business logic to a technical programmer is also fraught with human error. TANSTAAFL.
    - bwanab 12y ago
      Not necessarily. There have been a number of disasters in the last few years caused by errors that have been directly attributed to spreadsheet usage. Many financial firms are reining in excel use by their business users. Prototyping a solution is fine, but for production use they are requiring an auditable solution that has proper source code control and can't be tweaked by the end user. Spreadsheets are great products but for production use they are really two edged swords.
      - brudgers 12y ago
        Sure, but that shift is happening under the same logic that leads businesses to run ERP applications on big iron mainframes even here in the 21st century. It's a matter of degree, but human error remains. The subprime clusterfuck wasn't based on using Excel.
- whyever 12y ago
  I don't really see why you need those advanced features. In my experience, as soon as I'm requiring non-basic features, I actually shouldn't be using spreadsheets.

by calebm 12y ago

I'm really excited about the interactive widgets. I've been curious about the idea of creating a spreadsheet widget to provide excel-like functionality in Jypyter.

jasongrout 12y ago

Cool! You can see some of the widgets people have been doing at https://github.com/ipython/ipython/wiki/widgets https://github.com/ipython/ipython/wiki/widgets. If you come up with something, let us know and add your widget there.

carreau 12y ago

You mean like that : https://www.youtube.com/watch?v=_JZFSFR6Yeo https://www.youtube.com/watch?v=_JZFSFR6Yeo ? (link to code in youtube description)

calebm 12y ago
Yes, something like this but more full-featured.

scoutoss 12y ago

You might also be interested in https://github.com/quantopian/qgrid https://github.com/quantopian/qgrid, which renders pandas DataFrames interactively with SlickGrid (https://github.com/mleibman/SlickGrid https://github.com/mleibman/SlickGrid)

brudgers 12y ago

The thing about Excel is there are many 50~80% use case implementations. But none with all 30 years of Microsoft's spreadsheet experience baked in. The long tail use cases are where Excel excels, and in spreadsheets there are a lot of snowflake use cases.

baldfat 12y ago
The biggest thing about "Excel" and spreadsheets is the work you do is not reproducible and it is the main reason why you should program all your work. What people do with macros and spreadsheets is very dangerous and unless it is documented it has too much human error capability.
- brudgers 12y ago
  The business case for using Excel overwhelms engineering best practices up to somewhere around five or six sigmas. The big ball of mud software architecture is good enough to make money. Anyway explaining business logic to a technical programmer is also fraught with human error. TANSTAAFL.
  - bwanab 12y ago
    Not necessarily. There have been a number of disasters in the last few years caused by errors that have been directly attributed to spreadsheet usage. Many financial firms are reining in excel use by their business users. Prototyping a solution is fine, but for production use they are requiring an auditable solution that has proper source code control and can't be tweaked by the end user. Spreadsheets are great products but for production use they are really two edged swords.
    - brudgers 12y ago
      Sure, but that shift is happening under the same logic that leads businesses to run ERP applications on big iron mainframes even here in the 21st century. It's a matter of degree, but human error remains. The subprime clusterfuck wasn't based on using Excel.
whyever 12y ago
I don't really see why you need those advanced features. In my experience, as soon as I'm requiring non-basic features, I actually shouldn't be using spreadsheets.