Re: [Semediawiki-user] [SRF] Shorten long page names within the result table and calendar

[James H. K. <jam...@gm...>]

Hi Alex,

The hint with the "link=none" seems to work.

Thanks

MWJames

On Sat, Jul 17, 2010 at 3:34 AM, Alex Kozak <ak...@cr...> wrote:
> James,
> If you pass #ask results into a template that does some processing, you
> might have to add the "link=none" parameter to the #ask query so that you
> can process the results as strings and not, in your example, as links to
> pages.
> I agree that storing a display name in another property is sub-optimal... it
> was just a potential work-around.
> - Alex
>
> On Fri, Jul 16, 2010 at 11:31 AM, James Hong Kong
> <jam...@gm...> wrote:
>>
>> Hi ,
>>
>> First I thought, I could have live with a solution that stores some
>> page name as property but that implies that all pages are created via
>> a form/ or contain a template (because we don't want to have a user to
>> maintain this property) but this is just not practical in terms of
>> effort and time to maintain pages with lower priority but still
>> contain necessary information.
>>
>> Secondly why do I have to maintain a property that contains
>> information that is already available (such as the page name as a
>> unique identifier). As I see it, property values should be used to
>> define a document in manner it can be used for some reasoning but I
>> just don't see the need nor a concept for reasons of design to
>> maintain/store data just to allow a work around.
>>
>> Long page names are a problem for display no matter what and their
>> should be a solution to provided a short version without making double
>> entry nor storing unnecessary information as property.
>>
>> Using a template as output
>>
>> In an earlier post I made a comment about using a template as output
>>
>> (http://smw.referata.com/wiki/Use_the_ask_template_format_to_create_tabular_output),
>>  I made some testing to manipulate the display of page names by doing
>> some thing like [[{{{1}}}|{{#sub:{{{1}}}|0|10}}]] but as expected it
>> did not work because the internal structure  within the output routine
>> (the page identifier is represented as URL an not as string therefore
>> the manipulation with #sub and the [[ ]] does not work) don't allow
>> this kind of construction and breaks the link within the cell.
>>
>> Cheers,
>> MWJames
>>
>>
>> On Fri, Jul 16, 2010 at 3:12 PM, Alex Kozak <ak...@cr...>
>> wrote:
>> > Sorry I meant [[has display name::{{#titleparts:<stuff here>}}]] (forgot
>> > the
>> > trailing ]]).
>> >
>> > AK
>> >
>> > On Thu, Jul 15, 2010 at 11:09 PM, Alex Kozak
>> > <ak...@cr...>wrote:
>> >
>> >> I've run into this a few times, and one way to do it might be to just
>> >> set a
>> >> property based on how you'd like to display it... something like [[has
>> >> display name::{{#titleparts:<stuff here>}} and then just set up your
>> >> query
>> >> in such a way that ?has display name is the first column. And then
>> >> maybe you
>> >> could pass that into a template to make the results links.
>> >>
>> >> Or you could just pass the regular result into a template that
>> >> processes
>> >> the page column like you said originally.
>> >>
>> >> Just an idea.
>> >>
>> >> AK
>> >>
>> >> On Thu, Jul 15, 2010 at 10:27 PM, Patrick Nagel
>> >> <ma...@pa...>wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> just a quick comment from my side, regarding
>> >>>
>> >>> On 2010-07-15 17:18 UTC Smith, Tim wrote:
>> >>> > 1.  Tangentially related, When will SMW break the paradigm of using
>> >>> > the
>> >>> > page name as the URI?  The Page name should be represented by a
>> >>> > property
>> >>> > and the URI of a page should be some unique, non-descript string
>> >>> > within
>> >>> > the given namespace.
>> >>> [...]
>> >>> > Note that number #1 also removes the chance of page name collision
>> >>> > and
>> >>> > enhances the ability to fully support namespaces.
>> >>>
>> >>> I sincerely hope that the answer is "never". Having the page name as
>> >>> the
>> >>> URI
>> >>> is what makes SMW easy to grasp, and what makes it fit in so nicely
>> >>> into
>> >>> the
>> >>> (Media)Wiki concept (I am aware of the limitations that come along
>> >>> with
>> >>> it).
>> >>>
>> >>> Tim, I think if you cannot identify your "data units" by unique page
>> >>> names,
>> >>> you should not be using a Wiki (Semantic- or not) to organise that
>> >>> data.
>> >>>
>> >>> Patrick.
>> >>>
>> >>> --
>> >>> Key ID: 0x86E346D4            http://patrick-nagel.net/key.asc
>> >>> Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4
>> >>>
>> >>>
>> >>>
>> >>> ------------------------------------------------------------------------------
>> >>>
>> >>> This SF.net email is sponsored by Sprint
>> >>> What will you do first with EVO, the first 4G phone?
>> >>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> >>> _______________________________________________
>> >>> Semediawiki-user mailing list
>> >>> Sem...@li...
>> >>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >> Alex Kozak
>> >> Program Assistant
>> >> Creative Commons
>> >>
>> >
>> >
>> >
>> > --
>> > Alex Kozak
>> > Program Assistant
>> > Creative Commons
>> >
>> > ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by Sprint
>> > What will you do first with EVO, the first 4G phone?
>> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> > _______________________________________________
>> > Semediawiki-user mailing list
>> > Sem...@li...
>> > https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>> >
>
>
>
> --
> Alex Kozak
> Program Assistant
> Creative Commons
>