[tw] Re: Library tracker plugin - help extending with an API?

[László Zsigmond]

Have managed to add an api_url and api_on to settings's filed.

Learned that js is not allowed inside a tiddler, as complete newbie I ask, 
how should I procede to do these:

   1. replace inside the api_url inputterm with the more than 3 characters 
   typed input from the title's edit-text and inputtauthor with author 
   edit-text
   2. get item.volumeInfo.authors && item.volumeInfo.title && 
   item.volumeInfo.industryIdentifiers && item.volumeInfo.publishedDate
   3. get an autofill window with labels of the above, if selected insert 
   item.volumeInfo.title to title, and item.volumeInfo.authors to author


for a first step this would be enough :D

Here is complete description of how to do the autocomplete part using 
jquery: https://www.librarieshacked.org/tutorials/autocompletewithapi


2016. július 2., szombat 20:45:29 UTC+3 időpontban Jed Carty a következőt 
írta:
>
> It took me a minute to realize that you are probably talking about my 
> plugin (the one listed here 
> ).
>  
> It is helpful to put a link to what you are talking about in posts like 
> this, I often forget about things I have made and if it isn't my plugin you 
> are talking about than I don't know where to look to find it.
>
> I am to the point where I think that I need to update many of my plugins 
> and to make a more unified interface and settings for them.
>
> As for your actual suggestions:
>
> I agree about the language field. I was living in the US when I first made 
> it and had maybe 3 non-english language books total so I didn't think about 
> it. This is much more relevant now that I moved to France. When I get to 
> updating the library tracker I will add that as a default field. Until then 
> you can add custom fields under the settings tab.
>
> The previously selected value is kept when you add a book, so this may not 
> actually be about my plugin. But I should add collections or something 
> similar that you can add books to with preselected information. I will try 
> to add that in a future release.
>
> We have been looking at importing and exporting tiddlers from tiddlywiki 
> lately and I think that I should make sure that the tiddlers are in a form 
> that can be nicely imported or exported using the built-in methods instead 
> of making something new. Hopefully we will be improving the built-in 
> methods.
>
> Making tiddlywiki work with 3rd party services seems to be a theme lately. 
> The problem with something like this is that different services often have 
> unique apis that are a pain to work with. I am not at all opposed to making 
> add-on plugins to add this sort of functionality, but I don't think I will 
> every make it a priority.
> If the service being contacted allows queries via xmlhttprequests than it 
> probably won't be difficult but I still wouldn't have much motivation to 
> work on it.
> Updating drop-downs in real time based on calls to 3rd party services in 
> tiddlywiki should be possible, but I think that it would take some work to 
> make it operate smoothly.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/de7b648b-0ffa-479d-b92a-49bda8e68932%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Library tracker plugin - help extending with an API?

[László Zsigmond]

I was referring only to book metadata, entries of the Library tracker
plugin. As I would like to import entries to that plugin's book model it
would take more than just importing a csv line into one tiddler, it has
separate tiddlers with lists of authors, etc., so it's a bit more complex,
I'll just go with writing a python script to do the import.

On Tue, Jul 5, 2016 at 5:27 PM, 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> I have an experimental csv2json converter in this thread:
> https://groups.google.com/forum/#!searchin/tiddlywiki/csv|sort:date/tiddlywiki/qabE7I41Hos/L4kDni7ZBQAJ
>
> When you say "thousand books", do you mean the whole book, or just meta
> data about the books? I don't think TW could handle the *content* of more
> than a couple books (depending on size of course).
>
> Good luck,
> Mark
>
> On Tuesday, July 5, 2016 at 1:26:58 AM UTC-7, László Zsigmond wrote:
>>
>> Haven't signed up for the thread, was thinking it is done automatically,
>> but well, now I got your answer, thank you!
>>
>> You are right, I should have linked it, it is your pluging and I wasn't
>> attentive enough to see that last used values are kept on new book edits.
>>
>> Unique apis that are a pain to work with: would just start out with
>> google books api and accept apis that can recieve the same parameters and
>> results in a json with the same layout, keys.
>>
>> First I would like to get my exisiting library get imported, I've read
>> that it is cumbersome to import csv into tiddlywiki, better of to convert
>> externally the cvs to json and then import it into tiddlywiki.
>> Do you have any suggestions / descriptions on how to do this import? Like
>> there are some ways of transforming csv to json, like to json/keyed
>> json/json array/json column array.
>> Would you advice to have a separate tiddlywiki for book collections? With
>> some thusand books won't ruin the tiddlywiki experience?
>>
>>
>> Best wishes,
>> Laci
>>
>>
>>
>> 2016. július 2., szombat 20:45:29 UTC+3 időpontban Jed Carty a következőt
>> írta:
>>>
>>> It took me a minute to realize that you are probably talking about my
>>> plugin (the one listed here
>>> ).
>>> It is helpful to put a link to what you are talking about in posts like
>>> this, I often forget about things I have made and if it isn't my plugin you
>>> are talking about than I don't know where to look to find it.
>>>
>>> I am to the point where I think that I need to update many of my plugins
>>> and to make a more unified interface and settings for them.
>>>
>>> As for your actual suggestions:
>>>
>>> I agree about the language field. I was living in the US when I first
>>> made it and had maybe 3 non-english language books total so I didn't think
>>> about it. This is much more relevant now that I moved to France. When I get
>>> to updating the library tracker I will add that as a default field. Until
>>> then you can add custom fields under the settings tab.
>>>
>>> The previously selected value is kept when you add a book, so this may
>>> not actually be about my plugin. But I should add collections or something
>>> similar that you can add books to with preselected information. I will try
>>> to add that in a future release.
>>>
>>> We have been looking at importing and exporting tiddlers from tiddlywiki
>>> lately and I think that I should make sure that the tiddlers are in a form
>>> that can be nicely imported or exported using the built-in methods instead
>>> of making something new. Hopefully we will be improving the built-in
>>> methods.
>>>
>>> Making tiddlywiki work with 3rd party services seems to be a theme
>>> lately. The problem with something like this is that different services
>>> often have unique apis that are a pain to work with. I am not at all
>>> opposed to making add-on plugins to add this sort of functionality, but I
>>> don't think I will every make it a priority.
>>> If the service being contacted allows queries via xmlhttprequests than
>>> it probably won't be difficult but I still wouldn't have much motivation to
>>> work on it.
>>> Updating drop-downs in real time based on calls to 3rd party services in
>>> tiddlywiki should be possible, but I think that it would take some work to
>>> make it operate smoothly.
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/sbNSbjB4p0A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/95792f74-1bef-44e4-8ff8-a99e9ce02d04%40googlegroups.com
> 

[tw] Re: Library tracker plugin - help extending with an API?

['Mark S.' via TiddlyWiki]

I have an experimental csv2json converter in this thread: 
https://groups.google.com/forum/#!searchin/tiddlywiki/csv|sort:date/tiddlywiki/qabE7I41Hos/L4kDni7ZBQAJ

When you say "thousand books", do you mean the whole book, or just meta 
data about the books? I don't think TW could handle the *content* of more 
than a couple books (depending on size of course).

Good luck,
Mark

On Tuesday, July 5, 2016 at 1:26:58 AM UTC-7, László Zsigmond wrote:
>
> Haven't signed up for the thread, was thinking it is done automatically, 
> but well, now I got your answer, thank you!
>
> You are right, I should have linked it, it is your pluging and I wasn't 
> attentive enough to see that last used values are kept on new book edits.
>
> Unique apis that are a pain to work with: would just start out with google 
> books api and accept apis that can recieve the same parameters and results 
> in a json with the same layout, keys.
>
> First I would like to get my exisiting library get imported, I've read 
> that it is cumbersome to import csv into tiddlywiki, better of to convert 
> externally the cvs to json and then import it into tiddlywiki.
> Do you have any suggestions / descriptions on how to do this import? Like 
> there are some ways of transforming csv to json, like to json/keyed 
> json/json array/json column array. 
> Would you advice to have a separate tiddlywiki for book collections? With 
> some thusand books won't ruin the tiddlywiki experience?
>
>
> Best wishes,
> Laci
>
>
>
> 2016. július 2., szombat 20:45:29 UTC+3 időpontban Jed Carty a következőt 
> írta:
>>
>> It took me a minute to realize that you are probably talking about my 
>> plugin (the one listed here 
>> ).
>>  
>> It is helpful to put a link to what you are talking about in posts like 
>> this, I often forget about things I have made and if it isn't my plugin you 
>> are talking about than I don't know where to look to find it.
>>
>> I am to the point where I think that I need to update many of my plugins 
>> and to make a more unified interface and settings for them.
>>
>> As for your actual suggestions:
>>
>> I agree about the language field. I was living in the US when I first 
>> made it and had maybe 3 non-english language books total so I didn't think 
>> about it. This is much more relevant now that I moved to France. When I get 
>> to updating the library tracker I will add that as a default field. Until 
>> then you can add custom fields under the settings tab.
>>
>> The previously selected value is kept when you add a book, so this may 
>> not actually be about my plugin. But I should add collections or something 
>> similar that you can add books to with preselected information. I will try 
>> to add that in a future release.
>>
>> We have been looking at importing and exporting tiddlers from tiddlywiki 
>> lately and I think that I should make sure that the tiddlers are in a form 
>> that can be nicely imported or exported using the built-in methods instead 
>> of making something new. Hopefully we will be improving the built-in 
>> methods.
>>
>> Making tiddlywiki work with 3rd party services seems to be a theme 
>> lately. The problem with something like this is that different services 
>> often have unique apis that are a pain to work with. I am not at all 
>> opposed to making add-on plugins to add this sort of functionality, but I 
>> don't think I will every make it a priority.
>> If the service being contacted allows queries via xmlhttprequests than it 
>> probably won't be difficult but I still wouldn't have much motivation to 
>> work on it.
>> Updating drop-downs in real time based on calls to 3rd party services in 
>> tiddlywiki should be possible, but I think that it would take some work to 
>> make it operate smoothly.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/95792f74-1bef-44e4-8ff8-a99e9ce02d04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Library tracker plugin - help extending with an API?

[László Zsigmond]

Haven't signed up for the thread, was thinking it is done automatically, 
but well, now I got your answer, thank you!

You are right, I should have linked it, it is your pluging and I wasn't 
attentive enough to see that last used values are kept on new book edits.

Unique apis that are a pain to work with: would just start out with google 
books api and accept apis that can recieve the same parameters and results 
in a json with the same layout, keys.

First I would like to get my exisiting library get imported, I've read that 
it is cumbersome to import csv into tiddlywiki, better of to convert 
externally the cvs to json and then import it into tiddlywiki.
Do you have any suggestions / descriptions on how to do this import? Like 
there are some ways of transforming csv to json, like to json/keyed 
json/json array/json column array. 
Would you advice to have a separate tiddlywiki for book collections? With 
some thusand books won't ruin the tiddlywiki experience?


Best wishes,
Laci



2016. július 2., szombat 20:45:29 UTC+3 időpontban Jed Carty a következőt 
írta:
>
> It took me a minute to realize that you are probably talking about my 
> plugin (the one listed here 
> ).
>  
> It is helpful to put a link to what you are talking about in posts like 
> this, I often forget about things I have made and if it isn't my plugin you 
> are talking about than I don't know where to look to find it.
>
> I am to the point where I think that I need to update many of my plugins 
> and to make a more unified interface and settings for them.
>
> As for your actual suggestions:
>
> I agree about the language field. I was living in the US when I first made 
> it and had maybe 3 non-english language books total so I didn't think about 
> it. This is much more relevant now that I moved to France. When I get to 
> updating the library tracker I will add that as a default field. Until then 
> you can add custom fields under the settings tab.
>
> The previously selected value is kept when you add a book, so this may not 
> actually be about my plugin. But I should add collections or something 
> similar that you can add books to with preselected information. I will try 
> to add that in a future release.
>
> We have been looking at importing and exporting tiddlers from tiddlywiki 
> lately and I think that I should make sure that the tiddlers are in a form 
> that can be nicely imported or exported using the built-in methods instead 
> of making something new. Hopefully we will be improving the built-in 
> methods.
>
> Making tiddlywiki work with 3rd party services seems to be a theme lately. 
> The problem with something like this is that different services often have 
> unique apis that are a pain to work with. I am not at all opposed to making 
> add-on plugins to add this sort of functionality, but I don't think I will 
> every make it a priority.
> If the service being contacted allows queries via xmlhttprequests than it 
> probably won't be difficult but I still wouldn't have much motivation to 
> work on it.
> Updating drop-downs in real time based on calls to 3rd party services in 
> tiddlywiki should be possible, but I think that it would take some work to 
> make it operate smoothly.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b952481f-1540-4cad-a711-d574c7afec58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Library tracker plugin - help extending with an API?

[Jed Carty]

It took me a minute to realize that you are probably talking about my 
plugin (the one listed here 
).
 
It is helpful to put a link to what you are talking about in posts like 
this, I often forget about things I have made and if it isn't my plugin you 
are talking about than I don't know where to look to find it.

I am to the point where I think that I need to update many of my plugins 
and to make a more unified interface and settings for them.

As for your actual suggestions:

I agree about the language field. I was living in the US when I first made 
it and had maybe 3 non-english language books total so I didn't think about 
it. This is much more relevant now that I moved to France. When I get to 
updating the library tracker I will add that as a default field. Until then 
you can add custom fields under the settings tab.

The previously selected value is kept when you add a book, so this may not 
actually be about my plugin. But I should add collections or something 
similar that you can add books to with preselected information. I will try 
to add that in a future release.

We have been looking at importing and exporting tiddlers from tiddlywiki 
lately and I think that I should make sure that the tiddlers are in a form 
that can be nicely imported or exported using the built-in methods instead 
of making something new. Hopefully we will be improving the built-in 
methods.

Making tiddlywiki work with 3rd party services seems to be a theme lately. 
The problem with something like this is that different services often have 
unique apis that are a pain to work with. I am not at all opposed to making 
add-on plugins to add this sort of functionality, but I don't think I will 
every make it a priority.
If the service being contacted allows queries via xmlhttprequests than it 
probably won't be difficult but I still wouldn't have much motivation to 
work on it.
Updating drop-downs in real time based on calls to 3rd party services in 
tiddlywiki should be possible, but I think that it would take some work to 
make it operate smoothly.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/64964133-f1b6-4d08-b511-1425d6bd9b7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.