Piggydb V5.0 released

This release includes several bug fixes and minor improvements and is released as stable version.

The first step of V5.x development was to introduce Tag-Fragment, which was an attempt to upgrade the role of tags from a mere index to representation of important concepts in a database:

 

About these ads

4 Comments on “Piggydb V5.0 released”

  1. Jerome J. Slote says:

    Congratulations, Daisuke. Brilliant work. I’ll continue our discussion about tags and intermediate fragments at next opportunity.

    Regards — Jerome

  2. Jerome J. Slote says:

    Greetings Daisuke

    Sorry to be a little scarce here. I really did have a story to tell about intermediate fragments vs. tags, but Version 5 operates so seamlessly and effortlessly that I haven’t been thinking about it as much. It’s become the perfect system for the management of ideas and writing. I hope things are going splendidly for yourself and family as well.

    Here’s a technique for folks who use the Stylish extension to modify Piggydb’s display. You can hide and reveal the sidebar, creating extra horizontal space for fragments, with this user style:

    Name: Piggydb Hide Sidebar
    ———–
    @namespace url(http://www.w3.org/1999/xhtml);
    @-moz-document url-prefix(“http://localhost:8080/”) {

    td.sidebar {
    display: none !important;
    } }
    ————
    Simple as that under Piggydb’s layered architecture. Thanks always.

    Jerome

    • Hi Jerome,

      Nice to hear from you and thank you for your kind words and sharing the tip as always.

      As for the data model, I’m still thinking about it, but I have not reached a conclusion yet. So I’m going to focus on the usability side for the time being.

      As I tweeted yesterday, the next version 5.1 will be released soon. Looking forward to your feedback ;-)

      Best regards,
      Daisuke

  3. Just dropping in…

    I’m looking forward to see what you will bring with the next update. However, in the current state it just looks terrible to me. The picture above shows exactly what I dislike right now; there are now two layers of information, both with close to the same options and capabilities and therefor obscuring a clear use-scenario. Instead of bringing more ‘order’ to a large dataset it encourages dis-organization. The above picture really tells a story; there seems to be no clear distinction between tags and fragments anymore.

    I’m still hoping you will implement some features that will bring back some order and maintainability for the dataset, but quite frankly from where you are going, I have now idea or suggestions on how to go about it.

    Regards,
    Hans Peter.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 26 other followers