Thank you, friend - I really owe you one! You were right, I was
using only numbers as search terms before. As the kids say,
'You da man!'
And well done (with only a glance, no less)!
Thank you!
tsc
--
You received this message because you are subscribed to the Google Groups
"leo-editor" gro
On Mon, 8 Jan 2018 13:11:53 -0800 (PST)
tscv11 wrote:
> *- I'd need a more detailed description o fhow it's broken for you -
> not starting, or whatever, to debug.*
> Please check my original post - I have edited it to include
> details about the problem. If you still need more information
> I wi
*- I'd need a more detailed description o fhow it's broken for you - not
starting, or whatever, to debug.*
Please check my original post - I have edited it to include
details about the problem. If you still need more information
I will tell you whatever you need to know.
As far as the fail in g
On 07/01/18 14:25, Terry Brown wrote:
> On Sun, 7 Jan 2018 10:31:22 -0800
> Chris George wrote:
>
>> What I envision is the ability to use a .db file to store binary
>> files in their entirety. The only place the file would exist is in
>> the .db file. So no references to the file system at all,
On Sun, 7 Jan 2018 22:38:12 -0800 (PST)
tscv11 wrote:
> I cannot understand. Please help me understand. I uploaded to github
> (with everything working), I started trying to make my local copy run
> as @auto. Somehow things got broken. Here is the 'kicker' - I
> downloaded the master from github,
I cannot understand. Please help me understand. I uploaded to github
(with everything working), I started trying to make my local copy run
as @auto. Somehow things got broken. Here is the 'kicker' - I downloaded
the master from github, tested it - and got the same error! (I did make sure
the @auto
On Sun, 7 Jan 2018 15:20:42 -0800 (PST)
tscv11 wrote:
> Just so you know:
>
> Adding "c.__ = {}" to main seems to have fixed the problem.
Makes sense.
> I tend
> to get discouraged easily and I was unfair to Leo!
Leo is Python. It's large and complex and complicated in places, so
potentially
The github repository for leo4sqlite is back online.
https://github.com/tscv11/leo4sqlite
tsc
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr
Just so you know:
Adding "c.__ = {}" to main seems to have fixed the problem. I tend
to get discouraged easily and I was unfair to Leo! I'll post to github
soon - any pointers for using Leo and git together? Also, why no
response to my questions about the plugin documentation, etc.?
Thanks,
tsc
I don't think I'll upload it unless unless I've got it working. I keep
trying to fix it but no luck so far, and no clue. As much as I love
Leo I'm thinking of moving on to something else. These inexplicable
(to me) errors drive me nuts! I get errors with "plain python", sure,
but I'm always able to
On Sun, 7 Jan 2018 14:04:44 -0800 (PST)
tscv11 wrote:
> Well, the script was working when I posted it. I tried to change
> some things in my copy and ended up with a new error:
>
> AttributeError: 'Commands' object has no attribute '__'
>
> line 626: action = "
Well, the script was working when I posted it. I tried to change
some things in my copy and ended up with a new error:
AttributeError: 'Commands' object has no attribute '__'
line 626: action = "insert blob"
* line 627: c.__['action'] = action
line
On Sun, 7 Jan 2018 10:31:22 -0800
Chris George wrote:
> What I envision is the ability to use a .db file to store binary
> files in their entirety. The only place the file would exist is in
> the .db file. So no references to the file system at all, no litter
> of files here and there, just one f
What I envision is the ability to use a .db file to store binary files in
their entirety. The only place the file would exist is in the .db file. So
no references to the file system at all, no litter of files here and there,
just one file that contains it all.
Then I could unleash the power of the
On Sat, 6 Jan 2018 21:24:26 -0800 (PST)
tscv11 wrote:
> Let me know if you want to look at my script in its' current
> incarnation.
It looks like https://github.com/tscv13/leo4sqlite went away - that
would probably be the simplest / most common way of sharing the current
state of code.
I think
On Sun, 7 Jan 2018 05:51:32 -0600
"Edward K. Ream" wrote:
> On Sat, Jan 6, 2018 at 4:07 PM, Terry Brown
> wrote:
>
> It's more a question of BLOB management than visualization. Leo lets
> > you manage hundreds or thousands of little bits of text. That's
> > impressive. So can that same manag
On Sat, Jan 6, 2018 at 4:07 PM, Terry Brown wrote:
It's more a question of BLOB management than visualization. Leo lets
> you manage hundreds or thousands of little bits of text. That's
> impressive. So can that same management extend to keeping track of
> binary formats.
Would supporting bi
Let me know if you want to look at my script in its' current incarnation.
When it comes to blobs it will:
1. insert
2. extract
3. view
4. open
(not sure how 'edit' should be different from 'open')
If you give me a better idea of how you'd like it done, I'll try adding the
choice to
save outlin
On Sat, 6 Jan 2018 15:42:18 -0600
"Edward K. Ream" wrote:
> > For Leo handling BLOBs would mean managing a collection of PDF / SVG /
> > bitmap (image formats) / spreadsheet / etc. kind of files, with the
> > option to view them (possibly in a pane in Leo, but in an external
> > viewer is fine to
On Sat, Jan 6, 2018 at 10:41 AM, Terry Brown wrote:
For Leo handling BLOBs would mean managing a collection of PDF / SVG /
> bitmap (image formats) / spreadsheet / etc. kind of files, with the
> option to view them (possibly in a pane in Leo, but in an external
> viewer is fine too), edit them (m
tscv11 has been bringing up the idea of BLOBs in Leo, something that's
come up before but never moved forward.
Binary Large OBject (BLOB) is the term used by databases for binary
assets which don't fit in any of the regular text / int / real
number kind of fields.
For Leo handling BLOBs would mea
21 matches
Mail list logo
