kurl VS shared

[9] https://github.com/pyrustic/kurl

- ensures that more an app is recommended by different developers, as well as a chance to be in the promotion list often (until the user decides to install it).

The choice to put a Promoted button on which the user can click may seem naive. Implementing intrusive pop-ups can be recommended as a more pragmatic method. This choice to trust the altruistic curiosity of users was influenced by an observation (I have 0 statistics to show) I made here on Hackernews: there are always users who click on Newest (https://news.ycombinator.com/shownew) to bring up posts that might deserve attention, though these users are not affiliated with these posts.

I want Hubstore to make it easy to distribute and promote Python apps (built with Pyrustic Framework or not). This is still a beta version for early-adopters.

Under the hood:

- Hubstore is built with Pyrustic Framework [1]

- data storage is done with Shared [2]

- autocomplete is done with Suggestion [3]

- GUI-compatible multithreading is done with Threadom [4]

- Hubstore consumes Python Wheels

- Hubstore uses Github's Release Asset feature [5]

- Apps can be built and released with Backstage [6]

- the dark theme is based on Cyberpunk-Theme [7]

- all views implement Viewable [8]

- Hubstore uses Kurl [9] to fetch resources from api.github.com

I would like to know what you think [10] of this project.

[1] https://github.com/pyrustic/pyrustic

[2] https://github.com/pyrustic/shared

[3] https://github.com/pyrustic/suggestion

[4] https://github.com/pyrustic/threadom

[5] https://github.blog/2013-07-02-release-your-software/

[6] https://github.com/pyrustic/backstage

[7] https://github.com/pyrustic/cyberpunk-theme

[8] https://github.com/pyrustic/viewable

[9] https://github.com/pyrustic/kurl

[10] http://sl4.org/crocker.html

Hi HN !

Before discovering JSON, I worked on projects where I had to design relational databases [1] and write SQL queries. I understood the difference between a relational database and a file format, but couldn't resist the temptation to adopt JSON to store data locally.

Ever since I adopted JSON to store data locally, I wanted a class with an intuitive interface to play with JSON files. Eventually, the class evolved into a library.

I had to make a graphical SQL editor to test a GUI framework, so I created the LiteDao package (Lite Data Access object) which offers an intuitive interface to connect to a database with SQLite. The project worked as I wanted it to.

So, I had two different packages to play with data. I wanted to unify these two packages into a single class. But I failed to do so.

I came back to the challenge, and this time I had the idea of a single package with three classes with almost same intuitive interface that meet three needs: the need to expose a configuration file so that the user can modify values, the need to store collections and binary data without worrying about how they are actually saved, and the need to work with a relational database. These classes are respectively named Document, Dossier, and Database.

I managed to implement it in Python and added a command line interface [2] that allows different applications to exchange collections and binary data.

I would like to know what you think [3] of this project which is still in beta and which I already use in several other projects which are also in beta.

[1] https://www3.ntu.edu.sg/home/ehchua/programming/sql/Relation...

[2] https://github.com/pyrustic/shared#command-line-interface

[3] https://news.ycombinator.com/item?id=12886522 (Crocker's rules)

[2] https://github.com/pyrustic/shared

Hi HN !

A few days ago I wrote Shared [1] a library to store, expose, read and edit data collections. Data collections are stored on the hard drive in separate files. I needed a mechanism to know when the content of a data collection has changed, so only the updated data collection will be stored. Thus came to me the idea of writing Probed.

This is a work in progress, I will write some documentation and tests later. Tell me what you think [2].

[1] https://github.com/pyrustic/shared

[2] http://sl4.org/crocker.html