Hi Måns That's very helpful, thank you. Annoyingly, the menu bar support in node-webkit is quite platform specific. Currently, on Mac TiddlyDesktop generates a single menu bar which it assigns to the main window. OS X then makes that menu bar available for all windows belonging to the application. On Windows, one has to create a menu bar for each window, including the main window.
Some material I've read suggests that menu behaviour in node-webkit under Linux differs according to the window manager. So, handling menus at all seems like a big can of worms. What I propose to do instead is provide access to developer tools via a button against each wiki in the main wiki list. That way I'll be able to make the implementation entirely platform independent. Many thanks, Jeremy On Mon, Jan 20, 2014 at 8:29 AM, Måns <humam...@gmail.com> wrote: > Hi Jeremy > > Some times I get several developer menu bars. > > Most often I have two developer menu bars when I open a tw. > When I click on the developer button one of them is removed. > Some of my classic tws produce a new developer menu bar every time I open > a new tiddler.... > Those extra panels dissapear if I: > a) Save the wiki or > b) click on the developer button.. > > See video example: http://youtu.be/ODTxREid1zQ > > Cheers Måns Mårtensson > > Den søndag den 19. januar 2014 23.46.36 UTC+1 skrev Måns: > >> Hi Jeremy >> >> >https://github.com/rogerwang/node-webkit/wiki/Support-mp3- >> and-h264-in-video-and-audio-tag >> >> Thanks for the pointer. >> >"The folder location may vary according to the linux distro you are >> using. Its located in the /opt/google/chrome on Ubuntu. Copy >> libffmpegsumo.so and paste it in the node-webkit folder." >> It didn't work for me.. >> >> >node-webkit doesn't provide context menus by default, but it should be >> possible to add them. I've created a ticket: https://github.com/ >> Jermolene/TiddlyDesktop/issues/8 >> >> Thanks :-) >> >> Cheers Måns Mårtensson >> >> Den søndag den 19. januar 2014 23.08.12 UTC+1 skrev Jeremy Ruston: >>> >>> Hi Måns >>> >>> I can't use tobias' twyp plugin (great youtube plugin for searching and >>>> embedding videos) in a tw classic when it's served from within >>>> TiddlyDesktop - >>>> In a TW5 it won't work if I use the embed code of a video from >>>> Youtube... >>>> >>> >>> node-webkit doesn't directly support patent encumbered codecs (ie H264 >>> and MP3) without a great deal more work: >>> >>> https://github.com/rogerwang/node-webkit/wiki/Support-mp3- >>> and-h264-in-video-and-audio-tag >>> >>> node-webkit is supposed to work with Adobe Flash, but I haven't been >>> successful in getting it to work so far. >>> >>> >>>> Another problem is that I get no popup menu when I right click marked >>>> text in edit mode - or right click a link in view mode... >>>> >>> Is this intentional - a bug or a shortcomming of the nodekit framework? >>>> >>> >>> node-webkit doesn't provide context menus by default, but it should be >>> possible to add them. I've created a ticket: >>> >>> https://github.com/Jermolene/TiddlyDesktop/issues/8 >>> >>> Best wishes >>> >>> Jeremy >>> >>> >>>> >>>> Cheers Måns Mårtensson >>>> >>>> Den søndag den 19. januar 2014 16.21.39 UTC+1 skrev Jeremy Ruston: >>>>> >>>>> >>>>> I didn't look deeper into the file api possibilities of nodeWebkit but >>>>>> I have security concerns ... >>>>>> >>>>>> - TiddlySpace has an include mechanism, that makes it easy to >>>>>> include code from othere spaces, into your space. >>>>>> >>>>>> - If you download a TiddlySpace to your harddisk, you include all >>>>>> the 3rd party stuff. >>>>>> - You are basically executing "untrusted code" on your computer. >>>>>> >>>>> >>>>> One of the bigger changes between TiddlyDesktop 0.0.1 and 0.0.2 is >>>>> that now TiddlyWiki documents are sandboxed. They do not have direct >>>>> access >>>>> to node.js APIs, they just operate as if they were in an ordinary browser. >>>>> >>>>> Saving is handled the same way as TiddlyFox: >>>>> >>>>> * TiddlyDesktop inserts a DIV with the ID "tiddlyfox-message-box" and >>>>> attaches a listener for the custom event "tiddlyfox-save-file" >>>>> * For TiddlyWiki Classic, it also inserts a script tag containing >>>>> overrides for loadFile and saveFile that duplicate the behaviour of >>>>> TiddlyWiki5 >>>>> * For TiddlyWiki5, when the saver is asked to save changes, it looks >>>>> for the message box DIV and inserts a DIV with attributes containing the >>>>> text and filename to be saved. It listens for the event >>>>> "tiddlyfox-have-saved-file" on the newly inserted message DIV >>>>> * TW5 then triggers the custom event "tiddlyfox-save-file" on that new >>>>> DIV >>>>> * TiddlyDesktop sees the event, extracts the text and filename from >>>>> the DIV, and saves the file >>>>> * TiddlyDesktop triggers the custom event "tiddlyfox-have-saved-file" >>>>> on the message DIV >>>>> * TiddlyWiki5 sees the event, removes the message DIV, and then calls >>>>> the callback to provide the confirmation UI >>>>> >>>>> >>>>>> - Since the browser holds everything in a "restricted sandbox" >>>>>> this is "kind of save" since javascript has no write access to the >>>>>> "whole" >>>>>> filesystem. >>>>>> - TiddlyFox (browser plugin) bypasses some of those restrictions >>>>>> but you (jeremy) refused to provide a "full blown" file api ... imo for a >>>>>> good reason. >>>>>> >>>>> >>>>> So, I've applied the same security reasoning to TiddlyDesktop as we've >>>>> already got for TiddlyFox >>>>> >>>>> >>>>>> - With nodeWebkit you want to allow to bypass the browser security >>>>>> restrictions. So javascript from somewhere in the web, should be able to >>>>>> have "unrestricted access" to my harddisk. ... really ??? >>>>>> >>>>> >>>>> No. We wouldn't give embedded TW's unfettered access to unsafe >>>>> operations. >>>>> >>>>> Best wishes >>>>> >>>>> Jeremy. >>>>> >>>>> >>>>>> >>>>>> -mario >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Jeremy Ruston >>>>> mailto:jeremy...@gmail.com >>>>> >>>> >>> >>> >>> -- >>> Jeremy Ruston >>> mailto:jeremy...@gmail.com >>> >> -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
