profile
viewpoint
Darío Hereñú kant Planet Earth... oxygen addicted, paradox collector

kant/-vue-ndingMachine 0

Vending machine made with vueJs

kant/10x-scATAC-2019 0

Publication Page for Satpathy*, Granja* et al 2019

kant/1password-teams-open-source 0

Get a free 1Password Teams membership for your open source project

kant/2018-08-18-ttt-LatinAmerica 0

Online instructor training

kant/21-points 0

❤️ 21-Points Health is an app you can use to monitor your health.

kant/21kHz-rack-plugins 0

Modules for VCV Rack

kant/4bars 0

Ableton Live CLI - High Precision Loop Production and Asset Management

kant/a11yproject.com 0

A community–driven effort to make web accessibility easier.

kant/abdominal-multi-organ-segmentation 0

abdominal multi-organ segmentation using pytorch

issue commentomeka/Omeka

Zend 1 Framework EOL

If the other main point to maintain Omeka Classic (the important first is to maintain old installs) is related to the simplicity for novices, so the right way to manage this case is to create a simplified admin interface for Omeka S, that looks like Omeka Classic, so users will have a little greater simplicity, but a lot more power and standardized data.

mbuechner

comment created time in an hour

issue commentomeka/Omeka

Zend 1 Framework EOL

Omeka Classis is not discontinued. We maintain the portions of Zend 1 that we ship with Omeka Classic and will continue to do so, the end of life issue is not something to worry about. We took on the responsibility of assuring that those elements of the application are viable and stable.

mbuechner

comment created time in 9 hours

issue commentomeka/Omeka

Zend 1 Framework EOL

Thanks, @Daniel-KM! With other words Omeka is discontinued. Is that correct? I read Issue https://github.com/omeka/Omeka/issues/720 where @sharonmleon wrote:

We've made very public promises to users and funders that we will maintain it as an ongoing concern and we will honor those promises.

So, replacing Zend 1 (EOL four years ago!) is not a part of this promise?

mbuechner

comment created time in 13 hours

issue commentomeka/Omeka

Zend 1 Framework EOL

If you want to use Zend 3, use Omeka S: this is the main technical difference between them.

And Omeka S is as simple as Omeka 2 to use, but can do a lot more. Furthermore, most of the plugins are now available on Omeka S, so there is no reason to stay on Omeka Classic, except to maintain old sites (and this is something that is important for an heritage application).

mbuechner

comment created time in 17 hours

issue commentbbolli/tumblr-utils

Only 50 posts are backed up using --incremental

I forgot to mention that --no-post-clobber was only available on my fork's experimental branch. I just moved it to the main branch, so a fresh clone of my fork will have that option now. In this case you need it to make a quick non-incremental backup: --incremental stops when it sees familiar posts, --no-post-clobber just skips them (and should go far enough to discover posts that weren't backed up). In theory, --no-post-clobber has no effect if you are already using --incremental. It also shouldn't change the behavior of future incremental backups, but only find posts that were missed by previous incremental backups.

Assuming none of your previous incremental backups were interrupted, it sounds like --incremental could actually be malfunctioning. But it relies on such a simple and seemingly guaranteed property of blogs (older posts have lower IDs, the API returns the newest posts first) that I would need solid evidence to believe it. It would help to have the name of the blog you're backing up, but if you'd prefer, I could write a script to make a list of post IDs and dates from a backup, and you could run it after a backup without --incremental to see if the ordering is broken in a way that confuses --incremental.

jorong1

comment created time in a day

issue commentbbolli/tumblr-utils

Only 50 posts are backed up using --incremental

I got sidetracked sorry but this is still not working as before. I confirm there are more than 50 posts available. The last update I did was 2020-09-03, and so far there's been a few thousand new posts on the specific blog.

--incremental works as you describe, it only does 50 posts. Then if I try again, it does nothing. The backup on 2020-09-03 was done with bbolli's tools but then I tried an incremental I think and it may have caused a bad stop. But I cleaned up the files as well so that it should have been before whatever update I did.

Using https://github.com/Cebtenzzre/tumblr-utils/commit/e5537c02bbe0c5c93a561de16d4f7ea65d5bf436

python tumblr-utils-cebtenzzre/tumblr_backup.py --incremental --save-video-tumblr --no-ssl-verify --save-audio --save-video-tumblr --json --no-post-clobber --timestamping

usage: tumblr_backup.py [options] blog-name ...
tumblr_backup.py: error: unrecognized arguments: --no-post-clobber

So now I guess I'd need to do without incremental, no clobber and timestamping which would basically download the entire blog again (which is like 70000 posts). But I get the error above, can't use no-post-clobber

Where do I go from here?

jorong1

comment created time in a day

issue commentomeka/Omeka

New Zend Framework

I can't avoid a feeling of unease that Omeka's still using Zend 1. Are there any plans to switch to Zend 2 or 3 in future?

mbuechner

comment created time in a day

issue openedomeka/Omeka

New Zend Framework

created time in a day

startedrbonghi/jetson_stats

started time in 2 days

issue openedmozilla/chromeless

Is this project dead?

It looks so promising, so easy to get up and running, and distribute. AND IT USES GECKO! Will Chrome V8 be our only option for HTML/JS/CSS based apps? (nwjs, electron)

created time in 5 days

starteddstein64/vimgolf

started time in 5 days

startedjuanbrujo/cleaver-beerjs

started time in 6 days

startedjuanbrujo/Talus

started time in 6 days

fork juanbrujo/made-in-chile

🇨🇱 A list of cool projects made in Chile

fork in 6 days

fork juanbrujo/huemul

:sparkles: Hubot para devsChile

http://devschile.cl

fork in 7 days

issue closedfirebug/firebug

Doesn't work properly in Firefox 51.0.1

Hey everyone.

Plugin doesn't work properly in Firefox 51.0.1. (2 days ago everything was good). When I'm trying to open firebug panel, I see default FF devtools instead of. And plugin is switched off. The same behavior is via context menu "Inspect in Firebug" and via clicking to plugin's icon.

  • Win7
  • Firefox 51.0.1
  • Firebug 2.0.18

closed time in 9 days

matiosfree

created repositoryjuanbrujo/image-size-proportion

I've always wanted to have the proportions of an image to scale quickly without using an image editor... so I made this one.

created time in 9 days

issue openedomeka/Omeka

Provide a more obvious reset input for browse users filter

Right now in order to reset the browse users filters, the user enters a blank query in the text input. It might be helpful to provide a dedicated rest button to clear.

created time in 9 days

startedkant/Deep-Learning-CNN-for-Image-Recognition

started time in 9 days

startedkant/DeepLearning-SeGAN-Segmentation

started time in 9 days

startedkant/Computer-Vision

started time in 9 days

PR closed DataTables/DataTables

Update ssp.class.php

It is prevented from counting the same primary key more than once for sql views. This was a requirement for me.

+2 -2

4 comments

1 changed file

hhuseyincihangir

pr closed time in 10 days

pull request commentDataTables/DataTables

Update ssp.class.php

I'm still not really getting it (sorry!), and it isn't something that's been reported to me before. If you are reading from a VIEW you still want the cardinality of the VIEW. Are you saying that you cannot get that cardinality from a simple row count.

That's fair enough, but probably not something I'd merge into master unless it was something that was commonly needed.

hhuseyincihangir

comment created time in 10 days

PR opened omeka/Omeka

Input labels for admin edit pages

This PR is intended to address issue #929 dealing with input labels when editing metadata. It adds a fieldset around metadata inputs and a legend element that's visually hidden but visible to screen readers to group multiple instances of the same metadata input. It also adds an aria-live: polite tag around each of the metadata fields, so that screen readers are notified when inputs are added. There's also a minor change to the gray text color to increase the contrast. All of these changes are based on the new-admin-theme branch to work with those updates. Happy to revise the changes based on feedback.

+6385 -3052

0 comment

87 changed files

pr created time in 10 days

pull request commentDataTables/DataTables

Update ssp.class.php

Sorry to throw out the contributing document without reading it. I forgot.

In different situations, views can be more than one of the same primary key. When the data table is made with this view, more data is seen than in the counter. Hence I needed such a fix.

Even if the primary key is unique in the table or view, this code does not pose a problem.

hhuseyincihangir

comment created time in 10 days

pull request commentDataTables/DataTables

Update ssp.class.php

Sorry to throw out the contributing document without reading it. I forgot.

In different situations, views can be more than one of the same primary key. When the data table is made with this view, more data is seen than in the counter. Hence I needed such a fix.

hhuseyincihangir

comment created time in 10 days

pull request commentDataTables/DataTables

Update ssp.class.php

Thanks for this - although contributions should be made to the DataTablesSrc repo, per the Contributing document.

Also, I don't quite understand this - is the primary key not unique? Those queries are used to count the total number of rows that can be displayed. If you are reducing that number, then you aren't returning the number of rows in the table.

hhuseyincihangir

comment created time in 11 days

PR opened DataTables/DataTables

Update ssp.class.php

It is prevented from counting the same primary key more than once for sql views. This was a requirement for me.

+2 -2

0 comment

1 changed file

pr created time in 11 days

push eventomeka/Omeka

John Flatness

commit sha 7ad4093b5b45e2e9dc8ede185879b707b5393bc0

Don't decode entities when outputting a rich title

view details

push time in 14 days

create barnchomeka/Omeka

branch : rich_titles

created branch time in 15 days

more