Methods of Image upload in TW5?
67 views
Skip to first unread message
leeand00
Jun 12, 2012, 10:00:33 AM6/12/12
to tiddly...@googlegroups.com
I know that when I'm using Tiddlywiki 2.x.x and taking screenshots, I have a tendency to either save the photos to a directory next to my wiki, or a tool like ZUploader which takes screenshots and uploads them to a photosite and returns the URL of the image.
Now my understanding is that Tiddlywiki 5 will be able to store images internally as a 64base encoding much like the AttachFile Plugin that Eric Wrote, and incorporating MIME types.
I feel that I waste alot of time saving the images to the drive, and that uploading the images makes them visible to the general public (this is not always desirable), so another better solution is needed. I think TW5 in development would offer a wonderful opportunity to fix this issue, if utilizing node.js in some way we could have something that listens for binary files to be uploaded using a screenshot uploader of some sort similar to ZUploader. ZUploader could be pointed to the URL of the wiki on one of the ports, and send the screenshot to the TW5.
I feel that I waste alot of time saving the images to the drive, and that uploading the images makes them visible to the general public (this is not always desirable), so another better solution is needed. I think TW5 in development would offer a wonderful opportunity to fix this issue, if utilizing node.js in some way we could have something that listens for binary files to be uploaded using a screenshot uploader of some sort similar to ZUploader. ZUploader could be pointed to the URL of the wiki on one of the ports, and send the screenshot to the TW5.
It's just an idea I thought I would throw out there, please discuss and let me know what you think. (Or let me know if this has already been done or is already a planned functionality).
Thank you,
Andrew J. Leer
Jeremy Ruston
Jun 12, 2012, 10:08:05 AM6/12/12
to tiddly...@googlegroups.com
> I know that when I'm using Tiddlywiki 2.x.x and taking screenshots, I have a
> tendency to either save the photos to a directory next to my wiki, or a tool
> like ZUploader which takes screenshots and uploads them to a photosite and
> returns the URL of the image.
>
> Now my understanding is that Tiddlywiki 5 will be able to store images
> internally as a 64base encoding much like the AttachFile Plugin that Eric
> Wrote, and incorporating MIME types.
That is correct.
> tendency to either save the photos to a directory next to my wiki, or a tool
> like ZUploader which takes screenshots and uploads them to a photosite and
> returns the URL of the image.
>
> Now my understanding is that Tiddlywiki 5 will be able to store images
> internally as a 64base encoding much like the AttachFile Plugin that Eric
> Wrote, and incorporating MIME types.
> I feel that I waste alot of time saving the images to the drive, and that
> uploading the images makes them visible to the general public (this is not
> always desirable), so another better solution is needed. I think TW5 in
> development would offer a wonderful opportunity to fix this issue, if
> utilizing node.js in some way we could have something that listens for
> binary files to be uploaded using a screenshot uploader of some sort similar
> to ZUploader. ZUploader could be pointed to the URL of the wiki on one of
> the ports, and send the screenshot to the TW5.
little HTTP under node.js: it allows binary uploads of tiddlers to
work. It should work with ZUploader just fine.
I'm imagining a world in which users initially work with the single
file variant of TiddlyWiki, with the power users upgrading to using
node.js when they run into limitations like this. Installing node.js
is happily trivial, and running node.js apps can be made as simple as
double clicking a shortcut in Windows.
(The other easy way to get image uploading working in a more
conventional manner is to use an online service such as TiddlySpace,
which has very complete handling of binary tiddlers, retrofitted into
tw2).
Best wishes
Jeremy
> It's just an idea I thought I would throw out there, please discuss and let
> me know what you think. (Or let me know if this has already been done or is
> already a planned functionality).
>
> Thank you,
> Andrew J. Leer
>
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/tiddlywikidev/-/jsdYVTd0P80J.
> To post to this group, send email to tiddly...@googlegroups.com.
> To unsubscribe from this group, send email to
> tiddlywikide...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/tiddlywikidev?hl=en.
--
Jeremy Ruston
mailto:jeremy...@gmail.com
PMario
Jun 12, 2012, 11:58:28 AM6/12/12
to TiddlyWikiDev
I did create the picasagallery space [1] some time ago. It is possible
to store pictures at picasaweb.com and display them within a
TiddlyWiki / TiddlySpace. The whole stuff only works, if you are
online.
There is also a possibility to configure "TiddlySpace member only"
access for "restricted picasaweb albums".
I personally only attach small files (max ~80kByte) directly to
TW.html
If files are bigger, they are stored on disk and accessed by links.
-m
[1] http://picasagallery.tiddlyspace.com/
to store pictures at picasaweb.com and display them within a
TiddlyWiki / TiddlySpace. The whole stuff only works, if you are
online.
There is also a possibility to configure "TiddlySpace member only"
access for "restricted picasaweb albums".
I personally only attach small files (max ~80kByte) directly to
TW.html
If files are bigger, they are stored on disk and accessed by links.
-m
[1] http://picasagallery.tiddlyspace.com/
Reply all
Reply to author
Forward
0 new messages