? Not right now I don't think. Well, maybe. You'd still have to run it
as a second instance.
On Sat, Jan 24, 2015 at 6:29 AM, Danielo Rodríguez rdani...@gmail.com
wrote:
El sábado, 24 de enero de 2015, 0:56:31 (UTC+1), Arlen Beiler escribió:
Actually, I just read over your emails again, and finally
.
:)
-Arlen
On Fri, Jan 23, 2015 at 6:47 PM, Arlen Beiler arlen...@gmail.com wrote:
Doing it that way node-webkit just opens and then closes. I would like to
know if you have tested this on windows. Having everything on the same
folder works, but not on different folders. I even tried from
Doing it that way node-webkit just opens and then closes. I would like to
know if you have tested this on windows. Having everything on the same
folder works, but not on different folders. I even tried from the command
line with nw.exe tw5folder and it does not throw any error.
I remember
Hey, for an interesting demo of what can be done with just CSS, check this
out.
http://bartaz.github.io/impress.js/.
-Arlen
On Thu, Jan 22, 2015 at 8:02 AM, Tobias Beer beertob...@gmail.com wrote:
Hi Scott, wow, some real interesting pointers.
http://jlongster.com/s/dom3d
I like that.
, Jan 22, 2015 at 3:43 PM, Danielo Rodríguez rdani...@gmail.com
wrote:
El jueves, 22 de enero de 2015, 19:28:48 (UTC+1), Arlen Beiler escribió:
Ok, I just discovered something. The body tag needs the class tc-body for
it to look right. I think that's what the few glitches were from. I've
I'm sorry, those 7 steps are for running TiddlyWiki on Node.JS as a
webserver. And you open it in a regular browser. The way it is there, with
each tiddler in a separate file, is what I'm calling the Node.JS version,
since I don't know what else to call it. Sorry for the confusion.
Now in order
Ok, I just discovered something. The body tag needs the class tc-body for
it to look right. I think that's what the few glitches were from. I've
updated my gist.
On Thu, Jan 22, 2015 at 1:14 PM, Arlen Beiler arlen...@gmail.com wrote:
I'm sorry, those 7 steps are for running TiddlyWiki
The biggest reason was just to have an easy way to use TiddlyWiki, since I
usually use Chrome, and both Chrome and Firefox feel pretty heavy on my old
computer. I wasn't even planning to get into the Node.JS version, but I got
to thinking about it and decided to take on the challenge. I really
as complicated as I first thought.
-Arlen
On Wed, Jan 21, 2015 at 4:53 AM, Danielo Rodríguez rdani...@gmail.com
wrote:
El miércoles, 21 de enero de 2015, 3:48:09 (UTC+1), Arlen Beiler escribió:
What do you need is a sync module that uses Node-webkit. I think you can
base your work on the FS syncer
Well, if you download Node-Webkit and open a TW5 file in it, it detects
that node is available and tries to load everything from the file system.
This of course does not work. So what I did as a workaround, was to add a
line to bootprefix.js if( $tw.nodeWebKit ) $tw.node = null;. This took
care of
instructions and
tiddlydesktop or the instructions to make TW work on node webkit described
here: http://tiddlywiki.com/dev/#TiddlyWiki%20on%20node-webkit ?
El martes, 20 de enero de 2015, 16:39:08 (UTC+1), Arlen Beiler escribió:
Sure looks like it. I've finally got the other format working as well
to post
later.
For now, enjoy: http://stackoverflow.com/a/28035710/258482
-Arlen Beiler
--
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
Ok, here's the saver: https://gist.github.com/Arlen22/3ff06f8a2f9f7e6b740c
Make sure you set the module-type and type fields.
On Mon, Jan 19, 2015 at 8:09 PM, Arlen Beiler arlen...@gmail.com wrote:
Hi Everyone,
As you may be aware, single file TiddlyWiki does not seem to work on
Node-WebKit
On Thu, Dec 11, 2014 at 12:33 PM, Jeremy Ruston jeremy.rus...@gmail.com
wrote:
Hi Arlen
On Wed, Dec 10, 2014 at 11:16 PM, Arlen Beiler arlen...@gmail.com wrote:
Here is a modification to the RevealWidget that allows for other methods
of hiding the reveal section, including Javascript
a thought.
-Arlen
On Sat, Dec 13, 2014 at 9:20 AM, Arlen Beiler arlen...@gmail.com wrote:
The server.js file uses static.tiddler.html for the template. The
following code would be at the end of the head element in that template.
JQuery could be used to link buttons to the associated reveal, but I
Here is a modification to the RevealWidget that allows for other methods of
hiding the reveal section, including Javascript in static HTML. It should
be noted that EVERY reveal on the page will reveal. A little CSS will fix
that. This is a first step toward allowing tabs to work. If the core devs
Some CSS @media print { .tw-topbar { display:none; } } should take care of
it. As far a s the switching, that's an idea, but I think I'd rather see a
noprint or printonly class solution to that, where the html contained both,
but one only shows up on print and the other everywhere else. Also, if
I ran into a problem like this earlier, but it seemed to only happen when
editing and I was saving and editing tiddlers too fast. However, that
problem seems to have somehow gotten fixed as of 5.0.9-pr.
Could this possibly be some kind of dropped connection? Or does the browser
reopen the
Hi Everyone,
I noticed that the editors on tiddlywiki.com use a regular textarea
editor. How can I get this in my node wiki. I just did an npm update (which
incidentally lost my system tiddlers, but I have a backup), but it's still
the regular line numbers one.
Thanks, Arlen
--
You received
Hello,
I downloaded a copy of my tiddlywiki from NodeJS and this showed up in
the console. It ended with Internal JavaScript Error: Well, this is
embarrassing. It is recommended that you restart TiddlyWiki by refreshing
your browser: Uncaught NetworkError: A network error occurred
I do
601 - 620 of 620 matches
Mail list logo
