We’re indeed pulled in every direction these days, with financial instability, the non-existent career track, and environmental upheaval. And all the pressures on families and relationships. The tyranny of the urgent. Piggydb is a calling, a living creation, a statement of personal excellence. I know you’re enhancing it even when you take a break from it, and that the smallest of changes can quickly reestablish momentum. Our life’s work brings positive energy to our other engagements.

Wishing you and your loved ones and community a fabulous 2012.

Jerome

Thank you so much for your support in 2011, especially in this difficult time.

Sorry for delaying new releases. Being interrupted by unexpected events (what an eventful year it has been!), I’ve been struggling to regain the pace. I hope to release at least one new version in this month. Your comments really motivated me

As for the Batch Operations. I’ve been thinking of removing the (slow) page transition from the feature and I will take your suggestion in consideration with this improvement.

Best regards,
Daisuke

I hope the close of the year finds you well. A great year it has been for Piggydb.

Small suggestion for an enhancement on the Batch Operations screen, fragment-batch.htm. When a user selects several fragments for batch operations, those fragments may have a number of different parent fragments and tags. But only those parents and tags which the selected fragments all share in common will be displayed in the “Tag” and “Parent Fragment” sidebar widgets.

These widgets offer an “intersect” view. Could they instead display a “union” view? For an n of seven fragments, Piggydb might display

Tag1 (3) ☒ ☑
Tag2 (5) ☒ ☑
Tag3 (4) ☒ ☑

ParentFragment1 (6) ☒ ☑
ParentFragment2 (4) ☒ ☑

Thus it would show relationships that apply to only some of the fragments, allowing the user either to remove them ☒ or apply them to the whole set ☑. The objective of batch operations is usually to get disparate fragments into alignment, and this enhancement would make it easier to categorize like fragments alike.

Thanks for taking a look.

Warmest Regards
Jerome

Never mind. it works now. had another server running on that port and forgot about it.

greetings,
simon

I wasn’t able to log in to my piggydb under windows xp.
i used the user “owner” and password “owner” but that seems not to be the right password.

I use firefox 8.0.1 as browser, java JRE 6 is also installed.

greetings,
simon

200 characters is just where I set the max, entirely by chance. That feels like a good length to express one idea naturally and compactly. Much thanks.

Jerome

You can modify the ‘maxlength’ attribute of the title input at HTML level, but not the actual maximum length of title because it is defined in the database schema (200 is the actual maximum).

1) Is there any functional reason for a user not to change the title length if he prefers it lengthier?

As I wrote above, since the maximum length is defined in the database schema, it is not technically easy to provide a way to change it. Although you can do it at HTML level up to 200 characters.

2) Are $titleMaxLength or the fragment creation form set in the binary realm, or can they be user-edited?

The fragment creation form is defined in FragmentFormPanel.htm:

https://github.com/marubinotto/Piggydb/blob/master/src/main/resources/marubinotto/piggydb/ui/page/control/FragmentFormPanel.htm

Currently, I’m working on a new version of fragment form, so FragmentFormPanel.htm will be removed in future versions.

Maybe, the current ‘maxlength’ attribute is too short for a title. I will consider whether I should change it. Thank you for your pointing out.

Best regards,
Daisuke

I’ve been experimenting with adjusting the maximum length of a fragment title. It seems to be working very well. But I’ve managed to accomplish this only by hardcoding the new value into fragment-editor.htm . So the greater length is available only on fragment updates, not on creation.

Generally I find Piggydb mod points by viewing page source, then running the terrific PRGrep against the source folder to find obvious keywords and edit the correct file. But the keywords around the fragment creation form don’t come up on the grep. I’m guessing they’re part of Piggydb’s binary substructure.

So my two questions for you today are: 1) Is there any functional reason for a user not to change the title length if he prefers it lengthier? 2) Are $titleMaxLength or the fragment creation form set in the binary realm, or can they be user-edited?

Hope all is going well for you.

Warmest Regards
Jerome

Most of us have wide monitors these days and lots of horizontal space.

Best regards,
Daisuke