[tw] tbGTD dropdown menus

[Владимир Петрин]

Hi. I'm new to tbGTD, but already really like it. There only one thing 
botherig me. The thing is tree-like structure of dropdown menus in "new 
tiddler" window, or in edit mode. I don't want to see my actions and other 
stuff like that there, only tags and projects. I don't want to see leaves 
of the tree in dropdown menus, cause it makes them too big, overloaded.
For example, there is some action, and i want to mark it as #done, i click 
action menu, and under the #done tag it shows me all done actions. It's 
like that with every tag. With little tags it's not a big problem, i can 
type them manually, but with projects it's uncomfortable.
Is' there a way to change behavior of dropdown menus?

-- 
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.

Re: [tw] Some further TW5 thoughts/opinions

[David Gifford]

Hi Jeremy

Sounds interesting! (my way of saying I kinda get it but can't quite 
visualize it yet). Build it, and walk me through it, and I will be the 
first one in line to try it out.

Dave


On Wednesday, July 31, 2013 7:59:47 AM UTC-5, Jeremy Ruston wrote:
>
> I understand the rough idea, that in addition to tags, fields would also 
>> become important for identifying tiddlers and even grouping tiddlers and 
>> tags.
>
>
> That's not quite it. Under the hood, tags are stored in a special field 
> called "tags". The content of that field is a list of tiddler titles. The 
> proposal is to make the "tags" field less special by making it possible to 
> give any field the same structure and behaviour.
>  
>
>> And a benefit would be the ability to graph the field data into things 
>> like d3. But could you briefly describe what the user would see, what you 
>> expect the user to want to do with it, and what steps s/he would have to do 
>> to get there?
>>
>
> This change wouldn't be particularly important to a casual end user; it 
> would be more something that somebody setting up and configuring a 
> TiddlyWiki would encounter.
>
> The change would manifest itself in several ways:
>
> * When adding a new field to the tiddler, one would be able to stipulate 
> the type of the field. The list of types would include "string", "date", 
> "integer", "color", "tiddler title", and, now, "tiddler list". (At the 
> moment fields have a type but it only manifests itself in Chrome where 
> "color" fields get a colour picker in the editor)
>
> * Certain widgets and filter operations that currently apply to tags will 
> be broadened to cover other tiddler list fields. For example, if I've added 
> a field called "extags" that is defined as a tiddler list that I am using 
> as a separate tags field, then I would be able to write a filter like 
> [extag[MyTag]] to test for a tag within that field
>
> * Things like drag and drop reordering of lists would be implemented as 
> standard widgets that could operate on any tiddler list field
>
> It's one of those cases where by we're taking an existing core mechanism 
> within TW5 and extending and generalising it just a little so that it can 
> be used to address more our missing features. It's actually a 
> simplification of the design of TW5, accomplished through extending it's 
> capabilities.
>
> Best wishes
>
> Jeremy
>  
>
>>
>> Dave
>>
>>
>>
>>> With respect to the comments about handling multiple tag fields, I'm 
>>> increasingly interested in the idea of generalising "list of tiddlers" as a 
>>> field type; the tags field would then just be an instance of that field 
>>> type. So you'd be able to create many different fields each of the type 
>>> "list of tiddlers". This idea also fits in nicely with the work I've been 
>>> doing on D3 integration: in D3 the fundamental datatype is the list (or 
>>> array). This would allow us to model a table as a list of lists, which 
>>> would fit very naturally.
>>>
>>> A potential side effect of the change is that the ordering of the tags 
>>> applied to a tiddler would be properly retained, allowing users to reorder 
>>> tags to convey their relative importance.
>>>
>>> Does that make sense?
>>>
>>> Best wishes
>>>
>>> Jeremy
>>>
>>>
>>>
>>>
>>> On Tue, Jul 30, 2013 at 10:34 PM, David Gifford wrote:
>>>
 A, it didn't work. After the hangout I tried adding the tag creater 
 to the TiddlerInfo window. But afterward I opened the information area and 
 clicked in the tag window, and the information area closed. Apparently it 
 doesn't like me.

 Dave


 On Monday, July 29, 2013 10:45:36 AM UTC-5, David Gifford wrote:
>
> OR - and here is a wild idea - 
>
> What if you moved tag creation from the edittemplate to the 
> information area in the viewtemplate?
>
> What if you ditched the information icon and replaced it with a tag 
> icon like http://www.iconsea.com/**uploadi**mage/smallsort/4015/**
> vdfo2orj4n**q.png,
>  
>
>
> And clicking the tag icon opened the same information area at the top 
> of the tiddler, and had the following:
>
> At the top, the add tag area currently found in the viewtemplate
> Beneath it, the proposed ability to add new fields for custom tag 
> categories
> Beneath it, the tabbed folders of references, tagging and fields that 
> is already in the information area
>
> This would be clean, the tag icon would make sense to any user who has 
> used Evernote, Wordpress, and other products that use tags, and would 
> lessen the time that people would have to spend in the scary edittemplate 
> nether regions. And it would remove clutter from the edittemplate and 
> make 
> it less scary. The edittemplate would just be for changing the title and 
> content, and for those who need it, fields at the 

[tw] Re: TiddlyWiki 2.8.1 is parsing commented-out CSS definitions

[PMario]

Hi Toden,

The behaviour you explain is a bit weired but can be explaned.

[[StyleSheetTest]] contains
/* some comment */

StyleSheet contains:

/*** 
[[StyleSheetTest]] 
div.tiddler {background-color: gold;} 
***/ 

---

The tiddlywiki core does include the StyleSheetTest tiddler into the 
StyleSheet tiddler, prior to activating it. 

So for the core it looks like this:

/*** 
/* some comment */ 
div.tiddler {background-color: gold;} 
***/

Now you have a problem. 

/*** 
/* some comment */  <-- this closes the comment now
div.tiddler {background-color: gold;} <- this is valid CSS now, since it is 
outside the comment
***/<- this one is an error now

have fun!
mario

-- 
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.

Re: [tw] Troubles with Java 7 Update 25

[PMario]

Hi Eric,
I'm following this topic with interest and I'd like to know, what you think 
about this:
tiddlyweb at home - a new possibility

https://groups.google.com/forum/?fromgroups=#!topic/tiddlywiki/FNiWVM3ODRM

have fun!
mario

-- 
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.

[tw] INTRO: tiddlyweb at home - a new possibility

[PMario]

Hi folks, 
Have a look and tell me, what you think.

Hint: It's about a new possibility to use tiddlyweb on your home computer. 

"tiddlyweb at home - a new possibility" - 
http://www.youtube.com/watch?v=LFNAlxp5fdg
I hope you like it :)

have fun!
mario

-- 
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.

[tw] Re: TiddlyWiki Hangout #7

[PMario]

Since the sound quality in the hangout wasn't that good, I did record a 
short intro video about the 

"tiddlyweb at home with vagrant" - 
http://www.youtube.com/watch?v=LFNAlxp5fdg

I hope you like it :)

have fun!
mario

-- 
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.

Re: [tw] Time Slots for future TiddlyWiki Hangouts

[Marc Ferguson]

I'm sorry I haven't been able to be at your hangouts but I do have a
question about development. Have you had any discussion about using Markup
language to facilitate tiddler creation? Both TW and Markup seem to be
traveling parallel paths and have much in common.


On Wed, Jul 31, 2013 at 7:11 AM, Jeremy Ruston wrote:

> The last few TiddlyWiki hangouts have been held from 4pm to 6pm BST on a
> Tuesday. Before scheduling the next run of hangouts, I'd like to try to
> check whether we've hit on the best time slot for as many attendees as
> possible. I've established a Doodle poll here:
>
> http://doodle.com/wr9bdv2mak9abwrn
>
> We'll use it to vote on the time for the next Hangout, and if the slot
> works well then we'll adopt it as the new regular time slot. (I'm not
> planning to change the day from Tuesday).
>
> For this exercise, you might want to respond according to how your
> calendar generally looks on a Tuesday, and indicate "yes" for slots that
> you would ordinarily be able to attend, even if something is due to prevent
> you from attending on August 6th.
>
> If you've any other comments about time slots, do please reply here.
>
> Many thanks,
>
> Jeremy
>
> --
> 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.
>
>
>

-- 
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.

[tw] Time Slots for future TiddlyWiki Hangouts

[Jeremy Ruston]

The last few TiddlyWiki hangouts have been held from 4pm to 6pm BST on a
Tuesday. Before scheduling the next run of hangouts, I'd like to try to
check whether we've hit on the best time slot for as many attendees as
possible. I've established a Doodle poll here:

http://doodle.com/wr9bdv2mak9abwrn

We'll use it to vote on the time for the next Hangout, and if the slot
works well then we'll adopt it as the new regular time slot. (I'm not
planning to change the day from Tuesday).

For this exercise, you might want to respond according to how your calendar
generally looks on a Tuesday, and indicate "yes" for slots that you would
ordinarily be able to attend, even if something is due to prevent you from
attending on August 6th.

If you've any other comments about time slots, do please reply here.

Many thanks,

Jeremy

-- 
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.

Re: [tw] Some further TW5 thoughts/opinions

[Jeremy Ruston]

>
> I understand the rough idea, that in addition to tags, fields would also
> become important for identifying tiddlers and even grouping tiddlers and
> tags.


That's not quite it. Under the hood, tags are stored in a special field
called "tags". The content of that field is a list of tiddler titles. The
proposal is to make the "tags" field less special by making it possible to
give any field the same structure and behaviour.


> And a benefit would be the ability to graph the field data into things
> like d3. But could you briefly describe what the user would see, what you
> expect the user to want to do with it, and what steps s/he would have to do
> to get there?
>

This change wouldn't be particularly important to a casual end user; it
would be more something that somebody setting up and configuring a
TiddlyWiki would encounter.

The change would manifest itself in several ways:

* When adding a new field to the tiddler, one would be able to stipulate
the type of the field. The list of types would include "string", "date",
"integer", "color", "tiddler title", and, now, "tiddler list". (At the
moment fields have a type but it only manifests itself in Chrome where
"color" fields get a colour picker in the editor)

* Certain widgets and filter operations that currently apply to tags will
be broadened to cover other tiddler list fields. For example, if I've added
a field called "extags" that is defined as a tiddler list that I am using
as a separate tags field, then I would be able to write a filter like
[extag[MyTag]] to test for a tag within that field

* Things like drag and drop reordering of lists would be implemented as
standard widgets that could operate on any tiddler list field

It's one of those cases where by we're taking an existing core mechanism
within TW5 and extending and generalising it just a little so that it can
be used to address more our missing features. It's actually a
simplification of the design of TW5, accomplished through extending it's
capabilities.

Best wishes

Jeremy


>
> Dave
>
>
>
>> With respect to the comments about handling multiple tag fields, I'm
>> increasingly interested in the idea of generalising "list of tiddlers" as a
>> field type; the tags field would then just be an instance of that field
>> type. So you'd be able to create many different fields each of the type
>> "list of tiddlers". This idea also fits in nicely with the work I've been
>> doing on D3 integration: in D3 the fundamental datatype is the list (or
>> array). This would allow us to model a table as a list of lists, which
>> would fit very naturally.
>>
>> A potential side effect of the change is that the ordering of the tags
>> applied to a tiddler would be properly retained, allowing users to reorder
>> tags to convey their relative importance.
>>
>> Does that make sense?
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>>
>>
>> On Tue, Jul 30, 2013 at 10:34 PM, David Gifford wrote:
>>
>>> A, it didn't work. After the hangout I tried adding the tag creater
>>> to the TiddlerInfo window. But afterward I opened the information area and
>>> clicked in the tag window, and the information area closed. Apparently it
>>> doesn't like me.
>>>
>>> Dave
>>>
>>>
>>> On Monday, July 29, 2013 10:45:36 AM UTC-5, David Gifford wrote:

 OR - and here is a wild idea -

 What if you moved tag creation from the edittemplate to the information
 area in the viewtemplate?

 What if you ditched the information icon and replaced it with a tag
 icon like http://www.iconsea.com/**uploadi**mage/smallsort/4015/**
 vdfo2orj4n**q.png,


 And clicking the tag icon opened the same information area at the top
 of the tiddler, and had the following:

 At the top, the add tag area currently found in the viewtemplate
 Beneath it, the proposed ability to add new fields for custom tag
 categories
 Beneath it, the tabbed folders of references, tagging and fields that
 is already in the information area

 This would be clean, the tag icon would make sense to any user who has
 used Evernote, Wordpress, and other products that use tags, and would
 lessen the time that people would have to spend in the scary edittemplate
 nether regions. And it would remove clutter from the edittemplate and make
 it less scary. The edittemplate would just be for changing the title and
 content, and for those who need it, fields at the bottom.



>>
>>
>> --
>> 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.go

Re: [tw] Some further TW5 thoughts/opinions

[David Gifford]

Hi Jeremy

I understand the rough idea, that in addition to tags, fields would also 
become important for identifying tiddlers and even grouping tiddlers and 
tags. And a benefit would be the ability to graph the field data into 
things like d3. But could you briefly describe what the user would see, 
what you expect the user to want to do with it, and what steps s/he would 
have to do to get there?

Dave



> With respect to the comments about handling multiple tag fields, I'm 
> increasingly interested in the idea of generalising "list of tiddlers" as a 
> field type; the tags field would then just be an instance of that field 
> type. So you'd be able to create many different fields each of the type 
> "list of tiddlers". This idea also fits in nicely with the work I've been 
> doing on D3 integration: in D3 the fundamental datatype is the list (or 
> array). This would allow us to model a table as a list of lists, which 
> would fit very naturally.
>
> A potential side effect of the change is that the ordering of the tags 
> applied to a tiddler would be properly retained, allowing users to reorder 
> tags to convey their relative importance.
>
> Does that make sense?
>
> Best wishes
>
> Jeremy
>
>
>
>
> On Tue, Jul 30, 2013 at 10:34 PM, David Gifford 
> 
> > wrote:
>
>> A, it didn't work. After the hangout I tried adding the tag creater 
>> to the TiddlerInfo window. But afterward I opened the information area and 
>> clicked in the tag window, and the information area closed. Apparently it 
>> doesn't like me.
>>
>> Dave
>>
>>
>> On Monday, July 29, 2013 10:45:36 AM UTC-5, David Gifford wrote:
>>>
>>> OR - and here is a wild idea - 
>>>
>>> What if you moved tag creation from the edittemplate to the information 
>>> area in the viewtemplate?
>>>
>>> What if you ditched the information icon and replaced it with a tag icon 
>>> like http://www.iconsea.com/**uploadimage/smallsort/4015/**
>>> vdfo2orj4nq.png,
>>>  
>>>
>>>
>>> And clicking the tag icon opened the same information area at the top of 
>>> the tiddler, and had the following:
>>>
>>> At the top, the add tag area currently found in the viewtemplate
>>> Beneath it, the proposed ability to add new fields for custom tag 
>>> categories
>>> Beneath it, the tabbed folders of references, tagging and fields that is 
>>> already in the information area
>>>
>>> This would be clean, the tag icon would make sense to any user who has 
>>> used Evernote, Wordpress, and other products that use tags, and would 
>>> lessen the time that people would have to spend in the scary edittemplate 
>>> nether regions. And it would remove clutter from the edittemplate and make 
>>> it less scary. The edittemplate would just be for changing the title and 
>>> content, and for those who need it, fields at the bottom.
>>>
>>>
>>>
>
>
> -- 
> Jeremy Ruston
> mailto:jeremy...@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.

[tw] Re: TiddlyWiki Hangout #7

[Jeremy Ruston]

Thanks Mario, I've copied your annotations across to the video:

http://www.youtube.com/watch?v=3SsSh_p_zno

Best wishes

Jeremy


On Wed, Jul 31, 2013 at 12:02 AM, PMario  wrote:

> Hi Jeremy,
>
> Just finished the annotations :)
>
> hangout-7: https://www.youtube.com/watch?v=3SsSh_p_zno
> annotations: http://pmario.tiddlyspace.com/#2013-07-30-TW5-hangout-7
>
> -m
>



-- 
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.

Re: [tw] Some further TW5 thoughts/opinions

[Jeremy Ruston]

Hi Dave

When trying to move the tag editor into the info panel I think you ran into
the same problem as me:

http://www.youtube.com/watch?feature=player_detailpage&v=3SsSh_p_zno&t=5963

It's caused by a shortcoming in the popup handling.

With respect to the comments about handling multiple tag fields, I'm
increasingly interested in the idea of generalising "list of tiddlers" as a
field type; the tags field would then just be an instance of that field
type. So you'd be able to create many different fields each of the type
"list of tiddlers". This idea also fits in nicely with the work I've been
doing on D3 integration: in D3 the fundamental datatype is the list (or
array). This would allow us to model a table as a list of lists, which
would fit very naturally.

A potential side effect of the change is that the ordering of the tags
applied to a tiddler would be properly retained, allowing users to reorder
tags to convey their relative importance.

Does that make sense?

Best wishes

Jeremy




On Tue, Jul 30, 2013 at 10:34 PM, David Gifford  wrote:

> A, it didn't work. After the hangout I tried adding the tag creater to
> the TiddlerInfo window. But afterward I opened the information area and
> clicked in the tag window, and the information area closed. Apparently it
> doesn't like me.
>
> Dave
>
>
> On Monday, July 29, 2013 10:45:36 AM UTC-5, David Gifford wrote:
>>
>> OR - and here is a wild idea -
>>
>> What if you moved tag creation from the edittemplate to the information
>> area in the viewtemplate?
>>
>> What if you ditched the information icon and replaced it with a tag icon
>> like http://www.iconsea.com/**uploadimage/smallsort/4015/**
>> vdfo2orj4nq.png,
>>
>>
>> And clicking the tag icon opened the same information area at the top of
>> the tiddler, and had the following:
>>
>> At the top, the add tag area currently found in the viewtemplate
>> Beneath it, the proposed ability to add new fields for custom tag
>> categories
>> Beneath it, the tabbed folders of references, tagging and fields that is
>> already in the information area
>>
>> This would be clean, the tag icon would make sense to any user who has
>> used Evernote, Wordpress, and other products that use tags, and would
>> lessen the time that people would have to spend in the scary edittemplate
>> nether regions. And it would remove clutter from the edittemplate and make
>> it less scary. The edittemplate would just be for changing the title and
>> content, and for those who need it, fields at the bottom.
>>
>>
>>


-- 
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.

[tw] Re: TiddlySpace.com FrontPage - Feedback/Survey in advance of redesign

[Ben Paddock]

On Tuesday, July 30, 2013 3:11:22 AM UTC+1, Scott Simmons wrote:

> I answered the survey, but it didn't occur to me until I clicked the final 
> "submit" that there IS something I've always wanted from TiddlySpace that 
> isn't there:
>
> A way to browse/navigate/discover existing spaces -- maybe something as 
> (seemingly) simple as the upper nav bar on all Blogspot blogs.
>

Have you seen http://tsiscover.tiddlyspace.com/tsiscover?  It's an 
experiment and having some user feedback on it would help develop it 
further. 

-- 
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.