In http://groups.google.com/group/simile-widgets on Tue, Apr 14, 2009 at
11:08 PM, David Huynh <dfhuynh(a)alum.mit.edu> wrote:
I've updated the trunk to fix #1
http://trunk.simile-widgets.org/timeline/examples/compact-painter/compact-p…
Let me know how it feels.
This is a great improvement! I liked the new interface enough that I wanted
to try it out in Xwiki:
example:
http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/test
code:
http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/test?raw=1http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/StyleSheet?raw=1http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/DataJson?raw=1
Niels
http://nielsmayer.com
>
> Larry, if you have some time, I'd be grateful for some help on
> implementing your #2 point. It's been a while since I touch all the
> settings in Timeline and don't remember how they propagate. After that,
> maybe we should consider a 2.4 release.
>
> David
>
> David Huynh wrote:
> > OK, sounds like we have consensus... I'll implement them when I get a
> > chance.
> >
> > David
> >
> > John Callahan wrote:
> >
> >> I totally agree with both of Larry's cents. Items 1) and 2) as Larry
> >> described them would work very well for my applications.
> >>
> >> - John
> >>
> >>
> >>
> >> Larry Kluger wrote:
> >>
> >>
> >>> Hi,
> >>>
> >>> I like David's slim scrollbar, I think it's more attractive than the
> >>> usual windows toolbar.
> >>> I also agree with David's point that a standard window toolbar may
> >>> influence people away from realizing that they can scroll a Timeline
> >>> along the time axis.
> >>>
> >>> My 2 cents on the issue are:
> >>> 1) The scrollbar should always be visible if there are more events
> >>> than can be shown on the available tracks. It should be usable as a
> >>> handle for moving the Timeline since its affordance is to act as a
> handle.
> >>> (Affordance is a UI term. An object's affordance is the behavior that
> >>> we expect from an object, given its appearance and context.)
> >>>
> >>> 2) I think the bouncing off the top and bottom of the band effect is
> >>> great for when the touch gesture is used on an iPhone, iTouch, or some
> >>> of the newer Macs. But having it occur as the result of a
> >>> mouse-interaction doesn't feel right to me. I'd appreciate some way to
> >>> turn that behavior off and I don't recommend it as a default (except
> >>> when the browser has a touch interface).
> >>>
> >>> Note that Timeline works pretty well out of the box on the iTouch.
> >>> Enabling the Timeline to be scrolled vertically really solves one of
> >>> the few problems with Timeline on an iPhone etc. The only other issue
> >>> is to change the bubbles' show/hide UI when used with an iPhone.
> >>> That's on my list.
> >>>
> >>> Regards,
> >>>
> >>> Larry
> >>>
> >>>
> ------------------------------------------------------------------------
> >>> *From:* David Huynh <dfhuynh(a)alum.mit.edu>
> >>> *To:* simile-widgets(a)googlegroups.com
> >>> *Sent:* Wednesday, March 25, 2009 12:17:24 AM
> >>> *Subject:* Re: dragging vertically in timelines
> >>>
> >>>
> >>> David Karger wrote:
> >>>
> >>>
> >>>> you mean use a native vertical scrollbar? That would seem to create a
> >>>> "mixed metaphor" ui;
> >>>>
> >>>>
> >>> That was one of the reasons I didn't want to use a native vertical
> >>> scrollbar.
> >>>
> >>>
> >>>
> >>>> i am guessing you can come up with a better
> >>>> consistent metaphor. It took me quite a while to notice the vertical
> >>>> scrollbar, and I'm puzzled why it is "read only".
> >>>>
> >>>>
> >>>>
> >>> The intention is that it's only an indicator, and the body of the band
> >>> is the interactor.
> >>>
> >>> I think people ain't used to scrolling horizontally as much, so if
> >>> vertical scrolling were any more emphasized than it is, then that might
> >>> totally inhibit any hint that horizontal scrolling is possible. (A
> >>> native vertical scrollbar would really emphasize vertical scrolling.)
> >>> But I could be wrong.
> >>>
> >>>
> >>>
> >>>> farfetched, but what if you made the timeline into a "barrel" that
> >>>> rolled away at the top and bottom (images shrinking) to indicate there
> >>>> is more present?
> >>>>
> >>>>
> >>>>
> >>> "Barrel" like this?
> >>> http://z.about.com/d/ipod/1/0/e/3/-/-/iphone_gallery_10.jpg
> >>> I can add some gradients.
> >>>
> >>> David
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> > >
> >
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "SIMILE Widgets" group.
> To post to this group, send email to simile-widgets(a)googlegroups.com
> To unsubscribe from this group, send email to
> simile-widgets+unsubscribe(a)googlegroups.com<simile-widgets%2Bunsubscribe(a)googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/simile-widgets?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
Hi
I`m trying to figure a way to check if a user is a member of one group.
I`m looking for something like:
a) retrieve the groups membership of an user in velocity
or
b) check if a user is a member of a specify group.
Thanks in advance
Regards,
Bruno
walid.kharroubi(a)hraccess.com :
> but do you think it's possible to implement a streaming service in xwiki
> using groovy class with importing a streaming api(the streaming server will
> be vlc for example)?
>
Xwiki is better suited as a framework for creating and presenting streaming
applications but not for the actual streaming implementation. It is correct
to look at implementations specifically designed for streaming (e.g. VLC,
Darwin <http://developer.apple.com/opensource/server/streaming/index.html>,
etc) rather than trying to tame performance issues such as object/thread
overhead,. out-of-memory and running out of threads -- common issues when
many long-running streaming downloads occur in a servlet environment..
On the client end, Xwiki creates the HTML/CSS/javascript scaffolding, with
streaming implemented via streaming "plugins" in the web-browser (e.g.
mozilla plugin, a java applet or flash). These plugins could be accessed in
Xwiki via special velocity macros that cleanly encapsulate all the
scaffolding required to achieve this. The macro would allow easy
parametrization and placement of these "streaming UI objects" in a
Xwiki-based document/application.
For example VLC has a mozilla broser plugin that you can control with a
javascript API.
http://www.videolan.org/doc/play-howto/en/ch04.html#id310965 suggests the
following could be encapsulated within a velocity macro to implement this
functionality:
<embed type="application/x-vlc-plugin"
pluginspage="http://www.videolan.org" version="VideoLAN.VLCPlugin.2"
width="640"
height="480"
id="vlc">
</embed>
<script language="Javascript">
<!--
var vlc = document.getElementById("vlc");
vlc.audio.toggleMute();
!-->
</script>
In my experience, it is straightforward to integrate these kinds of things
with Xwiki, once you get adjusted to the possiblity of "computation"
happening in three places and at different times: browser, server and
plugin; and figuring out the dependencies and interactions therein.
Unfortunately, from a pragmatic perspective, expecting your users to install
VLC or other special browser plugins is the kiss-of-death. Most users will
just blow it off and move on to something else that uses Flash and "works
right out of the box" for the majority of users. (Therefore you can be
doctrinaire about being "purely open source" and it just means you'll be
strongly limiting your customer base and needlessly limiting your own
project's potential for success).
It would be nice to have a truly abstract streaming media macro that would
implement the same generic API for streaming media within Xwiki. The macro
would determine at run-time, whether the browser is enabled with specific
plugins needed to display a specific media type (such as the VLC moz
plugin); if not available, the macro would dynamically switch-in the
flash-based equivalent for people using IE or who don't want to install the
VLC moz plugin. For example given a "mp4", the macro would first attempt to
use VLC, on failure it might try the platform's browser-embeddable media
presenter if media-compatible (e.g. MS windows media), and would finally try
a "generic" flash player such as the Jeroen "JW" Wijering players (
http://www.longtailvideo.com/players/ ).
Who else is working on streaming media issues in Xwiki? Would love to see
some group interest and coding participation towards better integration of
streaming media in Xwiki.
Niels
http://nielsmayer.com
PS: some of my work-in-progress on some streaming clients in Xwiki (not
actual velocity macros yet, but at least they work).
http://nielsmayer.com/xwiki/bin/view/Macros/JW-Player?raw=1http://nielsmayer.com/xwiki/bin/view/Macros/YT-Chromeless?raw=1
Hai..
I'm trying to integrate the date picker to poll application date fields.
I would like to know is there a way that to set the object property name
(like $pobj.pollOpen) as the 'relative' in the javascript.
ex:
<script type="text/javascript">
var dpicker = new DatePicker({
relative : 'how to set the object parameter',
language: "$context.language"
});
</script>
Also I want to know that can we use the date picker inside the #info macro.
ex:#info("The poll is open from $pobj.pollOpen to $pobj.pollClose.")
Thank you.
~ Chathura Prabuddha Ganegoda~
Undergraduate,
Department of Computer Science & Engineering,
University of Moratuwa,
Sri Lanka.
http://gacpganegoda.blogspot.com/
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.9 Milestone 1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
First milestone of the XWiki Enterprise 1.9 version.
Main changes:
* New Office Importer feature: document splitting.
* Document syntax can be changed from the WYSIWYG editor.
Important bug fixes:
* Various bugfixes in syntax 2.0.
* Various bugfixes in the xwiki syntax 1.0 to 2.0 converter.
Note that general goals for XWiki Enterprise 1.9 are:
* Finish/stabilize/document new rendering
* Finish/stabilize/document new wysiwyg editor
* Finish/stabilize/document office importer + doc splitter/management
* Finish/stabilize/document webdav
* Finish/stabilize/document REST support
* Usability improvements
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise19M1
Thanks,
The XWiki dev team
fciubotaru (SVN) wrote:
> Author: fciubotaru
> Date: 2009-04-14 19:28:28 +0200 (Tue, 14 Apr 2009)
> New Revision: 18649
>
> Modified:
> xoffice/trunk/xword/XWikiLib/XWikiLib.csproj
> xoffice/trunk/xword/XWord/AddinActions.cs
> xoffice/trunk/xword/XWord/XWikiAddIn.cs
> Log:
> XOFFICE-74 Navigation Pane does not auto-refresh the tree view when creating a new page
> Patch submited by Teofil Achirei, reviewed by Florin Ciubotaru
> public string currentPageFullName = "";
> +
> /// <summary>
> + /// Specifies if the current page was published on the server.
> + /// It does not specify if the last modifications were saved, but
> + /// if the local document has a coresponding wiki page. It's FALSE
> + /// until first saving to wiki.
> + /// </summary>
Shouldn't properties start with uppercase? I thought that's the convention.
> + public bool currentPagePublished = false;
> + /// <summary>
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi devs,
It is possible to define two XWiki classes with a relationship of
inheritance?
Example: I have MyDocumentClass and MyHeaderClass, it is possible to say all
properties of MyHeaderClass are properties of MyDocumentClass ?
Maybe I should prefer composition to inheritance ;-)
So, can I define a new datatype (like Number, String, TextArea, …), and
create a propertie of type MyHeaderClass in the definition of
MyDocumentClass ?
Thanks,
Benoît
Hi,
I had already proposed a strategy for XE 2.0 in this thread:
http://tinyurl.com/dacg4q
Namely the idea was to release 1.9 final on the 1st of June and
promote it as 2.0 on the 15th of June. Several persons have raised
some objection privately to me and thus I'd like to make a new proposal:
* We still release 1.9 for the 1st of June
* We consider the 2.0 release as a normal release that we release
early September:
- 2.0 M1: 22 June 2009
- 2.0 M2: 13 July 2009
- 2.0 M3: 3 Aug 2009
- 2.0 RC1: 17 Aug 2009
- 2.0 RC2/Final: 31 Aug 2009
* During the 2.0 development period we continue fixing bugs and
stabilizing the platform:
- wysiwyg, rendering, office import
- search w/ lucene plugin
- known outstanding bugs
* We add a new skin
* We continue adding UI improvements
Note that we must be careful not to overload ourselves since almost
everyone will be a mentor for the GSOC and we'll have a lot of
students to mentor during the summer. That'll probably slow us down by
half during the GSOC period.
Here's my +1
Thanks
-Vincent